- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Random refactoring on UITheme or what?

by Hilaire Fernandes

Slice in the Inbox. https://pharo.fogbugz.com/f/cases/13118/Clean-up-the-mess-in-UITheme-hierar… Thanks Hilaire Le 22/03/2014 18:11, Ben Coman a Ã©crit : > Hilaire Fernandes wrote: >> Sure. >> Oh, by the way I realize the Polymoprh examples where scalped in Pharo3 >> because of the protocol change of ListModel. This is really *not* nice. >> Fixing that as well. >> >> Hilaire >> > Thanks Hilaire. > >> Le 22/03/2014 17:10, phil(a)highoctane.be a >> Ã©crit : >> >>> Pharo3Theme is a renamed glamourTheme under Watery with some >>> leftovers. >>> >>> Maybe a PharoTheme just under UITheme would be cleaner. >>> >>> > > > > -- Dr. Geo http://drgeo.eu

March 22, 2014

[Fixed] Re: Random refactoring on UITheme or what?

by Hilaire Fernandes

Slice in the Inbox. https://pharo.fogbugz.com/f/cases/13118/Clean-up-the-mess-in-UITheme-hierar… Thanks Hilaire Le 22/03/2014 18:11, Ben Coman a Ã©crit : > Hilaire Fernandes wrote: >> Sure. >> Oh, by the way I realize the Polymoprh examples where scalped in Pharo3 >> because of the protocol change of ListModel. This is really *not* nice

March 22, 2014

Removing grey background from explorer rows

by Sebastian Sastre

I want the whole background to be white How do I remove the even odd even odd with and grey background in explorers? sebastian o/

March 22, 2014

Re: [Pharo-dev] Location of Metacello package dependency

by Johan Brichau

Why can you not reference the main repository? The meta repository is just a place where the configuration loader tool fetches them. Platform-specific elements go in the separate 'sections' of a baseline or version method. Don't make separate branches of the same ConfigurationOf class. You will not only make your life hard but also confuse all users! Maybe you can explain why you think you need those? Johan > On 22 Mar 2014, at 18:20, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > I have some packages A that depend on another package B. > In Metacello, I can easily declare the dependency > spec > className: 'ConfigurationOfB'; > versionString: #'stable'; > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > But the repository is hardcoded here. > > My problem is that I'd like to edit a ConfigurationOfA valid for pharo 1.x, 2.0.x and 3.0.x (so far so good) and put a copy in MetaRepoForPharo20 and another copy in MetaRepoForPharo30. > > Since the repository is hardcoded, this is going to be a problem because the MetaRepo will then cross-ref other repositories and weaken robustness or miss uptodate ConfigurationOfB... > > I'd like to avoid maintaining many branches of ConfigurationOfA. > > How do others resolve this?

March 22, 2014

Nautilus Plugins > Layout glitch

by phil＠highoctane.be

See https://pharo.fogbugz.com/default.asp?13117

March 22, 2014

Location of Metacello package dependency

by Nicolas Cellier

I have some packages A that depend on another package B. In Metacello, I can easily declare the dependency spec className: 'ConfigurationOfB'; versionString: #'stable'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]. But the repository is hardcoded here. My problem is that I'd like to edit a ConfigurationOfA valid for pharo 1.x, 2.0.x and 3.0.x (so far so good) and put a copy in MetaRepoForPharo20 and another copy in MetaRepoForPharo30. Since the repository is hardcoded, this is going to be a problem because the MetaRepo will then cross-ref other repositories and weaken robustness or miss uptodate ConfigurationOfB... I'd like to avoid maintaining many branches of ConfigurationOfA. How do others resolve this?

March 22, 2014

Re: [Pharo-dev] Random refactoring on UITheme or what?

by Ben Coman

Hilaire Fernandes wrote: > Sure. > Oh, by the way I realize the Polymoprh examples where scalped in Pharo3 > because of the protocol change of ListModel. This is really *not* nice. > Fixing that as well. > > Hilaire > Thanks Hilaire. > Le 22/03/2014 17:10, phil(a)highoctane.be a Ã©crit : > >> Pharo3Theme is a renamed glamourTheme under Watery with some leftovers. >> >> Maybe a PharoTheme just under UITheme would be cleaner. >> >>

March 22, 2014

Re: [Pharo-dev] Random refactoring on UITheme or what?

by Hilaire Fernandes

Sure. Oh, by the way I realize the Polymoprh examples where scalped in Pharo3 because of the protocol change of ListModel. This is really *not* nice. Fixing that as well. Hilaire Le 22/03/2014 17:10, phil(a)highoctane.be a Ã©crit : > Pharo3Theme is a renamed glamourTheme under Watery with some leftovers. > > Maybe a PharoTheme just under UITheme would be cleaner. > -- Dr. Geo http://drgeo.eu

March 22, 2014

Re: [Pharo-dev] Random refactoring on UITheme or what?

by phil＠highoctane.be

Pharo3Theme is a renamed glamourTheme under Watery with some leftovers. Maybe a PharoTheme just under UITheme would be cleaner. Phil Le 22 mars 2014 16:49, "Hilaire Fernandes" <hilaire.fernandes(a)gmail.com> a Ã©crit : > I don't think so. These are orthogonal. > > I will propose a simple hierarchy for the theme: > > UITheme > +-UIPharoTheme > +-UIVistaryTheme > +-UIWateryTheme > > I will propose to delete all the other themes as they should belong to > other package. > > Hilaire > > Le 22/03/2014 15:27, Nicolas Cellier a Ã©crit : > > Personnally, I find a huge progress in usability of 3.0 tools versus 2.0 > > which was really awfull. If it must be at the price of broken themes (we > > can hope temporarily), I buy it. > > -- > Dr. Geo http://drgeo.eu > > >

March 22, 2014

Re: [Pharo-dev] Bug in Rectangle?

by Pharo4Stef

> From the st80 ages, rectangle have allways been oriented. > You have an origin and a corner inst var, not 2 corners or vertices. > And you have creation messages Rectangle class>>origin:corner: > The conventions are that of latin scribes, the orientation of rectangle should be (left->right , top->down) > > There is an assumption that a rectangle with negative width (right->left) or height (bottom->top) should be treated as empty. > And this was globally well maintained except a few breakages introduced in Squeak along the years (but I hope I corrected most of the slips since then). > > Now Igor and Stephane had another view more geometric and un-oriented, and wanted to change conventions/handling of empty rectangles in Pharo. > I don't know how far they went, or even if it is feasible at all... IMO, it's a recipe for maximizing breakage/gain ratio. It is clearly not. :) We removed bugs in the invalid rectangle areas and others. And we fixed all the places that were created negative dimensions (like in framelayout) because rectangle where hijack to represent two points that were not a rectangle. We also introduce margin which is really nice to represent 1,2, or 4 digits and avoid to overuse again a rectangle. > Note that VW has Rectangle class>>vertex:vertex:, and we probably should add such message... > > > > > 2014-03-21 15:15 GMT+01:00 Noury Bouraqadi <bouraqadi(a)gmail.com>: > Inverting the origin and the corner of a rectangle changes the result of intersection. > I guess it's a bug, though I imagine that changing the code of Rectangle is likely to have deep/undesired consequences.. > > (0@0 corner: 100@100) intersects: (-50@ -50 corner: 80@80) ==> true > (100@100 corner: 0@0) intersects: (-50@ -50 corner: 80@80) ==> false !!!! > > Noury > > > > >

March 22, 2014