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

Re: [Pharo-project] World Graphics and Halos

by Rob Rothwell

Yep...that seemed to fix it! Now if I could just figure out how to remove a Morph from the World without Halos! If I do System->About it is so big now that it won't all fit on my screen, so I can't reach the ok button to close it and I am stuck with it! Rob On Sat, Mar 14, 2009 at 7:11 PM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > Attached a .cs to the issue with a fix, also including the solution Gary > suggested for the taskbar-issue that was reported. > (I don't know how to remove methods in .cs files, and haven't yet gotten > around to learn how to make slices, so BorderedMorph>>areasRemainingToFill: > would have to be removed by hand..) > > Cheers, > Henry > > On 14.03.2009 22:04, Rob Rothwell wrote: > > Done. > > Issues 655 > >> >> On Mar 14, 2009, at 8:14 PM, Rob Rothwell wrote: >> >> > Hi all, >> > >> > Open up a 10250 dev image and click anywhere within the bounds of >> > the "Pharo" graphic. >> > >> > The world menu pops up and leaves part of itself behind when you >> > click somewhere else on the screen. >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 14, 2009

Re: [Pharo-project] World Graphics and Halos

by Henrik Sperre Johansen

Attached a .cs to the issue with a fix, also including the solution Gary suggested for the taskbar-issue that was reported. (I don't know how to remove methods in .cs files, and haven't yet gotten around to learn how to make slices, so BorderedMorph>>areasRemainingToFill: would have to be removed by hand..) Cheers, Henry On 14.03.2009 22:04, Rob Rothwell wrote: > Done. > > Issues 655 > > > On Mar 14, 2009, at 8:14 PM, Rob Rothwell wrote: > > > Hi all, > > > > Open up a 10250 dev image and click anywhere within the bounds of > > the "Pharo" graphic. > > > > The world menu pops up and leaves part of itself behind when you > > click somewhere else on the screen. >

March 14, 2009

Re: [Pharo-project] World Graphics and Halos

by Rob Rothwell

Done. Issues 655 and 666. Take care, Rob On Sat, Mar 14, 2009 at 3:45 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > dear rob > > can you open a bug tracker entry? > two entries :) > Stef > > On Mar 14, 2009, at 8:14 PM, Rob Rothwell wrote: > > > Hi all, > > > > Open up a 10250 dev image and click anywhere within the bounds of > > the "Pharo" graphic. > > > > The world menu pops up and leaves part of itself behind when you > > click somewhere else on the screen. > > > > Then, if you turn halos on and try to remove the graphic (or any > > morph for that matter) you get a DNU... > > > > Just wondering if anyone can confirm before a file an issue; also > > wondering if this is one or two issues? > > > > Take care, > > > > 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 >

March 14, 2009

Re: [Pharo-project] World Graphics and Halos

by StÃ©phane Ducasse

dear rob can you open a bug tracker entry? two entries :) Stef On Mar 14, 2009, at 8:14 PM, Rob Rothwell wrote: > Hi all, > > Open up a 10250 dev image and click anywhere within the bounds of > the "Pharo" graphic. > > The world menu pops up and leaves part of itself behind when you > click somewhere else on the screen. > > Then, if you turn halos on and try to remove the graphic (or any > morph for that matter) you get a DNU... > > Just wondering if anyone can confirm before a file an issue; also > wondering if this is one or two issues? > > Take care, > > Rob > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 14, 2009

[Pharo-project] World Graphics and Halos

by Rob Rothwell

Hi all, Open up a 10250 dev image and click anywhere within the bounds of the "Pharo" graphic. The world menu pops up and leaves part of itself behind when you click somewhere else on the screen. Then, if you turn halos on and try to remove the graphic (or any morph for that matter) you get a DNU... Just wondering if anyone can confirm before a file an issue; also wondering if this is one or two issues? Take care, Rob

March 14, 2009

[Pharo-project] [ANN] 654 inconsistent highlight color

by Sebastian Sastre

I've submitted an issue and added the patch I'm using for quite some time, best sebastian

March 14, 2009

Re: [Pharo-project] Setting package test

by Adrian Lienhard

