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

Re: [Pharo-project] About AXAnnouncements (was: some Announcements related questions)

by Alexandre Bergel

> http://axdemo.seasidehosting.st/ I get a: Error: "/seaside/" not found. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 30, 2009

Re: [Pharo-project] Is serving files different in Pharo?

by Michael Rueger

Torsten Bergmann wrote: > Mart-Mari Breedt wrote on Pharo list [1] >> I got the answer to my problem here: http://bugs.squeak.org/view.php?id=7397 >> > > Why isnt the fix included into KomServer by default > or the implementation in pharo changed by default? the implementation in Phao changed. asUrl shouldn't be used anymore. There are already one or two other places where seaside takes care of differences between Pharo and Squeak IIRC. But isn't Pharo now the default platform for seaside? Michael > > Pharo has: > > mimeType > ^MIMEDocument guessTypeFromName: self name. > > The fix is > > mimeType > ^MIMEDocument guessTypeFromName: self asUrl > > Should we or seaside dev care? > > Bye > T. > > [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-October/015314.ht…

Oct. 30, 2009

[Pharo-project] Is serving files different in Pharo?

by Torsten Bergmann

Mart-Mari Breedt wrote on Pharo list [1] > >I got the answer to my problem here: http://bugs.squeak.org/view.php?id=7397 > Why isnt the fix included into KomServer by default or the implementation in pharo changed by default? Pharo has: mimeType ^MIMEDocument guessTypeFromName: self name. The fix is mimeType ^MIMEDocument guessTypeFromName: self asUrl Should we or seaside dev care? Bye T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-October/015314.ht… -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02

Oct. 30, 2009

Re: [Pharo-project] Is serving files different in Pharo?

by Mart-Mari Breedt

Hallo, I got the answer to my problem here: http://bugs.squeak.org/view.php?id=7397 Kind regards, Mart-Mari -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mart-Mari Breedt Sent: 29 October 2009 03:46 PM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Is serving files different in Pharo? Hallo, I have just install and started playing a bit with Pharo today. The first thing I tried was to take one of my Seaside projects from Squeak and see if I can get it going in Pharo? Everything went very smoothly, except for the following annoying problem - which I - rather embarrassingly - can't seem to figure out myself. Any help/hints/pointers will be greatly appreciated. For my Squeak/Seaside project I've subclassed WAKomEncoded and have overridden the createService selector to allow for a custom entry point and the ability to serve files from this point. createService | basePath seaside assembly | basePath := 'encore'. seaside := self entryPoint: (WADispatcher default setName: basePath). assembly := ModuleAssembly core. assembly serverRoot: FileDirectory default fullName. assembly alias: '/' , basePath to: [assembly addPlug: [:request | seaside process: request]]. assembly documentRoot: FileDirectory default fullName. assembly directoryIndex: 'index.html index.htm'. assembly serveFiles. ^ (HttpService startOn: port named: 'comanche') plug: assembly rootModule; yourself. The custom entry point still works fine, but for some strange reason none of my files are served correctly. Is there a different approach to serving files from within Pharo/Seaside that I should make use of? I have downloaded and used this Pharo package: pharo1.0-10491-rc1dev09.10.5.zip. And installed these additional packages: DynamicBindings-GiovanniCorriga.10.mcz KomHttpServer-GiovanniCorriga.50.mcz KomServices-gc.19.mcz OSProcess-dtl.53.mcz Seaside2.8a1-lr.594.mcz Scriptaculous-lr.250.mcz HTML5-mb.10.mcz Thanks in advance! Kind regards, Mart-Mari LTE USA â09, 4-5 November (non exhibitor) Click mailto:events@aircominternational.com?subject=LTE%20USA%20'09%20%20meeting%20request to book a meeting AfricaComâ09, 11-12 November stand C13, Cape Town, South Africa Click mailto:events@aircominternational.com?subject=AfricaCom%20meeting%20request to book a meeting Disclaimer: This e-mail message is confidential and should not be used by, or disclosed to, anyone except the addressee. If you receive this message in error, please advise the sender immediately.. Since e-mail transmission is not secure or error free, we do not accept responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your systems. You should therefore virus-check all attachments before opening. AIRCOM may monitor incoming and outgoing emails through its networks and by responding to this email, you consent to such monitoring. The views and opinions expressed in this e-mail are those of the author only and not of AIRCOM. We do not intend to enter into any legal commitments or contracts by e-mail. P Save a tree. Don't print this e-mail unless it's really necessary

