December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Syntax highlighting changed in 10500?

by Mariano Martinez Peck

On Tue, Dec 15, 2009 at 12:06 AM, Alain Plantec <alain.plantec(a)free.fr>wrote: > Mariano Martinez Peck a Ã©crit : > > > > > > On Mon, Dec 14, 2009 at 10:22 PM, Simon Denier <Simon.Denier(a)inria.fr > > <mailto:Simon.Denier@inria.fr>> wrote: > > > > > > On 14 dÃ©c. 2009, at 19:50, Lukas Renggli wrote: > > > > > The syntax highlighting should be made a preference with our > > shiny new > > > preference framework. > > > > > > I don't want any other coloring, I am using that color scheme > > for over > > > 15 years now. > > > > > > Power to the people! > > > > Yep, let's do some preferences for that. How do we start? :) > > > > > > Maybe creating a issue and cc alain :) > Hello ! > > I guess we can do that > > when the core will not contain any Preferences reference > and my package comments reviewed > and the settings I've coded also documented > and a documentation written > I will be happy to help. :) > > hahahahhaha. It seems you have a lot of things to do Alain ;) I agree those tasks are more important than this. For now, we should have just create an issue so that not forget about it. Thank you very much for all what you are doing. It is very useful. > For now, the core still contains a lot of Preferences references :( > > Alain > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 15, 2009

Re: [Pharo-project] [Fwd: windowColorSpecification]

by Lukas Renggli

I like the colors too. I cannot work with the OS X theme where everything looks exactly the same. Also it would be cool if the transcript could be orange again. Lukas 2009/12/15 Bart Gauquie <bart.gauquie(a)gmail.com>: > I actually like it that the type of Â windows are having different colors. In > the bar at the bottom, I can quickly determine monticello browser, test > runner, package browser, method finder, just by checking the color. I vote > against throwing away the colors. > The default behaviour of the gray colors is absolutely more suitable than > the colored version. > Kind regards, > > Bart > > On Tue, Dec 15, 2009 at 1:58 PM, Marcus Denker <denker(a)acm.org> wrote: >> >> On Dec 15, 2009, at 1:53 PM, Alain Plantec wrote: >> >> > >> > >> > From: Alain Plantec <alain.plantec(a)univ-brest.fr> >> > Date: December 15, 2009 1:52:28 PM GMT+01:00 >> > To: Pharo-project(a)lists.gforge.inria.fr >> > Subject: windowColorSpecification >> > Reply-To: alain.plantec(a)univ-brest.fr >> > >> > >> > Hi all, >> > >> > For now, Pharo has kept the squeak color specification framework based >> > on the >> > WindowColorSpec class and on the dynamic discovery of window colors. >> > (it relies on the searching of all windowColorSpecification >> > implementors). >> > Do we want to keep that ? >> > I would vote for getting rid of it. >> >> Please remove it! I personally think that the only use of window-colors is >> to be able >> to tell windows appart quickly. (but even that I personally think is not >> worth having an >> ugly UI for). But than *changing* the window color is the last thing that >> anyone should >> be able to do! >> >> Â Â Â Â Marcus >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The important thing > is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - Albert > Einstein > Gravitation is not responsible for people falling in love. - Albert Einstein > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 15, 2009

[Pharo-project] [update 1.1] #11104

by Marcus Denker

11104 ----- Issue 1609: Preferences migration part10

Dec. 15, 2009

[Pharo-project] Fwd: Bounce action notification

by StÃ©phane Ducasse

