- Pharo-dev - lists.pharo.org

[Pharo-project] New Pharo-dev AND web based on 10259

by Torsten Bergmann

Damien Cassou wrote: ><serge.stinckwich at gmail.com> wrote: >> ScriptLoader loadSuperOB. does not work in this image. > >It does not surprise me because this script is not maintained. Try to >execute only the parts that make sense: OB*, AST, Shout, eCompletion >and the refactorings tools are already installed. Yes - it gives a #DNU for #longDescriptions after loading into the newest pharo image (#10259) But you can easily implement OBCodeTabPanel#longDescriptions like this: longDescriptions ^#() That should work for now... Bye Torsten -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

March 25, 2009

[Pharo-project] Font update at image startup as preference

by Torsten Bergmann

fixed - see issue 689 (this time as a changeset for easier integration due to the massive unicode changes in the pharo inbox). -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

March 25, 2009

[Pharo-project] Using seaside.builder.st right from your image

by Torsten Bergmann

Thanks to Lukas there is a new feature in the builder.seaside.st allowing you to directly load a builder configuration within the image itself. (see conversation below). Using the three URL parameters (distribution, packages and download) you can now write: (HTTPSocket httpGet: 'http://builder.seaside.st/?distribution=Seaside%202.9.0-alpha3&packages=all…') fileIn to load Seaside29alpha3 package right from the (pharo) image. Tip: If you need a different configuration, use builder.seaside.st and have a look at the comment in the generated load script. At the beginning you will find the specific URL with all your packages. That should make loading Seaside even easier and help to automate loading/integration tests. Keep on talking small Torsten -------- Original-Nachricht -------- Datum: Tue, 24 Mar 2009 17:08:46 +0100 Von: Lukas Renggli <YYY(a)ZZZ.com> An: Torsten Bergmann <YYY(a)ZZZ.de> Betreff: Re: Seaside Builder Installer script I've added two new features: - The parameter 'download' directly downloads the chosen definition. The value of the parameter is the label on the download link in the UI, including whitespace. Example: ?download=Load%20Script - The parameter 'package' also allows the value 'all' to automatically select all available packages. The latest deployment is based on Seaside 2.9a3 and noticeably faster (mainly because of the new JQuery libraries). Lukas On Tue, Mar 24, 2009 at 4:26 PM, Torsten Bergmann <YYY(a)ZZZ.de> wrote: > Very helpful, thanks! > > Bye > Torsten > > -------- Original-Nachricht -------- >> Datum: Tue, 24 Mar 2009 15:20:33 +0100 >> Von: Lukas Renggli <YYY(a)ZZZ.com> >> An: Torsten Bergmann <YYY(a)ZZZ.de> >> Betreff: Re: Seaside Builder Installer script > >> > But is it also possible to get the script using this parameter >> > convention? If so this would be helpful to directly >> > load a specific configuration right from the image: >> > >> > Â something in the like of: >> > >> > (HTTPDocument getURL: >> "http://builder.seaside.st/?distribution=allmyselectedSS29Packages?script=lo…) fileIn >> >> Yes, that would be easy to add. >> >> I need to do a new deployment on based on Seaside 2.9a3 anyway (it is >> still running on Seaside 2.9a2). I will add that ASAP. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch > > -- > Aufgepasst: Sind Ihre Daten beim Online-Banking auch optimal geschÃ¼tzt? > Jetzt absichern: https://homebanking.gmx.net/?mc=mail@footer.hb > -- Lukas Renggli http://www.lukas-renggli.ch -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

March 25, 2009

[Pharo-project] Another MIME-related problem

by Igor Stasenko

Image is pharo-dev #10259 Try following: (Installer monticello http: 'http://scribo.aidaweb.si/repository') install: 'Scribo-np.172'. it says that 'unknown' mime type is invalid. I don't sure if it problem on a server side - Aida, or its because of changes to MIME.. Are 'unknown' mime type string is valid mime type? -- Best regards, Igor Stasenko AKA sig.

March 24, 2009

Re: [Pharo-project] Seaside Builder Installer script

by Keith Hodges

Torsten Bergmann wrote: > Hi Lukas, > > open builder.seaside.st and download an "Installer Script" from the advanced page. This is broken since Installer DNU #http: > > The generated pattern is > > (Installer http: 'someurl') > install: 'somepackeg' > > but should be > > (Installer monticello http: 'someurl') > install: 'somepackeg' > > This will work at least in latest Pharo. > > Maybe the builder could be extended to have a "Pharo" and a > "Squeak" script option. Now the installer is always loaded from > pbwiki at the beginning of the script. > > Installer should now be loaded from the latest in squeaksource. See how the LPF.st script does it. > If in Pharo it would be better to use "ScriptLoader new installingInstaller" which downloads the Installer using Monicello > and Squeaksource and allows to still have "Installer" as an MC package. > > Thx > Torsten > If I understand correctly ScriptLoader is a collection of scripts for loading things into Pharo. Installer was explicitly designed to be the first thing that you load into an image, even a kernel image, from which you can load everything else. Installer's is intended to be a way of publishing scripts that may load into different images (this is what LevelPlayingField uses) with different variants. This is now embodied in Installer-Scripts, so we have a duplication here. Now that we have Seaside29 with its complicated dependecies, we find the seaside crew developing their own way of handling this, since they obviously feel that Universes is not the way to go for their multiple target platforms. Sake/Packages was designed to be able to define packages with dependencies (so we have more duplication here), and to able to account for variations between the potential target images in which to load, AND for users to be able to add additional target variants of their own. If you want a load script that loads into an image without Sake/Packages loaded, it would be trivial to get Sake/Packages to generate one for your particular image/target, based upon its dependency knowledge, and this is the way that Bob will probably use to build Seaside29 one click images. Keith

