FogBugz (Case [Issue]6489) Spec - Spec-ify DropListModel / TextModel

A FogBugz case was edited by Benjamin Van Ryseghem.

Case ID:      6489
Title:        Spec-ify DropListModel / TextModel
Status:       Work Needed
Category:     Enhancement
Project:      Spec
Area:         Misc
Priority:     6 - Fix If Time
Milestone:    Pharo3.0: 29/04/2013
Assigned To:  Everyone

URL:          https://pharo.fogbugz.com/default.asp?6489

In a way it's cool. But actually on the other hand it removes a lot of flexibility.

Here is an example:
<code> {DropListItem named: 'Diff' do: [ browser textConverter: (DiffChangeRecordConverter methodReference: browser textConverter method referencesList: aList) ].
DropListItem named: 'Source' do: [ browser textConverter: (SourceMethodConverter method: browser textConverter method) ]}.</code>

You can see that the method invoked is not the same. So what to do to make it work then ?
- force user to define a common method using extensions ?
- switch case ? :(

And it's actually the same for the label

I would like to discuss this point a bit before integrating the change


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=6489) from this case.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker