September 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.1] #11412

by StÃ©phane Ducasse

Yes thanks because the system does not handle well the idea that a bug could be fixed in a brnach and not in another one. Annoying becuse I spend time reading and reading the same all over. Anyway Marcus should push 1.1.1 but not redo 1.2 :) Stef On Sep 5, 2010, at 5:28 PM, Henrik Johansen wrote: > A couple of issues that applies to 1.1.1 was marked as closed when they were integrated in 1.2, I reverted to fixed in case you are up for another round :) > > Cheers, > Henry > > Den 5. sep. 2010 kl. 16:34 skrev Marcus Denker <marcus.denker(a)inria.fr>: > >> 11412 >> ----- >> >> Issue 2912: Cog changes for 1.1.1 >> Issue 2896: Make sure system notifications for Smalltalk are up-to-date >> Issue 2893: Network bugs >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2010

Re: [Pharo-project] [Moose-dev] glamorous theme :)

by StÃ©phane Ducasse

tx Doru don;t you want to put a bit of blue in the look instead of all this grey. Stef On Sep 5, 2010, at 11:23 AM, Sven Van Caekenberghe wrote: > > On 05 Sep 2010, at 09:54, StÃ©phane Ducasse wrote: > >> screenshots PLEASE! > > http://homepage.mac.com/svc/Screenshots/Screenshot-20100905T111347.png > > Doru, > > I made the #baseSelectionColor almost black (I didn't like the blue, de gustibus non est disputandum ;-) by overwriting it: > > baseSelectionColor > ^ "Color r: 0.38 g: 0.64 b: 0.88" Color darkGray muchDarker > > I could subclass as well I guess, or you could make it into a variable with a setter, what do you think ? > > Anyway, very well done, it feels very fast, which was a goal I presume. > > Sven > > PS: the name is a nice pun too! > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2010

Re: [Pharo-project] [Moose-dev] Re: glamorous theme :)

by StÃ©phane Ducasse

a bit too grey for me, I prefer anymorphic on that front. Stef On Sep 5, 2010, at 10:15 AM, laurent laffont wrote: > I like it. > > Screenshot: http://picasaweb.google.com/lh/photo/C8Psie5Q-msL2ZDAiIf3BQ?feat=directlink > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > > On Sun, Sep 5, 2010 at 9:54 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > screenshots PLEASE! > On Sep 4, 2010, at 11:18 PM, Tudor Girba wrote: > > > Hi, > > > > Over the past week I worked on a new theme for Pharo called the Glamorous Theme :). The theme is developed in the context of the Glamour project, and its goal is to create a look that: > > - does not look like a specific operating system. In particular, the icons should be operating system agnostic, because, for example, people in Windows are confused by the red, yellow, green buttons of apple. > > - uses a limited amount of colors and effects. > > > > It is still work in progress, but you can get the current version by executing: > > > > Gofer new > > squeaksource: 'Glamour'; > > package: 'Glamour-Morphic-Theme'; > > load. > > GLMUITheme defaultSettings: nil. > > GLMUITheme beCurrent. > > GLMUITheme setPreferredWorldBackground. > > > > Cheers, > > Doru > > > > -- > > www.tudorgirba.com > > > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Sept. 5, 2010

Re: [Pharo-project] About using RB changes in Gaucho and Pharo

by StÃ©phane Ducasse