My usability problem was that I didn't understood that I need to "accept" changes in text fields. Somehow I didn't make the connection to method source panes (for which I think the feedback whether a method was saved is important). Therefore, also reverting to the default value did not work because this action does not override currently unsaved content. So everything works; just some usability issues that may be improved... (a simple text like "Save text fields with ctrl-s" might even be enough). Cheers, Adrian On Mar 14, 2009, at 17:00 , Alain Plantec wrote: > Adrian Lienhard a Ã©crit : >> Hi Alain, >> >> Nice to see you making progress! >> > thank you Adrian >> I've taken a quick look at the GUI and the code. Here some feedback: >> >> - When I change a value, why do I get a red border (for me this >> indicates that the change is invalid)? >> > no, there is no control over what is typed except with range and > multiple value. > The red border can be seen when you leave a widget. > it indicates that you have entered something. > You need to explicitly accept your input with cmd-s or return. > With a simple TextEntry, one can use autoAccept: in order > to avoid the red border (the text is accepted while you are typing). > But here, I'm using editable drop lists (very useful for old values > retrieval), > and one have to explicitly accept what is entered in order to indicate > to the drop list > that an input has to be recorded. > This is exactly the same when you edit some code in a browser. > You have to accept it to compile it (red border arises if you leave an > unaccepted > code pane) >> - Set to default doesn't do anything >> > It works here: try to create a setting somewhere. As an example > UISettings>>smartUpdating > <setting> > ^ SmartUpdating > ifNil: [SmartUpdating := SettingValue new name: 'Smart > updating'; > parent: #uiSettingNode; > default: true] > > you should see the new setting with a checked checkbox. > > another example: > MorphicSettings>>haloTheme > <setting> > ^ HaloTheme > ifNil: [HaloTheme := MultipleSettingValue new > name: 'Theme'; > parent: #haloEnabled ; > default: #Classic; > domainValues: #(#Iconic #Classic #Custom)] > > you should see a drop list with #Classic as the current value. > here, if you don't specify a default, then the default is > automatically > set to the > first domain value (#Iconic here). > > You can always come back to the default value with cmd-s or from the > tree popup menu. > > is it ok ? >> - Dropdown lists are displayed at the wrong position on the screen >> (I'm using the default theme, Watery2) >> > yes, it has been fixed by 10252. >> - At first I didn't recognize the slider control (glyph contrast >> setting) >> > I think I will set the bakground to lightgray in order to make them > easily viewed. >> - Instead of using the old change notification mechanism, you could >> use Announcements >> > ah, yes, I would like but old change notification is used by morphic > and > Polymorph. > I have to use it in order to make fields well updated. >> - The method #domainValues: looks a bit fishy with the isKindOf: >> checks >> > yes, I agree, I use isKindOf: in several places but all these bad > codes > will be improved when > the framework will be stable. >> - The method #maxNameWidthForFont: can be simplified by using >> #detectMax: >> > I didn't know it, thanks. >> A search/filter would certainly be useful. >> > it will be implemented. > > thanks for your remarks, nice to have feedbacks. > > Cheers > Alain >> Cheers, >> Adrian >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> On Mar 14, 2009, at 01:38 , Alain Plantec wrote: >> >> >>> Hi all, >>> Preference is now renamed as Setting. >>> Please, can you can load these two packages and play with the >>> settings. >>> 'SettingTree open' open the browser. >>> Examples of setting are located in the Setting-SandBox category. >>> You can use <pharo> or <setting> as pragma. >>> the pragma list the browser is able to recognize is now a parameter. >>> (see SettingCollector class side). >>> as an example, It will be possible for an application to use its own >>> pragma symbol. Thus, the browser will be able to show application >>> specific >>> settings. >>> I will add 'saving', 'saving as', choose, open, and 'filtering' >>> features (by package or by setting name as available in current >>> preference browser). >>> If you have more ideas or needs, please let me know. >>> >>> Cheers >>> alain >>> >>> <Setting-alain_plantec.1.mcz><SettingSupport-alain_plantec. >>> 1.mcz><Setting >>> tree.gif>_______________________________________________ >>> 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

March 14, 2009

Re: [Pharo-project] [ANN] 10252

by Michael Rueger

Michael Rueger wrote: > Gary Chambers wrote: >> A lot more could be done with Rome, though only then availbale for platforms >> with Cario... > > That is not entirely true. > Rome has also a Balloon backend, though ti hasn't been updated in a while. > It should also be possible to build a BitBlt back end with fallbacks for > unsupported features like certain gradients. Hmm, thinking about it a second more ;-) BitBlt would only make sense for relatively simple graphics as otherwise you would need Balloon's features for drawing curves etc. Michael

March 14, 2009

Re: [Pharo-project] [ANN] 10252

by Michael Rueger

Gary Chambers wrote: > A lot more could be done with Rome, though only then availbale for platforms > with Cario... That is not entirely true. Rome has also a Balloon backend, though ti hasn't been updated in a while. It should also be possible to build a BitBlt back end with fallbacks for unsupported features like certain gradients. Michael

March 14, 2009

Re: [Pharo-project] Setting package test

by Alain Plantec

Adrian Lienhard a Ã©crit : > Hi Alain, > > Nice to see you making progress! > thank you Adrian > I've taken a quick look at the GUI and the code. Here some feedback: > > - When I change a value, why do I get a red border (for me this > indicates that the change is invalid)? > no, there is no control over what is typed except with range and multiple value. The red border can be seen when you leave a widget. it indicates that you have entered something. You need to explicitly accept your input with cmd-s or return. With a simple TextEntry, one can use autoAccept: in order to avoid the red border (the text is accepted while you are typing). But here, I'm using editable drop lists (very useful for old values retrieval), and one have to explicitly accept what is entered in order to indicate to the drop list that an input has to be recorded. This is exactly the same when you edit some code in a browser. You have to accept it to compile it (red border arises if you leave an unaccepted code pane) > - Set to default doesn't do anything > It works here: try to create a setting somewhere. As an example UISettings>>smartUpdating <setting> ^ SmartUpdating ifNil: [SmartUpdating := SettingValue new name: 'Smart updating'; parent: #uiSettingNode; default: true] you should see the new setting with a checked checkbox. another example: MorphicSettings>>haloTheme <setting> ^ HaloTheme ifNil: [HaloTheme := MultipleSettingValue new name: 'Theme'; parent: #haloEnabled ; default: #Classic; domainValues: #(#Iconic #Classic #Custom)] you should see a drop list with #Classic as the current value. here, if you don't specify a default, then the default is automatically set to the first domain value (#Iconic here). You can always come back to the default value with cmd-s or from the tree popup menu. is it ok ? > - Dropdown lists are displayed at the wrong position on the screen > (I'm using the default theme, Watery2) > yes, it has been fixed by 10252. > - At first I didn't recognize the slider control (glyph contrast > setting) > I think I will set the bakground to lightgray in order to make them easily viewed. > - Instead of using the old change notification mechanism, you could > use Announcements > ah, yes, I would like but old change notification is used by morphic and Polymorph. I have to use it in order to make fields well updated. > - The method #domainValues: looks a bit fishy with the isKindOf: checks > yes, I agree, I use isKindOf: in several places but all these bad codes will be improved when the framework will be stable. > - The method #maxNameWidthForFont: can be simplified by using > #detectMax: > I didn't know it, thanks. > A search/filter would certainly be useful. > it will be implemented. thanks for your remarks, nice to have feedbacks. Cheers Alain > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > On Mar 14, 2009, at 01:38 , Alain Plantec wrote: > > >> Hi all, >> Preference is now renamed as Setting. >> Please, can you can load these two packages and play with the >> settings. >> 'SettingTree open' open the browser. >> Examples of setting are located in the Setting-SandBox category. >> You can use <pharo> or <setting> as pragma. >> the pragma list the browser is able to recognize is now a parameter. >> (see SettingCollector class side). >> as an example, It will be possible for an application to use its own >> pragma symbol. Thus, the browser will be able to show application >> specific >> settings. >> I will add 'saving', 'saving as', choose, open, and 'filtering' >> features (by package or by setting name as available in current >> preference browser). >> If you have more ideas or needs, please let me know. >> >> Cheers >> alain >> >> <Setting-alain_plantec.1.mcz><SettingSupport-alain_plantec. >> 1.mcz><Setting >> tree.gif>_______________________________________________ >> 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 > > >

March 14, 2009