Hi sean Now Iâm not sure that this was a good move even if ben worked a lot on the new list because alain told me that he had some concerns about the logic (but that since he cannot help he did not want to say anything) for drwaing elements and this impacted his code. Stef On 09 Feb 2014, at 07:57, Sean P. DeNigris <sean@clipperadams.com> wrote:
It seems ListComposableModel was replaced by ListModel in Pharo 3.0. This is a significant non-backward-compatible change, yet it was extremely difficult to find out what was going on - no hits searching the mailing lists and the Issue "10462: Add SpecModel for NewList" says nothing about removing ListComposableModel. I think it's important to think "how are users going to figure out wth happened here" when we make changes like this.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Difficult-to-Track-Changes-tp4742400.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.