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

Re: [Pharo-project] List of next large actions

by StÃ©phane Ducasse

On Jul 25, 2011, at 10:02 PM, Luc Fabresse wrote: > > > > 2011/7/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Jul 25, 2011, at 9:46 PM, Luc Fabresse wrote: > > > Hi Stef, > > > > - Add RBengine > > - step one add RBEngine packages > > > > what is RBEngine? > > the engine doing refactoring= > AST (for Opal :)) > Refactoring > RBModel = selection of the entities to be manipulated > RBCritics > RBASTPatternMatcher > > Yes ok, I mis-read. > I was thinking of something related to RPackge ;-) No I'm working on it :) Now one of these days we should sync and think about modules for pharo :)

July 25, 2011

Re: [Pharo-project] List of next large actions

by Luc Fabresse

2011/7/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Jul 25, 2011, at 9:46 PM, Luc Fabresse wrote: > > > Hi Stef, > > > > - Add RBengine > > - step one add RBEngine packages > > > > what is RBEngine? > > the engine doing refactoring= > AST (for Opal :)) > Refactoring > RBModel = selection of the entities to be manipulated > RBCritics > RBASTPatternMatcher > Yes ok, I mis-read. I was thinking of something related to RPackge ;-) Luc > > > > > > #Luc > > > > - step two (check RPackage changes) > > > > - Add OCompletion > > > > - Add Ecompletion > > > > - Integrate SystemAnnouncer > > - step one load package > > - would be cool to convert SystemChangeNotifierTest into tests > usable for SystemAnnouncer (even if RPackage has a lot of tests). > > - step two replace SystemChangeNotifier emission > > > > - Integrate Ring > > - SystemNavigation should use Ring Objects > > - Replace Source* and MethodReference by Ring Object > > > > > > May be I missed some points but it would be good to have that in 1.4 > > > > Stef > > > > >

July 25, 2011

Re: [Pharo-project] List of next large actions

by StÃ©phane Ducasse

On Jul 25, 2011, at 9:46 PM, Luc Fabresse wrote: > Hi Stef, > > - Add RBengine > - step one add RBEngine packages > > what is RBEngine? the engine doing refactoring= AST (for Opal :)) Refactoring RBModel = selection of the entities to be manipulated RBCritics RBASTPatternMatcher > > #Luc > > - step two (check RPackage changes) > > - Add OCompletion > > - Add Ecompletion > > - Integrate SystemAnnouncer > - step one load package > - would be cool to convert SystemChangeNotifierTest into tests usable for SystemAnnouncer (even if RPackage has a lot of tests). > - step two replace SystemChangeNotifier emission > > - Integrate Ring > - SystemNavigation should use Ring Objects > - Replace Source* and MethodReference by Ring Object > > > May be I missed some points but it would be good to have that in 1.4 > > Stef >

July 25, 2011

Re: [Pharo-project] List of next large actions

by Luc Fabresse

Hi Stef, - Add RBengine > - step one add RBEngine packages > what is RBEngine? #Luc > - step two (check RPackage changes) > > - Add OCompletion > > - Add Ecompletion > > - Integrate SystemAnnouncer > - step one load package > - would be cool to convert SystemChangeNotifierTest into tests > usable for SystemAnnouncer (even if RPackage has a lot of tests). > - step two replace SystemChangeNotifier emission > > - Integrate Ring > - SystemNavigation should use Ring Objects > - Replace Source* and MethodReference by Ring Object > > > May be I missed some points but it would be good to have that in 1.4 > > Stef >

July 25, 2011

[Pharo-project] List of next large actions

by StÃ©phane Ducasse

Hi guys I will be offline or busy with kids for some days and I wanted to make a list of todos for when I want to do something. - Integrate FS - step one add FS packages - step two integrated = use FS - Add RBengine - step one add RBEngine packages - step two (check RPackage changes) - Add OCompletion - Add Ecompletion - Integrate SystemAnnouncer - step one load package - would be cool to convert SystemChangeNotifierTest into tests usable for SystemAnnouncer (even if RPackage has a lot of tests). - step two replace SystemChangeNotifier emission - Integrate Ring - SystemNavigation should use Ring Objects - Replace Source* and MethodReference by Ring Object May be I missed some points but it would be good to have that in 1.4 Stef

July 25, 2011

Re: [Pharo-project] [update 1.4] #14057

by StÃ©phane Ducasse

On Jul 25, 2011, at 6:08 PM, Gary Chambers wrote: > I did check. Having a single accessor (with mutation) does not cover all the cases. Some users require *no* getter, for instance, so would be erroneous to update in response to a change. Ok I finally got it :) we are open to change :) our goal was to clean the ugly "ok let us compile a method on the fly" Stef > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, July 25, 2011 4:36 PM > Subject: Re: [Pharo-project] [update 1.4] #14057 > > > Did you check what we did? > Because it would give us some confidence :) > > Stef > > On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > >> Some trickyness. >> >> Use of a combined accessor vs. separate get/set selectors may cause some problems since less flexible. >> Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and UITheme helpers. >> >> Regards, Gary >> >> ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> To: "pharo-project open-source Smalltalk" <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, July 22, 2011 6:31 PM >> Subject: [Pharo-project] [update 1.4] #14057 >> >> >> 14057 >> ----- >> >> - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor killing tha big monster - Part two. :) >> http://code.google.com/p/pharo/issues/detail?id=4513 >> >> Gary it would be good that you check because we have two ways to to a perform: accessor and setValueSelector while only one would be enough. >> >> Stef and Igor >> > > >

