January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] problems with RPackage and cie...

by Benjamin

Step to reproduce: Open latest Pharo30719. Create a new package with shortcut or menu. Name it âAST-Monkeyâ (to have a RPackage not a Tag) Go in another package. Select some classes. CMD M + CMD C (and probably with the menu too) (note that the Drag nâ Drop works) Type the name of the package âAST-Monkeyâ + enter BOUM Might be that you fixed the drag n drop in the PackageTreeNautilusUI but not the move class. Ben On 24 Jan 2014, at 10:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I would really like a reproducible caseâ¦ in the form of an image, if no else. > > btwâ¦ moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems. > > Esteban > > On 24 Jan 2014, at 13:28, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> >> >> Le 23/01/2014 18:57, Benjamin Van Ryseghem a Ã©crit : >>> Just that you know I faced it again :( >>> I created a new RPackage, move classes in the newly created RPackage. >>> And when I wanted to commit the code, it was empty. >> >> Have you tried with the old Browser to see if your classes were in the right category? >> >> (When I see something suspicious like that happening, I often open the three browsers to double check: AltBrowser, Nautilus and Browser). >> >> And I have not seen anything suspicious that I could pinpoint to RPackage so far. Small bugs easily corrected, yes. Big totally out of sync, no. >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > >

Jan. 24, 2014

Re: [Pharo-dev] [Pharo-users] Life, Ukraine, Developers

by Pablo EstefÃ³

I wish you the best for you guys and please stay safe! Which are the reliable channels to know whats happening and spread the word? On Jan 22, 2014, at 15:06, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > My dear Pharo friends, > > I have no idea if you are aware, but now a big country named Ukraine is facing a very hard times. People are fighting for their rights while the current government tries to convert the country into Somalia - like regime. > > Why should you care? Because you will like Ukrainians. And referring to the context: we develop a lot. If you are not familiar: https://github.com/fre5h/DoctrineEnumBundle/pull/12 > > I donât want to cry here, but me, Igor Stasenko and some other pharo developers are from Ukraine, and we are extremely worried about our Home. I just ask you to think about our country for a minute. Tell your friends: âYou know, there is this nice country called Ukraine, where people are being shot just because they want to have a freedom of speechâ. And if you believe in God, please say a short prayer for Ukraine, I trust that this is important. > > Sorry guys for taking your time, but I was touched by this pull request and just wanted to share what is happening around. > Cheers! > Uko

Jan. 24, 2014

Re: [Pharo-dev] About doing things late (1 month before release)

by Marcus Denker

On 24 Jan 2014, at 14:48, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > On 24 Jan 2014, at 10:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> And I can not be the only person who decides things. I think people have no idea how tiring it is >> to take a decisions like that all the time. >> >> The tiring thin about integrating is not the integration. Itâs the fact that one has to *decide* something >> like that 10 times a day. >> > > > Should I say that then maybe we should change the integration process? > As already proposed multiple times? What will it help? Who will then decide? Why does that person not help deciding now? Marcus

Jan. 24, 2014

Re: [Pharo-dev] problems with RPackage and cie...

by Stephan Eggermont

Esteban wrote: >I would really like a reproducible caseâ¦ in the form of an image, if no else. > >btwâ¦ moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems. I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac Open the image, open a Nautilus browser Add new package AZ Select AST-Core, Nodes Select RBProgramNode Copy the class with right-click menu Rename to AZProgramNode Enter your name (should have happened when creating the new package!) Drag AZProgramNode to AZ Category is not updated. Stephan

Jan. 24, 2014

Re: [Pharo-dev] About doing things late (1 month before release)

by Benjamin

On 24 Jan 2014, at 10:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > And I can not be the only person who decides things. I think people have no idea how tiring it is > to take a decisions like that all the time. > > The tiring thin about integrating is not the integration. Itâs the fact that one has to *decide* something > like that 10 times a day. > Should I say that then maybe we should change the integration process? As already proposed multiple times? Ben

Jan. 24, 2014

Re: [Pharo-dev] About doing things late (1 month before release)

by Torsten Bergmann

It is not the first time we do a release and not the last time and in the worst case we have some updates afterwards. So the warning is clear: no radical changes anymore. But we should try to improve and stabilize the system (as ever). Step by step... Thx T. @Marcus: we appreciate this decision making!

Jan. 24, 2014

Re: [Pharo-dev] About doing things late (1 month before release)

by Marcus Denker

On 24 Jan 2014, at 14:24, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 24 Jan 2014, at 14:19, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> On 24 Jan 2014, at 10:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> In beta normally we should not change things that require people to change again code... >> >> Then do not integrate them ... >> > > The issue was âfix to includeâ which is defined as âdo not think, include, all discussion has been > doneâ. And I can not be the only person who decides things. I think people have no idea how tiring it is to take a decisions like that all the time. The tiring thin about integrating is not the integration. Itâs the fact that one has to *decide* something like that 10 times a day. Marcus

Jan. 24, 2014

Re: [Pharo-dev] About doing things late (1 month before release)

by Marcus Denker

On 24 Jan 2014, at 14:19, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > On 24 Jan 2014, at 10:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> In beta normally we should not change things that require people to change again code... > > Then do not integrate them ... > The issue was âfix to includeâ which is defined as âdo not think, include, all discussion has been doneâ. Marcus

Jan. 24, 2014

Re: [Pharo-dev] problems with RPackage and cie...

by Esteban Lorenzano

I would really like a reproducible caseâ¦ in the form of an image, if no else. btwâ¦ moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems. Esteban On 24 Jan 2014, at 13:28, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 23/01/2014 18:57, Benjamin Van Ryseghem a Ã©crit : >> Just that you know I faced it again :( >> I created a new RPackage, move classes in the newly created RPackage. >> And when I wanted to commit the code, it was empty. > > Have you tried with the old Browser to see if your classes were in the right category? > > (When I see something suspicious like that happening, I often open the three browsers to double check: AltBrowser, Nautilus and Browser). > > And I have not seen anything suspicious that I could pinpoint to RPackage so far. Small bugs easily corrected, yes. Big totally out of sync, no. > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Jan. 24, 2014

Re: [Pharo-dev] About doing things late (1 month before release)

by Benjamin

On 24 Jan 2014, at 10:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > In beta normally we should not change things that require people to change again code... Then do not integrate them ... Ben

Jan. 24, 2014