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

Re: [Pharo-project] Issue 2279: [BUG]MultiByteFileStream(Object)>>error: on changes file throwing ***System Error Handling Failed*** running test coverage

by Mariano Martinez Peck

On Tue, Apr 6, 2010 at 11:27 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > This could be a problem with the coverage analysis. You have to be > extra careful with coverage analysis on system classes like > collections and filestreams, because they are used everywhere. > > In such case, should we add them to TestRunner >> promptForPackages or similar ? Cheers MAriano > Lukas > > On Tuesday, April 6, 2010, Stan Shepherd <stan.shepherd414(a)gmail.com> > wrote: > > > > VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: > > #10074] > > Image: Pharo-1.0-10517-rc4 [Latest update: #10517] > > > > Steps to reproduce: > > 1.In TestRunner, select Tests-Traits , TestTraits > > 2.Select Run Coverage button. > > 3.In dialog, select Files > > > > > > stack trace attached ** to issue ** > > http://code.google.com/p/pharo/issues/detail?id=2279 > > -- > > View this message in context: > http://n4.nabble.com/Issue-2279-BUG-MultiByteFileStream-Object-error-on-cha… > > 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 > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > 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 Tudor Girba

In Moose we use mainly: Type-Engineering = (Re)engineering the code base to enhance its quality Type-Defect = Report of a software defect Type-Enhancement = Request for enhancement and from time to time: Type-Project = Long-term project or autonomous task Type-Review = Request for a code review Type-Other = Some other kind of issue Cheers, Doru On 7 Apr 2010, at 16:30, 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). > > 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 > > > _______________________________________________ > 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 "Sometimes the best solution is not the best solution."

April 7, 2010

Re: [Pharo-project] Menu navigation

by Mariano Martinez Peck

Hi Sean: As far as I understand, part of the new improvements of the Pharo 1.1 architecture will make this kind of things easier: 1) We completely removed Preferences class. It was a mess and with million of dependencies, difficult to extend, etc. Now, in Pharo 1.1 we have a new Setting framework where each package can define using metadata (pragmas) their own settings. Then, this Setting framework will scan the pragmas and build the Setting browser according to that. 2) We changed the way the menu registration works. Now it is easier to change the menu, without needing to hack inside the core code. I think it is also done using pragmas. For both incredible works, you have to thanks Alain :) Cheers Mariano On Wed, Apr 7, 2010 at 4:44 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > > StÃ©phane Ducasse wrote: > > > > Now sean as mariano mentioned it if some behavior are really used all > time > > then we will change to > > make them easier to use. > > > > I appreciate that - my purpose was about the general flow of sub-menus, > rather than that specific one, which I used as an example (but which I > happen to use every time I open the image because, in full screen mode, > Pharo (and Squeak) opens on the primary display instead of the display it > was last used/saved on) > > > StÃ©phane Ducasse wrote: > > > > What you can also do is to define a Script to do it for you and to setup > > your image the exact way you want. > > > Cool, I'll try that. Is there a good place to look for info on how to do > that? > > > StÃ©phane Ducasse wrote: > > > > In 1.1 I would like to change the Code recovering subsub list. This is > too > > deep. > > I tried and broke it so I should retry. > > > > This part went right over my head :) > > Sean > -- > View this message in context: > http://n4.nabble.com/Menu-navigation-tp1754368p1754453.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

Re: [Pharo-project] Menu navigation

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > >> Maybe they could coexist, since clicking on a menu item with a submenu >> doesn't seem to do anything useful now? > > Yes this is probably a good suggestion. > But if we click on a menu with a submenu what should happen? > The menu on the right should slide and replace the current one. > I have the impression that may be the theme should be able to implement > thes two different > behavior separated. > I think the sliding behavior could be the best of both worlds. Now that I think about that, the current implementation is definitely superior for searching for unknown menu options - in Squeak, when you click on an item with a sub-menu, the original menu disappears, so you have to start over if it's not what you wanted. The behavior I'm suggesting seems to work better when you already know exactly where you're going. Sean -- View this message in context: http://n4.nabble.com/Menu-navigation-tp1754368p1754468.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 laurent laffont

