- Pharo-dev - lists.pharo.org

[Pharo-project] [Hudson] truncated build history

by Marcus Denker

-> we configured it to just keep 7 days of builds (the images are quite large) -> There is now a project for Pharo 1.3 Core https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/ -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 19, 2011

Re: [Pharo-project] Any Clue..

by Diogenes Moreira

Thanks.. On Wed, Jan 19, 2011 at 9:57 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > I have seen this only a couple of times, and I am not aware of a shortcut > to returning to a working image and recovering lost changes. As an aside, I > am suspicious that opening an image more than once leads to much more > badness than is generally acknowledged. I am convinced it was central to my > most recent meltdown. The only reason I don't have more trouble is that I > have learned to scan the task bar before launching Pharo. > > We need a cross-platform way to detect that a given image is open and to at > least optionally warn and offer to exit without doing any damage. Dolphin > does so by creating a Windows synchronization object (either a semaphore or > an event??) tied to the image name, and if that object exists, it sternly > warns against proceeding. Deployed executables do not do this check by > default. > > Good luck retrieving your work! > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Diogenes Moreira > [diogenes.moreira(a)gmail.com] > Sent: Wednesday, January 19, 2011 7:42 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] Any Clue.. > > Hi folks.. > > this morning, at try start my enviroment, pharo said... "Read failed or > premature end of image file".. Any Clue to solve it, will be welcome. > > Well I can get a clean image and apply de changes.. but somebody have a > shortcut..?? > > Best > >

Jan. 19, 2011

Re: [Pharo-project] Any Clue..

by Schwab,Wilhelm K

I have seen this only a couple of times, and I am not aware of a shortcut to returning to a working image and recovering lost changes. As an aside, I am suspicious that opening an image more than once leads to much more badness than is generally acknowledged. I am convinced it was central to my most recent meltdown. The only reason I don't have more trouble is that I have learned to scan the task bar before launching Pharo. We need a cross-platform way to detect that a given image is open and to at least optionally warn and offer to exit without doing any damage. Dolphin does so by creating a Windows synchronization object (either a semaphore or an event??) tied to the image name, and if that object exists, it sternly warns against proceeding. Deployed executables do not do this check by default. Good luck retrieving your work! ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Diogenes Moreira [diogenes.moreira(a)gmail.com] Sent: Wednesday, January 19, 2011 7:42 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Any Clue.. Hi folks.. this morning, at try start my enviroment, pharo said... "Read failed or premature end of image file".. Any Clue to solve it, will be welcome. Well I can get a clean image and apply de changes.. but somebody have a shortcut..?? Best

Jan. 19, 2011

[Pharo-project] Any Clue..

by Diogenes Moreira

Hi folks.. this morning, at try start my enviroment, pharo said... "Read failed or premature end of image file".. Any Clue to solve it, will be welcome. Well I can get a clean image and apply de changes.. but somebody have a shortcut..?? Best

Jan. 19, 2011

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

by Norbert Hartl

It depends where you look at. ConfigurationOfXMLSupport exists in MetacelloRepository as well as in XMLSupport. The latter one being the official one, the former one being very outdated. My sugesstion would be to remove ConfigurationOfXMLSupport from MetacelloRepository to lower the confusion. Norbert On 19.01.2011, at 13:18, Tudor Girba wrote: > 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

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