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

Re: [Pharo-project] Polymorph and OB Browser Colors Quick Solution

by David RÃ¶thlisberger

Hi Gary, > I notice the back/forward buttons are created with a morph as the label. > Might be better to refactor OBDraggableButton to be under > PluggableButtonMorphPlus (or implement enablement protocol) and use just > a string or text, using enablement rather than on/off state - that > should help avoid use of the hardcoded font. ok, I changed the back/forward buttons to be subclasses of PluggableButtonMorphPlus. But I did not change the label to just be a string or text, because it doesn't seem to be possible to get colored labels for buttons if you don't generate the string morph yourself. Because when you pass a text, PluggableButtonMorph just uses its string, but not the assigned attributes... > Button bar heights are also a problem if fixed size. > Similarly, OBButtonModel might benefit from some attention (hence the > "different" style of the instance/class/traits buttons etc.). These > buttons also. ok, I will check that. Thanks, David > ------------------------------------------------------------------------ > *From:* David RÃ¶thlisberger <squeak(a)webcitas.ch> > *To:* Pharo-project(a)lists.gforge.inria.fr > *Sent:* Friday, 30 January, 2009 3:17:46 PM > *Subject:* Re: [Pharo-project] Polymorph and OB Browser Colors Quick > Solution > > Thanks, Gary, for this new patch. Indeed this works better. :) > I adapted some parts and committed it for the moment. From the Polymorph > point of > view: Is this what you need? > Because I need to adapt it again as OB does not work properly in Squeak > now, so I > would like to know whether it does what you want for Polymorph or not. > > It's enough when you load latest OB-Morphic to get it. > > David > > > Found the correct one now... attached. > > > > Regards, Gary. > > > > ----- Original Message ----- From: "David RÃ¶thlisberger" > > <squeak(a)webcitas.ch <mailto:squeak@webcitas.ch>> > > To: <Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr>> > > Sent: Thursday, January 29, 2009 1:43 PM > > Subject: Re: [Pharo-project] Polymorph and OB Browser Colors Quick > Solution > > > > > >> Hi Gary, > >> > >>> Not heard from David since I emailed on 30th Dec about getting OB to be > >>> less hardcoded about direct use of model colours, along with having > >>> buttons changed to PluggableButtonMorphPlus (to use enablement rather > >>> than on/off state to indicate enablement)... > >> > >> yep, sorry, I was busy with other stuff. > >> > >> But still I'm not sure about the question I sent to you beginning of > >> this year as an > >> answer to your mail from the 30th of December: > >> > >> "Concerning the first issue about #adoptPaneColor: > >> In my Squeak 3.9 (and I think also in my latest Pharo) image this > >> method is already > >> present in Morph. Is your change therefore needed at all, and if so, > >> where should we > >> commit it? I don't think it should be part of OB." > >> > >> To give you some more context: You once posted to the mailing list a > >> CS-patch > >> containing the #adoptPaneColor: as an OB-extension method for Morph. > >> But as for me > >> this method (with the same source code) is already present in Morph, I > >> cannot imagine > >> that this patch fixes the problem. > >> I therefore think we should fix this color problem differently. > >> If you know another solution, please let me know, otherwise I will > >> dive into it. > >> > >> I will in the meantime look at the PluggableButtonMorphPlus issue. > >> > >> Cheers, > >> David > >> > >> > >>> Regards, Gary. > >>> > >>> ----- Original Message ----- > >>> *From:* Rob Rothwell <mailto:r.j.rothwell@gmail.com > <mailto:r.j.rothwell@gmail.com>> > >>> *To:* Pharo Development > <mailto:pharo-project@lists.gforge.inria.fr > <mailto:pharo-project@lists.gforge.inria.fr>> > >>> *Sent:* Tuesday, January 27, 2009 11:32 PM > >>> *Subject:* [Pharo-project] Polymorph and OB Browser Colors Quick > >>> Solution > >>> > >>> I know OB has some issues with the Polymorph themes such that you > >>> are always left with the standard browser window color border in the > >>> window panes of an OB Browser. > >>> > >>> At any rate, a simple "Preferences setPreference: > >>> #browserWindowColor toValue: (Color r: 0.815 g: 0.811 b: 0.811)" > >>> seems to set it to a decent color for the Watery2 or Watery theme, > >>> but I was wondering if there is a better place to set something like > >>> this more...dynamically...when different themes are chosen. > >>> > >>> Thanks, > >>> > >>> Rob > >>> > >>> > >>> >

Feb. 2, 2009

[Pharo-project] Renaming instance variable

by Alexandre Bergel

Renaming an instance variable using the refactoring command raises an error. The method "RBScanner class>>isVariable:" triggers the error. ISSUE #472 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 2, 2009

Re: [Pharo-project] MVCMenuMorph and Flaps status

by Damien Cassou

On Sun, Feb 1, 2009 at 7:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I would say that project and flaps are to be removed. > What the other think? I like flaps, you can just drag&drop the application you want without clicking. -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 2, 2009

Re: [Pharo-project] a couple of issues

by Damien Cassou