Now on INRIAGForge server: https://gforge.inria.fr/frs/download.php/26793/squeak-3.11.3.2151-pharo-src… Laurent Laffont On Wed, Apr 7, 2010 at 12:37 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > laurent if you want register using the rmod team and let me know so that I > add you to the pharo project. > > stef > > On Apr 7, 2010, at 9:09 AM, laurent laffont wrote: > > > On Wed, Apr 7, 2010 at 9:07 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > thanks laurent > > > > Do you have an account in the inria gforge? > > > > No > > > > Laurent Laffont > > > > > > On Apr 7, 2010, at 8:34 AM, laurent laffont wrote: > > > > > 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 > > > _______________________________________________ > > > 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 > > > _______________________________________________ > 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 Michael Haupt

Hi StÃ©phane, On Wed, Apr 7, 2010 at 3:45 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > the one of potataoe and the code that we can find on Jsqueak web site. > I imagine that they are not the same. they are not. As far as I understood it, the code available from the JSqueak page is JSqueak as originally released by Dan, and is not further developed, while the Potato SourceForge page and repository represent ongoing (well, as far as it goes with the manpower available) development. Best, Michael

April 7, 2010

Re: [Pharo-project] Menu navigation

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > Now sean as mariano mentioned it if some behavior are really used all time > then we will change to > make them easier to use. > I appreciate that - my purpose was about the general flow of sub-menus, rather than that specific one, which I used as an example (but which I happen to use every time I open the image because, in full screen mode, Pharo (and Squeak) opens on the primary display instead of the display it was last used/saved on) StÃ©phane Ducasse wrote: > > What you can also do is to define a Script to do it for you and to setup > your image the exact way you want. > Cool, I'll try that. Is there a good place to look for info on how to do that? StÃ©phane Ducasse wrote: > > In 1.1 I would like to change the Code recovering subsub list. This is too > deep. > I tried and broke it so I should retry. > This part went right over my head :) Sean -- View this message in context: http://n4.nabble.com/Menu-navigation-tp1754368p1754453.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 7, 2010

Re: [Pharo-project] Menu navigation

by StÃ©phane Ducasse

> > 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. ok I see what you mean > Maybe they could coexist, since clicking on a menu item with a submenu > doesn't seem to do anything useful now? Yes this is probably a good suggestion. But if we click on a menu with a submenu what should happen? The menu on the right should slide and replace the current one. I have the impression that may be the theme should be able to implement thes two different behavior separated. > -- > View this message in context: http://n4.nabble.com/Menu-navigation-tp1754368p1754402.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 Torsten Bergmann

Stef wrote >Because I would like to change the default color of comments. >Green is really ugly for the release. Please no! This is subject to personal taste. In most text editors and IDE's I know the comments are always green by default independent from language. So I would keep it since this is what is common in developer tools. If you want you can have your own. So shout is already what most users may expect. Please keep it. See C/C++ Eclipse http://img.brothersoft.com/screenshots/softimage/e/eclipse_ide_for_c-c++_de… C/C++ VStudio http://www.lisisoft.com/imglisi/4/OptimizeUtilities/51119text-editor-pro-sc… PHP Antechius http://www.lisisoft.com/imglisi/7/HelpfileTools/37086phpedscreen.jpg JavaScript http://assets.devx.com/articlefigs/19100.png Java Eclipse http://www.oio.de/public/opensource/eclipse/eclipse_editor.jpg C# Eclipse http://emonic.sourceforge.net/html/CSharpEditorWithCompletion.jpg VB SharpDevelop http://www.borncity.de/Net/Img/SharpDevelop.jpg ... Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

April 7, 2010

Re: [Pharo-project] Menu navigation

by StÃ©phane Ducasse

in 1.1 this is even more complex :) because you have to use the default setting browser. Now sean as mariano mentioned it if some behavior are really used all time then we will change to make them easier to use. What you can also do is to define a Script to do it for you and to setup your image the exact way you want. In 1.1 I would like to change the Code recovering subsub list. This is too deep. I tried and broke it so I should retry. Stef On Apr 7, 2010, at 3:56 PM, Sean P. DeNigris 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 > > 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. > > _______________________________________________ > 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