July 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] **Important Please read** Towards First Class Tasks

by Tudor Girba

Thanks. I entered a row for the Glamorous Toolkit. The next thing is to enter the issues. Doru On 24 Jul 2011, at 11:35, Damien Cassou wrote: > On Sun, Jul 24, 2011 at 11:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> I would do it if you give me access to edit the page. > > that should work with your tudor.girba(a)gmail.com account. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

July 24, 2011

Re: [Pharo-project] [Pharo-users] **Important Please read** Towards First Class Tasks

by Damien Cassou

On Sun, Jul 24, 2011 at 11:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I would do it if you give me access to edit the page. that should work with your tudor.girba(a)gmail.com account. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 24, 2011

Re: [Pharo-project] [Pharo-users] **Important Please read** Towards First Class Tasks

by Tudor Girba

I would do it if you give me access to edit the page. Cheers, Doru On 24 Jul 2011, at 10:29, StÃ©phane Ducasse wrote: > Doru can you add the page on morphic on this list? > Marcus can you add a page to OPAL? > with pending todo? > Damien can you add one for Coral? > > > >> http://code.google.com/p/pharo/wiki/Teams > > > > I added RPackage > http://code.google.com/p/pharo/wiki/RPackageRoadmap > so that people can follow the effort. > > > Stef > > Here is what I wrote. > > > Introduction > > The current status is that RPackage works well with a one to one mapping package - category. > > Done: > > â¢ All the events have been migrated from systemNotifier to SystemAnnouncer?. The package SystemAnnouncement? is ready for inclusion. This means that RPackage does not rely on systemnotifier to keep its data in sync. This also means that SystemAnnouncer? can be folded in the system and that other tools can use it. And that we will be able to remove SystemNotifier?. Nautilus is only based on SystemNotifier?. > â¢ A lot of tests. In addition tests are written in a way that the central RPackageOrganizer is not impacted by test running. > â¢ Nautilus and Moose using RPackage. Nautilus is based on RPackage. Moose uses RPackage as a cache since months. > â¢ Identification of the clients using PackageInfo?. We started to identify clients of PackageInfo? to prepare migration phase. > Next steps: > > â¢ Clean RPackage (because some functionality were copied from PackageInfo?): > â¢ Problem Gofer and the some package of RefactoringEngine? rely on this API > â¢ Solution: include Refactoring packages in 1.4 and modify it there. In 1.4 we want OCompletion, Ecompletion and Refactoring in the image so this fits well. In subsequent versions we may republish them as separate packages. > â¢ Adding Package Tags. Since people do not want (but have no time to do it - funny isn't) to have one -one mapping between category and package. We will add tags the idea is to be able to have classes sorted inside a package. > Pack1 > - Tag1 > ClassA > ClassB > - Tag2 > ClassC > ClassD > ClassA > Pack2 > - Tag1 > - Tag3 > â¢ MC shoud use RPackage to save information > â¢ Tags should be saved in MC package > â¢ New MC Browser -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

July 24, 2011

Re: [Pharo-project] does anybody want to continue the comment of the day effort?

by laurent laffont

I will continue after my holidays. Laurent. On Sun, Jul 24, 2011 at 10:56 AM, Max Leske <maxleske(a)gmail.com> wrote: > Although I haven't had anything to contribute up to now, I vote to continue > it. If there is a comment I can help with, I will. > > Max > > > On 24.07.2011, at 10:02, StÃ©phane Ducasse wrote: > > > HI guys > > > > does any of you want to continue the comment of the day effort? > > Because it was really important. > > > > Stef > > > > >

July 24, 2011

Re: [Pharo-project] does anybody want to continue the comment of the day effort?

by Max Leske

Although I haven't had anything to contribute up to now, I vote to continue it. If there is a comment I can help with, I will. Max On 24.07.2011, at 10:02, StÃ©phane Ducasse wrote: > HI guys > > does any of you want to continue the comment of the day effort? > Because it was really important. > > Stef >

