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

Re: [Pharo-project] who is maintaining shout?

by Lukas Renggli

> Because I would like to change the default color of comments. > Green is really ugly for the release. This is my color scheme I am using since 1992 when I first programmed in BASIC and Pascal. I don't know why people use my own personal fork of the code? Looks like Shout has no official maintainer. Lukas -- Lukas Renggli www.lukas-renggli.ch

April 7, 2010

Re: [Pharo-project] How to manage todo?

by StÃ©phane Ducasse

> I propose that we use >> >> Type-Task or Type-ToDo for the management of some items that are not directly bug. >> Marcus? adrian? is it ok for you? > > As a frist step good. I personally would like to destinguish bugs from feature requests. Bugs > are bad and I want as little as possible. Feature request are good and I want as many as possible... > > Another aspect is: Bugs I feel kind of responsible to fix. Feature request I say: If this is really important, > someone will do it. (someone not me). Ok I like this distinction. I will recategorise. I added some TODO items (like going to the prefecture) Stef > > 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

April 7, 2010

Re: [Pharo-project] How to manage todo?

by Adrian Lienhard

On Apr 7, 2010, at 15:50 , StÃ©phane Ducasse wrote: > I propose that we use > > Type-Task or Type-ToDo for the management of some items that are not directly bug. > Marcus? adrian? is it ok for you? yes, looks good Adrian > Stef > > On Apr 7, 2010, at 3:38 PM, StÃ©phane Ducasse wrote: > >> Hi guys >> >> We have bug entries and now I have one question. >> Do we want to mix or not todo within them? >> I deleted all the old tasks from the inria web site. >> Now we could use it. >> >> Do you have experience managing todo (which may be orthogonal to issue and bug trcking)? >> >> Stef >> _______________________________________________ >> 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

April 7, 2010

Re: [Pharo-project] Menu navigation

by Sean P. DeNigris

Mariano Martinez Peck wrote: > > I would be more detailed. Why don't you say the menu labels instead of > move > xxx ? > >> What is the advantage of this way? > > I have no idea. What I do am aware of is that we want clean and short > menus > for Pharo. Having looong list menus is unconfortable to work with. How > frequently do you use that option ? how many people use that ? > I put the user movements to emphasize the greater amount and variety of effort required (not thinking of readers reproducing the steps :( ). System -> Preferences... -> Full screen on My point, which you clarified for me, is more that the way submenus appear in Squeak seems to flow better i.e. when you want to open a submenu, you click on it and it replaces the outer menu in the same place vertically so you can just continue to move down, as opposed to hovering, moving to the right (which breaks the 'moving down' flow, and navigating the submenu. Maybe they could coexist, since clicking on a menu item with a submenu doesn't seem to do anything useful now? -- View this message in context: http://n4.nabble.com/Menu-navigation-tp1754368p1754402.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 7, 2010

Re: [Pharo-project] How to manage todo?

by Marcus Denker

On Apr 7, 2010, at 3:50 PM, StÃ©phane Ducasse wrote: > I propose that we use > > Type-Task or Type-ToDo for the management of some items that are not directly bug. > Marcus? adrian? is it ok for you? As a frist step good. I personally would like to destinguish bugs from feature requests. Bugs are bad and I want as little as possible. Feature request are good and I want as many as possible... Another aspect is: Bugs I feel kind of responsible to fix. Feature request I say: If this is really important, someone will do it. (someone not me). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 7, 2010

Re: [Pharo-project] Menu navigation

by Mariano Martinez Peck

On Wed, Apr 7, 2010 at 3:56 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > It seems that the world menu navigation is not as usable as that of Squeak. > > For example, to go to full screen mode: > Squeak: click -> move down -> click -> move down -> click > Pharo: click -> move down -> move right -> click -> move down -> click > > I would be more detailed. Why don't you say the menu labels instead of move xxx ? I have ever seen full screen. > What is the advantage of this way? > > I have no idea. What I do am aware of is that we want clean and short menus for Pharo. Having looong list menus is unconfortable to work with. How frequently do you use that option ? how many people use that ? Cheers Mariano > Sean > -- > View this message in context: > http://n4.nabble.com/Menu-navigation-tp1754368p1754368.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 7, 2010

[Pharo-project] who is maintaining shout?

by StÃ©phane Ducasse

