January 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Smalltalk for small projects only?

by GÃ¶ran Krampe

On 01/29/2012 07:02 PM, Frank Shearar wrote: > - GSOC 2010 had a proposal > l(http://gsoc2010.esug.org/projects/git-mercurial) - Goran, did this > get off the ground? AFAIK, not really. regards, GÃ¶ran

Jan. 29, 2012

Re: [Pharo-project] Smalltalk for small projects only?

by GÃ¶ran Krampe

On 01/29/2012 05:02 PM, Sven Van Caekenberghe wrote: > PS: one of the things that we should take from git, as many others have said on this list, is selective commits. If I ever get around to picking up Deltas again it would make a really good tool to enable this on top of current MC (or any other tool of course). I do have an itch with Deltas but might end up pushing it into Amber first. regards, GÃ¶ran

Jan. 29, 2012

Re: [Pharo-project] Block explained continued

by Helene Bilbo

I read your text and am confused about "returing" _from_ or _to_ the homecontext and "escaping to" the homecontext. Do I understand it right this way: - As a block is executed always in it's home-context, when there is an explicit return statement inside the block, this return statement will also be executed in the home-context, which means this return statement makes the execution return *from* the home-context (*not* return from the context in which the value message was sent *to* the home-context?)? - The word 'continuation' is used when there is an explicit return statement in a block - It means the execution continues in the context "before" the home-context? -- View this message in context: http://forum.world.st/Block-explained-continued-tp4338472p4339548.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 29, 2012

Re: [Pharo-project] [squeak-dev] Re: [Smalltalk for small projects only?

by Otto Behrens

Oh, and make some changes in a file (method). Change the timestamp in the file to be more recent. Load the package. The change should be in your image. On Mon, Jan 30, 2012 at 12:46 AM, Otto Behrens <otto(a)finworks.biz> wrote: >> How can one try this out ? >> What to load/install ? > > I added something in the README: > > To use it, take a Pharo-1.3 image and just load MonticelloFileTree. > Open a monticello browser and select a package. +Repository has a new > menu item called "file tree"; select any directory on your PC. Save > the package there. You should see a directory <package name>.tree in > the directory after you saved. The GemStone-Extensions package > contains the gemstone hacks to make it work in GLASS. > > HTH

Jan. 29, 2012

[Pharo-project] [update 1.4] #14298

by Marcus Denker

14298 ----- Issue 5220: MenuRegistration do not allow menu with more than 2 levels of deapth http://code.google.com/p/pharo/issues/detail?id=5220 Issue 5222: mc slowdown with big package-cache http://code.google.com/p/pharo/issues/detail?id=5222 Issue 5182: Problem in PluggableListMorph http://code.google.com/p/pharo/issues/detail?id=5182 -- Marcus Denker -- http://marcusdenker.de

Jan. 29, 2012

Re: [Pharo-project] [squeak-dev] Re: [Smalltalk for small projects only?

by Otto Behrens

> How can one try this out ? > What to load/install ? I added something in the README: To use it, take a Pharo-1.3 image and just load MonticelloFileTree. Open a monticello browser and select a package. +Repository has a new menu item called "file tree"; select any directory on your PC. Save the package there. You should see a directory <package name>.tree in the directory after you saved. The GemStone-Extensions package contains the gemstone hacks to make it work in GLASS. HTH

Jan. 29, 2012

Re: [Pharo-project] loading Seaside 3.0.6.3 in Pharo 1.4

by Esteban Lorenzano

Hi, I just did (ConfiguurationOfSeaside project version: #stable) load. I don't know which version is metacello configuration loading. best, Esteban El 29/01/2012, a las 7:14p.m., Philippe Marschall escribiÃ³: > On 29.01.2012 21:23, Esteban Lorenzano wrote: >> Hi, >> >> I loaded last version of seaside into a pharo 1.4 image. >> Everything looks working fine, but there a couple of fixes: >> >> 1) >> >> KomLogger>>#attachTranscript >> self detachTheTranscript. >> ^(self streams detect: [:ea | ea isTranscriptStream] ifNone: [nil]) >> ifNil: [self addStream: TranscriptStream new] >> >> >> "TranscriptStream" is not anymore on pharo and should be replaced with ThreadSafeTranscript > > Are you using full Comanche or KomHttpServerLight? We moved to KomHttpServerLight because we involuntarily have to maintain it and the KomHttpServerLight code base is much smaller. KomHttpServerLight doesn't have the KomLogger class. > >> 2) String>>#withBlanksTrimmed is deprecated, and now it should use #trimBoth > > Who's sending this? I have no such senders (with KomHttpServerLight). > >> how can I proceed to apply this fixes into seaside (without breaking other platforms)? > > -> seaside-dev mailing list > > Cheers > Philippe > >

Jan. 29, 2012

Re: [Pharo-project] [squeak-dev] Re: [Smalltalk for small projects only?

by Sven Van Caekenberghe

Otto, On 29 Jan 2012, at 23:12, Otto Behrens wrote: > Some stuff in the README on the > https://github.com/finworks/smallsource. Let me know what you need. > I'm writing more as we speak... :-) How can one try this out ? What to load/install ? Thx, Sven

Jan. 29, 2012

Re: [Pharo-project] loading Seaside 3.0.6.3 in Pharo 1.4

by Philippe Marschall

On 29.01.2012 23:14, Philippe Marschall wrote: > On 29.01.2012 21:23, Esteban Lorenzano wrote: >> Hi, >> >> I loaded last version of seaside into a pharo 1.4 image. >> Everything looks working fine, but there a couple of fixes: >> >> 1) >> >> KomLogger>>#attachTranscript >> self detachTheTranscript. >> ^(self streams detect: [:ea | ea isTranscriptStream] ifNone: [nil]) >> ifNil: [self addStream: TranscriptStream new] >> >> >> "TranscriptStream" is not anymore on pharo and should be replaced with >> ThreadSafeTranscript > > Are you using full Comanche or KomHttpServerLight? We moved to > KomHttpServerLight because we involuntarily have to maintain it and the > KomHttpServerLight code base is much smaller. KomHttpServerLight doesn't > have the KomLogger class. Or Zinc since you're on Pharo 1.4 and already have Zinc anyway. Cheers Philippe

Jan. 29, 2012

Re: [Pharo-project] loading Seaside 3.0.6.3 in Pharo 1.4

by Philippe Marschall

On 29.01.2012 21:32, Guido Stepken wrote: > Marcus Denker IMHO is the only one, who is able to do a diff - diff - > diff (with his Moose tools) on VA, Pharo, Seaside Code to filter out a > adaption/portability layer between these Smalltalk and make future ports > of packets an ease!? > > SPORT was a great start, why was it discontinued??? To my knowledge SPort is not discontinued. It's still used for Swazoo and AFAIK Burce is also working on it. But you probably wanted to ask why Seaside doesn't use it. The short answer is that it doesn't quite solve the problems of Seaside. The long answer is, well longer. Cheers Philippe

Jan. 29, 2012