>
> Stef has been talking about making Keymapping some kind of official
> "package" for 3.9 (not included with "base" but maybe with full?
> Stef?).  So, I'm working on commenting the classes and building these
> packaged keymaps.

Hi david

Yes I would like to have keymapping as an official full package. So  
this is
excellent that you clean and revise your package.

Now I need feedback on the following wish that is going in my mind.
***Ideally*** I would like that basic Squeak could work without  
keymapping UI or extra stuff.

What is the *minimal* stuff that we can put in basic that would put  
in place
the architecture to replace the old paragraphEditor table and that  
could be used
by keymapping in full.

Does this idea make sense?
I think that this is important to work at the infrastructural level,  
following the way
the filelist got services for tools to register themselves.
This is why we will push the services-kernel of romain so that all  
the browsers
can be enhanced by functionality by new tools. I think that this is a  
good way to support
extensibility and modularisation.

Now my question is can we make such infrastructural changes in  
layered form so that
the minimal can be push down and the rest stays at the full level?

Stef