- Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20312

by Marcus Denker

20312 ----- Issue 6732: Failing test: OpenToolTest http://code.google.com/p/pharo/issues/detail?id=6732 Issue 6681: Failing test: GoferApiTest>>#testRepositoryErrors http://code.google.com/p/pharo/issues/detail?id=6681 Issue 6742: Search Dialog not accepting input http://code.google.com/p/pharo/issues/detail?id=6742 Issue 6741: Replace the whole HttpUrl downloading protocol http://code.google.com/p/pharo/issues/detail?id=6741 -- Marcus Denker -- http://marcusdenker.de

Sept. 28, 2012

[Pharo-project] [update 2.0] #20311

by Marcus Denker

- reload packages dirty after changesets -- Marcus Denker -- http://marcusdenker.de

Sept. 28, 2012

[Pharo-project] [update 2.0] #20310

by Marcus Denker

20310 ----- Issue 6694: Failing tests: RBBrowserEnvironmentTest http://code.google.com/p/pharo/issues/detail?id=6694 Issue 5217: LanguageEnvironment should cache converters http://code.google.com/p/pharo/issues/detail?id=5217 Marcus -- Marcus Denker -- http://marcusdenker.de

Sept. 28, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by Mariano Martinez Peck

On Thu, Sep 27, 2012 at 6:46 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Sven, > > The versions in ConfigurationOfZTimestamp aren't quite defined correctly > ... bleedingEdge defaults to loading the latest baseline version. A > baseline version is declared by setting the blessing to #baseline: > > spec blessing: #baseline. > > Your versions in ConfigurationOfZTimestamp are importing from the > '1-baseline' but are not changing the blessing, so Metacello doesn't know > that 1, 2, and 3 are literal versions and not baselines. So version 3 looks > like the "latest baseline version".. > Dale, but baselines are supposed to mandatory have the "spec blessing: #baseline.", right? so why would metacello think that versions 1, 2, and 3 are baselines instead of versions? > > To fix, this remember to set the blessing in your literal version > specifications setting the blessing to something other that #baseline like > #development: > > spec blessing: #development. > > while the version is under development or #release: > > spec blessing: #release. > > when the version is released (i.e., you will not be changing it any more). > > Dale > > ----- Original Message ----- > | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > | To: "Pharo-project(a)lists.gforge.inria.fr Development" < > Pharo-project(a)lists.gforge.inria.fr> > | Sent: Thursday, September 27, 2012 8:31:47 AM > | Subject: [Pharo-project] Metacello bleedingEdge question > | > | Hi, > | > | I have a question. > | > | The following works as expected and loads the latest versions of the > | code: > | > | ConfigurationOfZincHTTPComponents project bleedingEdge load. > | > | The following does not and keeps loading only the #stable one and not > | the latest one. > | > | ConfigurationOfZTimestamp project bleedingEdge load. > | > | I can't see any difference, but I am a Metacello newbie. > | > | Has anyone any idea where I should look ? > | > | Thx, > | > | Sven > | > | -- > | Sven Van Caekenberghe > | http://stfx.eu > | Smalltalk is the Red Pill > | > | > | > | > | > > -- Mariano http://marianopeck.wordpress.com

Sept. 28, 2012

Re: [Pharo-project] [Vm-dev] Re: No GUI on MacOSX 10.5.8 using Cocoa VM

by StÃ©phane Ducasse