Oct. 30, 2009

[Pharo-project] New Pharo based on core 10492

by Damien Cassou

http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 30, 2009

Re: [Pharo-project] Making packages shipped with Pharo ready for 1.0

by Damien Cassou

On Tue, Oct 27, 2009 at 10:22 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Damien will certainly pick up the gofer script you posted. > > Indeed, OB-Web is loaded and obviously should not. Also we should > check that the version of OB is the newest one. I'm building the November images right now with all the updated packages. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 30, 2009

Re: [Pharo-project] Making packages shipped with Pharo ready for 1.0

by Damien Cassou

On Tue, Oct 27, 2009 at 5:04 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > BTW, Damien, do we know for each package who the maintainer is? Does > each package have one? I've updated http://code.google.com/p/pharo/wiki/Packages with the known maintainers. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 30, 2009

Re: [Pharo-project] About AXAnnouncements (was: some Announcements related questions)

by Lukas Renggli

> Just to make things clear, AXAnnouncements > - is not "a port of the original announcement implementation" Ok, excellent. Just trying to avoid possible issues. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 30, 2009

Re: [Pharo-project] Hashed collection improvements: Some code

by Martin McClure

Andres Valloud wrote: > Nicolas, > > Would you like Martin's approach better if the selector was > #basicIdentityHash instead of #primIdentityHash? Is it a matter of > naming only, or is there something else? > > Andres. > > Nicolas Cellier wrote: >> After-thoughts: my opinion is: >> Martin solution is more pragmatical : it is tailored for getting most >> improvment with minimal change in system. >> But formally, I prefer Andres design for it's clarity. >> - I do not like the idea that #identityHash and #primIdentityHash do >> behave differently >> - #scaledIdentityHash does clearly express itself on the contrary >> But that turns into german discussions ;) My thoughts in choosing the naming: #identityHash Answers a value with a good range, suitable for general use, can be used in code that is portable across Smalltalk dialects. Today the range is not good across all dialects, but maybe this will improve if we start the movement here in Pharo). #primIdentityHash Used (almost) only by ProtoObject>>identityHash. Has a limited range; that range might get better when VM/image format changes. Could also be used by packages that want to do something very special and don't care that they will not be portable across dialects. The use in MethodDictionary is an example of this special non-portable use. I'd certainly be open to a better name for #primIdentityHash. Regards, -Martin

Oct. 30, 2009

[Pharo-project] About AXAnnouncements (was: some Announcements related questions)

by Levente Uzonyi

Hi! Just to make things clear, AXAnnouncements - is not "a port of the original announcement implementation" - is (more or less) based on Vassili Bykov's blog (http://www.cincomsmalltalk.com/userblogs/vbykov/blogView?searchCategory=Ann…) just like the Announcements package in Pharo - is released under the MIT license (http://www.squeaksource.com/AXAnnouncements.html) We implemented the framework as the blog entries came out and integrated it into our rudimentary ajax framework (that's where the AX prefix came from). Later we abandoned the ajax framework but found announcements really useful (especially with seaside components), so we extracted the code and moved it to squeaksource. Our ajax framework demo was available at http://axdemo.seasidehosting.st/. For a quick comparison: AXAnnouncements is bloated and has lower code quality than Announcements, but it implements more features, like suspension and interception of announcements, weak subscriptions and allows different base class for the announcements hierarchy per announcer. Cheers, Levente

Oct. 30, 2009