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

Re: [Pharo-project] who is using softSqueak and standard Squeak

by StÃ©phane Ducasse

Yes! Partick if you want to extend the default theme to add color please do. We can create a repo PharoThemes and we are done. I would really like to remove the standard squeak because it is terrible. I set it up since some updates and I cannot work with it anymore. Stef On Mar 29, 2011, at 9:10 AM, Patrick Barroca wrote: > On Mon, Mar 28, 2011 at 9:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > When I see how much code we cleaned.... I think that there should be soemthing else > than the color. > > Stef > > > > Yep, from my small experience making Sandcastles Themes, UIThemes are composed of colours, font and border styles, icon set, even UI layout (windows title area for example) AFAIK. > > BTW, I'm in favor of packaging themes outside of pharo but there should be an official place (repo) where one can list them. > > I'm thinking of something like http://art.gnome.org/themes. > > -- > Patrick Barroca

March 29, 2011

Re: [Pharo-project] Issue 3878 in pharo: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText

by pharo＠googlecode.com

Comment #2 on issue 3878 by stephane...(a)gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 can you deprecate enableTextChange because this class is used by other clients?

March 29, 2011

Re: [Pharo-project] Issue 3898 in pharo: Remove some dead code from PasteUpMorph

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3898 by stephane...(a)gmail.com: Remove some dead code from PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3898 in 13116

March 29, 2011

[Pharo-project] Getting Pharo 1.2 on Hudson green/blue again

by Torsten Bergmann

Hi Markus, I think I've found out what the problem with the hudson build for Pharo 1.2 is: - the Pharo-1.2.st Skript used to build it includes this line: ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) which now returns 1.3. instead of 1.2 since the config was extended. Guess who did it: ConfigurationOfPharo-MarcusDenker.148 on 22 March 2011, the day when the hudson build broke So change the line in Pharo-1.2.st to: ((Smalltalk at: #ConfigurationOfPharo) project version: '1.2-beta2') perform: #silently: with: true; perform: #load. and the build works. At least it does manually when I try it here. If that works you either send me a beer or you take the time to exchange the VM to the customized ones I've sent you so we can move 1.2 out of the door and concentrate on 1.3... Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

March 29, 2011

Re: [Pharo-project] Issue 3888 in pharo: Move Digital Signatur code to System-Hashing package

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3888 by stephane...(a)gmail.com: Move Digital Signatur code to System-Hashing package http://code.google.com/p/pharo/issues/detail?id=3888 13116

March 29, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by laurent laffont

On Tue, Mar 29, 2011 at 9:10 AM, Patrick Barroca <patrick.barroca(a)gmail.com>wrote: > On Mon, Mar 28, 2011 at 9:22 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> >> When I see how much code we cleaned.... I think that there should be >> soemthing else >> than the color. >> >> Stef >> >> >> > Yep, from my small experience making Sandcastles Themes, UIThemes are > composed of colours, font and border styles, icon set, even UI layout > (windows title area for example) AFAIK. > > BTW, I'm in favor of packaging themes outside of pharo but there should be > an official place (repo) where one can list them. > > I'm thinking of something like http://art.gnome.org/themes. > We could just list them in http://book.pharo-project.org/ with a screenshot. Better: having settings loading them on the fly when we choose it like in KDE plasma preferences. Laurent. > > -- > Patrick Barroca >

March 29, 2011

Re: [Pharo-project] Issue 3888 in pharo: Move Digital Signatur code to System-Hashing package

by pharo＠googlecode.com

Comment #2 on issue 3888 by stephane...(a)gmail.com: Move Digital Signatur code to System-Hashing package http://code.google.com/p/pharo/issues/detail?id=3888 13116

March 29, 2011

Re: [Pharo-project] Issue 3899 in pharo: clean up #maybeDuplicateMorph:

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3899 by stephane...(a)gmail.com: clean up #maybeDuplicateMorph: http://code.google.com/p/pharo/issues/detail?id=3899 in 13116

March 29, 2011

Re: [Pharo-project] Issue 3892 in pharo: clean AbstractHierarchicalList

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3892 by stephane...(a)gmail.com: clean AbstractHierarchicalList http://code.google.com/p/pharo/issues/detail?id=3892 in 13116

March 29, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by Patrick Barroca

On Mon, Mar 28, 2011 at 9:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > When I see how much code we cleaned.... I think that there should be > soemthing else > than the color. > > Stef > > > Yep, from my small experience making Sandcastles Themes, UIThemes are composed of colours, font and border styles, icon set, even UI layout (windows title area for example) AFAIK. BTW, I'm in favor of packaging themes outside of pharo but there should be an official place (repo) where one can list them. I'm thinking of something like http://art.gnome.org/themes. -- Patrick Barroca

March 29, 2011