[Pharo-project] [COTDC] 12 - PluggableListMorphByItem

Igor Stasenko siguctua at gmail.com
Wed Feb 16 00:59:58 CET 2011


On 15 February 2011 22:24, Nicolas Cellier
<nicolas.cellier.aka.nice at gmail.com> wrote:
> 2011/2/15 Igor Stasenko <siguctua at gmail.com>:
>> On 15 February 2011 19:03, Gary Chambers <gazzaguru2 at btinternet.com> wrote:
>>> "Essentially useless in its current form. Probably intended to eventually
>>> deal with actual objects in the list rather than indexing/string-forms."
>>
>>
>> every time i looking at those pluggableXYZ. and it always one thought
>> don't let me rest:
>>  - we don't need them.
>>
>> They are implementing/perverting functionality of base widgets.
>> Because for most of them, they addding no value comparing
>> to base widgets, but just some extended interface(s) on top.
>>
>
> Totally agree with Igor. Looking at the name, it already smells like a
> case of composition by inheritance.
> It reminds me the RWBinaryOrTextStreamWhatElse hierarchy.
>
> Maybe it has some cousins like
> PluggableMultipleSelectionListMorphByItem PluggableTreeMorphByItem
> etc... ;)
> If Pluggability is a noble feature for a GUI to have, maybe there is
> no much reason to carry a HardcodedListMorphByItem...

Yeah... no tools using ListMorph. Everyone using PluggableListMorph
and its variants..
So, why just not merge all stuf to ListMorph?

>
> Nicolas
>
>>
>>> Regards, Gary
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>>
>>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.




More information about the Pharo-project mailing list