Begin forwarded message: > From: mailman(a)gforge.inria.fr > Date: December 15, 2009 1:54:24 PM GMT+01:00 > To: pharo-project-owner(a)lists.gforge.inria.fr > Subject: Bounce action notification > > This is a Mailman mailing list bounce action notice: > > List: Pharo-project > Member: jeffrey(a)jeffestep.com > Action: Subscription disabled. > Reason: Excessive or fatal bounces. > > > > The triggering bounce notice is attached below. > > Questions? Contact the Mailman site administrator at > mailman(a)lists.gforge.inria.fr. > > From: Mail Delivery System <Mailer-Daemon(a)sol.ocssolutions.com> > Date: December 15, 2009 1:53:50 PM GMT+01:00 > To: pharo-project-bounces(a)lists.gforge.inria.fr > Subject: Mail delivery failed: returning message to sender > > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > jeffrey(a)jeffestep.com > This message has been rejected because it has > a potentially executable attachment "windowColorSpecification.eml" > This form of attachment has been used by > recent viruses or other malware. > If you meant to send this file then please > package it up as a zip file and resend it. > > ------ This is a copy of the message, including all the headers. ------ > > Return-path: <pharo-project-bounces(a)lists.gforge.inria.fr> > Received: from mail4-relais-sop.national.inria.fr ([192.134.164.105]:5762) > by sol.ocssolutions.com with esmtps (TLSv1:RC4-SHA:128) > (Exim 4.69) > (envelope-from <pharo-project-bounces(a)lists.gforge.inria.fr>) > id 1NKWuk-0007CS-8e > for jeffrey(a)jeffestep.com; Tue, 15 Dec 2009 12:53:50 +0000 > X-IronPort-AV: E=Sophos;i="4.47,400,1257116400"; > d="eml'208?scan'208,208";a="52141271" > Received: from gforge-bdd-prod.irisa.fr (HELO gforge-wpj-prod.irisa.fr) ([131.254.249.8]) > by mail4-relais-sop.national.inria.fr with ESMTP; 15 Dec 2009 13:53:49 +0100 > Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]) > by gforge-bdd-prod.gforge.inria.fr with esmtp (Exim 4.63) > (envelope-from <alain.plantec(a)free.fr>) id 1NKWuP-0004dm-B2 > for Pharo-project(a)lists.gforge.inria.fr; Tue, 15 Dec 2009 13:53:45 +0100 > X-IronPort-Anti-Spam-Filtered: true > X-IronPort-Anti-Spam-Result: Av4CAMAVJ0vUGyoGkWdsb2JhbACUIoRMglEBAQEBCQsKBxMDvAKEKwQ > X-IronPort-AV: E=Sophos;i="4.47,400,1257116400"; > d="eml'208?scan'208,208";a="39911020" > Received: from smtp6-g21.free.fr ([212.27.42.6]) > by mail3-smtp-sop.national.inria.fr with ESMTP; > 15 Dec 2009 13:53:36 +0100 > Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) > by smtp6-g21.free.fr (Postfix) with ESMTP id 559D1E0805A; > Tue, 15 Dec 2009 13:53:30 +0100 (CET) > Received: from [192.168.0.12] (bro29-1-82-245-181-73.fbx.proxad.net > [82.245.181.73]) > by smtp6-g21.free.fr (Postfix) with ESMTP id 2421BE08131; > Tue, 15 Dec 2009 13:53:28 +0100 (CET) > Message-ID: <4B2786C7.4070400(a)free.fr> > Date: Tue, 15 Dec 2009 13:53:27 +0100 > From: Alain Plantec <alain.plantec(a)free.fr> > User-Agent: Thunderbird 2.0.0.23 (X11/20090817) > MIME-Version: 1.0 > To: Pharo-project(a)lists.gforge.inria.fr > Content-Type: multipart/mixed; boundary="------------040606080405030205080709" > Subject: [Pharo-project] [Fwd: windowColorSpecification] > X-BeenThere: pharo-project(a)lists.gforge.inria.fr > X-Mailman-Version: 2.1.9 > Precedence: list > Reply-To: Pharo-project(a)lists.gforge.inria.fr, alain.plantec(a)free.fr > List-Id: <pharo-project.lists.gforge.inria.fr> > List-Unsubscribe: <http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project>, > <mailto:pharo-project-request@lists.gforge.inria.fr?subject=unsubscribe> > List-Archive: <http://lists.gforge.inria.fr/pipermail/pharo-project> > List-Post: <mailto:pharo-project@lists.gforge.inria.fr> > List-Help: <mailto:pharo-project-request@lists.gforge.inria.fr?subject=help> > List-Subscribe: <http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project>, > <mailto:pharo-project-request@lists.gforge.inria.fr?subject=subscribe> > Sender: pharo-project-bounces(a)lists.gforge.inria.fr > Errors-To: pharo-project-bounces(a)lists.gforge.inria.fr > X-Spam-Status: No, score=-6.6 > X-Spam-Score: -65 > X-Spam-Bar: ------ > X-Spam-Flag: NO > > This is a multi-part message in MIME format. > --------------040606080405030205080709 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > > > --------------040606080405030205080709 > Content-Type: message/rfc822; > name="windowColorSpecification.eml" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline; > filename="windowColorSpecification.eml" > > X-Account-Key: account2 > X-Mozilla-Keys: > Return-Path: <alain.plantec(a)univ-brest.fr> > Received: from murder ([unix socket]) > by cassis-gw.univ-brest.fr (Cyrus v2.3.11) with LMTPA; > Tue, 15 Dec 2009 13:52:39 +0100 > X-Sieve: CMU Sieve 2.3 > Received: from localhost (cassis-gw.univ-brest.fr [127.0.0.1]) > by cassis-gw.univ-brest.fr (Postfix) with ESMTP id 18226690DC1 > for <plantec(a)univ-brest.fr>; Tue, 15 Dec 2009 13:52:39 +0100 (CET) > X-Virus-Scanned: amavisd-new at univ-brest.fr > Received: from cassis-gw.univ-brest.fr ([127.0.0.1]) > by localhost (cassis-gw.univ-brest.fr [127.0.0.1]) (amavisd-new, port 10024) > with ESMTP id fPQ-PUprkL9Q for <plantec(a)univ-brest.fr>; > Tue, 15 Dec 2009 13:52:34 +0100 (CET) > Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) > by cassis-gw.univ-brest.fr (Postfix) with SMTP id 54C14690DC6 > for <alain.plantec(a)univ-brest.fr>; Tue, 15 Dec 2009 13:52:34 +0100 (CET) > Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) > by smtp6-g21.free.fr (Postfix) with ESMTP id C4E4BE0810D; > Tue, 15 Dec 2009 13:52:31 +0100 (CET) > Received: from [192.168.0.12] (bro29-1-82-245-181-73.fbx.proxad.net [82.245.181.73]) > by smtp6-g21.free.fr (Postfix) with ESMTP id CD384E0819A; > Tue, 15 Dec 2009 13:52:28 +0100 (CET) > Message-ID: <4B27868C.5090102(a)univ-brest.fr> > Date: Tue, 15 Dec 2009 13:52:28 +0100 > From: Alain Plantec <alain.plantec(a)univ-brest.fr> > Reply-To: alain.plantec(a)univ-brest.fr > Organization: UBO > User-Agent: Thunderbird 2.0.0.23 (X11/20090817) > MIME-Version: 1.0 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: windowColorSpecification > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > Hi all, > > For now, Pharo has kept the squeak color specification framework based > on the > WindowColorSpec class and on the dynamic discovery of window colors. > (it relies on the searching of all windowColorSpecification implementors). > Do we want to keep that ? > I would vote for getting rid of it. > What do you think ? > Thanks > > Alain > > > > > --------------040606080405030205080709 > Content-Type: text/plain; charset="us-ascii" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > --------------040606080405030205080709-- > > > >

