- Pharo-dev - lists.pharo.org

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

by GARY CHAMBERS

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. In Polymorph if the "label" (morph) of a PluggableButtonMorphPlus responds to #enabled: the enablement of the button gets forwarded to the label morph as well. 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. I guess there's a lot in OB to do with specifying the style of in a rather fixed manner (#styleWith:...) (clearly to make it look good with original Morphic) rather than relying on default behaviour that Polymorph leverages. The Vistary theme seems to highlight problems with button colours/states better while Watery2 highlights any pane colour problems. Getting there, I think though. Regards, Gary ________________________________ 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> > To: <Pharo-project(a)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> >>> *To:* Pharo Development <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 >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 30, 2009

[Pharo-project] a couple of issues

by Tudor Girba

Hi, There are a couple of issues I stumbled across in Pharo and I thought of reporting them: - When loading Pier and Seaside there were some Warnings related to some instance variables that blocked the loading. This is a rather strange behavior, especially given that they are warnings. I would rather prefer to have the list of warnings presented to me at the end because like this I can have the code loading without me needing to pay attention. - Apple+B does not work on methods anymore. - Apple+W does not close the window. It seems that the outside window never gets the focus it needs to act on this shortcut. - Spawning a browser takes quite a long time. - Why is mouse swap preference not enabled by default? Otherwise, it looks really nice :) Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by David RÃ¶thlisberger

> I meant the two different styles of blue buttons that you see on the > screenshot below. > Is this the latest version I am looking at? no, can you execute 'ScriptLoader loadOBAlpha' to get the latest version? David > On Jan 30, 2009, at 16:01 , David RÃ¶thlisberger wrote: > >> Hi Adrian, >> >> >>> Furthermore, In the OB Browser there are two types of blue buttons. It >>> would be nice to have a consistent style for buttons. >> >> What exactly do you mean with two styles of blue buttons? One style >> for instance / ? >> / class buttons and different one for browse, hierarchy, variables, etc.? >> >> What we have now in the very latest version of OB is that we get a >> blue button only >> for radio button like panels (such as instance / ? / class) to denote >> the current >> selection and for all other button panels such as browse, hierarchy, >> etc. we get >> either a greyed out button if this action is not active at the moment >> or a normal >> button if it is active, but no blue buttons. >> Is this what you want? >> >> David >> >> _______________________________________________ >> 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

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by Adrian Lienhard

Hi David, I meant the two different styles of blue buttons that you see on the screenshot below. Is this the latest version I am looking at? Cheers, Adrian On Jan 30, 2009, at 16:01 , David RÃ¶thlisberger wrote: > Hi Adrian, > > >> Furthermore, In the OB Browser there are two types of blue buttons. >> It >> would be nice to have a consistent style for buttons. > > What exactly do you mean with two styles of blue buttons? One style > for instance / ? > / class buttons and different one for browse, hierarchy, variables, > etc.? > > What we have now in the very latest version of OB is that we get a > blue button only > for radio button like panels (such as instance / ? / class) to > denote the current > selection and for all other button panels such as browse, hierarchy, > etc. we get > either a greyed out button if this action is not active at the > moment or a normal > button if it is active, but no blue buttons. > Is this what you want? > > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 30, 2009

Re: [Pharo-project] Using pharo in a course?

by Marco D'Ambros

Good news Stef.. we will use Pharo in our course "Software AtÃ¨lier IV - Software Engineering for Web Development". cheers Marco On Jan 29, 2009, at 6:23 PM, StÃ©phane Ducasse wrote: > Btw if you use pharo please let us know because this is important for > us that we list such use > and also the companies. > > > > Stef > > On Jan 29, 2009, at 5:53 PM, Marco D'Ambros wrote: > >> Hi all! >> >> I will start teaching a course about software engineering and web >> development, and I decided to do it with seaside. >> I was wondering whether to use pharo or squeak... which are the >> benefits and drawbacks of pharo with respect to squeak, in the >> context >> of a bachelor course? >> The students know about object oriented programming but don't about >> smalltalk, so in the first weeks we will teach smalltalk. >> >> Any suggestions? >> >> Thanks and cheers >> Marco D'Ambros >> >> _______________________________________________ >> 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

