> On 7 Nov 2017, at 21:25, Esteban Lorenzano <[email protected]> wrote: > > > >> On 7 Nov 2017, at 17:22, Sven Van Caekenberghe <[email protected]> wrote: >> >> >> >>> On 7 Nov 2017, at 21:17, stephan <[email protected]> wrote: >>> >>> On 07-11-17 21:11, Sven Van Caekenberghe wrote: >>>> Nobody (trying to use|using) Seaside on Pharo 7 ?? >>> >>> I already did one pull request. >> >> OK, thanks, let's hope things keep moving forward. I am ready to test and >> help. >> >>> That is not enough because of the flattening of traits >> >> Yes, that is a though one for external libraries. > > why? (not putting it in doubt, just wanting to know ;) )
Like I said in another email, for example STON adds methods to Class, MetaClass and ClassDescription *Traits*. Now it has to add to the classes itself (right ?). So a single code base cannot deal with Pharo 7 and older version without splitting. I like to keep simple projects like STON simple (Seaside is huge in comparison and deals with this stuff all the time and already has the complex infrastructure for it). > Esteban > >> >>> Stephan