Dec. 15, 2009

Re: [Pharo-project] Ugly disabled buttons

by Tim Mackinnon

> > On Dec 13, 2009, at 12:58 PM, Tudor Girba wrote: > >> I would also vote for dimming :) Of course fix the font problem, however I would vote more for sorting out the ugly buttons in the first place - they look very dated and clunky. I particularly like how when you maximise the browser the height of the buttons gets bigger (taking up more precious vertical space). I wish we had a combination of Tabs and some proper toolbar buttons to make it look more visually appealing. Tim >> > > Yes! > > I added a bug report: http://code.google.com/p/pharo/issues/detail?id=1604 > >> Cheers, >> Doru >> >> >> On 13 Dec 2009, at 12:55, Lukas Renggli wrote: >> >>> That's the fuzzy label of Polymorph. It sort of works with true-type >>> fonts, but makes the bitmap fonts unreadable. I don't like it in any >>> case, have never seen a user-interface using something like that. Why >>> not just dim the color? >>> >>> Lukas >>> >>> 2009/12/13 Adrian Lienhard <adi(a)netstyle.ch>: >>>> The disabled buttons look ugly with the new strike fonts. Does >>>> somebody know >>>> what the reason is and how to fix it? We cannot ship Pharo like >>>> this... >>>> >>>> Cheers, >>>> Adrian >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> http://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 >> >> -- >> www.tudorgirba.com >> >> "Speaking louder won't make the point worthier." >> >> >> _______________________________________________ >> 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

Dec. 15, 2009

Re: [Pharo-project] [Fwd: windowColorSpecification]

by Alain Plantec

Bart Gauquie a Ã©crit : > I actually like it that the type of windows are having different > colors. In the bar at the bottom, I can quickly determine monticello > browser, test runner, package browser, method finder, just by checking > the color. I vote against throwing away the colors. Hi Bart, But we can keep the colors, For UITheme that make use of them we can maybe simply use existing defaultColor message as an example. > > The default behaviour of the gray colors is absolutely more suitable > than the colored version. I'm confused :) Alain > > Kind regards, > > Bart > > On Tue, Dec 15, 2009 at 1:58 PM, Marcus Denker <denker(a)acm.org > <mailto:denker@acm.org>> wrote: > > > On Dec 15, 2009, at 1:53 PM, Alain Plantec wrote: > > > > > > > From: Alain Plantec <alain.plantec(a)univ-brest.fr > <mailto:alain.plantec@univ-brest.fr>> > > Date: December 15, 2009 1:52:28 PM GMT+01:00 > > To: Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > > Subject: windowColorSpecification > > Reply-To: alain.plantec(a)univ-brest.fr > <mailto:alain.plantec@univ-brest.fr> > > > > > > Hi all, > > > > For now, Pharo has kept the squeak color specification framework > based on the > > WindowColorSpec class and on the dynamic discovery of window colors. > > (it relies on the searching of all windowColorSpecification > implementors). > > Do we want to keep that ? > > I would vote for getting rid of it. > > Please remove it! I personally think that the only use of > window-colors is to be able > to tell windows appart quickly. (but even that I personally think > is not worth having an > ugly UI for). But than *changing* the window color is the last > thing that anyone should > be able to do! > > Marcus > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The important > thing is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - > Albert Einstein > Gravitation is not responsible for people falling in love. - Albert > Einstein > ------------------------------------------------------------------------ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 15, 2009

