- Pharo-dev - lists.pharo.org

[Pharo-project] Alien Plugin for Linux

by Fernando olivero

Hi, is there an Alien plugin for linux ? I recall somebody working on it. Would be nice if its made available somewhere on the web. Thanks, Fernando

Sept. 27, 2010

[Pharo-project] Sound

by Schwab,Wilhelm K

Hello all, What is the state of sound in Pharo? On Linux? I can solve my current problem in various ways, including saving .wav files and playing them elsewhere, but options are always good. Bill

Sept. 27, 2010

Re: [Pharo-project] ECompletion/OCompletion tests takes A LIFE!!

by StÃ©phane Ducasse

mariano can you open a bug entry. Stef On Sep 26, 2010, at 6:21 PM, Mariano Martinez Peck wrote: > Hi. I am loading OCompletion in PharoCore 1.1 while building the Dev image. If I just take a core image, load OCompletion and run tests, they take a lot of time, not acceptable. > > Now....if I build a Dev image (with OB, RB, etc) and at the end I try to run OCompletion tests, the tests takes HOURS. The image seems frozen, but actually is working. If I interrupt I see the problem is in > > ECUntypedModel >> initializeSelectors > > the part of > > > [ Smalltalk environment keysDo: > [ :each | > selectors add: (ECGlobalEntry > contents: each > type: #globalVar) ]. > > > takes a lot of time > > and it seems related to "ECPreferences caseSensitive" and "ECUntypedModel >> resetSelectors" > > I don't know what else to say. To reproduce, take a PharoCore 1.1 and evaluate: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOCompletion'; > load. > > (ConfigurationOfOCompletion project version: '1.2') load: 'Core Tests' > > Then, run all the tests inside OCompletionTests. You will see that after running some threads....it will look like frozen. There, do an interrupt and analize. > > IF you do that for a Dev image, it takes muuuuch more. I guess this is because "Smalltalk environment keys" will have muuuuuch more elements than a simple core. > > Anyway, help is appreciated. > > Cheers > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 27, 2010

Re: [Pharo-project] MethodName is now Finder

by StÃ©phane Ducasse

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

Sept. 27, 2010

Re: [Pharo-project] ('a' == 'a') == true ?

by StÃ©phane Ducasse

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

Sept. 27, 2010

Re: [Pharo-project] Update Pharo image to the last version

by StÃ©phane Ducasse

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

Sept. 27, 2010

[Pharo-project] [update 1.2] #12147

by Marcus Denker

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.

Sept. 27, 2010

Re: [Pharo-project] [Esug-list] [ANN] Glamour on Seaside - first version

by Alexandre Bergel

Really cool!!! It works well, even though I feel it can be faster. Cheers, Alexandre On 26 Sep 2010, at 17:15, Tudor Girba wrote: > 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 > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 27, 2010

Re: [Pharo-project] [Moose-dev] [ANN] Glamour on Seaside - first version

by Hannes Hirzel

On 9/26/10, Tudor Girba <tudor.girba(a)gmail.com> wrote: > 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 > Thank you. Where do I find the Seaside web server panel? http://localhost:8080 gives no answer. On which port does Seaside run? Regards --Hannes

Sept. 27, 2010

[Pharo-project] [ANN] pre-built 1.2 Core#12146

by Marcus Denker

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.

Sept. 27, 2010