Next steps of the Pharo Kernel

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Next steps of the Pharo Kernel

Pavel Krivanek-3
Hi,

this is the list of things that should be done for at start of the
Pharo 3.0 release:
- make KeyChain package (UsersManager) standalone package or at least
clean Kernel and MC dependencies.
- include RPackage, probably will require to include the next Ring parts.
- SoundSystem cleanup
- rename Morphic package to Morphic-Base

Cheers,
-- Pavel

Reply | Threaded
Open this post in threaded view
|

Re: Next steps of the Pharo Kernel

Marcus Denker-4

On Mar 19, 2013, at 11:40 AM, Pavel Krivanek <[hidden email]> wrote:

> Hi,
>
> this is the list of things that should be done for at start of the
> Pharo 3.0 release:
> - make KeyChain package (UsersManager) standalone package or at least
> clean Kernel and MC dependencies.
> - include RPackage, probably will require to include the next Ring parts.
> - SoundSystem cleanup
> - rename Morphic package to Morphic-Base

Sounds good!

        Marcus
Reply | Threaded
Open this post in threaded view
|

Re: Next steps of the Pharo Kernel

stephane ducasse
In reply to this post by Pavel Krivanek-3

On Mar 19, 2013, at 11:40 AM, Pavel Krivanek <[hidden email]> wrote:

> Hi,
>
> this is the list of things that should be done for at start of the
> Pharo 3.0 release:
> - make KeyChain package (UsersManager) standalone package or at least
> clean Kernel and MC dependencies.

Yes

> - include RPackage, probably will require to include the next Ring parts.
But RPackage is already included?

> - SoundSystem cleanup
yes

> - rename Morphic package to Morphic-Base

I would like to check all the extensions of polymorph to see how they can be folded in the system.
New version of Keymapping that guillermo already prepared.

>
> Cheers,
> -- Pavel
>