January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by Sean P. DeNigris

Thanks for all the pointers. I'll check them out and make a prototype... Sean -- View this message in context: http://forum.world.st/Issue-3545-in-pharo-FEATURE-Multiple-Worlds-tp3222698… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 19, 2011

Re: [Pharo-project] Issue 3551 in pharo: Morph>>morphsInFrontOverlapping: and friends' behavior does not match comment

by pharo＠googlecode.com

Comment #1 on issue 3551 by sean.p.d...(a)gmail.com: Morph>>morphsInFrontOverlapping: and friends' behavior does not match comment http://code.google.com/p/pharo/issues/detail?id=3551 it also seems to include other top-level morphs that are *behind* it, but *not* ones in front of it - weird...

Jan. 19, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by Fernando Olivero

A little bit different than you are looking for, try it out and see. http://www.squeaksource.com/WorkingSet Fernando On Wed, Jan 19, 2011 at 12:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Romain robbes implemented a mac like expose in squeak a while ago. > I do not remember the name of the project. > > Stef > > On Jan 19, 2011, at 11:45 AM, Sean P. DeNigris wrote: > >> >> Does anyone have a great example of a multiple desktop switching UI >> (something like Mac Spaces)? Â I might take a hack at creating one for Pharo >> on top of this API and I'm looking for inspiration. >> >> Thanks. >> Sean >> -- >> View this message in context: http://forum.world.st/Issue-3545-in-pharo-FEATURE-Multiple-Worlds-tp3222698… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > >

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by Tudor Girba

The last version 1.1.6 is marked as #release. Cheers, Doru On 19 Jan 2011, at 12:26, laurent laffont wrote: > I put ConfigurationOfXMLSupport version 1.0 because blessing was #release. But I agree to change. > > Laurent > > On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > >> Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. >> > > What would be important: we need the latest version in Pharo 1.2... else how can we ever have a version where the tests are green? > (not of XML, but in general) > > Marcus > >> Cheers, >> Doru >> >> >> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: >> >>> Hi, >>> >>> I have a problem with the XMLSupport version from Pharo 1.2. >>> >>> The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. >>> So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. >>> >>> I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. >>> >>> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. >>> >>> Thanks, >>> >>> Fabrizio >>> >> >> -- >> www.tudorgirba.com >> >> "We cannot reach the flow of things unless we let go." >> >> >> >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

Jan. 19, 2011

[Pharo-project] Issue 3551 in pharo: Morph>>morphsInFrontOverlapping: and friends' behavior does not match comment

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3551 by sean.p.d...(a)gmail.com: Morph>>morphsInFrontOverlapping: and friends' behavior does not match comment http://code.google.com/p/pharo/issues/detail?id=3551 Morph #morphsInFrontOverlapping: #morphsInFrontOf:overlapping:do: #morphsInFrontOverlapping:do: all include the morphs submorphs in the returned collection, but the comments state "Return all top-level morphs", which means the submorphs shouldn't be included, no? Pharo1.2rc1 Latest update: #12310 Steps to reproduce: 1. Open a window (e.g. a browser) 2. Inspect it 3. evaluate: "self morphsInFrontOverlapping: self bounds"

Jan. 19, 2011

Re: [Pharo-project] Issue 3550 in pharo: MenuItemMorph>>mouseDown: has unnecessary check

by pharo＠googlecode.com

Comment #1 on issue 3550 by sean.p.d...(a)gmail.com: MenuItemMorph>>mouseDown: has unnecessary check http://code.google.com/p/pharo/issues/detail?id=3550 Fix in inbox: SLICE-Issue-3550-MenuItemMorphmouseDown-has-unnecessary-check-SeanDeNigris.1

Jan. 19, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by StÃ©phane Ducasse

> > Yes, if thats easy to do. > > I played with JavaFX last year and (even when it is now abondened > and will reappear as Java API) it was a nice way to easily build > visual appealing applications with transition effects, shadows, ... > (see http://javafx.com/samples) > > Would like to see that in future for Pharo too easily allow people > to build sexy apps. Me too. Now again this is a question of time not vision. There is simpleMorphic waiting for us > > Thx > T.

Jan. 19, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by StÃ©phane Ducasse

Romain robbes implemented a mac like expose in squeak a while ago. I do not remember the name of the project. Stef On Jan 19, 2011, at 11:45 AM, Sean P. DeNigris wrote: > > Does anyone have a great example of a multiple desktop switching UI > (something like Mac Spaces)? I might take a hack at creating one for Pharo > on top of this API and I'm looking for inspiration. > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Issue-3545-in-pharo-FEATURE-Multiple-Worlds-tp3222698… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 19, 2011

Re: [Pharo-project] [ANN 1.3 started] Core 1.3#13001

by StÃ©phane Ducasse

Excellent! I will give a try to check that everything is running for 1.3 and we will start moving fast again. Stef On Jan 19, 2011, at 12:51 PM, Marcus Denker wrote: > > https://gforge.inria.fr/frs/download.php/28163/PharoCore-1.3-13001.zip > > .. same as 1.2rc1, just a 13 Scriptloader. > > (this way we can deep-freeze 1.2 and start adding to 1.3 instead) > > Hudson project to follow.... > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by StÃ©phane Ducasse

+1 Stef On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. > > Cheers, > Doru > > > On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > >> Hi, >> >> I have a problem with the XMLSupport version from Pharo 1.2. >> >> The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. >> So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. >> >> I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. >> >> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. >> >> Thanks, >> >> Fabrizio >> > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > >

Jan. 19, 2011