- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Your earlier problems accessing Monticello

by Benjamin

If a slice is proposed, you should "resolve" the case which flags the issue as Fix Review Needed :) Ben On Apr 23, 2013, at 7:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 23 Apr 2013, at 19:18, Guido Chari <charig(a)gmail.com> wrote: > >> Sorry for the delay, but yes i confirm this solves my issue. > > Thanks, that is good to know ! > >> What i see is that it is not yet integrated into 3.0 > > Yeah, it is ready for inclusion, maybe I gave it the wrong status. > > https://pharo.fogbugz.com/default.asp?10102 > https://pharo.fogbugz.com/f/cases/10102/SocketStream-next-should-not-signal… > >> Cheers, >> Guido. >> >> >> 2013/3/23 Guido Chari <charig(a)gmail.com> >> Yes, i'm sure this will do the fix. Nevertheless, as soon as i come back home i will send you the confirmation. >> >> Thanks >> >> >> 2013/3/23 Camillo Bruni <camillobruni(a)gmail.com> >> Guido is right now in Lille :P so you have to wait for a week. >> From what I recall it was exactly that bug we had over in Argentina :) >> >> On 2013-03-23, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> Hi Guido, >>> >>> Some time ago you were unable to access Monticello from inside your particular network situation. >>> >>> http://forum.world.st/Unable-to-use-Monticello-in-last-images-from-Jenkins-… >>> >>> We just were able to solve a similar case. >>> >>> http://forum.world.st/Problem-downloading-packages-with-Monticello-from-Sma… >>> >>> Would it be possible to verify, first that your old problem still exists, and then try again with the following patch. >>> >>> SocketStream>>next: count >>> "Read count elements and return them in a collection. >>> If the receiver is #atEnd before count elements were read, return a smaller collection." >>> >>> ^ self nextInto: (self streamBuffer: count) >>> >>> That would be most helpful. >>> >>> Thx, >>> >>> Sven >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >>> >> >> >> >> > >

April 23, 2013

Re: [Pharo-project] Your earlier problems accessing Monticello

by Sven Van Caekenberghe

On 23 Apr 2013, at 19:18, Guido Chari <charig(a)gmail.com> wrote: > Sorry for the delay, but yes i confirm this solves my issue. Thanks, that is good to know ! > What i see is that it is not yet integrated into 3.0 Yeah, it is ready for inclusion, maybe I gave it the wrong status. https://pharo.fogbugz.com/default.asp?10102 https://pharo.fogbugz.com/f/cases/10102/SocketStream-next-should-not-signal… > Cheers, > Guido. > > > 2013/3/23 Guido Chari <charig(a)gmail.com> > Yes, i'm sure this will do the fix. Nevertheless, as soon as i come back home i will send you the confirmation. > > Thanks > > > 2013/3/23 Camillo Bruni <camillobruni(a)gmail.com> > Guido is right now in Lille :P so you have to wait for a week. > From what I recall it was exactly that bug we had over in Argentina :) > > On 2013-03-23, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Guido, > > > > Some time ago you were unable to access Monticello from inside your particular network situation. > > > > http://forum.world.st/Unable-to-use-Monticello-in-last-images-from-Jenkins-… > > > > We just were able to solve a similar case. > > > > http://forum.world.st/Problem-downloading-packages-with-Monticello-from-Sma… > > > > Would it be possible to verify, first that your old problem still exists, and then try again with the following patch. > > > > SocketStream>>next: count > > "Read count elements and return them in a collection. > > If the receiver is #atEnd before count elements were read, return a smaller collection." > > > > ^ self nextInto: (self streamBuffer: count) > > > > That would be most helpful. > > > > Thx, > > > > Sven > > > > -- > > Sven Van Caekenberghe > > http://stfx.eu > > Smalltalk is the Red Pill > > > > > > > >

April 23, 2013

Re: [Pharo-project] (was: Moose-dev) #stable and Metacello

by Dale Henrichs

