Just about catching up with work emails etc... Great to see you at ESUG, a most excellent event! I'll post the EToys removals package (more for reference, has #toRemove stubs and changed methods) once I've reviewed the changes (over 600 changed/removed methods). I'm sure I've missed a couple ;-) Should be able to do that tomorrow and rename the Pinesoft-Widgets to Polymorph. Would be nice to replace the Balloon engine with Cario sometime... Regards, Gary. ----- Original Message ----- From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project@lists.gforge.inria.fr> Sent: Saturday, August 30, 2008 11:35 AM Subject: [Pharo-project] Discussion summary and milestones
Hi all
we got an extremely positive ESUG. Thanks all of you for your great software: Thanks Gary it was great to see you. Now I would like to summarize some of the discussions we got.
For milestone1 -----------------
- we will integrate the Polymorph package of gary. This means we may try to remove some old morphic and integrate really gary's work. Now this task could be continued further in milestone 2.
- gary could you send around (not only to adrian) the etoy removal so that we do it?
- Marcus plans to integrate the stack interpreter made by eliot so that we will get fullclosures.
- We will integrate the freetype plugging (we will need some VM guys probably).
- We want to have a one click image!
- internally we will work on a core and set of package but publicly we would like to avoid to have a distribution that is not tested/used.
For the dev image we would like to only have a set of selected packages, so the idea is that damien will collect the key package that would go in the dev version. (which may be the one click image). We really want to have package without overrides.
- We would like to push the idea of a package manifesto.
For milestone 2 ------------------- - GTK binding
- the newcompiler will replace the old one
- marcus is really interested in COG and helping there. I will try to help and learn from mathieu.
- popUp plague -> notification mechanism (check the OBNotification hierarchy). We need to push infrastructural work so that everything benefit of it.
There are certainly point I forgot to mention but the future is full of new perspectives.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project