14 Nov
2015
14 Nov
'15
1:56 p.m.
We need to have a process and tools to manage changes to external
package without pain.
This is not easy to manage the system with subsystems managed as
independent projects.
We asked an engineer to work on that since 3 years. And one day it will
happen.
Stef
I am kinda
suprised that Roassal is not included with the Pharo
image, looks to me like something Pharo could easily take great
advantage of to extend its visual coding style.
There are two opposing forces at work here: In the development
environment we want very rich tools. In production, we want to be able
to work with as little baggage as possible. So Pharo is moving towards
as much externally loadable code as possible, getting to a
pharo-kernel. When the tools are able to support remote editing and
debugging, we can have many pharo-kernel images controlled by one big
development environment.
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev