- Pharo-dev - lists.pharo.org

[Pharo-project] How to try Shapes and Gaucho?

by Denis Kudriashov

Hello ss3 repo for Shapes and Gaucho closed for reading or maybe empty. So is it possible to get it somewhere? maybe there is prepared image? Actually I gather migrate our applications to last Pharo and use latest achievemens like fuel and tanker. And of course I want vector graphics for user interface by athens. And I very very excited about shapes which gives clean and powerfull morphic replacement (Am I right?) But to understand amount of work for such big changes I should see shapes livelly. I need code. Best regards, Denis

Sept. 28, 2012

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

by Fernando Olivero

Hi, maybe in Pharo some of these keyboard shortcuts were removed (for now), but providing the same operations via pop-up menus doesn't make it a modal UI. One could argue that remembering and triggering keyboard shortcuts simply avoids showing the menu at all, at the expense of a big VI-like learning curve . The community behind Pharo does not want modes in the UI! Of course for power users, remembering tons of shortcuts might be better (not for me though), but there are plans to add default and customizable keybindings ( using the work of Guille Polito). Fernando On Fri, Sep 28, 2012 at 9:40 PM, Chris Muller <asqueaker(a)gmail.com> wrote: >> yes, exactly like this: http://wiki.squeak.org/squeak/900 >> >> Bert Freudenberg added the following: >> >> Tip: You do not have to perform a "find" for the "replace" to work. >> Just select a word you want to have replaced, overtype it with your >> new word, and hit (ctrl-j). Very handy for renaming variables. >> >> This would be perfect. > > You should not expect that -- Pharo used to have it but it was removed > in favor of a more mainstream editor look-and-feel -- so that it be > would more attractive to new users. Command+J / Control+J are just > two of several powerful code-editing capabilities Pharo originally > inherited from Squeak, along with my other favorites Command+E = > Exchange the last two selections and Command+[, (, {, or | = Surround > the highlighted text with that bracket-type pair. (not sure if those > are still there in Pharo). > > Pharo favors _familiarity_ for new users somewhat at the cost of > productivity for its experienced users. It somewhat resembles eclipse > -- with pop-up dialogs and a seemingly "modal" philosophy. Squeak, by > constrast, has kept pushing the "simple-but-powerful" philosphy of its > IDE to near extremes. While it's less familiar for new uesrs, once > learned, general navigation and editing require _far fewer_ gestures. >

Sept. 28, 2012

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

by Chris Muller

> yes, exactly like this: http://wiki.squeak.org/squeak/900 > > Bert Freudenberg added the following: > > Tip: You do not have to perform a "find" for the "replace" to work. > Just select a word you want to have replaced, overtype it with your > new word, and hit (ctrl-j). Very handy for renaming variables. > > This would be perfect. You should not expect that -- Pharo used to have it but it was removed in favor of a more mainstream editor look-and-feel -- so that it be would more attractive to new users. Command+J / Control+J are just two of several powerful code-editing capabilities Pharo originally inherited from Squeak, along with my other favorites Command+E = Exchange the last two selections and Command+[, (, {, or | = Surround the highlighted text with that bracket-type pair. (not sure if those are still there in Pharo). Pharo favors _familiarity_ for new users somewhat at the cost of productivity for its experienced users. It somewhat resembles eclipse -- with pop-up dialogs and a seemingly "modal" philosophy. Squeak, by constrast, has kept pushing the "simple-but-powerful" philosphy of its IDE to near extremes. While it's less familiar for new uesrs, once learned, general navigation and editing require _far fewer_ gestures.

Sept. 28, 2012

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

by StÃ©phane Ducasse

find -> replaceAll On Sep 28, 2012, at 6:41 PM, Sabine KnÃ¶fel wrote: > 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] Metacello bleedingEdge question

by StÃ©phane Ducasse

dale at the end do we really need latestVersion because I'm still confused by it. On Sep 28, 2012, at 3:42 PM, Dale Henrichs wrote: > #latestVersion is defined as the latest version whose blessing is neither #baseline nor #development.

Sept. 28, 2012

[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