- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Comment #2 on issue 3522 by stephane.ducasse: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 If you have some cycles I would like to integrate a version in 1.2 because having a good help is important.

Jan. 13, 2011

[Pharo-project] PharoConf Annecy 2011

by laurent laffont

Hi, PharoConf Annecy will took place at IMUS (UniversitÃ© of Savoie), 10th February. Website here: http://pharoconf-annecy.seasidehosting.st/ (in french, but google translate starts to be wonderful :) It's a local event focused on real code, coding-dojo, katas using Pharo. If you're not far from Annecy, welcome ! Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Jan. 13, 2011

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by Alain Plantec

Hi all, yes, I agree list selection and selection colors (and some others) can be changed from the setting browser. I think that in the core only the default theme should be present. The others should be packaged separately and loadable on-demand or when a package is loaded as it is for moose/glamour. Cheers Alain Le 13/01/2011 21:27, Mariano Martinez Peck a Ã©crit : > > > On Thu, Jan 13, 2011 at 9:15 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > > 12302 > ----- > > - GLMOrangeUITheme. Thanks Igor Stasenko > > > I don't agree with this kind of changes. > Tomorrow I want Watery2BlackTheme and GLMYellowUITHeme and what? we > are going to integrate it also? > > I don't understand. The change should be to create a setting to set > the color and then igor runs a script in his own image that set it to > orange. Me to yellow. And you to pink. > > > - Issue 3538: Add a "Browse test" in the TestRunner failed/error > list. Thanks Benjamin van Ryseghem > > Stef > >

Jan. 13, 2011

Re: [Pharo-project] Issue 3224 in pharo: Migrating MethodReference to MethodReferenceWithSource

by pharo＠googlecode.com

Updates: Status: Closed Comment #18 on issue 3224 by stephane.ducasse: Migrating MethodReference to MethodReferenceWithSource http://code.google.com/p/pharo/issues/detail?id=3224 finalllllly in 12303

Jan. 13, 2011

[Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by Mariano Martinez Peck

On Thu, Jan 13, 2011 at 9:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > 12302 > ----- > > - GLMOrangeUITheme. Thanks Igor Stasenko > I don't agree with this kind of changes. Tomorrow I want Watery2BlackTheme and GLMYellowUITHeme and what? we are going to integrate it also? I don't understand. The change should be to create a setting to set the color and then igor runs a script in his own image that set it to orange. Me to yellow. And you to pink. > > - Issue 3538: Add a "Browse test" in the TestRunner failed/error list. > Thanks Benjamin van Ryseghem > > Stef >

Jan. 13, 2011

Re: [Pharo-project] Issue 3530 in pharo: New pass on RML + new tool for inspecting Senders

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3530 by stephane.ducasse: New pass on RML + new tool for inspecting Senders http://code.google.com/p/pharo/issues/detail?id=3530 12301

Jan. 13, 2011

[Pharo-project] [update 1.2] #12302

by StÃ©phane Ducasse

12302 ----- - GLMOrangeUITheme. Thanks Igor Stasenko - Issue 3538: Add a "Browse test" in the TestRunner failed/error list. Thanks Benjamin van Ryseghem Stef

Jan. 13, 2011

Re: [Pharo-project] Issue 3538 in pharo: Add a "Browse test" in the TestRunner failed/error list

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3538 by stephane.ducasse: Add a "Browse test" in the TestRunner failed/error list http://code.google.com/p/pharo/issues/detail?id=3538 in 12302 Thanks ben this is cool

Jan. 13, 2011

Re: [Pharo-project] Issue 3538 in pharo: Add a "Browse test" in the TestRunner failed/error list

by pharo＠googlecode.com

Comment #2 on issue 3538 by stephane.ducasse: Add a "Browse test" in the TestRunner failed/error list http://code.google.com/p/pharo/issues/detail?id=3538 in 12302 Thanks ben this is cool

Jan. 13, 2011

Re: [Pharo-project] Changes for PharoDev

by StÃ©phane Ducasse

> Hi. Today, we have a good way to manage packages/projects (Metacello) and a good way to automatically build images (Hudson). > > Several months ago, I suggested to remove the PharoWeb image for several reasons (I won't mention them here, check in the mailing list). > > People have different ideas of what to put in dev images and we cannot all agree. So, I won't say anything new, but just suggest something: > > Pharo1.2 is beta and it is almost there. We shouldn't change it that much before the release. So, I would include in the Pharo1.2 image what we were including more or less in Pharo1.1. > > The dev image is being built using ConfigurationOfPharo. This conf, has defined different groups, included the 'Dev' group which us used for building the dev image. Now, what about adding to ConfugurationOfPharo, much more projects, and creating groups for them. Then, with Hudson we can REALLY EASY build another image, but not with the 'Dev' group, but with 'Web' for example. Web is just an example, but we can put as much as we want. > > I would create a PharoWeb which can contain ALL seaside related stuff (core, addons, pier, margitte, blah). We can use ConfigurationOfSeaside. The same for Aida. We can also add WebClient, Zn, seaside testing, or whatever web related you want. Not you mariano. Somebody that needs the web stuff. To make sure that the system works people should have the energy to maintain a config. Fix the conflicts.... > Then we can create a PharoExtras, where we can put (in addition to pharoDev) what it is now in PharoNonCore, plus MemoryMonitor, XMLSupport, Mocker, AutoTest, KeyBindings, etc etc etc. Things that are not "dev tools" but that they are working in pharo and that would be welcome for newcomers. Keybinding should probably be evaluated and part of it deeply integrated in the system > Last comment is that it would be nice if all this can be done using the new symbolicVersions of the new Metacello version. Yes > > what do you think ? What I said before. Let us focus on the infrastructure so that other people can join and maintain their own assets. > cheers > > mariano > > ps: if you like it, we need help to update ConfigurationOfPharo and probably all its referenced confs (to use the stale symbolic version) Exactly :)

Jan. 13, 2011