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

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Mariano Martinez Peck

On Tue, Jun 8, 2010 at 9:46 AM, Niko Schwarz <niko.schwarz(a)googlemail.com>wrote: > Of course not. Just switch the default download (the big one, all over > the site) site to 1.1. > > I just suggest to switch from 1.0 to 1.1 as stable at the same time > that we switch from 1.1 to 1.2 for development. I think this is a good idea. > Then we never have 3 > "current" versions at once. > > Cheers, > > Niko > > -- > 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 >

June 8, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by Denis Kudriashov

Excelent 2010/6/8 Niko Schwarz <niko.schwarz(a)googlemail.com> > We've further improved on the issue in > http://code.google.com/p/pharo/issues/detail?id=2469. > > It's committed to the inbox, now. > > Niko > > On Tue, May 25, 2010 at 10:34 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > thanks a lot denis for checking that. > > I should say thatI'm quite busy right now. :) > > > > Stef > > > > On May 25, 2010, at 7:05 PM, Denis Kudriashov wrote: > > > >> Ok, > >> > >> Eliot send some fix for code simulation in squeak list. > >> With it decompilation work good and my tests does not crach VM. But some > of tests failed (they like infinit loop) > >> > >> I attach Eliot fix. > >> > >> 2010/5/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> http://code.google.com/p/pharo/issues/detail?id=2469 > >> > >> > >> > >> Stef > >> > >> > >> On May 23, 2010, at 4:18 PM, Denis Kudriashov wrote: > >> > >> > I found more bad cases with code simulation. And I think any > manipulations with context (errors signals, simaphore, ...) not work in > simulation mode. Transcript printing failed because of simaphore accessing > (for thread safety) > >> > > >> > I create CodeSimulationTests (see attachement) with some tests which > not work and which crash VM. > >> > > >> > Maybe this tests not correct. But I hope it helps to indicate and > solve issues > >> > > >> > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> > Thanks! > >> > > >> > Stef > >> > > >> > On May 23, 2010, at 11:13 AM, Denis Kudriashov wrote: > >> > > >> > > And If you replace Transcript code with > >> > > > >> > > self halt. > >> > > > >> > > You will see that debugging with through button does not work. Code > simulation failure raised (but without VM crash) > >> > > > >> > > 2010/5/23 Denis Kudriashov <dionisiydk(a)gmail.com> > >> > > I has Pharo1.0 one click, Windows 7. > >> > > I attach class ClassWithTranscriptPrinting. > >> > > see class side method #debug > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> > > > >> > > Hi denis > >> > > > >> > > can you report clearly your bug > >> > > - image > >> > > - vm > >> > > - os > >> > > - scenario > >> > > > >> > > I could not compile > >> > > Transcript>>show:'something' > >> > > > >> > > so I do not know how you did it. > >> > > > >> > > > >> > > > >> > > On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: > >> > > > >> > > > Hello > >> > > > > >> > > > Just insert > >> > > > Transcript>>show:'something' > >> > > > at any method begin. > >> > > > > >> > > > Now debug sender of your method by debugger Through button. > >> > > > > >> > > > If no Transcript opened VM will crash! > >> > > > _______________________________________________ > >> > > > 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 > >> > > >> > > <CodeSimulationTests.st>_______________________________________________ > >> > 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 > >> > >> > <ContextPart-tryNamedPrimitiveInforwithArgs.st>_______________________________________________ > >> 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 > > > > > > -- > 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 >

June 8, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Niko Schwarz

Of course not. Just switch the default download (the big one, all over the site) site to 1.1. I just suggest to switch from 1.0 to 1.1 as stable at the same time that we switch from 1.1 to 1.2 for development. Then we never have 3 "current" versions at once. Cheers, Niko -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

June 8, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Schwab,Wilhelm K