Because I would like to change the default color of comments. Green is really ugly for the release. Stef defaultStyleTable "color can be a valid argument to Color class>>colorFrom: , or nil to use the editor text color. Multiple emphases can be specified using an array e.g. #(bold italic). If emphasis is not specified, #normal will be used. if pixel height is not specified , then the editor font size will be used. " ^#( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default black ) (invalid red ) (excessCode red ) (comment (gray muchDarker) italic) (unfinishedComment (red muchDarker) italic) (#'$' (red muchDarker) ) (character (red muchDarker) ) (integer (red muchDarker) ) (number (red muchDarker) ) (#- (red muchDarker) ) (symbol (blue muchDarker) bold) (stringSymbol (blue muchDarker) bold) (literalArray (blue muchDarker) bold) (string (magenta muchDarker) normal) (unfinishedString red normal ) (assignment nil bold ) (ansiAssignment nil bold) (literal nil italic) (keyword (blue muchDarker) ) (binary (blue muchDarker) ) (unary (blue muchDarker) ) (incompleteKeyword (gray muchDarker) underlined) (incompleteBinary (gray muchDarker) underlined) (incompleteUnary (gray muchDarker) underlined) (undefinedKeyword red ) (undefinedBinary red ) (undefinedUnary red ) (patternKeyword nil bold) (patternBinary nil bold) (patternUnary nil bold) (#self (red muchDarker) bold) (#super (red muchDarker) bold) (#true (red muchDarker) bold) (#false (red muchDarker) bold) (#nil (red muchDarker) bold) (#thisContext (red muchDarker) bold) (#return (red muchDarker) bold) (patternArg (blue muchDarker) italic) (methodArg (blue muchDarker) italic) (blockPatternArg (blue muchDarker) italic) (blockArg (blue muchDarker) italic) (argument (blue muchDarker) italic) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 (green muchDarker) ) (rightParenthesis1 (green muchDarker) ) (leftParenthesis2 (magenta muchDarker) ) (rightParenthesis2 (magenta muchDarker) ) (leftParenthesis3 (red muchDarker) ) (rightParenthesis3 (red muchDarker) ) (leftParenthesis4 (green darker) ) (rightParenthesis4 (green darker) ) (leftParenthesis5 (orange darker) ) (rightParenthesis5 (orange darker) ) (leftParenthesis6 (magenta darker) ) (rightParenthesis6 (magenta darker) ) (leftParenthesis7 blue ) (rightParenthesis7 blue ) (blockStart black ) (blockEnd black ) (blockStart1 (green muchDarker) ) (blockEnd1 (green muchDarker) ) (blockStart2 (magenta muchDarker) ) (blockEnd2 (magenta muchDarker) ) (blockStart3 (red muchDarker) ) (blockEnd3 (red muchDarker) ) (blockStart4 (green darker) ) (blockEnd4 (green darker) ) (blockStart5 (orange darker) ) (blockEnd5 (orange darker) ) (blockStart6 (magenta darker) ) (blockEnd6 (magenta darker) ) (blockStart7 blue ) (blockEnd7 blue ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black bold ) (primitiveOrExternalCallEnd black bold ) (methodTempBar gray ) (blockTempBar gray ) (blockArgsBar gray ) (primitive (green muchDarker) bold) (pragmaKeyword (green muchDarker) bold) (pragmaUnary (green muchDarker) bold) (pragmaBinary (green muchDarker) bold) (externalFunctionCallingConvention (green muchDarker) bold) (module (green muchDarker) bold) (blockTempVar gray italic) (blockPatternTempVar gray italic) (instVar black bold) (workspaceVar black bold) (undefinedIdentifier red bold) (incompleteIdentifier (gray darker) (italic underlined)) (tempVar (gray darker) italic) (patternTempVar (gray darker) italic) (poolConstant (gray darker) italic) (classVar (gray darker) bold) (globalVar black bold) )

April 7, 2010

[Pharo-project] Menu navigation

by Sean P. DeNigris

It seems that the world menu navigation is not as usable as that of Squeak. For example, to go to full screen mode: Squeak: click -> move down -> click -> move down -> click Pharo: click -> move down -> move right -> click -> move down -> click What is the advantage of this way? Sean -- View this message in context: http://n4.nabble.com/Menu-navigation-tp1754368p1754368.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by Schwab,Wilhelm K

To anyone who might be struggling with this: I don't call Ubuntu 9.10 the Kranky Kangaroo for nothing =:0 The apt-get line kept prompting for a CD. After a couple of false starts, I found instructions to go to /etc/apt /sources.list and comment out the line referencing the cd. That _appears_ to have worked. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of laurent laffont Sent: Wednesday, April 07, 2010 1:34 AM To: An open mailing list to discuss any topics related to an open-source Smalltalk Subject: [Pharo-project] Linux Pharo VM on Pharo website Hi, I've prepared the following archive. It may replace the "Unix (3.11-3)" download link. http://lolgzs.free.fr/pharo/squeak-vm/squeak-3.11.3.2151-pharo-src.tar.gz In this archive: - patched squeak-vm rev. 2151. (The 2 patches are for FT2Plugin build and multiple options in CFLAGS to work. Patchs in archive). - awk gnuification - README with instructions to build and regenerate this source from VMMaker - All Pharo-1.0 tests green (on my machine ...) - it has been built/tested by several people in order to send me tinyBenchmark results :) The tinyBenchmarks are not as good as Exupery one, but this vary a lot depending on the CPU. Cheers, Laurent Laffont

April 7, 2010

Re: [Pharo-project] How to manage todo?

by StÃ©phane Ducasse

I propose that we use Type-Task or Type-ToDo for the management of some items that are not directly bug. Marcus? adrian? is it ok for you? Stef On Apr 7, 2010, at 3:38 PM, StÃ©phane Ducasse wrote: > Hi guys > > We have bug entries and now I have one question. > Do we want to mix or not todo within them? > I deleted all the old tasks from the inria web site. > Now we could use it. > > Do you have experience managing todo (which may be orthogonal to issue and bug trcking)? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 7, 2010