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

[Pharo-project] [ANN] Glamour on Seaside - first version
by Tudor Girba Sept. 27, 2010

Sept. 27, 2010

Hi, We are happy to announce the first version of Glamour on Seaside. This work was carried out by Andrei Vasile Chis and was sponsored by ESUG. The project offers a Seaside-based rendering of Glamour browsers. In other words, once you have a browser in Glamour, you can now simply display it on the web. You can obtain the code in two ways: - Nightly built image: http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/lastSucces… - Metacello configuration loadable in Pharo 1.1 (not Core) Gofer new squeaksource: 'Glamour'; package: 'ConfigurationOfGlamourSeaside'; load. (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. A couple of examples are available on the Moose server: http://online.moosetechnology.org/glamour/basicExamples (a number of example browsers) http://online.moosetechnology.org/moose/metaBrowser (a browser for the meta-model of Moose) Several developments are planned for the near future, so stay tuned for more news. We would highly appreciate any kind of feedback. Cheers, Andrei and Doru

3 3

[Pharo-project] debug it in the debugger bring a halt.
by StÃ©phane Ducasse Sept. 27, 2010

Sept. 27, 2010

compileSelectionFor: anObject in: evalContext | methodNode method failed | failed := false. methodNode := [ Compiler new compileNoPattern: self selectionAsStream in: anObject class context: evalContext notifying: self ifFail: [ failed := true ] ] on: OutOfScopeNotification do: [:ex | ex resume: true]. failed ifTrue: [ ^ nil ]. self halt: 'old generate: use'. method := methodNode generate: #(0 0 0 0). ^method copyWithTempsFromMethodNode: methodNode clearly a bad use of halt instead of deprecated. Fixed in 3007 Stef

1 0

Re: [Pharo-project] Syntax extension for the Mercury Search bar
by Simon Denier Sept. 27, 2010

Sept. 27, 2010

On 27 sept. 2010, at 14:36, Lukas Renggli wrote: >> As a remainder, this is what you can do from the search bar. Type: >> ClassName (starts with uppercase, look up class definition) >> #ClassName (look up references to ClassName) >> methodName (starts with lowercase, look up implementors of methodName) >> #methodName (look up senders of methodName) >> - 'string' (look up for string in methods (not the same as look up in method source, which is much slower)) > > There is another one if you have the refactoring tools loaded. If the > expression contains a backquote it searches for parse tree patterns, > e.g. > > `@expr instVarNamed: `#string > > finds all the senders of #instVarNamed: that have a plain > string-literal as its argument. ahah, didn't know this one (however, talk about cryptic syntax when it comes to parse tree patterns :)) > >> The search bar also works with completion, so it doubles as a useful launch bar actually. > > The fact that completion works is quite accidental and should be improved :-) > >> Any idea welcomed > > Actually, Colin and I were discussing about removing the Mercury > panel. We observed that almost nobody uses or knows how to use it. I > personally never use it, I find other ways to navigate much more > efficient and simpler to perform without the need of typing > cryptographic sequences of characters :-) Well I use it a lot, but the fact is I never used it before O2, which provided a nice ghost help about the syntax. I don't know how to put a ghost in the OB widgets though so that people can learn how to use it. My main concern with other navigation ways is that I need to pay attention to the selected pane to run a specific search (Find class works only in the left most pane, at least until now), and they do not necessarily accept a partial match (or have completion enabled, even by accident :)) > > The mercury panel is highly extensible, so maybe it would make sense > to move it into an externally maintained package? Yeah perhapsit does not belong to the browser. It seems more handy as a kind of launcher/quick search like Algernon (I have something like that also). > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

3 2

Re: [Pharo-project] MethodName is now Finder
by StÃ©phane Ducasse Sept. 27, 2010

Sept. 27, 2010

may be we could integrate that with the method finder? Now it would be good not to have to reimplement everything yet another time. Stef >> Benjamin >> >> I would rename patterns into example-based >> Then >> when on selector >> I would propose classes if the guy type something that looks like a class or a part of a class name >> similarly on class >> I would propose selector if the guy started to type something like a selectors >> The idea is to help the user as much as possible. >> We did the same with the sender and implementor, you can browse a class if you type Point and press cmd-M instead of cmd-B > > > Yep, did you have a look the Mercury search bar in OB? It has a nifty syntax to look for: > - ClassName (starts with uppercase, look up class definition) > - #ClassName (look up class references) > - method (starts with lowercase, look up implementors) > - #method (look up senders) > - 'string' (look up for string in methods (not the same as look up in method source, which is much slower)) > > I would rename 'select classes' into something else, 'scoping classes', because it is really about the scope. > Actually, I would love to extend the Mercury syntax to be able to scope things. > > > >> >> Else did you try to remove the progress bar? >> because this looks strange. >> >> Stef >> >>> I've fix some bug and discover how to script packages loading ^^ >>> >>> Now, just run >>> >>> >>> Gofer new >>> squeaksource: 'PharoTaskForces'; >>> package: 'ConfigurationOfFinder'; >>> load >>> >>> ConfigurationOfFinder loadDefault >>> >>> >>> >>> >>> Ben >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] ('a' == 'a') == true ?
by StÃ©phane Ducasse Sept. 27, 2010

Sept. 27, 2010

On Sep 27, 2010, at 10:32 AM, Johan Brichau wrote: > I convinced the teacher who will be taking over my Smalltalk courses at UCLouvain (starting this week) to use Pharo :-) gorgeous! > One of the introductory exercises in these courses shows the difference between '==' and '='. However, in Pharo (&Squeak) the following goes wrong imho: > > 'a' == 'a' -> true > $a asString == $a asString -> false > > It seems that when you evaluate the expression, the (semantically identical) strings are represented as the same literal in the compiled block. > For example, try to evaluate the following code by evaluating each statement in a separate doit. Then do it again as a single block... > > |a b| > a := 'a'. > b := 'a'. > a == b inspect > > > Do I make it an issue? Is there already an issue? (did not find one) > Am I wrong? > > Johan > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] Update Pharo image to the last version
by StÃ©phane Ducasse Sept. 27, 2010

