We should also clean the package naming structure
XXX
XXX-Core
XXX-Test-Core
XXX-Foo
XXX-Test-Foo
Stef
On Jun 29, 2010, at 3:42 PM, Stéphane Ducasse wrote:
> **Yes** I really want to come up with a pragma and to annotate tests to
> populate the help.
>
>
> On Jun 27, 2010, at 10:45 AM, laurent laffont wrote:
>
>> + More HelpSystem.
>> + MetacelloRepository GUI, newbies struggle to find a package, must be easy.
>>
>> Laurent
>>
>> On Sun, Jun 27, 2010 at 10:31 AM, Stéphane Ducasse
>> <stephane.duca...@inria.fr> wrote:
>> 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
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
