- Pharo-dev - lists.pharo.org

Re: [Pharo-project] What happened to demo mode?

by laurent laffont

Added: http://book.pharo-project.org/book/CustomizingPharo/DemoMode Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ On Sun, Oct 24, 2010 at 10:10 AM, Jorge Ressia <jorge.ressia(a)gmail.com>wrote: > Hi Oscar, > > I found this explanation from Alain, > > in Pharo 1.0 > Preferences setDemoFonts > > in Pharo 1.1 > from the setting browser, > style button (top button bar) then load item then you choose demo mode. > or > DemoSettingStyle new load > > The steps for Pharo 1.1 work well for the latest image. > > Cheers, > > On Sun, Oct 24, 2010 at 9:51 AM, Oscar Nierstrasz > <oscar.nierstrasz(a)gmail.com> wrote: > > > > > > There used to be a fast way to set LARGE FONTS for showing a demo with > Pharo. Is that hidden away somewhere now? > > > > I can only find individual settings for the fonts in multiple places. > > > > Demo mode is really, *really* important! Please put it back if it is > missing, and make it really easy to find! > > > > - on > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Jorge Ressia > www.jorgeressia.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 24, 2010

Re: [Pharo-project] What happened to demo mode?

by Jorge Ressia

Hi Oscar, I found this explanation from Alain, in Pharo 1.0 Preferences setDemoFonts in Pharo 1.1 from the setting browser, style button (top button bar) then load item then you choose demo mode. or DemoSettingStyle new load The steps for Pharo 1.1 work well for the latest image. Cheers, On Sun, Oct 24, 2010 at 9:51 AM, Oscar Nierstrasz <oscar.nierstrasz(a)gmail.com> wrote: > > > There used to be a fast way to set LARGE FONTS for showing a demo with Pharo. Â Is that hidden away somewhere now? > > I can only find individual settings for the fonts in multiple places. > > Demo mode is really, *really* important! Â Please put it back if it is missing, and make it really easy to find! > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Jorge Ressia www.jorgeressia.com

Oct. 24, 2010

Re: [Pharo-project] "ProfStef" vs "Pharo Tutorial"

by laurent laffont

On Tue, Oct 19, 2010 at 4:35 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi! > > Hi. Sorry for late response I have troubles to do all that I want these times :) > Some student asked me for a tutorial about Pharo, I guess they haven't seen > ProfStef. Maybe Having "Pharo Tutorial" in the Help menu would be more > explicit. > Indeed I would like to remove ProfStef Browser for Pharo 1.2 as we can browse the tutorials in HelpSystem (See last ConfigurationOfProfStef). Then I can replace "ProfStef" menu entry by "Pharo Tutorial" to evaluate "ProfStef go" in 1.2 Cheers, Laurent > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 24, 2010

[Pharo-project] What happened to demo mode?

by Oscar Nierstrasz

There used to be a fast way to set LARGE FONTS for showing a demo with Pharo. Is that hidden away somewhere now? I can only find individual settings for the fonts in multiple places. Demo mode is really, *really* important! Please put it back if it is missing, and make it really easy to find! - on

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by Tudor Girba

