February 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by Marcus Denker

On 25.02.2009, at 19:59, Keith Hodges wrote: > Oscar Nierstrasz wrote: >> Hi Folks, >> >> I spent some time yesterday together with Stef to take a closer look >> at the Pharo scripting project. >> >> We have repackaged and renamed the project as "Coral". It is >> available >> on SqueakSource at: >> >> http://www.squeaksource.com/Coral >> >> > I really didnt understand what Coral Saphire was all about, in > InstallerLauncher you could ask squeak to execute a script and > output to > stdout. When I looked at Saphir I could see all sorst of parsers etc. > Whats it all for? Having a grammar? Smalltalk has no language element to define classes and methods. There is only "fileout" syntax. (expressions seperated by ! that get evaluated when loaded). Nobody wants to write scripts that way. And the proof is that nobody does it. Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

John M McIntosh wrote: > So does contentType -> ^self somthing mimeType yes, should really be in the compatibility category Michael

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by John M McIntosh

So does contentType -> ^self somthing mimeType On 25-Feb-09, at 12:03 PM, Michael Rueger wrote: > Hi all, > > ok, suggestion: > if we change Kom and Seaside to use the message contentType where they > expect a mime type string, then it would be easy to make it work on > both > Pharo and Squeak without too much trouble. > Seaside doesn't call mimeType on many places and usage is somewhat > inconsistent right now as in > httpResponse contentType = aHandler mimeType > > Comments? Suggestions? > > Michael -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

Hi all, ok, suggestion: if we change Kom and Seaside to use the message contentType where they expect a mime type string, then it would be easy to make it work on both Pharo and Squeak without too much trouble. Seaside doesn't call mimeType on many places and usage is somewhat inconsistent right now as in httpResponse contentType = aHandler mimeType Comments? Suggestions? Michael

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

John M McIntosh wrote: > Ok, well it seems to me having KOM and pharo working is *very* > important, actually > I'm relying on that for a meeting I'm having on friday. Obviously I'll > use a version of > Pharo from last month... > > Going forward you can burn all those bridges, but I'm not sure people > supporting that > other non-pharo stuff would care. > > Could you have a shim layer that is loaded to respect KOM's > expectations for behaviour? > Well or otherwise built a completely new MIME system for Pharo and let > KOM continue > with the obsolete one? The changes are actually not many, but at a few critical points they matter and Kom is very aggressive in overriding stuff. That makes it hard coming up with an intermediate layer. But working on it :-) Michael

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

Lukas Renggli wrote: > I am not criticizing your effort to make Kom work on Pharo. I fully > agree with you that Pharo should move forward and if necessary break > backward compatibility. My question was only if this was the case with > the changes on Kom. Not in the current version. I'm looking at it again, had some ideas this morning how to make it work for now. Michael

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by John M McIntosh

Ok, well it seems to me having KOM and pharo working is *very* important, actually I'm relying on that for a meeting I'm having on friday. Obviously I'll use a version of Pharo from last month... Going forward you can burn all those bridges, but I'm not sure people supporting that other non-pharo stuff would care. Could you have a shim layer that is loaded to respect KOM's expectations for behaviour? Well or otherwise built a completely new MIME system for Pharo and let KOM continue with the obsolete one? On 25-Feb-09, at 10:13 AM, Michael Rueger wrote: > Michael Rueger wrote: >> Lukas Renggli wrote: >>>> what seasiders think? >>>> I would be in favor to get a KOM pharo version >>> Having two incompatible versions of Kom makes distribution even more >>> painful as it is today. I would prefer to have compatible versions >>> if >>> this is possible. > > I will see that I can get Pharo, Kom and Squeak compatible enough for > now, no point in riding this out on principle. > > Nevertheless the issue still stands, that at some point we have to > make > that decision. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Feb. 25, 2009

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by Keith Hodges

Oscar Nierstrasz wrote: > Hi Folks, > > I spent some time yesterday together with Stef to take a closer look > at the Pharo scripting project. > > We have repackaged and renamed the project as "Coral". It is available > on SqueakSource at: > > http://www.squeaksource.com/Coral > > I really didnt understand what Coral Saphire was all about, in InstallerLauncher you could ask squeak to execute a script and output to stdout. When I looked at Saphir I could see all sorst of parsers etc. Whats it all for? Keith

Feb. 25, 2009

Re: [Pharo-project] MessageNotUnderstood: UndefinedObject>>includes:

by Hilaire Fernandes

2009/2/25 Matthew Fulmer <tapplek(a)gmail.com>: > Don't mess with morphic from threads other than the UI thread. > Don't add morphs. Don't run World doOneCycle. Ah, the black art of Morph... Thanks for the tip bellow, it helps a lot. > > The proper way to do this is to inject events into the UI > thread: > > WorldState addDeferedUIMessage: > [MyMorph new openInWorld] > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Feb. 25, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Lukas Renggli

>> Having two incompatible versions of Kom makes distribution even more >> painful as it is today. I would prefer to have compatible versions if >> this is possible. > > As I said, we are at or at least close to the point where we have to > make the decision which version to support. If you want to have Pharo > stay compatible with Squeak, we can just as well abandon Pharo now. > It's as simple as that. I am not criticizing your effort to make Kom work on Pharo. I fully agree with you that Pharo should move forward and if necessary break backward compatibility. My question was only if this was the case with the changes on Kom. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 25, 2009