[Moose-dev] Re: glamour and moose finder update

[Tudor Girba]

Any morph widget is too slow to display more than a couple of hundred  
elements. The MorphTreeMorph is no exception.

What's more, when you have more than a couple of hundred, you do not  
really need to see them all, because you want to manipulate them via a  
query.

The filter just hides the data, but you can still manipulate it. So,  
you actually do not lose much. A better approach would be to have a  
list that expands automatically once you get at the bottom of the  
visible items.

The reason for moving to the MorphTreeMorph are the followings:
- by depending on one single morph widget, we reduce the maintenance  
team
- it is actively developed and maintained, which is not a given in the  
Morphic world
- it offers a proper tree behavior

Cheers,
Doru


On 13 Nov 2009, at 14:13, Stéphane Ducasse wrote:

> Hi doru
>
> can you tell us:
> 	- does it means that MorphTreeMorph was too slow?
> 	- what was the reason of the change?
> 	- any information that would make us understand the tradeoffs.
> Stef
>
> On Nov 13, 2009, at 2:47 AM, Tudor Girba wrote:
>
>> Hi,
>>
>> You might notice that in the rendering of MooseFinder is slightly  
>> different. In particular, you will only get a limited amount of  
>> items displayed in the group view.
>>
>> This is due to a change in Glamour: we now use only the  
>> MorphTreeMorph widget to render both lists and trees.
>>
>> If you encounter issues, please report them.
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "What is more important: To be happy, or to make happy?"
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev at iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev at iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Every thing should have the right to be different."