June 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] HTML Parser

by GermÃ¡n Arduino

Trying PetitParser of Lukas. Seems to work ok to my current (small) html needs. Cheers. 2010/6/30 GermÃ¡n Arduino <garduino(a)gmail.com>: > Hi: > > I used to use HTML Parser on squeak, a package of Avi and Julian if I > not bad remember. That package needed Yaxo also. > > What are using on Pharo to parsing HTML on these days? > > Thanks. > > -- > ================================================= > GermÃ¡n S. Arduino Â <gsa @ arsol.net> Â Twitter: garduino > Arduino Software & Web Hosting Â http://www.arduinosoftware.com > PasswordsPro Â http://www.passwordspro.com > ================================================= >

June 30, 2010

[Pharo-project] HTML Parser

by GermÃ¡n Arduino

Hi: I used to use HTML Parser on squeak, a package of Avi and Julian if I not bad remember. That package needed Yaxo also. What are using on Pharo to parsing HTML on these days? Thanks. -- ================================================= GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================

June 30, 2010

Re: [Pharo-project] CLFramework and Pharo

by Rob Rothwell

Message: 5 > Date: Wed, 30 Jun 2010 23:50:24 +0200 > From: St?phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] CLFramework and Pharo > To: Pharo-project(a)lists.gforge.inria.fr > Message-ID: <77E6AD68-79FF-4590-9FB6-7B2E1C961001(a)inria.fr> > Content-Type: text/plain; charset=iso-8859-1 > > But you rely on XML. > Second the builder (ie generating the XML) is not the problem as far as I > know. > but more how to assemble the widget and make sure that the layout > are kept or specified. > > Then how using an external tools can make sure that this tool got well the > way layoutMorph > and other works? > > Stef > > > My knowledge is limited, but XML seems more portable than code Smalltalk. > > I do not understand why we want portability. > Please note that the VWspec are as portable as XML between Smalltalk they > are just arrays ( > probably we would get a problem for the UI.Node notation but this is not > the problem. > Another place to see such an example is Smalltalk/X. I think they conformed to the VW Specs as well... Rob

June 30, 2010

[Pharo-project] [update 1.2] #12026

by StÃ©phane Ducasse

12026 ----- - Issue 2069: Be able to load DummyUIManager in a Pharo image. Part two

June 30, 2010

[Pharo-project] NoSQL binding status and more (was Re: ESUG will sponsor the XMLRPC project!)

by GÃ¶ran Krampe

Hi! On 06/30/2010 10:36 PM, Adrian Lienhard wrote: > Taking about more future oriented stuff, I think it would be nice to have good support for document DBs (like CouchDB and MongoDB) and key/value stores (like Redis). > At least for the former category of DBs, I know that a few people have been working on DB clients (see squeaksource.com) but I don't know how complete and stable they are. > > Adrian Braindump: For CouchDB there are two client libs on SS, one based on Curl and the other straight on SocketStream. Both are... quite limited, but I think they are pretty stable since the CouchDB API is RESTful its kinda easy. MongoDB has MongoTalk on SS by no other than Kent Beck. It looks quite ambitious and with a single little tweak the tests went green for me. MongoDB has IMHO more "buzz" right now and CouchDB seems slightly "stalling". I would guess MongoDB will grab more and more developer mindshare as time goes by, since it fits better with most apps actually. I am not aware of any binding for Redis. And yes, Redis is "neat" in its own way. I wrote a quite ambitious binding for Tokyo Tyrant, its on SS and has tests too. I think it is stable, but I am not that interested currently. My next little project in this arena would be a binding for Riak, since I think it is next to MongoDB and CouchDB one of the more interesting ones out there. It also has a RESTful API just like CouchDB and using WebClient seems logical these days. Finally I think another *hole* in our toolshed is support for all the funky new cool MQ products. I started implementing STOMP the other day and it will just take an hour or two to get it finished. Yes, there is an AMQP protocol implementation on SS, but I found it... quite undocumented. Given the author it is probably very correct though. regards, GÃ¶ran

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024 (new version)

by Mariano Martinez Peck

On Wed, Jun 30, 2010 at 11:54 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Yes I will! > > Stef > > > We are reaching 2.2 MB with shrinking based on this classes structure. > > Stay tuned :-) > > I like when I hear that. This will start to be really sexy. > And it would be incredible much more sexy if we can load the network package (and maybe monticello). Having a PharoKernel of 2.2 where I can then load network/monticello is a dream. Then I can deploy a Pharo production seaside image of a couple of MB Hilarie do you know how far we are from that dream? > > > I will create the next patches for methods > > reorganization. > > > > Please don't forget the second part of this fix: > > http://code.google.com/p/pharo/issues/detail?id=2069 > > > > Many thanks! > > -- Pavel > > > > On Wed, Jun 30, 2010 at 9:58 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > >> 12024 > >> ----- > >> > >> - Issue 2105: Packages remodularization > >> > >> and now without obsolete classes > >> > >> Stef (thanks Pavel) > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024 (new version)

