- Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] todo after 1.0 is released

by StÃ©phane Ducasse

Yes http://code.google.com/p/pharo/issues/detail?id=2282 On Apr 7, 2010, at 3:17 PM, Adrian Lienhard wrote: > Usually I put the 1.1 tag on items I integrated in 1.0 and I didn't close the issues so they are not lost. The only one I remember that we may also want to integrate is the network rollback. Not sure what the plan is there. But it doesn't seem anybody is working on a better implementation so I suggest we also roll back in 1.1. > > Adrian > > On Apr 7, 2010, at 14:20 , Mariano Martinez Peck wrote: > >> On Wed, Apr 7, 2010 at 1:07 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr>wrote: >> >>> Hi Adrian >>> >>> Once 1.0 is released we should check that all the fixes that went in 1.0 >>> after the fork to 1.1 are integrated in 1.1. >>> >> >> The problem is how we can identify them ? >> I only remember >> http://code.google.com/p/pharo/issues/detail?id=1841 >> but it even is different in 1.1 >> >> Ahh maybe also the NetNameResolver problem ? >> >> >>> Would be nice also to remove the testsexpected to break so that we give >>> them a chance to be fixed in 1.1. >>> >>> >> Good idea. >> >> >>> 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 > > > _______________________________________________ > 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] Show Actions of a SystemWindow: bug?

by StÃ©phane Ducasse

add a bug entry :) On Apr 7, 2010, at 3:11 PM, Mariano Martinez Peck wrote: > > > 2010/4/6 Carla F. Griggio <carla.griggio(a)gmail.com> > Hello! > > I was fooling around with the latest rc3 image and I tried to use the "show actions" option in the menu of a SystemWindow and got this: > > MessageNotUnderstood: ToolSet class>>openMessageList:name:autoSelect: > ToolSet class(Object)>>doesNotUnderstand: #openMessageList:name:autoSelect: > SystemWindow(Morph)>>showActions > [] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > BlockClosure>>ensure: > CursorWithMask(Cursor)>>showWhile: > ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: > ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: > MouseButtonEvent>>sentTo: > ... > > This is the code in SystemWindow>>showActions: > > > Actually, it is Morph >> showActions ;) > > > > > ToolSet openMessageList: list name: 'Actions of ' , self printString autoSelect: false > > Shouldn't the last line be MessageSet openMessageList: list name: 'Actions of ' , self printString autoSelect: nil ? I tried it and it seemed to work OK, although I never tried that option before so I don't know what was it's original behaviour. > > > > I think your change is correct and it works. > It is funny it is almost the first time in my life I do a ctrl + click hahaha I saw that menu one or two times in my life :) > > Even more, I checked and it is broken since, at least, Squeak 3.9 haha > > So..Carla, can you open a bug ticket and submit the fix ? > > http://www.pharo-project.org/community/issue-tracking > > Thanks and good catch! > > Mariano > > > Cheers! > Carla. > > _______________________________________________ > 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] Redline Smalltalk

by StÃ©phane Ducasse

the one of potataoe and the code that we can find on Jsqueak web site. I imagine that they are not the same. On Apr 7, 2010, at 3:37 PM, Michael Haupt wrote: > Hi, > > On Wed, Apr 7, 2010 at 9:04 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >>> Potato is JSqueak. I don't get it. >> >> I know :) >> Now having two different repositories with not synchronized code is not really good. > > which two repositories? > > Best, > > Michael > > _______________________________________________ > 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] [For Testing] RC3 One-Click

by StÃ©phane Ducasse

good! Stef On Apr 7, 2010, at 3:39 PM, Mariano Martinez Peck wrote: > I agree with you Torsten. And thanks for the very fast upload :) > > 2010/4/7 Torsten Bergmann <astares(a)gmx.de> > >- splash.bmp says release candidate 2. It should be release stable 1.0 or RC3. > > Use the attached one. > > >This comes from the vm package. I personally honestly don't understand > >spash-screens. Is windows so slow in loading an image file? > > There is no reason to have one to fill load time since this is fast > as on any other platform. It is more or less a short intro screen to > display version info and show the logo. It is very common to provide > one and often you can already guess the version from the style of > the splash without reading the provided version info. > > As a developer you would ask "why" - wearing a marketing hat you > should say "absolutely necessary". > > Smalltalk should not only evolve in programming features but also > learn some marketing/branding so people will remember it. > > Read the german entry on Wikipedia for more infos: > [1] http://de.wikipedia.org/wiki/Splash_Screen > > Another bonus is that if one takes the one-click to develop a > commercial application he just has to replace the splash with > a custom one. > > If you dislike it, then just delete/rename the splash.bmp after > unzipping the one click and you are done. > > Bye > T. > > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > 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