Sept. 27, 2010

Dear Dario save your data download latest load your data. We would have prefered to be able to have an update which does not force you to do that but this is like that. Stef On Sep 27, 2010, at 2:41 PM, Dario Trussardi wrote: > Hi, > > i work with a Pharo image. > > The relative System About option report: > > Pharo-1.0 > Latest update: #10517. > > > Now my question is : > > > I can update this image to the last version ? > > > Or i need do : > > A) save my data > > B) download the last version > > C) restore my data > > > Thank for any considerations, > > Dario > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] [update 1.2] #12147
by Marcus Denker Sept. 27, 2010

Sept. 27, 2010

12147 ----- Issue 2965: Spelling mistake in font settings Issue 3004: Object>>Copy comment Issue 2997: Scriptloader cleanUpForRelease makes use of deprecated rehashAllSubInstances Issue 2983: ThemeSettings>>#menuSelectionColor: should return self Issue 2978: HelpBrowser refresh button do nothing -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [ANN] pre-built 1.2 Core#12146
by Marcus Denker Sept. 27, 2010

Sept. 27, 2010

https://gforge.inria.fr/frs/download.php/27527/PharoCore-1.2-12146.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Update Pharo image to the last version
by Dario Trussardi Sept. 27, 2010

Sept. 27, 2010

Hi, i work with a Pharo image. The relative System About option report: Pharo-1.0 Latest update: #10517. Now my question is : I can update this image to the last version ? Or i need do : A) save my data B) download the last version C) restore my data Thank for any considerations, Dario

1 0

[Pharo-project] Syntax extension for the Mercury Search bar
by Simon Denier Sept. 27, 2010

Sept. 27, 2010

OK, for those who don't know it, there is a nifty search tool in Omnibrowser, called the Mercury search bar, which comes at the top of OB (you can enabled it through Settings if it does not appear). As a remainder, this is what you can do from the search bar. Type: ClassName (starts with uppercase, look up class definition) #ClassName (look up references to ClassName) methodName (starts with lowercase, look up implementors of methodName) #methodName (look up senders of methodName) - 'string' (look up for string in methods (not the same as look up in method source, which is much slower)) The search bar also works with completion, so it doubles as a useful launch bar actually. Two things I would like to have: 1) look for package/system category 2) scope search, or environment search (open an environment on the given scope before starting the search) (3) ok a third, look for class hierarchy) Now for the first, any idea about an easy syntax to express a package search? I don't want to mix class and package search. So I was thinking of $PackageName or %PackageName, especially the first as it can not be recognized as a binary selector, but it looks weird. Second, I'm wondering about an inline syntax for scoping, like: methodName in: #PackageA -> will lookup for implementors of methodName in PackageA or simply cutting the Mercury textfield in two, with one for the search term and one for the scope) Any idea welcomed -- Simon

2 1