by StÃ©phane Ducasse

> Please don't forget the second part of this fix: > http://code.google.com/p/pharo/issues/detail?id=2069 I read all the code. I will integrate it now. I forgot to fix a Smalltalk at: instead of Smalltalk globals at: in Runarray. Stef

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024 (new version)

by StÃ©phane Ducasse

Yes I will! Stef > We are reaching 2.2 MB with shrinking based on this classes structure. > Stay tuned :-) I like when I hear that. This will start to be really sexy. > I will create the next patches for methods > reorganization. > > Please don't forget the second part of this fix: > http://code.google.com/p/pharo/issues/detail?id=2069 > > Many thanks! > -- Pavel > > On Wed, Jun 30, 2010 at 9:58 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> 12024 >> ----- >> >> - Issue 2105: Packages remodularization >> >> and now without obsolete classes >> >> Stef (thanks Pavel) >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 30, 2010

Re: [Pharo-project] CLFramework and Pharo

by StÃ©phane Ducasse

But you rely on XML. Second the builder (ie generating the XML) is not the problem as far as I know. but more how to assemble the widget and make sure that the layout are kept or specified. Then how using an external tools can make sure that this tool got well the way layoutMorph and other works? Stef > My knowledge is limited, but XML seems more portable than code Smalltalk. I do not understand why we want portability. Please note that the VWspec are as portable as XML between Smalltalk they are just arrays ( probably we would get a problem for the UI.Node notation but this is not the problem. > Exists external editor (UI Builders too) for generate code XAML. Then that > code could be "file in" used in a image of Pharo-Smalltalk where a class > could parse it and build the UI. The idea is use external tools like that... > > http://www.youtube.com/watch?v=kyrN_Ky3HWc&feature=PlayList&p=0DD1BED3F232B… > > Is a very sample tool, but exists anothers much more complete. Why re-create > a new ui builder when exists another external always best? I need only the > code for rebuild the UI, not all ui builder tool. > > I donÂ´t know nothing of Seaside, but I understand than the mechanism for > build the UI will be the same. The same XAML code could build a equivalent > UI, but in that case for HTML explorer. But this is exactly what is done in VW with windowsSpec you can get a builder (which builds the application UI) either for your desktop or for VWWave (long time ago before seaside even if less powerful). > Well, only is a idea, surely stupid XD > > PS- My name is Gerard, without last vowel. > > > -- > View this message in context: http://forum.world.st/CLFramework-and-Pharo-tp2273256p2274245.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 30, 2010

Re: [Pharo-project] [update 1.2] #12024 (new version)

by Pavel Krivanek

We are reaching 2.2 MB with shrinking based on this classes structure. Stay tuned :-) I will create the next patches for methods reorganization. Please don't forget the second part of this fix: http://code.google.com/p/pharo/issues/detail?id=2069 Many thanks! -- Pavel On Wed, Jun 30, 2010 at 9:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 12024 > ----- > > - Issue 2105: Â Packages remodularization > > and now without obsolete classes > > Stef (thanks Pavel) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 30, 2010