Hi Johan, I would definitely be interested in getting this as an external library around Mondrian and Moose. Cheers, Doru On 24 Oct 2010, at 07:09, Johan Fabry wrote: > If you instantiate a color but dont see it, does it matter that the color is not what you wanted? It's like considering the classical 'tree falls in the forest' question. > > Or if you prefer a more implementation-based view: if a morph cannot be drawn, do you halt the system? Right now it is not the case, a rectangle with a cross is drawn. > > In any case, I am open to suggestions for improvement! > > On 23 Oct 2010, at 18:46, Schwab,Wilhelm K wrote: > >> I don't like the idea of instantiating red if the name is not recognized. Since you don't have selectors (900+ might be a bit much), the compiler/Shout won't catch mistakes, and it will be an ongoing source of silent failures. >> >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Johan Fabry [jfabry(a)dcc.uchile.cl] >> Sent: Saturday, October 23, 2010 5:29 PM >> To: Pharo Development >> Subject: [Pharo-project] Proposal: adding 261 named colors >> >> Hi all, >> >> in the work of AspectMaps I was a bit let down by the named colors Pharo provides (Color red et cetera). Now I am happy to say that thanks to the XKCD color survey I was able to improve on this. I can now use 261 named colors thanks to a XKCDColor class, and I'd like to share the code, ideally to be included into Pharo. The code is available in bugreport http://code.google.com/p/pharo/issues/detail?id=3148 >> >> Here is the class comment fo XKCDColor: >> >> ---snip--- >> A color named according to the XKCD color survey, as published in http://blog.xkcd.com/2010/05/03/color-survey-results/ ("Over five million colors were named across 222,500 user sessions.") >> >> Of the full table of 954 colors that is published only those were selected that did not have a space in their name, ignoring e.g. electric lime, nasty green, macaroni and cheese, pinkish tan, but also light light blue, strong blue. This results in a table of 261 named colors, but with duplicates such as ochre and ocre. These were left in since as they are common misspellings it is more convenient for the user. >> >> To instantiate: XCDColor named: aString where aString is one of the 261 named colors. If the name is not known, the color red is instantiated. Instances of XKCDColor know their XKCD color name, returned by the name accessor. >> >> Thanks to Randall Monroe of http://xkcd.com for providing the data. >> ---snip--- >> >> And here is a picture of all the colors (Generated with Mondrian :-) ) >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > > _______________________________________________ > 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."

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by StÃ©phane Ducasse

ok I read the code :) I like 'swamp' Stef On Oct 23, 2010, at 11:30 PM, Johan Fabry wrote: > Hi all, > > in the work of AspectMaps I was a bit let down by the named colors Pharo provides (Color red et cetera). Now I am happy to say that thanks to the XKCD color survey I was able to improve on this. I can now use 261 named colors thanks to a XKCDColor class, and I'd like to share the code, ideally to be included into Pharo. The code is available in bugreport http://code.google.com/p/pharo/issues/detail?id=3148 > > Here is the class comment fo XKCDColor: > > ---snip--- > A color named according to the XKCD color survey, as published in http://blog.xkcd.com/2010/05/03/color-survey-results/ ("Over five million colors were named across 222,500 user sessions.") > > Of the full table of 954 colors that is published only those were selected that did not have a space in their name, ignoring e.g. electric lime, nasty green, macaroni and cheese, pinkish tan, but also light light blue, strong blue. This results in a table of 261 named colors, but with duplicates such as ochre and ocre. These were left in since as they are common misspellings it is more convenient for the user. > > To instantiate: XCDColor named: aString where aString is one of the 261 named colors. If the name is not known, the color red is instantiated. Instances of XKCDColor know their XKCD color name, returned by the name accessor. > > Thanks to Randall Monroe of http://xkcd.com for providing the data. > ---snip--- > > And here is a picture of all the colors (Generated with Mondrian :-) ) > > <Colors.png> > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by StÃ©phane Ducasse

johan what is the principle? There was a package on squeaksource or squeak map that adds a lot 512 or so color names. Stef

Oct. 24, 2010

Re: [Pharo-project] Smells looking at collections

by StÃ©phane Ducasse

>>> > Not trivial? Maybe not, but only a little bit harder than trivial. We are open to suggestions believe me :) > >> 2) well, this is difficult to get the money for the butter and the butter - we are trying. > > If you can compose classes the way you can add a trait to a class now with class and optional method level instance+class variable mapping, then you're done. It would be a lot simpler to use it _and_ it would also be a lot easier to implement it. Especially the tools part. I'm interested to hear more about that. Tell us more. The problem we faced was - offset access = you cannot reuse bytecode of a trait because the order of the offset can be different in each trait users - initialization of instances variables at the trait level and the composition at the class levele > >> 3) again if nobody does anything and we just all cry on ourselves then nothing will happen. > > Tools are a must. No tools - no users. Exact. >> So for now identifying traits and learning is the way. Then we can refactor, redesign > > Well, Traits are in Squeak since 2006, IIRC they were available a few years earlier. So in the last X (at least 4) years the only good candidate to become a Trait was Magnitude. Come on. I will not answer to such statement because I'm positive thinking. Stef