July 25, 2011

Re: [Pharo-project] A request or suggestion.

by Patrick Barroca

Yep TWM detect some types of windows, browsers, workspaces, monticello and propose a menu to list them and tile only this type. By the way, this could be cool to enable arbitrary window group in TWM ;) On Mon, Jul 25, 2011 at 6:06 PM, Gary Chambers <gazzaguru2(a)btinternet.com>wrote: > ** > I think I know what Friedrich means, groups of items under a single taskbar > entry (with popup shortlist). > Unfortunately there is no formal mechanism for identifying individual > windows as belonging to a a group. > > Any window can have whatever title/label it wants, models are not either > present or identical for the same "type" of window etc. > > Could introduce a "taskbar type" perhaps, maybe TWm does something similar > for grouping. > > Regards, Gary > > ----- Original Message ----- > *From:* Patrick Barroca <patrick.barroca(a)gmail.com> > *To:* Pharo-project(a)lists.gforge.inria.fr > *Sent:* Monday, July 25, 2011 4:31 PM > *Subject:* Re: [Pharo-project] A request or suggestion. > > Hello, > > TWM stands for Tiling Windows Manager, check screencasts at the author's > blog to see it in action: > http://magaloma.blogspot.com/. > > I think it could cover you needs pretty well ;) > > > On Mon, Jul 25, 2011 at 9:50 AM, Friedrich Dominicus < > frido(a)q-software-solutions.de> wrote: > >> StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> writes: >> >> > Check the settings because you can say to the window manager that it >> should stagger or position them in another way. >> > Else have a look at TWM >> > Stef >> I tried to change the window positioning but that was not what I wanted >> to have I want in the low applicaton bar a group of Workspaces a group >> of Browsers etc. >> >> So what option are you referring to? >> >> Regards >> Friedrich >> >> -- >> Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim >> Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus >> >> > > > -- > Patrick Barroca > > -- Patrick Barroca

July 25, 2011

Re: [Pharo-project] [update 1.4] #14057

by Gary Chambers

I did check. Having a single accessor (with mutation) does not cover all the cases. Some users require *no* getter, for instance, so would be erroneous to update in response to a change. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, July 25, 2011 4:36 PM Subject: Re: [Pharo-project] [update 1.4] #14057 Did you check what we did? Because it would give us some confidence :) Stef On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > Some trickyness. > > Use of a combined accessor vs. separate get/set selectors may cause some > problems since less flexible. > Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and > UITheme helpers. > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" > <stephane.ducasse(a)inria.fr> > To: "pharo-project open-source Smalltalk" > <Pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, July 22, 2011 6:31 PM > Subject: [Pharo-project] [update 1.4] #14057 > > > 14057 > ----- > > - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor > killing tha big monster - Part two. :) > http://code.google.com/p/pharo/issues/detail?id=4513 > > Gary it would be good that you check because we have two ways to to a > perform: accessor and setValueSelector while only one would be enough. > > Stef and Igor >

July 25, 2011

Re: [Pharo-project] A request or suggestion.

by Gary Chambers

I think I know what Friedrich means, groups of items under a single taskbar entry (with popup shortlist). Unfortunately there is no formal mechanism for identifying individual windows as belonging to a a group. Any window can have whatever title/label it wants, models are not either present or identical for the same "type" of window etc. Could introduce a "taskbar type" perhaps, maybe TWm does something similar for grouping. Regards, Gary ----- Original Message ----- From: Patrick Barroca To: Pharo-project(a)lists.gforge.inria.fr Sent: Monday, July 25, 2011 4:31 PM Subject: Re: [Pharo-project] A request or suggestion. Hello, TWM stands for Tiling Windows Manager, check screencasts at the author's blog to see it in action: http://magaloma.blogspot.com/. I think it could cover you needs pretty well ;) On Mon, Jul 25, 2011 at 9:50 AM, Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> writes: > Check the settings because you can say to the window manager that it should stagger or position them in another way. > Else have a look at TWM > Stef I tried to change the window positioning but that was not what I wanted to have I want in the low applicaton bar a group of Workspaces a group of Browsers etc. So what option are you referring to? Regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus -- Patrick Barroca

July 25, 2011

Re: [Pharo-project] Pharo 1.3 Seaside 'client' build ?

by StÃ©phane Ducasse

Yes!!! Stef On Jul 25, 2011, at 4:31 PM, Sven Van Caekenberghe wrote: > Hi (Marcus), > > I was looking for a Pharo 1.3 Seaside 'client' build on the CI server(s) but couldn't find it. > > It used to be available for 1.2.x (this seems to be gone as well). > > I think that for good reciprocal relations with Seaside, it would be very good to have a tested build of the current main Pharo images. It make a good testcase as well. And it saves quite some work, loading the Seaside config is pretty slow. > > I remember reading something about some clients being removed from the CI's, but I didn't register it fully. > > Thx, > > Sven > > PS: Another questions is: is 1.3 'released', if so where are the links on the website, where is the 'noise' ? > > >

July 25, 2011