Disclaimer : The following ideas are general ideas of my own that I am not even sure if I want to pursue them, in no way should be considered recommendations for Pharo 4 and are nothing more than random thoughts that make me curious.
1) Ok this one is a kinda crazy one but here we go. I was thinking of a component based software synthesis system. "Component based" means that every pharo tool and every pharo library is divided in a set of components. So far in Pharo we have objects, the problem however with objects is that offer complete freedom. A component on the other hand can be a single object or a small selection of objects that however has severe limitations in its design, meaning it follows a specific set of rules. These would be there to make components compatible with each other which in turn leads to the next part , "software synthesis". By software synthesis I mean the ability to use components together with ease (maybe drag n drop ? ) to create new libraries and new pharo tools. So in sort brake down Pharo into small legos, legos however have a very rigid way how they can be connected together. The benefit of this system is to allow users to create their own set of tools very quickly or to customise existing ones without the need of understanding methods or classes. Ideally these components will be self documented, meaning will come with its own component comments separate from calls and method comments. 2) Unification of Documentation. Both Pillar and git integration have been quite successful, continuing on this model make this a standard way of documenting and provide users a way to view pillar documentation from inside pharo and ideally offer a pillar editor too for easily expanding the documentation always with full integration with git and github repos. 3) Morphic Cleanup. I know Spec is the new kid in the block , together with Athens and Roassal. But the general design of Morphic is by far my favourite. Instead of moving away from Morphic I would prefer to see Morphic getting a clean up , make it smaller, easier and better documented (I can help there). If possible kick out of the image morphic libraries that are not necessary and have them only as optional third libraries. I also love the idea of improving shortcuts they are a big deal for people coming from emacs and vim. On Wed, Jun 4, 2014 at 9:02 PM, Esteban Lorenzano <[email protected]> wrote: > btw… a small clarification. > What I sent is just a brainstorm session. > That means: is something we would like, but > > a) is open to discussion, and > b) not necessarily we will have the time to implement everything we want. > For that, we also rely on the community… :) > > cheers, > Esteban > > On 04 Jun 2014, at 14:46, Stephan Eggermont <[email protected]> wrote: > > > If we can integrate libtorrent as well, we should be able to use our > dvcs as it is supposed to be used: peer-to-peer. Github is a fine place to > store backups :) > > > > I assume the embeddable vm work includes resurrecting coral? > > > > We can create a ConfigurationOfGlamour that avoids loading the whole of > Moose ;) > > > > Stephan > > >