Diego, I realize that you may not like the name #stable, but the mechanism behind #stable is what you want. In current usage, the #stable version is the 'recommended version'..... Dale ----- Original Message ----- | From: "Diego Lont" <diego.lont(a)delware.nl> | To: pharo-project(a)lists.gforge.inria.fr | Sent: Monday, April 22, 2013 5:39:19 AM | Subject: Re: [Pharo-project] (was: Moose-dev) #stable and Metacello | | Dale, Stef, | | I like to have "a recommended version" as default and not #'stable'. Because | I still want to recommend a version, even is this isn't stable. I can use | the blessings to mark it as "development" or "release". | | Using a 'recommended version' also makes it clear, that it depends on the | project (both using as used) wether is is wise to use this version or not. | For Moose 4.8 the 'recommended version' is the release candidate. | | Diego | | On Apr 18, 2013, at 9:55 PM, stephane ducasse wrote: | | > | > On Apr 18, 2013, at 6:29 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: | > | >> Stef, | >> | >> I think it is clear that #stable is not the right name, but I also think | >> it is better to have one "badly named," commonly used symbolic version | >> rather than a bunch of different names for the same thingâ¦ | > | > yes | > but this can be confusing. | >> Eventually we should change the convention, but I don't think we need to | >> hurry and do so:) | > | > first we need a tool to manage configuration for real. | > | > Stef | > | >> | >> Dale | >> | >> ----- Original Message ----- | >> | From: "stephane ducasse" <stephane.ducasse(a)free.fr> | >> | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> | >> | Sent: Wednesday, April 17, 2013 10:04:50 PM | >> | Subject: [Moose-dev] Re: #stable and Metacello (was Re: | >> | ConfigurationOfGlamourSeaside) | >> | | >> | Dale | >> | | >> | I thought that stable should be called milestoneDevelopment. | >> | I will add a note to the metacello chapter and versionner will handle | >> | the | >> | patterns we see. | >> | | >> | Stef | >> | |

April 23, 2013

Re: [Pharo-project] [squeak-dev] Metacello Preview

by Dale Henrichs

Some status: The Preview is functional (all tests passing:) on GemStone (included in base for GLASS 1.0-beta.9), Squeak 4.3 through 4.5 (is Squeak4.5 the trunk?) and Pharo 1.1 through 1.4. Christophe Demarey is helping me port the Metacello Preview/Metacello Scripting API to Pharo2.0. For the Squeak guys ... I did finally address the bug that was bugging me, but I'm still interested in some real world feedback ... There are a handful of users, but I haven't gotten enough bug reports to satisfy me that it is being beaten on:) Dale ----- Original Message ----- | From: "DeNigris Sean" <sean(a)clipperadams.com> | To: pharo-project(a)lists.gforge.inria.fr, "The general-purpose Squeak developers list" | <squeak-dev(a)lists.squeakfoundation.org> | Sent: Tuesday, April 23, 2013 9:15:40 AM | Subject: [squeak-dev] Metacello Preview | | [cross posted to pharo-project and squeak-dev] | | Dale has done some really cool work on Metacello! From the original | announcement at | http://forum.world.st/Metacello-Preview-release-1-0-beta-32-2-td4642064.html | : | | | The Metacello Preview release provides the following features: | | - Metacello Scripting API (user guide[1] and reference[2]) | - Metacello-Base package for inclusion in Squeak/Pharo base images | - support for git and GitHub (filetree:// and github:// repository loaded) | | In typical Dale fashion, he wants to provide our community with as much value | as possible, so he's been tentative to release his "preview" version until | he gets feedback from users and can tailor it to our real-world needs. | | I feel, after checking with Dale, that integrating the preview into Pharo and | Squeak trunk now will provide a balance between exposure and malleability, | to make sure we have an API we'll all love by the next respective releases. | | Cheers, | Sean | | |

April 23, 2013

Re: [Pharo-project] Your earlier problems accessing Monticello

by Guido Chari