Re: [Pharo-project] ProjectLauncher readDocumentAtStartup

by Michael Roberts

I agree the current class is pretty poor. It has some odd conventions when viewed from a unix command line. I had to debug really hard just to find out how to exactly construct the path. However lets please fix the current bug, it is just a small regression. It will at least behave as it use to. Then let's write a new one. I will check out the fix tonight. thanks! Mike On Tue, Dec 15, 2009 at 11:45 AM, Michael Rueger <m.rueger(a)acm.org> wrote: > Alain Plantec wrote: >> StÃ©phane Ducasse a Ã©crit : >>> BTW projectLauncher is a really funny class to support reading in .st files.... >>> >> yes its cool but >> showSplash and splashURL and eToyAuthentificationServer inst vars are >> never used; >> SplashMorph class var is never used (so none of its vars are used). >> The name, ProjectLauncher isn't that good (no other idea though) >> So I would at least clean it up (remove unused variables). > > It is (or rather was) the launcher used for loading etoys projects in > the squeakland image. And more as a side effect it was able to load > scripts. Or the script loading was moved into the ProjectLauncher after > I added the launcher framework way back then ;-) > >> I would also maybe find another name for it and move it to another package. > > We should throw away the current class and build a new > ScriptLoaderLauncher and register it with AutoStart. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 15, 2009

Re: [Pharo-project] [Fwd: windowColorSpecification]

by Bart Gauquie

I actually like it that the type of windows are having different colors. In the bar at the bottom, I can quickly determine monticello browser, test runner, package browser, method finder, just by checking the color. I vote against throwing away the colors. The default behaviour of the gray colors is absolutely more suitable than the colored version. Kind regards, Bart On Tue, Dec 15, 2009 at 1:58 PM, Marcus Denker <denker(a)acm.org> wrote: > > On Dec 15, 2009, at 1:53 PM, Alain Plantec wrote: > > > > > > > From: Alain Plantec <alain.plantec(a)univ-brest.fr> > > Date: December 15, 2009 1:52:28 PM GMT+01:00 > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: windowColorSpecification > > Reply-To: alain.plantec(a)univ-brest.fr > > > > > > Hi all, > > > > For now, Pharo has kept the squeak color specification framework based on > the > > WindowColorSpec class and on the dynamic discovery of window colors. > > (it relies on the searching of all windowColorSpecification > implementors). > > Do we want to keep that ? > > I would vote for getting rid of it. > > Please remove it! I personally think that the only use of window-colors is > to be able > to tell windows appart quickly. (but even that I personally think is not > worth having an > ugly UI for). But than *changing* the window color is the last thing that > anyone should > be able to do! > > Marcus > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- imagination is more important than knowledge - Albert Einstein Logic will get you from A to B. Imagination will take you everywhere - Albert Einstein Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Albert Einstein The true sign of intelligence is not knowledge but imagination. - Albert Einstein Gravitation is not responsible for people falling in love. - Albert Einstein

Dec. 15, 2009

Re: [Pharo-project] [Fwd: windowColorSpecification]

by Marcus Denker

On Dec 15, 2009, at 1:53 PM, Alain Plantec wrote: > > > From: Alain Plantec <alain.plantec(a)univ-brest.fr> > Date: December 15, 2009 1:52:28 PM GMT+01:00 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: windowColorSpecification > Reply-To: alain.plantec(a)univ-brest.fr > > > Hi all, > > For now, Pharo has kept the squeak color specification framework based on the > WindowColorSpec class and on the dynamic discovery of window colors. > (it relies on the searching of all windowColorSpecification implementors). > Do we want to keep that ? > I would vote for getting rid of it. Please remove it! I personally think that the only use of window-colors is to be able to tell windows appart quickly. (but even that I personally think is not worth having an ugly UI for). But than *changing* the window color is the last thing that anyone should be able to do! Marcus

Dec. 15, 2009

[Pharo-project] [Fwd: windowColorSpecification]

by Alain Plantec

Dec. 15, 2009