March 24, 2009

[Pharo-project] Seaside Builder Installer script

by Torsten Bergmann

Hi Lukas, open builder.seaside.st and download an "Installer Script" from the advanced page. This is broken since Installer DNU #http: The generated pattern is (Installer http: 'someurl') install: 'somepackeg' but should be (Installer monticello http: 'someurl') install: 'somepackeg' This will work at least in latest Pharo. Maybe the builder could be extended to have a "Pharo" and a "Squeak" script option. Now the installer is always loaded from pbwiki at the beginning of the script. If in Pharo it would be better to use "ScriptLoader new installingInstaller" which downloads the Installer using Monicello and Squeaksource and allows to still have "Installer" as an MC package. Thx Torsten -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

March 24, 2009

Re: [Pharo-project] New Pharo-dev AND web based on 10259

by Damien Cassou

On Tue, Mar 24, 2009 at 4:55 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > ScriptLoader loadSuperOB. does not work in this image. It does not surprise me because this script is not maintained. Try to execute only the parts that make sense: OB*, AST, Shout, eCompletion and the refactorings tools are already installed. -- Damien Cassou http://damiencassou.seasidehosting.st

March 24, 2009

Re: [Pharo-project] Concurrent programming (was: Would you start a new Smalltalk project today?)

by Alexandre Bergel

Thanks Michael and Antony about this discussion. cheers, Alexandre On 23 Mar 2009, at 09:30, StÃ©phane Ducasse wrote: > Michael > there is no problem. > discussion is also good. Dogma or trolling would be boring :) > > On Mar 23, 2009, at 12:42 AM, Michael van der Gulik wrote: > >> >> >> On Mon, Mar 23, 2009 at 11:39 AM, Antony Blakey <antony.blakey(a)gmail.com >>> wrote: >> >> On 23/03/2009, at 7:37 AM, Michael van der Gulik wrote: >> >> >> >>> Smalltalk, the language rather than the implementation, already has >>> fantastic support for concurrency. Smalltalkers just don't know how >>> to use it. We don't need to rethink the model, we just need to learn >>> to use what we have. >> >> Mutexes and semaphores are hardly 'fantastic'. The state of the art >> in >> support for concurrency is way beyond what Smalltalk provides - >> locking is both primitive and generally not scalable. >> >> >> Semaphores _are_ fantastic!! Lock-free algorithms are even cooler. >> >> The language lends itself to building up higher abstractions. Take >> for example Collection and all its subclasses; they're screaming out >> to have parallelised versions made: >> >> c := ConcurrentOrderedCollection new. >> c do: [ :each | ...this part gets executed in parallel...]. >> >> The caveat here is that you need to be careful about side-effects. >> >> This is just one example. I have some more rudimentary ideas at: >> http://gulik.pbwiki.com/Parallel+processing. >> >> Oh, and sorry to the Pharo guys for keeping this going. Let us know >> if you don't want threads like this on your list. >> >> Gulik. >> >> >> -- >> http://gulik.pbwiki.com/ >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 24, 2009

Re: [Pharo-project] tooltips for inspector 'mystery' buttons

by Damien Cassou

On Mon, Mar 23, 2009 at 5:33 PM, Dale Henrichs <dale.henrichs(a)gemstone.com> wrote: > With 10259, there are tool tips for the 'mystery' buttons in the inspectors... > > If you have added a custom inspector method, you need to add #tooltip: to your pragama like the following for Object>>basicInspectorNodes: > > Â <inspector: #'1' priority: 600 toolTip: 'Basic elements'> Nice, thank you -- Damien Cassou http://damiencassou.seasidehosting.st

March 24, 2009

Re: [Pharo-project] Fwd: [squeak-dev] Kernel fixes

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=688 On Mar 24, 2009, at 8:50 AM, Michael Rueger wrote: > Hi all, > > haven't looked at it in detail so I don't know for example which > "other changes" are needed, but I think we definitely should integrate > the necessary fixes (if not done so already, hope I'm not proving > myself ignorant here ;-)). > > Any takers? > > Michael > > > > ---------- Forwarded message ---------- > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: Tue, Mar 24, 2009 at 4:34 AM > Subject: [squeak-dev] Kernel fixes > To: The general-purpose Squeak developers list > <squeak-dev(a)lists.squeakfoundation.org> > > > Folks - > > While fixing Semaphore>>waitTimeoutMSecs: in our internal images, I > noticed that 3.10 was still missing a number of important Kernel fixes > that we've long taken for granted. If you run servers or rely > otherwise on heavy process/delay/semaphore usage you will definitely > want to apply the fixes provided at > http://bugs.squeak.org/view.php?id=7321 > > To install, either download the patches or just execute: > > Installer mantis fixBug: 7321. > > Do note that these fixes apply only to 3.10 since they assume other > changes to be present (so they won't work against 3.9 for example). > Also, they depend on each other so unless you are really careful you > should not pick and choose (this is why they are filed as a single > bug). > > Cheers, > - Andreas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 24, 2009