Oct. 24, 2010

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests

by StÃ©phane Ducasse

Lack of maintainers, too many unwanted features, lack of explanation, large changes... And this is not that several persons did not look at the code. It got more than the average. Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no real improvements. Stef On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: > Sad to hear that. > > Technical difficulties, or just lack of customers? ^^ > > --AA > > On Oct 23, 2010, at 08:05 , StÃ©phane Ducasse wrote: > >> It was too difficult to integrate. >> >> Stef >> >> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >> >>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>> >>> Niko >>> >>> On Wed, Feb 3, 2010 at 1:13 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> this loads well in the latest 1,1 core :) >>>> so now we should really have a look and these cool changes >>>> >>>> Stef >>>> >>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>> >>>>> SystemChangeNotifier uniqueInstance >>>>> noMoreNotificationsFor: TestCase. >>>>> Gofer it >>>>> disablePackageCache; >>>>> squeaksource: 'akuhn'; >>>>> package: 'SUnit'; >>>>> package: 'SUnitGUI'; >>>>> load. >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> http://scg.unibe.ch/staff/Schwarz >>> twitter.com/nes1983 >>> Tel: +41 076 235 8683 >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Oct. 24, 2010

Re: [Pharo-project] Proposal: adding 261 named colors

by Johan Fabry

If you instantiate a color but dont see it, does it matter that the color is not what you wanted? It's like considering the classical 'tree falls in the forest' question. Or if you prefer a more implementation-based view: if a morph cannot be drawn, do you halt the system? Right now it is not the case, a rectangle with a cross is drawn. In any case, I am open to suggestions for improvement! On 23 Oct 2010, at 18:46, Schwab,Wilhelm K wrote: > I don't like the idea of instantiating red if the name is not recognized. Since you don't have selectors (900+ might be a bit much), the compiler/Shout won't catch mistakes, and it will be an ongoing source of silent failures. > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Johan Fabry [jfabry(a)dcc.uchile.cl] > Sent: Saturday, October 23, 2010 5:29 PM > To: Pharo Development > Subject: [Pharo-project] Proposal: adding 261 named colors > > Hi all, > > in the work of AspectMaps I was a bit let down by the named colors Pharo provides (Color red et cetera). Now I am happy to say that thanks to the XKCD color survey I was able to improve on this. I can now use 261 named colors thanks to a XKCDColor class, and I'd like to share the code, ideally to be included into Pharo. The code is available in bugreport http://code.google.com/p/pharo/issues/detail?id=3148 > > Here is the class comment fo XKCDColor: > > ---snip--- > A color named according to the XKCD color survey, as published in http://blog.xkcd.com/2010/05/03/color-survey-results/ ("Over five million colors were named across 222,500 user sessions.") > > Of the full table of 954 colors that is published only those were selected that did not have a space in their name, ignoring e.g. electric lime, nasty green, macaroni and cheese, pinkish tan, but also light light blue, strong blue. This results in a table of 261 named colors, but with duplicates such as ochre and ocre. These were left in since as they are common misspellings it is more convenient for the user. > > To instantiate: XCDColor named: aString where aString is one of the 261 named colors. If the name is not known, the color red is instantiated. Instances of XKCDColor know their XKCD color name, returned by the name accessor. > > Thanks to Randall Monroe of http://xkcd.com for providing the data. > ---snip--- > > And here is a picture of all the colors (Generated with Mondrian :-) ) > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Oct. 24, 2010