July 24, 2011

Re: [Pharo-project] [Pharo-users] **Important Please read** Towards First Class Tasks

by StÃ©phane Ducasse

Doru can you add the page on morphic on this list? Marcus can you add a page to OPAL? with pending todo? Damien can you add one for Coral? > http://code.google.com/p/pharo/wiki/Teams I added RPackage http://code.google.com/p/pharo/wiki/RPackageRoadmap so that people can follow the effort. Stef Here is what I wrote. Introduction The current status is that RPackage works well with a one to one mapping package - category. Done: â¢ All the events have been migrated from systemNotifier to SystemAnnouncer?. The package SystemAnnouncement? is ready for inclusion. This means that RPackage does not rely on systemnotifier to keep its data in sync. This also means that SystemAnnouncer? can be folded in the system and that other tools can use it. And that we will be able to remove SystemNotifier?. Nautilus is only based on SystemNotifier?. â¢ A lot of tests. In addition tests are written in a way that the central RPackageOrganizer is not impacted by test running. â¢ Nautilus and Moose using RPackage. Nautilus is based on RPackage. Moose uses RPackage as a cache since months. â¢ Identification of the clients using PackageInfo?. We started to identify clients of PackageInfo? to prepare migration phase. Next steps: â¢ Clean RPackage (because some functionality were copied from PackageInfo?): â¢ Problem Gofer and the some package of RefactoringEngine? rely on this API â¢ Solution: include Refactoring packages in 1.4 and modify it there. In 1.4 we want OCompletion, Ecompletion and Refactoring in the image so this fits well. In subsequent versions we may republish them as separate packages. â¢ Adding Package Tags. Since people do not want (but have no time to do it - funny isn't) to have one -one mapping between category and package. We will add tags the idea is to be able to have classes sorted inside a package. Pack1 - Tag1 ClassA ClassB - Tag2 ClassC ClassD ClassA Pack2 - Tag1 - Tag3 â¢ MC shoud use RPackage to save information â¢ Tags should be saved in MC package â¢ New MC Browser

July 24, 2011

[Pharo-project] does anybody want to continue the comment of the day effort?

by StÃ©phane Ducasse

HI guys does any of you want to continue the comment of the day effort? Because it was really important. Stef

July 24, 2011

Re: [Pharo-project] Time Profile mostly unusable

by Hilaire Fernandes

Don't worry, we are already building cool stuff with Pharo! Hilaire Le 23/07/2011 20:51, StÃ©phane Ducasse a Ã©crit : > A final word on this thread. We are not changing for the sake of it. With time we are just getting to lower parts of the system. > I imagine that slowly we will arrive to a fixpoint in certain areas. And this is good. I would like to be able to focus on my research > and build cool stuff on top of pharo. > Now we are working on a roadmap slideshow to show where we are working and what is on our radar so that you can understand it. > > Stef > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

July 24, 2011

Re: [Pharo-project] Time Profile mostly unusable

by Norbert Hartl

Am 23.07.2011 um 20:51 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > A final word on this thread. We are not changing for the sake of it. With time we are just getting to lower parts of the system. > I imagine that slowly we will arrive to a fixpoint in certain areas. And this is good. I would like to be able to focus on my research > and build cool stuff on top of pharo. > Now we are working on a roadmap slideshow to show where we are working and what is on our radar so that you can understand it. > great! Norbert

July 23, 2011

Re: [Pharo-project] Time Profile mostly unusable

by StÃ©phane Ducasse

A final word on this thread. We are not changing for the sake of it. With time we are just getting to lower parts of the system. I imagine that slowly we will arrive to a fixpoint in certain areas. And this is good. I would like to be able to focus on my research and build cool stuff on top of pharo. Now we are working on a roadmap slideshow to show where we are working and what is on our radar so that you can understand it. Stef

July 23, 2011