On Sun, Feb 1, 2009 at 1:32 AM, Tudor Girba <girba(a)iam.unibe.ch> wrote: > I am not sure I understand why this would be a problem for MS Windows. > Or maybe I just do not understand the meaning of the swap option. Because on Windows, the right mouse button does what people expect (= what you get with the middle mouse button by default on MacOS and Linux). If you change the preference value, MacOS and Linux users will be happy (right mouse button for context menu), but Windows users won't appreciate (they would have to use their middle click to open the context menu). -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 2, 2009

Re: [Pharo-project] Window buttons

by Damien Cassou

On Sun, Feb 1, 2009 at 12:11 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Unfortunately the noviceMode preference seems to have disappeared from Pharo > (in Squeak, with that on, you'd get balloon help for the buttons). I think this preference is useless in that case. Please provide tooltips in every cases. On my linux distribition, I've never noticed them but I've just verified that tooltips are present on these 3 buttons on all windows. -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 2, 2009

Re: [Pharo-project] Questions, Ideas, suggestions?

by Alexandre Bergel

> First of all I have to say that I really like the idea behind Pharo > - especially the "Pharo wants to help people invent the future" > one! I managed to find where to lodge issues but where should one > submit questions, ideas and/or suggestions? This mailing list is probably the most appropriate. > I am not a bit fan of mailing lists so I was wondering if the > mailing list will be available from Nabble? Since Google Code is > used why not simply use Google Groups? We did not push the reflection very far actually. We had the infrastructure for mailing lists, and a lot of people who will read this email use intensively mailing lists. > The Pharo image already has a lot of UI improvements over the > default Squeak image but I still think that the default (and only) > font is an ugly font. The font in Ramon's customized Pharo image is > a little better but his font is too big. Since the windowing looks > like a Mac why not use a nice font too? Anyway, a nice default font > would be nice. The British crew is doing a tremendous work. They know what the words "beauty" and "elegance" mean and using their definitions makes me happy. I am sure there are aware of the remaining deficiency of the Pharo UI. Thanks for your comments, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 2, 2009

Re: [Pharo-project] a couple of issues

by David RÃ¶thlisberger

>> - Apple+B does not work on methods anymore. > > Yes > Apple-N neither on method list Under which configuration? I tested in pharo-dev 10205 using latest OB alpha. There it works for me. David

Feb. 2, 2009

Re: [Pharo-project] [MC] [ANN] Sourcetalk

by Lukas Renggli

>> Did you load Sourcetalk-Client-lr.4.st that I posted in the original >> announcement? > > No. I didn't know anything about that file. Where can I get it ? I was just > reading pdf user guide. What about including this in the ser guide ? It should become part of the standard Monticello distribution, but that hasn't happened yet. I sent the changes with my original announcement, but attached them again to this mail. Make sure to close all Monticello 2 browsers before loading. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 2, 2009

Re: [Pharo-project] Questions, Ideas, suggestions?

by Adrian Lienhard

Hi Geert, On Feb 2, 2009, at 02:50 , Geert Claes wrote: > First of all I have to say that I really like the idea behind Pharo - > especially the "Pharo wants to help people invent the future" one! I > managed to find where to lodge issues but where should one submit > questions, > ideas and/or suggestions? This is the right place. > I am not a bit fan of mailing lists so I was wondering if the > mailing list > will be available from Nabble? Since Google Code is used why not > simply use > Google Groups? There is http://dir.gmane.org/gmane.comp.lang.smalltalk.pharo.devel which allows you do read the mailing list as an RSS feed. > The Pharo image already has a lot of UI improvements over the > default Squeak > image but I still think that the default (and only) font is an ugly > font. > The font in Ramon's customized Pharo image is a little better but > his font > is too big. Since the windowing looks like a Mac why not use a nice > font > too? Anyway, a nice default font would be nice. Absolutely. There will be a good set of default fonts in version 1.0. Its on the todo list. Please also note that you can use other fonts than the one Ramon suggests in another mail. We have FreeType integrated so you have access to all your nice subpixel AA fonts (select: world menu->System->Preferences->System fonts)! Cheers, Adrian

Feb. 2, 2009

Re: [Pharo-project] Questions, Ideas, suggestions?

by Ramon Leon

> First of all I have to say that I really like the idea behind > Pharo - especially the "Pharo wants to help people invent the > future" one! I managed to find where to lodge issues but > where should one submit questions, ideas and/or suggestions? > > I am not a bit fan of mailing lists so I was wondering if the > mailing list will be available from Nabble? Since Google > Code is used why not simply use Google Groups? > > The Pharo image already has a lot of UI improvements over the > default Squeak image but I still think that the default (and > only) font is an ugly font. The font in Ramon's customized > Pharo image is a little better but his font is too big. > Since the windowing looks like a Mac why not use a nice font > too? Anyway, a nice default font would be nice. Set the fonts to whatever you like, I prefer a larger font so I do this... Preferences setDefaultFonts: #( (setSystemFontTo: 'Accuny' 14) (setListFontTo: 'Accuny' 14) (setMenuFontTo: 'Accuny' 14) (setWindowTitleFontTo: 'Accuny' 14) (setBalloonHelpFontTo: 'Accuny' 14) (setCodeFontTo: 'Accuny' 14) (setButtonFontTo: 'Accuny' 14) ). If you want them smaller, make them smaller, and keep your own short build script so you can quickly customize a new image to your liking loading all the packages you like and setting all the preferences the way you want them. Ramon Leon http://onsmalltalk.com

Feb. 2, 2009