Jan. 30, 2009

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

by David RÃ¶thlisberger

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> > To: <Pharo-project(a)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> >>> *To:* Pharo Development <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 >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> 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

Jan. 30, 2009

Re: [Pharo-project] Call for UI gripes

by David RÃ¶thlisberger

Hi Adrian, > Furthermore, In the OB Browser there are two types of blue buttons. It > would be nice to have a consistent style for buttons. What exactly do you mean with two styles of blue buttons? One style for instance / ? / class buttons and different one for browse, hierarchy, variables, etc.? What we have now in the very latest version of OB is that we get a blue button only for radio button like panels (such as instance / ? / class) to denote the current selection and for all other button panels such as browse, hierarchy, etc. we get either a greyed out button if this action is not active at the moment or a normal button if it is active, but no blue buttons. Is this what you want? David

Jan. 30, 2009

Re: [Pharo-project] Plugin organization

by Adrian Lienhard

On Jan 30, 2009, at 15:33 , Michael Rueger wrote: > StÃ©phane Ducasse wrote: > >> so what are the organizations we can use? >> Ideally I would like to have the test associated with their packages. >> >> XXX >> XXXTests > > The problem with that naming scheme is that then the tests would > always > be loaded together with their tests because of the simple string > matching Monticello does. > Which isn't something you want when doing application/runtime builds. > > That's why I proposed the Plugin-* and Tests-* naming schemes. +1 Adrian

Jan. 30, 2009

Re: [Pharo-project] Using pharo in a course?

by Adrian Lienhard

On Jan 30, 2009, at 15:32 , StÃ©phane Ducasse wrote: > ideally we planed for march now what is left to do: > - trait fixes > - etoy removal > - licensing. ...there is some more stuff. This is also documented at http://code.google.com/p/pharo/wiki/Milestones - default in-image font(s) - Alien FFI - Package management system with stable and unstable distributions - Remove SqueakMap from core - All tests green - Pharo one-click image - Prepare second update stream to maintain released version - Fix critical pending bugs We make progress, but a bit less fast than what I hoped. Anybody that wants to help is welcome... If you wonder what to do, just ask. Cheers, Adrian > Stef > > On Jan 30, 2009, at 3:20 PM, michael_atkisson(a)comcast.net wrote: > >> Not to add any pressure or be annoying, but what is the current >> estimate of when 1.0 will >> be released? I am just curious. >> >> -------------- Original message -------------- >> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> Use pharo (better UI). >>> Once we will have pharo 1.0 we will work on pharo by example. >>> Seaside is now developed using pharo. >>> >>> Stef >>> >>> >>> On Jan 29, 2009, at 5:53 PM, Marco D'Ambros wrote: >>> >>>> Hi all! >>>> >>>> I will start teaching a course about software engineering and web >>>> development, and I decided to do it with seaside. >>>> I was wondering whether to use pharo or squeak... which are the >>>> benefits and drawbacks of pharo with respect to squeak, in the >> context >>>> of a bachelor course? >>>> The students know about object oriented programming but don't >> about >>>> smalltalk, so in the first weeks we will teach smalltalk. >>>> >>>> Any suggestions? >>>> >>>> Thanks and cheers >>>> Marco D'Ambros >>>> >>>> _______________________________________________ >>>> 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

Jan. 30, 2009

Re: [Pharo-project] newDelta >0 failed in sqUnixMemory

by John M McIntosh

Yes, I can't recall it was what 50% of the performance of a 3.x compile out of the box, and after *much* tweaking of compiler flags it was mmm just 20% slower.. Well certainly the performance impact was measured in 10 of percent. On 30-Jan-09, at 4:33 AM, Michael Rueger wrote: > > John McIntosh and I actually spent some time a few ago compiling VMs > on > Windows and MacOS with the newest GCCs and ran into a bunch of > problems, > especially concerning performance. I had to put the work on the back > burner for now, but switching to newer compilers will take a bit of > extra work at some point. > > Michael -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Jan. 30, 2009