Hi yanni it may be worth to create a config and publish it on the github repository. Esteban is on vacation right now but may be we read the mailing-list. Now I do not know how specific version are managed. I can simply tell you that esteban is often losing days fighting with flags. Stef >> I'll try a bit more to get it to work on 10.5.8, now that I can build a VM. > > Okay, got it to work! > > Three changes: > > 1. SqueakOSXAppDelegate.h - use NSObject instead ofNSApplicationDelegate > > 2. sqSqueakOSXScreenAndWindow.h - use NSObject instead of NSWindowDelegate > > 3. SqueakOSXAppDelegate.m - use CoreGraphics instead of OpenGL > > //#ifndef USE_CORE_GRAPHICS > //# import "sqSqueakOSXOpenGLView.h" > //# define ContentViewClass sqSqueakOSXOpenGLView > //#else > # import "sqSqueakOSXCGView.h" > # define ContentViewClass sqSqueakOSXCGView > //#endif > > ==== > > Along the way, I found: > > Issue 5650: OneClick 1.4 can't be launched on MacOSX Mac Air 10.5.8 > http://code.google.com/p/pharo/issues/detail?id=5650 > > While I agree that support for old OS releases should have a reasonable limit, I don't buy 10.5 dropped when 10.8 is around the corner is the right limit. My machine is circa 2009, just three years or so. Apple may have good reason to want to move the user/developer base off of 10.5, because of hardware (pad/phone) and UI native widget changes. In the Squeak/Pharo case, we just need a single window to draw in - that should hardly obsolete a three year old computer. > > I'll add this thread to the issue report (5650). >

Sept. 27, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by StÃ©phane Ducasse

sven christophe is restarting to work on versioner and we hope to get a first version out. The idea is that versioner should help people producing and managing configurations Stef > Hi Dale, > > Thanks a lot for the quick and helpful reply. > > Adding > > spec blessing: #release > > to all explicit versions did indeed do the trick. > > Now I have to update all my configs ;-) > > I have still much to learn. > > Thx again, > > Sven > > On 27 Sep 2012, at 18:46, Dale Henrichs <dhenrich(a)vmware.com> wrote: > >> Sven, >> >> The versions in ConfigurationOfZTimestamp aren't quite defined correctly ... bleedingEdge defaults to loading the latest baseline version. A baseline version is declared by setting the blessing to #baseline: >> >> spec blessing: #baseline. >> >> Your versions in ConfigurationOfZTimestamp are importing from the '1-baseline' but are not changing the blessing, so Metacello doesn't know that 1, 2, and 3 are literal versions and not baselines. So version 3 looks like the "latest baseline version".. >> >> To fix, this remember to set the blessing in your literal version specifications setting the blessing to something other that #baseline like #development: >> >> spec blessing: #development. >> >> while the version is under development or #release: >> >> spec blessing: #release. >> >> when the version is released (i.e., you will not be changing it any more). >> >> Dale >> >> ----- Original Message ----- >> | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> >> | Sent: Thursday, September 27, 2012 8:31:47 AM >> | Subject: [Pharo-project] Metacello bleedingEdge question >> | >> | Hi, >> | >> | I have a question. >> | >> | The following works as expected and loads the latest versions of the >> | code: >> | >> | ConfigurationOfZincHTTPComponents project bleedingEdge load. >> | >> | The following does not and keeps loading only the #stable one and not >> | the latest one. >> | >> | ConfigurationOfZTimestamp project bleedingEdge load. >> | >> | I can't see any difference, but I am a Metacello newbie. >> | >> | Has anyone any idea where I should look ? >> | >> | Thx, >> | >> | Sven >> | >> | -- >> | Sven Van Caekenberghe >> | http://stfx.eu >> | Smalltalk is the Red Pill >> > >

Sept. 27, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by Sven Van Caekenberghe

