September 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] change n same words in browser with one action

by Sabine KnÃ¶fel

Hi, double clicking on one word in the SYSTEM browser (OBSystemBrowserAdaptor) selects this word in one color and all other appearances of this wort in another color. This is nice. Is there a possibility to change ALL the occurences of this word in one action? I did noch find this feature yet. I do not mean the search and replace dialog - to many clicks while developing. Greetings Sabine -- View this message in context: http://forum.world.st/change-n-same-words-in-browser-with-one-action-tp4649… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 28, 2012

Re: [Pharo-project] is branching structure defined in Metacello package names?

by Dale Henrichs

Yes, `Metacello-Platform.pharo-dale.15` indicates that the package is on the `pharo` branch of the `Metacello-Platform` package. See GoferVersionReference>>parseName: for parsing rules. Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Friday, September 28, 2012 4:46:05 AM | Subject: [Pharo-project] is branching structure defined in Metacello package names? | | hi guys | | | I discovered | | 'Metacello-Platform.pharo-dale | | So it is establish that this pharo is the branch? | | Stef | | | |

Sept. 28, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by Dale Henrichs

----- Original Message ----- | From: "Mariano Martinez Peck" <marianopeck(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Friday, September 28, 2012 12:59:46 AM | Subject: Re: [Pharo-project] Metacello bleedingEdge question | | | | | 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? Mariano, Short answer is that literal versions are defined by importing from the baseline, so the literal version inherits the blessing from the baseline. Therefore you have to specify a blessing of #development or #release in the literal version to distinguish it from the baseline. Long answer is... For loading purposes, it actually doesn't matter what the blessing is ... In Metacello, if a package spec has a `file` specified, then the `file` is loaded. if the `file` is not specified then the latest version of the mcz file is loaded ... By convention, when we define baseline versions we don't specify the `file` for the packages. By convention when we define literal versions we do specify the `file` for the packages. The expression: spec package: 'Example-Core' with: 'Example-Core-dkh.25' defines the `file` for the 'Example-Core' package spec to be 'Example-Core-dkh.25'. The blessing is used as an hint by Metacello when using the helper functions like #bleedingEdge or #latestVersion that implement functionality based on the conventions. #bleedingEdge is defined as the latest version with a #baseline blessing. #latestVersion is defined as the latest version whose blessing is neither #baseline nor #development. Versions with a #broken blessing are excluded from consideration... Dale

Sept. 28, 2012

[Pharo-project] is branching structure defined in Metacello package names?

by StÃ©phane Ducasse

hi guys I discovered 'Metacello-Platform.pharo-dale So it is establish that this pharo is the branch? Stef

Sept. 28, 2012

[Pharo-project] [update 2.0] #20313

by Marcus Denker

20313 ----- Issue 6745: Failing tests related to Zinc http://code.google.com/p/pharo/issues/detail?id=6745 Issue 6052: would be good that TestAsserter uses TAssertable http://code.google.com/p/pharo/issues/detail?id=6052 -- Marcus Denker -- http://marcusdenker.de

Sept. 28, 2012

[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