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

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

by Mariano Martinez Peck

On Wed, Apr 7, 2010 at 12:49 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Ok but this looks terrible. This is good like that we are sure that one day > a guy not knowing anything > will propose something mucccccch better. What ugly convention. And also > nobody ever worked with daltonian apparently > because green for comments means nothing. > > Anyway I'm happy not to use Shout when I code in core. Else this would be > first things I would have change. > Now may be Shout could be improve to not force the user to recompile a > method all the time. > So I will check if this is working and make sure that as a user I can > specify an array of spec and not been forced to dirty > a package all the time. > > Maybe add a new Setting for Shout for Pharo 1.1 ? > Stef > > On Apr 7, 2010, at 5:34 PM, Peter Hugosson-Miller wrote: > > > I absolutely agree with Torsten. Here's one I made myself for VaSt, and > I've been using it for 8 years now: > > > > <PehuTextEnhancer.png> > > > > Note (whatever you might think of all the other fonts and colours) that > the comments are green ;-) > > > > -- > > Cheers, > > Peter > > > > On Wed, Apr 7, 2010 at 4:39 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > 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 > > > > _______________________________________________ > > 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

[Pharo-project] Linux 3.11-3 vm and shared libraries

by Schwab,Wilhelm K

Hello all, I am trying to use the 3.11-3 vm to see if it fixes my double return value problem, and I cannot get it to load the library to do the test =:0 At this point, I am just guessing. Can someone who has been successful at it give me an example? What is the .so file named, how do you refer to it in #moduleName, where do you put the file relative to the vm? Bill

April 7, 2010

Re: [Pharo-project] Menu navigation

by StÃ©phane Ducasse

I know that people around me use Setup something.... so probably somebody will mention it to you. >> >> 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?

April 7, 2010

Re: [Pharo-project] Handle Close Event in Image - necessary for 1.0?

by Henrik Johansen

On Apr 7, 2010, at 12:38 25PM, StÃ©phane Ducasse wrote: > Thanks Henrik > this is something I understand. I will integrate that for 1.1 Yes, there's some new stuff there which won't work well if we ever move towards multi-window support, but the entire event-handling will have to be rewritten in that case anyways, so I didn't think too much of it. I'd say the first step in any case would be moving Event-object generation out of the HandMorph class... (did MVC make its own kind of events?) Probably a good idea to switch to something reacting to new events in the queue rather than polling it too, if we intend to ever switch the inputEventPollingFetcher for the actual InputEventFetcher some time in the future. Though, InputEventSensor installEventSensorFramework seems borken on Windows now (eventbuffer overflows with 4.0.2 VM ), and incredibly slow to signal semaphore (albeit not loosing any events anymore in 1.1) on a Mac 4.2.4 VM. On the 5.X series, it works like a dream though :D Cheers, Henry

April 7, 2010

Re: [Pharo-project] Redline Smalltalk

by StÃ©phane Ducasse

I know and this is why I mentioned to dan that it would be good to merge back because may be a poor guy will just reimplement exactly what the guy in potatoes already did long time ago. But at the end of the day I do not care because I know. I should stop to be altruist. Stef On Apr 7, 2010, at 4:45 PM, Michael Haupt wrote: > 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 > > _______________________________________________ > 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] who is maintaining shout?

by StÃ©phane Ducasse

Ok but this looks terrible. This is good like that we are sure that one day a guy not knowing anything will propose something mucccccch better. What ugly convention. And also nobody ever worked with daltonian apparently because green for comments means nothing. Anyway I'm happy not to use Shout when I code in core. Else this would be first things I would have change. Now may be Shout could be improve to not force the user to recompile a method all the time. So I will check if this is working and make sure that as a user I can specify an array of spec and not been forced to dirty a package all the time. Stef On Apr 7, 2010, at 5:34 PM, Peter Hugosson-Miller wrote: > I absolutely agree with Torsten. Here's one I made myself for VaSt, and I've been using it for 8 years now: > > <PehuTextEnhancer.png> > > Note (whatever you might think of all the other fonts and colours) that the comments are green ;-) > > -- > Cheers, > Peter > > On Wed, Apr 7, 2010 at 4:39 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > 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 > > _______________________________________________ > 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] who is maintaining shout?

by Schwab,Wilhelm K

I've pretty much grown to accept green for comments too. What I really want to see is a way to change the background color, though the current values should be the default. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Torsten Bergmann Sent: Wednesday, April 07, 2010 9:40 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] who is maintaining shout? 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 _______________________________________________ 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] Thanks for license agreement :)

by StÃ©phane Ducasse

Hi Justin and Yanni I checked my mailbox today and saw your license agreement. Thanks

April 7, 2010

Re: [Pharo-project] Bug or new feature in RB?

by Mariano Martinez Peck

On Wed, Apr 7, 2010 at 2:09 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > > So, my question is, shouldn't only apply the refactor to the initialize > > method of extended packages ONLY if that method is extended ? Because > > otherwise I think it is a bit dangerous. > > > > What do you think ? > > > > I attach screenshot also. > > I see no screenshot, but I can reproduce the problem. > Thanks Lukas. I forgot the screenshot...but I guess you already understood so it has no sense. > > The problem is that for some refactorings the refactoring engine needs > too look beyond the defined scope to be able to do something useful > (e.g. if a class is not contained in a scope but some methods, it > still needs some object that represents the class to enumerate the > methods). There are definitely issues when classes are not fully > contained within a scope, but I don't think that this is critical. > After all the changes are presented for review. > > Ok, thanks for the explanation and the consideration. I just wanted to be sure it was not an easy bug/fix. Cheers Mariano ps: did I already said that waiting 13 hours in a airport is boring ? Lukas > > -- > 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] who is maintaining shout?

by Peter Hugosson-Miller

I absolutely agree with Torsten. Here's one I made myself for VaSt, and I've been using it for 8 years now: [image: PehuTextEnhancer.png] Note (whatever you might think of all the other fonts and colours) that the comments are green ;-) -- Cheers, Peter On Wed, Apr 7, 2010 at 4:39 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > 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 > > _______________________________________________ > 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