On Sep 5, 2010, at 9:45 AM, Fernando olivero wrote: > When i started working on the new Gaucho, i tried to use/understand the current change model without success. yes we can all forget. This part is ugly and brittle > So i chose to use the RB engine ( thanks lukas for nicely maintaining it!) > > In the soon to be released Gaucho1.1 i'm using RB changes to record every change made to the system, changes that take part during a Gaucho development session. > So i will be able to provide an insight to the feasability of using RB changes to record and persist sessions, and easily provide undo's . Maybe this work could be plugged into a new Pharo changes system! Yes we plan to use RBChange as a foundation infrastructure. I with veronica plan to also have a declarative code model so that we can do decent recentChanges and the rest. BTW there is a nice Undo framework of a couple of classes in sophie I added a first fileout to the bug entry. > > > Fernando > > pd: > BTW, i enhanced the RB changes with AddPackageRefactoring and others related to the UI, ( in this way i'm also recording every UI event ). After the ESUG i will try to integrate the relevant ones to RB. what are the UI event? because I would like to replacement SystemChangeNotifier events by announcements (check systemAnnouncement) as in ConfigurationOfRPackage. > > >> >>> Refactoring-Core, but would work independently) >>> Refactoring-Changes (this is currently part of Refactoring-Core, >>> but would work independently) >> >> yes I'm curious to see if/how we could use changes to represent changeset. >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2010

Re: [Pharo-project] [update 1.1] #11412

by Schwab,Wilhelm K

+1 Please leave out the new inspector. Inspectors should be simple, and the explorer does a nice job of presenting a recursive tree; that's enough IMHO. One inspector change I did like was a port to Dolphin of VW's (???) "diving inspector." Double clicking on items did not open a new inspector; it simply changed the model of the current inspector. There was a context menu item to inspect which *did* open a new inspector, so nothing was lost and most of the time, it did exactly what was intended. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker(a)inria.fr] Sent: Sunday, September 05, 2010 11:50 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [update 1.1] #11412 On Sep 5, 2010, at 5:44 PM, Tudor Girba wrote: > Sounds cool. Will there be a Pharo 1.1.1 release? > > Yes, as soon as possible... the idea is to first do a core with all the small things people found. The idea here is to just collect what is fixed. Not fix more. (there can always be a 1.1.2 later... no need to no do the next tiny thing) Then do a 1.1 main image, here we can use the latest OB/RB from Lukas. Another thing I think we should do it to not add the newInspector this time. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2010

Re: [Pharo-project] [update 1.1] #11412

by Marcus Denker

On Sep 5, 2010, at 5:44 PM, Tudor Girba wrote: > Sounds cool. Will there be a Pharo 1.1.1 release? > > Yes, as soon as possible... the idea is to first do a core with all the small things people found. The idea here is to just collect what is fixed. Not fix more. (there can always be a 1.1.2 later... no need to no do the next tiny thing) Then do a 1.1 main image, here we can use the latest OB/RB from Lukas. Another thing I think we should do it to not add the newInspector this time. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Sept. 5, 2010

Re: [Pharo-project] [update 1.1] #11412

by Tudor Girba

Sounds cool. Will there be a Pharo 1.1.1 release? Cheers, Doru On 5 Sep 2010, at 16:55, Marcus Denker wrote: > > On Sep 5, 2010, at 4:47 PM, Lukas Renggli wrote: > >>> Issue 2912: Cog changes for 1.1.1 >> >> Cool, that means Cog works out of the box? >> > > This are the changes that Moose uses... so yes, I think so. (did not > test it yet, though). > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Beauty is where we see it."

Sept. 5, 2010

Re: [Pharo-project] [update 1.1] #11412

by Henrik Johansen

A couple of issues that applies to 1.1.1 was marked as closed when they were integrated in 1.2, I reverted to fixed in case you are up for another round :) Cheers, Henry Den 5. sep. 2010 kl. 16:34 skrev Marcus Denker <marcus.denker(a)inria.fr>: > 11412 > ----- > > Issue 2912: Cog changes for 1.1.1 > Issue 2896: Make sure system notifications for Smalltalk are up-to-date > Issue 2893: Network bugs > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2010

Re: [Pharo-project] [update 1.1] #11412

by Marcus Denker

On Sep 5, 2010, at 4:47 PM, Lukas Renggli wrote: >> Issue 2912: Cog changes for 1.1.1 > > Cool, that means Cog works out of the box? > This are the changes that Moose uses... so yes, I think so. (did not test it yet, though). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Sept. 5, 2010

Re: [Pharo-project] [update 1.1] #11412

by Lukas Renggli

> Issue 2912: Â Â Cog changes for 1.1.1 Cool, that means Cog works out of the box? Lukas -- Lukas Renggli www.lukas-renggli.ch

Sept. 5, 2010