Niko, Are you suggesting denying access to 1.0? IMHO, stable releases should be available "forever," though a couple of extra steps, such as going to an archive and hunting would be reasonable. If you are suggesting that we encourage the use of 1.1, then we need to do something like a second beta or at least an RC. I grabbed the most recent core and was quite impressed (can't live w/o shout though). The ConnectionQueue bug was marked as critical to 1.1. I agree that it needs to be fixed, and dropping the true return value as suggested might be the most direct approach. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Niko Schwarz [niko.schwarz(a)googlemail.com] Sent: Tuesday, June 08, 2010 4:28 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Three current versions: 1.0, 1.1, 1.2 I hear that we're working on 1.2 now. But pharo-project.org still hands out 1.0 versions to everyone who asks. So we'll get plenty of bug reports for 1.0. I think we should switch over to 1.1 on the home page soon. Niko -- 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

June 8, 2010

[Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Torsten Bergmann

>I hear that we're working on 1.2 now. But pharo-project.org still >hands out 1.0 versions to everyone who asks. So we'll get plenty of >bug reports for 1.0. > >I think we should switch over to 1.1 on the home page soon. Hi Nico, 1.0 is out 1.1. is in preparation for a release (only fixes are accepted now) if 1.1 will be released the page will change. New features (like the icon framework discussion) then go to 1.2. - there is no official closed 1.1 and therefore no prepared core for 1.2 yet. But packages can be prepared independently. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

June 8, 2010

Re: [Pharo-project] Three current versions: 1.0, 1.1, 1.2

by Marcus Denker

On Jun 8, 2010, at 10:28 AM, Niko Schwarz wrote: > I hear that we're working on 1.2 now. But pharo-project.org still > hands out 1.0 versions to everyone who asks. So we'll get plenty of > bug reports for 1.0. > > I think we should switch over to 1.1 on the home page soon. > 1.2 has not yet started. the idea is to do the 1.1 switch before... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 8, 2010

[Pharo-project] BrowserWindow title

by Denis Kudriashov

Hello, I just think that class name in BrowserWindow title is more appropriate then long browser name like "OB Package Browser: SomeClass". With little name task bar will be more suitable. What do you think?

June 8, 2010

Re: [Pharo-project] [BUG] VM crash during debbuging some code by Through button with Transcript>>show: in deepest inner methods

by Niko Schwarz

We've further improved on the issue in http://code.google.com/p/pharo/issues/detail?id=2469. It's committed to the inbox, now. Niko On Tue, May 25, 2010 at 10:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > thanks a lot denis for checking that. > I should say thatI'm quite busy right now. :) > > Stef > > On May 25, 2010, at 7:05 PM, Denis Kudriashov wrote: > >> Ok, >> >> Eliot send some fix for code simulation in squeak list. >> With it decompilation work good and my tests does not crach VM. But some of tests failed (they like infinit loop) >> >> I attach Eliot fix. >> >> 2010/5/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> http://code.google.com/p/pharo/issues/detail?id=2469 >> >> >> >> Stef >> >> >> On May 23, 2010, at 4:18 PM, Denis Kudriashov wrote: >> >> > I found more bad cases with code simulation. And I think any manipulations with context (errors signals, simaphore, ...) not work in simulation mode. Transcript printing failed because of simaphore accessing (for thread safety) >> > >> > I create CodeSimulationTests (see attachement) with some tests which not work and which crash VM. >> > >> > Maybe this tests not correct. But I hope it helps to indicate and solve issues >> > >> > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> > Thanks! >> > >> > Stef >> > >> > On May 23, 2010, at 11:13 AM, Denis Kudriashov wrote: >> > >> > > And If you replace Transcript code with >> > > >> > > self halt. >> > > >> > > You will see that debugging with through button does not work. Code simulation failure raised (but without VM crash) >> > > >> > > 2010/5/23 Denis Kudriashov <dionisiydk(a)gmail.com> >> > > I has Pharo1.0 one click, Windows 7. >> > > I attach class ClassWithTranscriptPrinting. >> > > see class side method #debug >> > > >> > > >> > > >> > > >> > > >> > > 2010/5/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> > > >> > > Hi denis >> > > >> > > can you report clearly your bug >> > > Â Â Â Â - image >> > > Â Â Â Â - vm >> > > Â Â Â Â - os >> > > Â Â Â Â - scenario >> > > >> > > I could not compile >> > > Â Â Â Â Transcript>>show:'something' >> > > >> > > so I do not know how you did it. >> > > >> > > >> > > >> > > On May 23, 2010, at 10:11 AM, Denis Kudriashov wrote: >> > > >> > > > Hello >> > > > >> > > > Just insert >> > > > Transcript>>show:'something' >> > > > at any method begin. >> > > > >> > > > Now debug sender of your method by debugger Through button. >> > > > >> > > > If no Transcript opened VM will crash! >> > > > _______________________________________________ >> > > > 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 >> > >> > <CodeSimulationTests.st>_______________________________________________ >> > 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 >> >> <ContextPart-tryNamedPrimitiveInforwithArgs.st>_______________________________________________ >> 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 > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

June 8, 2010

Re: [Pharo-project] Gaucho icons framework into Pharo1.1 ?

by Fernando olivero

On Jun 8, 2010, at 9:46 AM, Mariano Martinez Peck wrote: > > > On Tue, Jun 8, 2010 at 9:21 AM, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: > Hi Simon, the icons are the Oxygen family of icons from the GNOME project. > > I've made a icons framework importer , which loads an icon set into Pharo and creates a class for each icon set. > The idea is to have polymorphic classes of icons sets: > For example > > IconsFamilyBuilder>>build > | specs secs | > specs := self iconsSpecs . > specs do:[:each| each resourcesFolderName: self resourcesFolderName ]. > ^ GMIconFamily createFamilyNamed: self iconFamilyName specs: specs . > > Which has subclasses such as OxygenIconsBuilder, that creates GMIconFamilyOxygen. > The code is similar to that found in MenuIcons, but i've added the notion of icons sets. > > I would like to integrate it to Pharo1.1, so we should unify the MenuIcons and maybe the UIThemes methods found in the icons category, so we provide only one entry point for icons in the system, together with a simple importer and provider of icons. > > > Please don't. We need to freeze Pharo1.1. We are near to the release and only bug fixes should be integrated. > > But of course, this is more than welcome in Pharo 1.2 ;) > OK, i agree. I'll follow Alain guidelines for including the icons framework into Pharo1.2. > > Let me know what you think. > > > > Fernando > > > > > > > > > Who did the nice icons? > > > > > > -- > > Simon > > > > > > > > > > _______________________________________________ > > 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 > > <ATT00001..txt>

June 8, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by Fernando olivero

On Jun 8, 2010, at 10:07 AM, StÃ©phane Ducasse wrote: > > On Jun 8, 2010, at 9:28 AM, Fernando olivero wrote: > >> Hi Simon, >> >> On Jun 7, 2010, at 5:48 PM, Simon Denier wrote: >> >>> >>> OK two other things >>> >>> 1) (minor) I find myself repeatdly trying to extend a Shape size to display more instance variables and methods by looking for the resize handle in the bottom right corner >>> >> > > Fernando if you listen what simon is telling you is that he does not want to see the code in larger font. > he said that on his 30 inches screen he would like to see more method names at once. > Now looking at what your hand is doing is interesting: simon hand wanted to have a large number of methods > so he tried to grab the corner. > > In terms of UI assessment, one guru said that we can debug 50% of the problems by asking people to speak aloud when they try > an interface. So this is a cheap but really effective way of making progress. > >> We wanted to provide a concise and compact view of the shapes, due to the restrictions that the current Morphic is pixel based and not scalable, to take the most of the real estate of a pampas. Possibly once i migrate to a scalable and vectorized UI framework ( Morphic3 ?), resizing would be considered. > > You have a far easier solution if you want to let people work better. > Stef, i was not speaking of font resize, we used the scroller widget to reveal hidden attributes or methods, and not shape resizing, providing a compact view of the shapes for the reasons above expressed. Every shape is has a fixed dimension of 340p x 400px, because we wanted to avoid getting rid of real state quickly and not being able to attack this problem with the current Morphic. Even though i agree that the hand behaves differently, and this in direct conflict with the habits of Pharo users, there is no "resize" handle of visual cue in the bottom corner of the shapes ( at least for now , till the Morphic dependency is dropped). >> 2) when I want to edit a method, the shape takes the full screen and I can't see any other data. Why can't I edit the method in-place >>> >> >> This was a decision i took, based on the fact that this lets you focus on writing that method only, similar to what Ommwriter proposes. http://www.ommwriter.com/ > > Bad bad bad idea. > You never want to have a look at other code while programming. > For me this will be the reason 1 for not using gaucho. > Smalltalk is already bad because you have to open another browser but gaucho is a jail since you cannot even > look at something else. > Thats why we needed to release it! To get good feed back like this one! You are right, occluding other methods shapes behind the Code editor view is to restricting. I'll modify this behavior ASAP. > .... > if you want to run a real user experience feedback I can be a guinea pig > you can ask me to do some tasks and tape me. > > Stef Thanks Stef! I'll set up an experiment and will take your offer! Fernando

June 8, 2010