Sorry for the delay, but yes i confirm this solves my issue. What i see is that it is not yet integrated into 3.0 Cheers, Guido. 2013/3/23 Guido Chari <charig(a)gmail.com> > Yes, i'm sure this will do the fix. Nevertheless, as soon as i come back > home i will send you the confirmation. > > Thanks > > > 2013/3/23 Camillo Bruni <camillobruni(a)gmail.com> > >> Guido is right now in Lille :P so you have to wait for a week. >> From what I recall it was exactly that bug we had over in Argentina :) >> >> On 2013-03-23, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> > Hi Guido, >> > >> > Some time ago you were unable to access Monticello from inside your >> particular network situation. >> > >> > >> http://forum.world.st/Unable-to-use-Monticello-in-last-images-from-Jenkins-… >> > >> > We just were able to solve a similar case. >> > >> > >> http://forum.world.st/Problem-downloading-packages-with-Monticello-from-Sma… >> > >> > Would it be possible to verify, first that your old problem still >> exists, and then try again with the following patch. >> > >> > SocketStream>>next: count >> > "Read count elements and return them in a collection. >> > If the receiver is #atEnd before count elements were read, return >> a smaller collection." >> > >> > ^ self nextInto: (self streamBuffer: count) >> > >> > That would be most helpful. >> > >> > Thx, >> > >> > Sven >> > >> > -- >> > Sven Van Caekenberghe >> > http://stfx.eu >> > Smalltalk is the Red Pill >> > >> > >> >> >> >

April 23, 2013

[Pharo-project] Metacello Preview

by DeNigris Sean

[cross posted to pharo-project and squeak-dev] Dale has done some really cool work on Metacello! From the original announcement at http://forum.world.st/Metacello-Preview-release-1-0-beta-32-2-td4642064.html : > The Metacello Preview release provides the following features: > > - Metacello Scripting API (user guide[1] and reference[2]) > - Metacello-Base package for inclusion in Squeak/Pharo base images > - support for git and GitHub (filetree:// and github:// repository loaded) In typical Dale fashion, he wants to provide our community with as much value as possible, so he's been tentative to release his "preview" version until he gets feedback from users and can tailor it to our real-world needs. I feel, after checking with Dale, that integrating the preview into Pharo and Squeak trunk now will provide a balance between exposure and malleability, to make sure we have an API we'll all love by the next respective releases. Cheers, Sean

April 23, 2013

[Pharo-project] [update 3.0] #30056

by Esteban Lorenzano

30056 ----- 10363 Boolean clean up https://pharo.fogbugz.com/f/cases/10363 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/NativeBoost-Core-EstebanLore…

April 23, 2013

[Pharo-project] [update 3.0] #30055

by Marcus Denker

April 23, 2013

Re: [Pharo-project] A Pharo launcher

by Damien Cassou

On Tue, Apr 23, 2013 at 3:34 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Is that just me or I expected to be able to do that from the configurations > browser ? yes and no. The problem is that Pharo takes ages to load a configuration in the image. Also, I would like to use this launcher as the main entry point. I want to get a list of the recent images used for example. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 23, 2013

Re: [Pharo-project] A Pharo launcher

by Goubier Thierry

Is that just me or I expected to be able to do that from the configurations browser ? Start bare image, read nice description of all sorts of interesting stuff, select configuration, choose install and save image... Including the option to get a production server (i.e. trimForRelease if appropriate). Thierry Le 23/04/2013 00:21, Sven Van Caekenberghe a Ã©crit : > Excellent idea, good list of features. > > I like the idea of writing this tool in Pharo itself: eating your own dogfood and more flexibility. > > Sven > > On 22 Apr 2013, at 18:14, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> I think the idea to have a Pharo launcher that lets the user pick a >> Pharo template (either bare pharo 2.0, pharo+seaside, >> pharo+seaside+mongodb+ >> magritte+voyage, pharo+pier, ...) and then create >> a new image the user must save somewhere is important. I want people >> to have one Pharo icon on their desk and just click it (like in >> Eclipse, word processors, virtual box...). Here is a set of >> requirements for such an application, please comment. >> >> - must be implemented in Pharo 2.0 with maintained technology (spec or glamour) >> - must be cross-platform (we want 1 application for all Pharo users) >> - must download the list of templates from internet (so that we don't >> have to update the application all the time) >> - must propose different kinds of template (stable/unstable, desktop/web) >> - must rapidly create an image out of the selected template (either by >> downloading Fueled packages, or by downloading ready-made images) >> - must cache the created images so that they do not have to be >> recreated all the time (except when a newer version is available) >> - must force the user to copy the created image so he can freely >> change it and crash it without impacting the cache of created images. >> - must present a list of recently launched images so that the user can >> just pick a recent image instead of creating a new one >> >> >> Please comment (and implement this idea) >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

April 23, 2013