[Pharo-project] some explanations about what we are doing :)
hi guys Context: So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that. Actions: So now we are including several packages in the image so that we do not have two images. FS RB engine Shout OCompletion Collection-Arithmetics SystemAnnouncement this one is special and some of you may not know it. It is a package that raise announcement for system changes. The idea is that we will then 1- change all the tools to register to SystemAnnouncement 2- replace all the SystemChangeNotification hooks by SystemAnnouncement 3- remove our old friend SystemChangeNotifier. The idea is then to be able to integrate/enhance these packages deeper into the system FS for example to replace the old file package Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too).
On Fri, Aug 12, 2011 at 3:15 PM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
hi guys
Context: So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that.
Actions: So now we are including several packages in the image so that we do not have two images.
I am not against this, but I think it is a must to provide a #shrinkToPharoCore and a hudson associated to that.
FS RB engine Shout OCompletion Collection-Arithmetics SystemAnnouncement this one is special and some of you may not know it. It is a package that raise announcement for system changes. The idea is that we will then 1- change all the tools to register to SystemAnnouncement 2- replace all the SystemChangeNotification hooks by SystemAnnouncement 3- remove our old friend SystemChangeNotifier.
The idea is then to be able to integrate/enhance these packages deeper into the system FS for example to replace the old file package
Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too).
-- Mariano http://marianopeck.wordpress.com
On Aug 12, 2011, at 3:21 PM, Mariano Martinez Peck wrote:
On Fri, Aug 12, 2011 at 3:15 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: hi guys
Context: So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that.
Actions: So now we are including several packages in the image so that we do not have two images.
I am not against this, but I think it is a must to provide a #shrinkToPharoCore and a hudson associated to that.
yes good idea even if for FS and SystemAnnouncement will be inside the core.
FS RB engine Shout OCompletion Collection-Arithmetics SystemAnnouncement this one is special and some of you may not know it. It is a package that raise announcement for system changes. The idea is that we will then 1- change all the tools to register to SystemAnnouncement 2- replace all the SystemChangeNotification hooks by SystemAnnouncement 3- remove our old friend SystemChangeNotifier.
The idea is then to be able to integrate/enhance these packages deeper into the system FS for example to replace the old file package
Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too).
-- Mariano http://marianopeck.wordpress.com
On 12. aug. 2011, at 15:15, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
hi guys
Context: So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that.
Actions: So now we are including several packages in the image so that we do not have two images. FS RB engine Shout OCompletion Collection-Arithmetics SystemAnnouncement this one is special and some of you may not know it. It is a package that raise announcement for system changes. The idea is that we will then 1- change all the tools to register to SystemAnnouncement 2- replace all the SystemChangeNotification hooks by SystemAnnouncement 3- remove our old friend SystemChangeNotifier.
The idea is then to be able to integrate/enhance these packages deeper into the system FS for example to replace the old file package
Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too).
Ugh. Collection-Aritmetics was extracted exactly -because- it's nothing that belongs in image by default... As for RB, my impression through your conversations with Lukas is that it's not enough to include it, you need someone who understands the architecture for bug fixes/changes that preserve architectural integrity rather than end up as ugly hacks. I like the functionality of OCompletion, but from what little I've read of Shout, only it's mother could love it. (same applies to texteditor etc. though, so I guess it's not a very good argument against integrating it) FS + SystemAnnouncements, I'm all for :) Cheers, Henry
On 12 August 2011 16:52, Henrik Johansen <henrik.s.johansen@veloxit.no> wrote:
On 12. aug. 2011, at 15:15, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
hi guys
Context: So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that.
Actions: So now we are including several packages in the image so that we do not have two images.   FS   RB engine   Shout   OCompletion   Collection-Arithmetics   SystemAnnouncement     this one is special and some of you may not know it.     It is a package that raise announcement for system changes.     The idea is that we will then       1- change all the tools to register to SystemAnnouncement       2- replace all the SystemChangeNotification hooks by SystemAnnouncement       3- remove our old friend SystemChangeNotifier.
The idea is then to be able to integrate/enhance these packages deeper into the system   FS for example to replace the old file package
Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too).
Ugh. Collection-Aritmetics was extracted exactly -because- it's nothing that belongs in image by default...
I have no idea why it required.. hopefully we could remove users of it and unload it again :)
As for RB, my impression through your conversations with Lukas is that it's not enough to include it, you need someone who understands the architecture for bug fixes/changes that preserve architectural integrity rather than end up as ugly hacks.
I like the functionality of OCompletion, but from what little I've read of Shout, only it's mother could love it. (same applies to texteditor etc. though, so I guess it's not a very good argument against integrating it)
So true. But first we need to integrate this stuff, and then start working on cleaning it out.
FS + SystemAnnouncements, I'm all for :)
Cheers, Henry
-- Best regards, Igor Stasenko AKA sig.
El vie, 12-08-2011 a las 15:15 +0200, Stéphane Ducasse escribió:
SystemAnnouncement this one is special and some of you may not know it. It is a package that raise announcement for system changes. The idea is that we will then 1- change all the tools to register to SystemAnnouncement 2- replace all the SystemChangeNotification hooks by SystemAnnouncement 3- remove our old friend SystemChangeNotifier.
Fantastic! -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx
participants (5)
-
Henrik Johansen -
Igor Stasenko -
Mariano Martinez Peck -
Miguel Cobá -
Stéphane Ducasse