Suggestions:
1) Something like VW MemoryPolicy would probably be beneficial in the long-term
instead of polluting SmalltalkImage with a zillion
#initializeMemorySettingsProfileForWhatever to customize the Pharo GC
parameters for Seaside, QF or whatever else.
2) SystemNavigation needs a cleanup/revisit.
3) Utilities needs a cleanup/revisit.
4) The "more..." menu in the file browser is a mess, a real big mess! Needs
cleanup/revisit.
My 2 cents.
-----------------
Benoit St-Jean
A standpoint is an intellectual horizon of radius zero.
(Albert Einstein)
> From: [email protected]
> Date: Sun, 27 Jun 2010 10:31:47 +0200
> To: [email protected]
> Subject: [Pharo-project] 1.2 vision
>
> Hi all
>
> Of course we will integrate changes and changes and improvements.... now I
> believe that it would be nice to build a common
> vision. Here what I would like to get in 1.2.
>
> Now it does not mean that this is a definitive list and that we will have the
> energy to do all but like
> that you know that you can put energy do build this common vision :)
>
> - better infrastructure for integrating rb composite queries into the
> system
> The idea is to introduce a superclass on top of
> systemDictionary and to define there an API that
> is compatible with the one of RB (and potentially modified the
> one of RB)
>
> - another step towards using announcement for system notification
>
> - better tools for dev
>
> - have a look at the RB change model so that we could get a real undo
> and changes
>
> - clean Monticello so that package logic stays in package so that we
> can plug RPackage into the system.
> Right now this looks too brittle to do anything
>
> - make sure that we can have RPackage on the side of PakageInfo (we got
> really nice benchmark)
>
> - New Compiler in beta
>
> - Helvetia hooks
>
> - ROME API
>
> - Sophie Event Hierarchy
>
> - Define some architectural action to get the system more modular
>
> - Hudson infrastructure
>
> - metacello to manage core
>
> - metacelloRepository for 1.0/1.1/1.2
> Gofer
>
> - squeak collection optimisation?
>
> - Alien
>
> Open points:
>
> - What do we do with ToolBuilder? Not clear to me.
>
> - What should be done at the level of polymorph?
> - What should be done a the level of Pluggable****
> can we use the fact that we have now block closure to
> get it better.
>
> As you guess it will not come simply but this is important that we all head
> towards a common understanding
>
>
> Stef
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_________________________________________________________________
Learn more ways to connect with your buddies now
http://go.microsoft.com/?linkid=9734388_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