Hi Dale, Thanks a lot for the quick and helpful reply. Adding spec blessing: #release to all explicit versions did indeed do the trick. Now I have to update all my configs ;-) I have still much to learn. Thx again, Sven On 27 Sep 2012, at 18:46, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Sven, > > The versions in ConfigurationOfZTimestamp aren't quite defined correctly ... bleedingEdge defaults to loading the latest baseline version. A baseline version is declared by setting the blessing to #baseline: > > spec blessing: #baseline. > > Your versions in ConfigurationOfZTimestamp are importing from the '1-baseline' but are not changing the blessing, so Metacello doesn't know that 1, 2, and 3 are literal versions and not baselines. So version 3 looks like the "latest baseline version".. > > To fix, this remember to set the blessing in your literal version specifications setting the blessing to something other that #baseline like #development: > > spec blessing: #development. > > while the version is under development or #release: > > spec blessing: #release. > > when the version is released (i.e., you will not be changing it any more). > > Dale > > ----- Original Message ----- > | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> > | Sent: Thursday, September 27, 2012 8:31:47 AM > | Subject: [Pharo-project] Metacello bleedingEdge question > | > | Hi, > | > | I have a question. > | > | The following works as expected and loads the latest versions of the > | code: > | > | ConfigurationOfZincHTTPComponents project bleedingEdge load. > | > | The following does not and keeps loading only the #stable one and not > | the latest one. > | > | ConfigurationOfZTimestamp project bleedingEdge load. > | > | I can't see any difference, but I am a Metacello newbie. > | > | Has anyone any idea where I should look ? > | > | Thx, > | > | Sven > | > | -- > | Sven Van Caekenberghe > | http://stfx.eu > | Smalltalk is the Red Pill >

Sept. 27, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by Dale Henrichs

Sven, The versions in ConfigurationOfZTimestamp aren't quite defined correctly ... bleedingEdge defaults to loading the latest baseline version. A baseline version is declared by setting the blessing to #baseline: spec blessing: #baseline. Your versions in ConfigurationOfZTimestamp are importing from the '1-baseline' but are not changing the blessing, so Metacello doesn't know that 1, 2, and 3 are literal versions and not baselines. So version 3 looks like the "latest baseline version".. To fix, this remember to set the blessing in your literal version specifications setting the blessing to something other that #baseline like #development: spec blessing: #development. while the version is under development or #release: spec blessing: #release. when the version is released (i.e., you will not be changing it any more). Dale ----- Original Message ----- | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Thursday, September 27, 2012 8:31:47 AM | Subject: [Pharo-project] Metacello bleedingEdge question | | Hi, | | I have a question. | | The following works as expected and loads the latest versions of the | code: | | ConfigurationOfZincHTTPComponents project bleedingEdge load. | | The following does not and keeps loading only the #stable one and not | the latest one. | | ConfigurationOfZTimestamp project bleedingEdge load. | | I can't see any difference, but I am a Metacello newbie. | | Has anyone any idea where I should look ? | | Thx, | | Sven | | -- | Sven Van Caekenberghe | http://stfx.eu | Smalltalk is the Red Pill | | | | |

Sept. 27, 2012

[Pharo-project] Metacello bleedingEdge question

by Sven Van Caekenberghe

Hi, I have a question. The following works as expected and loads the latest versions of the code: ConfigurationOfZincHTTPComponents project bleedingEdge load. The following does not and keeps loading only the #stable one and not the latest one. ConfigurationOfZTimestamp project bleedingEdge load. I can't see any difference, but I am a Metacello newbie. Has anyone any idea where I should look ? Thx, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Sept. 27, 2012

Re: [Pharo-project] Roassal Survey

by Ben Coman

Ciprian Teodorov wrote: > Another feature that I think it is missing in most (if not all) graph > viewers/layout systems/editors is the possibility to have connection ports > on the hierarchical nodes in order to preserve the connections passing > through the hierarchy. > > some pointers: > > http://www.slideshare.net/teodorov/tools-and-crossbarbased-nanocmos-archite… > > http://stiff.univ-brest.fr/~cteodorov/manuscript-teodorov_FINAL.pdf > > > Cheers, > > Ciprian Teodorov > > > On Sep 26, 2012 6:16 PM, "Vanessa PeÃ±a Araya" <van.c.pena(a)gmail.com> wrote: > > Ciprian, I have skimmed through those links but can't quite understand your comment "in order to preserve the connections passing through the hierarchy" Can you expand some more on that - perhaps with a mock up in a paint program? If you are interested in following the development of Roassal, perhaps move your follow up to https://www.iam.unibe.ch/mailman/listinfo/moose-dev. <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> I have been very encouraged by the clean architecture and the responsiveness of the main developers to feature suggestions. cheers, Ben

Sept. 27, 2012