August 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Shout in Pharo 1.3

by StÃ©phane Ducasse

I would like to know too. Alain is on holiday else he could tell us. Can you open a ticket and put alain on cc? Stef > Does anybody has a version of Shout that correctly works in the > traditional tools in Pharo 1.3? > > I tried various versions of Shout, but could not find one that worked > correctly in the traditional tools. The problem I see is that Shout is > not properly setup/updated anymore, i.e. it does not callback to the > model (#shoutAboutToStyle:). When the browser/debugger changes the > method/definition/comment highlighting is not enabled/disabled and the > context is not changed. > > Does anybody have a working version of Shout and/or knows how to > easily make it work? > > It works in OB because I subclassed 3 editor classes and undone the > "new" way of how highlighting works. I thought I bring this up again, > because as far as I see there is still the same problem ... > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 9, 2011

[Pharo-project] Seaside on Pharo-Kernel

by Pavel Krivanek

Hi, there's possible to load Seaside to the Pharo-Kernel. 1) Load PharoKernel-Gofer image from CI server (https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Gofe…) 2) run the image with seaside.st script as an argument. That will create about 4.1 MB image with basic Seaside packages and basic examples. 3) run the image with run.st script (note that starting of the server in the seaside.st script will hang, currently I have no idea why). 4) see if everything works at http://localhost:8080/examples/examplebrowser Cheers, -- Pavel

Aug. 9, 2011

Re: [Pharo-project] On the way to 1.3 Release: images

by Marcus Denker

Thanks! > >> -> change the link >> http://www.pharo-project.org/pharo-download/unstable(-core) >> to point to the one jenkins build of 1.4 > > I changed /unstable-core to point to https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… > > I assume there is no /unstable build (yet)? > For 1.4, we want to not have multiple images anymore... this is really difficult to fix bugs in two images, it's hard to explain, it complicated harvesting fixes (two completely different ways), it confuses new people. So there is just one Pharo starting from 1.4 Right now, this is the same as what used to be the core image. But we will add everything there that is needed to make it that environment that we want to use for developing Pharo itself... >> >> -> clean up a bit, no need to have pages for old .1 release. > > On pharo-project.org? > yes... the page for 1.1.1 we should merge into the page for 1.1 (just to make it look cleaner) Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 9, 2011

Re: [Pharo-project] On the way to 1.3 Release: images

by Adrian Lienhard

Thanks, Marcus! On Aug 9, 2011, at 08:41 , Marcus Denker wrote: [...] > Next steps: [...] > -> change the links on pharo-project to point to these images for > http://www.pharo-project.org/pharo-download/stable > http://www.pharo-project.org/pharo-download/stable-core Done. > -> change the link > http://www.pharo-project.org/pharo-download/unstable(-core) > to point to the one jenkins build of 1.4 I changed /unstable-core to point to https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… I assume there is no /unstable build (yet)? > -> add a page or 1.3 on pharo-project.org I added a place holder with a link to the Wiki page http://www.pharo-project.org/pharo-download/release-1-3 It would be nice if we could move the text over and revise it a bit. Any taker? > > -> clean up a bit, no need to have pages for old .1 release. On pharo-project.org? Once we have the one-click image, we also need to update the download banner and the links on http://www.pharo-project.org/pharo-download Cheers, Adrian

Aug. 9, 2011

[Pharo-project] forward engineering UML models into Smalltalk code

by btc＠openInWorld.com

Aug. 9, 2011

Re: [Pharo-project] On the way to 1.3 Release: images

by Mariano Martinez Peck

On Tue, Aug 9, 2011 at 8:41 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Hi, > > So now we have images on Gforge that will be the release: > > Core: > > https://gforge.inria.fr/frs/download.php/28859/PharoCore-1.3-13298.zip > > Full: > https://gforge.inria.fr/frs/download.php/28860/Pharo-1.3-13298.zip > > > They are the ones build by Hudson, because magically the unix vm used > there reads cog images but saves interpreter images (didn't know that). > > I have just tested in Mac OS and it works with both, Cog and not Cog vms :) > So these images should even run on ancient VMs, as promised for 1.3. > > > Next steps: > > -> Build a one-click image. If nobody helps, I will do the same like > 1.2: > take the one of 1.2 and just copy some random VMs in there. > Worked > fine last time... > > I think Igor can help us to decide which VMs to use. I would use the latest stable of Jenkis. For the Windows VM, Torsten did some branding: http://forum.world.st/ANN-Customized-Cog-Win32-for-Pharo-1-3-based-on-Cog-r… However, that's not yet integrated to jenkis. Even more, that VM is "old" and I think the bug fixed in the last days is quite important. So I would try first to update ConfigurationOfCog and gitorious in order to get a last VM. I think Igor said he was going to do that. > -> change the links on pharo-project to point to these images for > http://www.pharo-project.org/pharo-download/stable > > http://www.pharo-project.org/pharo-download/stable-core > > -> change the link > > http://www.pharo-project.org/pharo-download/unstable(-core) > to point to the one jenkins build of 1.4 > > -> add a page or 1.3 on pharo-project.org > > -> clean up a bit, no need to have pages for old .1 release. > -> add actions done: http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotThree Maybe Laurent can help since he has access :) > > > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Mariano http://marianopeck.wordpress.com

Aug. 9, 2011

[Pharo-project] On the way to 1.3 Release: images

by Marcus Denker

Hi, So now we have images on Gforge that will be the release: Core: https://gforge.inria.fr/frs/download.php/28859/PharoCore-1.3-13298.zip Full: https://gforge.inria.fr/frs/download.php/28860/Pharo-1.3-13298.zip They are the ones build by Hudson, because magically the unix vm used there reads cog images but saves interpreter images (didn't know that). So these images should even run on ancient VMs, as promised for 1.3. Next steps: -> Build a one-click image. If nobody helps, I will do the same like 1.2: take the one of 1.2 and just copy some random VMs in there. Worked fine last time... -> change the links on pharo-project to point to these images for http://www.pharo-project.org/pharo-download/stable http://www.pharo-project.org/pharo-download/stable-core -> change the link http://www.pharo-project.org/pharo-download/unstable(-core) to point to the one jenkins build of 1.4 -> add a page or 1.3 on pharo-project.org -> clean up a bit, no need to have pages for old .1 release. Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 9, 2011

Re: [Pharo-project] PharoCore 1.3: Transcript Ctrl+S broken

by Marcus Denker

On Aug 9, 2011, at 7:58 AM, Lukas Renggli wrote: > Generally building an image should not stress SqueakSource much because all packages are cached (at lest if you use a simple gofer script). For a complete Seaside 3.0 build this is typically no more than a few requests (listing + the packages that changed). > > So this means that I should search on gforge to get the latest working version? > Ah, no.... the http://www.pharo-project.org/pharo-download/unstable-core actually points to the build server and should be up to date. (this is for the unstable, only stable points to gforge). So for tracking the latest, http://www.pharo-project.org/pharo-download/unstable-core is good. (even for stable, as this does not change and so gforge is up to date). We need to release 1.3, I am getting confused about everything. Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 9, 2011

Re: [Pharo-project] PharoCore 1.3: Transcript Ctrl+S broken

by Lukas Renggli

Generally building an image should not stress SqueakSource much because all packages are cached (at lest if you use a simple gofer script). For a complete Seaside 3.0 build this is typically no more than a few requests (listing + the packages that changed). So this means that I should search on gforge to get the latest working version? Lukas On Tuesday, 9 August 2011, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Aug 9, 2011, at 7:28 AM, Lukas Renggli wrote: > >> Ahh ok, I will rebuild my images then. I was using the ../unstable-core URL. >> > > Yes, this points to gforge and laggs the very latest by around 10 updates. The image > is always one that we know is not completely broken. (because very last update could > be not in a good state). > > The other reason is that Hudson needs to start somewhere... and loading update is > slow and tends to stress squeaksource. So Hudson takes the gforge image as a starter. > > Of course all that is done by hand (me uploading, me changing links... or even having > to tell Adrian to change links). > > This is all not perfect, but there is always the question: Do we stop to improve Pharo > until the process is perfect or do we do both in parallel? > > This can and will all be improved, step by step. > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 9, 2011

Re: [Pharo-project] PharoCore 1.3: Transcript Ctrl+S broken

by Marcus Denker

On Aug 9, 2011, at 7:28 AM, Lukas Renggli wrote: > Ahh ok, I will rebuild my images then. I was using the ../unstable-core URL. > Yes, this points to gforge and laggs the very latest by around 10 updates. The image is always one that we know is not completely broken. (because very last update could be not in a good state). The other reason is that Hudson needs to start somewhere... and loading update is slow and tends to stress squeaksource. So Hudson takes the gforge image as a starter. Of course all that is done by hand (me uploading, me changing links... or even having to tell Adrian to change links). This is all not perfect, but there is always the question: Do we stop to improve Pharo until the process is perfect or do we do both in parallel? This can and will all be improved, step by step. Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 9, 2011