Le dimanche 18 avril 2010 � 19:25 +0100, Julian Fitzell a �crit :

> 2010/4/18 Nicolas Petton <petton.nicolas@gmail.com>
> � � � � Now I'm not really happy with the codec stuff, as from a GNU
> � � � � Smalltalker
> � � � � point of view it seems too Squeak/Pharo oriented, but I can
> � � � � leave with
> � � � � that for now.
>
> To be honest, I'm not totally happy with that part either. :) It's
> good enough for now but reworking the encoding stuff is on my
> (personal, anyway) list for Seaside 3.1.

Why do you keep Grease into Seaside's repository? Couldn't it have its
own repository and roadmap?

I suppose it might have it's own repository sometime. It probably will have its own "roadmap". It will *definitely* have its own version numbering (though releases will probably coincide fairly closely with Seaside's releases, at least for a while - I'm imagining a 1.0 release to coincide with Seaside's 3.0 final).

For now it's more convenient for us to have it all in one repository. Also, we're not ready to cut the tie to Seaside... Grease is still, fundamentally, Seaside's compatibility layer. For now we're doing what we can to keep it general and inviting others to use it if it fits their needs (we certainly hope it does), but we need to ensure it's fitting our needs. Over time, as it becomes more general, if people are adopting it and we're more confident in its evolution, maybe we'll cut it loose.

Julian