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

Re: [Pharo-project] HTTP client library in Pharo?

by Andrei Stebakov

I also found that cookies were not correctly sent. Every cookie was sent with its own "Cookie: " header which is not correct. It should be in a format of "Cookies: name1=value1; name2=value2 " I temporarily fixed it in my current image, I'll try to send out the patch if it's not already fixed by someone else. Also cookie collection is too restrictive to the domain. Let's say your request goes to www.domain.com and in the cookies it'll have domain.com. Those cookies won't be collected since the current algorithm requires it to match from the start of the string (probably should only match the end of the string). Andrei On Sat, Jul 31, 2010 at 9:03 PM, Andrey Larionov <anlarionov(a)gmail.com> wrote: > I found WebClient resonably helpful. And in Pharo1.1 WebClient loaded > with Metacello passes all tests green on Linux. In more recent version > some test related to WebSockets are failed. > I found WebClient lack of multi-domain cookie support and response > encoding problems, but working on it right now. > > On Thu, Jul 29, 2010 at 20:06, Andrei Stebakov <lispercat(a)gmail.com> wrote: >> I've been trying to find a library for Pharo/Squeak which would handle >> GET/POST requests with the ability to manage cookies and deal with >> https servers. >> The HTTPSocket that's included in Pharo doesn't have cookies support. >> I tried to find any library that handles cookies and there came up >> CurlPlugin and SWHTTPClient. >> SWHTTPClient page has a broken link to the source code >> (http://map.squeak.org/package/15f42ec1-e93e-4bcf-ab2b-6746ae9d413f) >> CurlPlugin package for Win32 that I found on the main project page >> fails most of the tests and can't retrieve any http data. >> I also found WebClient/WebServer library at >> http://www.squeaksource.com/@QY3MLGU4hU3c8qcE/2xQek_iM which also >> fails most tests after installation. >> >> I wonder what people in smalltalk community are using when they need >> to do some web scraping when they need to keep some session in >> cookies? >> What would be the best library to invest time into (I am very new to Smalltalk)? >> >> Thank you, >> Andrei >> >> _______________________________________________ >> 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 >

Aug. 4, 2010

Re: [Pharo-project] update to OCompletion

by Romain Robbes

> > Message: 1 > Date: Wed, 4 Aug 2010 01:09:25 +0100 > From: Tim Mackinnon <tamackinnon(a)gmail.com> > Subject: Re: [Pharo-project] update to OCompletion > To: Pharo-project(a)lists.gforge.inria.fr > Message-ID: <8A0E7719-7C1D-4E1B-9F44-FA570521D722(a)gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > > Am I missing something here - in a fresh 1.1 one click image if I do: > ConfigurationOfOCompletion project latestVersion load > > I get an endless stream of errors: > > The method Boolean and:and: has been deprecated. > use and: > > Select Proceed to continue, or close this window to cancel the > operation.??????? > Which class, in which package, is sending it? I have no senders of #and:and: in my image. Romain -- Romain Robbes http://romain.robb.es rrobbes(a)dcc.uchile.cl

Aug. 4, 2010

Re: [Pharo-project] [ANN] PharoConfigurationBrowser

by Miguel Enrique CobÃ¡ MartÃnez

El miÃ©, 04-08-2010 a las 15:16 +0200, StÃ©phane Ducasse escribiÃ³: > Thanks! > As soon as miguel changes the name (universes to metacelloRepositories) I will integrate it. > > Stef Then we settle on www.squeaksource.com/MetacelloRepositoryForPharo10 www.squeaksource.com/MetacelloRepositoryForPharo11 www.squeaksource.com/MetacelloRepositoryForPharo12 ? Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Andrey Larionov

Why there should be repository per release? As i know MetacelloConfiguration already contains information about compatible Pharo versions. 2010/8/4 Miguel Enrique CobÃ¡ MartÃnez <miguel.coba(a)gmail.com>: > El miÃ©, 04-08-2010 a las 11:46 +0200, Torsten Bergmann escribiÃ³: >> Hi Miguel, >> >> hey, nice! If we follow this convention then it is easy to implement >> a universe browser that selects the correct universe repo and >> displays all loadable versions. Loading stuff should just be >> a few clicks away - I personally hate all this MC/Gofer typing ... >> >> Attached is a quick/simple implementation of such a browser: >> > > Mann, Sie sind Ã¼ber schnell! > > I tested it in PharoCore 1.0 and worked after a few changes, but the > interface is cool. +1 to aim it be the default universe browser in 1.2. > Simple, to the point. > In Pharo 1.0 I had: > > - Open it with Universe open (doesn't register on menu because of the > lacking pragmas) > - UniverseBrowser pharoUniverse returns PharoCore1.0 instead of Pharo10 > to build the universe name. This could be changed in two ways: > - Add a system property that states the image repository: > Â SystemVersion current universeName Â "Returns Pharo10 for image > releases 1.0, 1.0.1, 1.0.5, etc) > - Use the equivalent method in the gofer package I uploaded to > PharoInbox (if it is approved, so there is only a unique source for > converting image version string to universe names) > > Other than that, I like the browser. > > > >> Â - file in the attached changeset Â (I tried in Pharo 1.2) >> Â - open via World menu -> "Universe Browser" >> Â - select the configuration you want and from the context menu choose >> Â -- "Load configuration" Â Â Â Â Â Â Â Â Â Â -> only the config is loaded >> Â -- "Load configuration and latest version" Â -> the config and lates version Â is loaded >> >> Have fun! I used Pharo 1.2 - should work in Pharo 1.0 and 1.1 too >> (havent tested). >> >> Bye >> T. >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > Cheers > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Miguel Enrique CobÃ¡ MartÃnez

El miÃ©, 04-08-2010 a las 11:49 +0200, StÃ©phane Ducasse escribiÃ³: > Yes! > Good push > now I understand what you meant with Universe. > > Now two important comments for me: > > The problem One is that we are creating another vocabulary > - Why not sticking with MetacelloRepositoryForPharo10? I have no problem with changing name. I think though that MetacelloRepositoryForPharo10 is very long but as the tools hide it maybe isn't a big problem either. Lets vote and if so, change it as soon as possible. > Like that we will not have to explain an Universe is a metacello repository..... > > Second point: what I would like is to have that all the dependent packages and configurations are copied into the metacelloRepository. > I do not want to have dependency to any external servers. This way we will self-contained distribution. > Do you handle that? I have read the discussions and yes that would be good but some things concern me: - Repository size (maybe this is not a problem but the squeak source downtime come to mind) - Load in the squeak source when sync is being done. - Who syncs the packages, Metacello when uploadingÂ¡ Some webmaster? A cron? - What about conflicting names in packages. - Maybe RFB-MiguelCoba.25 in ConfigurationOfRFB ask it from lukas repo and ConfigurationOfOtherPackage requires RFB-MiguelCoba.25 from squeaksource RFB repository and for any reason the packages are distinct (maybe a bug was found and republished in lukas repo with the same version number, but squeaksource version was copied before the fix was done) Maybe those problems never show. Anyway, the idea of having all available is good, but maybe not a task of Metacello, but as an independent effort. Metacello will just use the redundant repositories when installing a package. Cheers > > Else this is great. > > Stef > > > On Aug 4, 2010, at 11:41 AM, Adrian Lienhard wrote: > > > Hi Miguel, > > > > Thanks! It's great to see progress on this front! > > > > Cheers, > > Adrian > > > > On Aug 4, 2010, at 10:21 , Miguel Enrique CobÃ¡ MartÃnez wrote: > > > >> Hi all, > >> > >> I have created three new repositories on squeaksource: > >> > >> http://www.squeaksource.com/UniverseForPharo10 > >> http://www.squeaksource.com/UniverseForPharo11 > >> http://www.squeaksource.com/UniverseForPharo12 > >> > >> They are the repositories for the current versions of Pharo. The idea is > >> that each new release add a new UniverseForXXX repository and populates > >> it with the current UniverseForXXX packages of the stable release. > >> > >> Right now they are mostly empty, but should be populated by the > >> community and the ConfigurationOfXXX maintainers. > >> > >> Most ConfigurationOfXXX packages in > >> > >> http://www.squeaksource.com/MetacelloRepository > >> > >> should be copied to UniverseForPharo10. Which versions? The last known > >> version that is working correctly on Pharo 1.0. This will be the > >> official universe for Pharo1.0. No ConfigurationOfXXX should be stored > >> on UniverseForPharo10 if it is not working correctly on Pharo10. > >> > >> Then two things can follow: > >> > >> - If the package already has ConfigurationOfXXX package versions that > >> work in Pharo 1.1, those versions should be copied to > >> UniverseForPharo11. > >> > >> - If the ConfigurationOfXXX only works for Pharo1.0 and the maintainer > >> want to create the configuration for Pharo 1.1, he/she must copy the > >> last working configuration for the package from UniverseForPharo10 to > >> UniverseForPharo11. There he/she can start modifying the package until > >> it works correctly in Pharo1.1 (use the blessing: tags wisely to avoid > >> marking a broken configuration as released) > >> > >> This will permit to populate the UniverseForPharo11 based on the last > >> working package versions from UniverseForPharo10. From that point they > >> will likely diverge because of maintenance releases to the packages in > >> any UniverseForXXX repository. > >> > >> The same will must be done to migrate from UniverseForPharo11 to > >> UniverseForPharo12. You get the idea. > >> > >> With time, MetacelloRepository should be deprecated in favor of this > >> UniverseForXXX repositories. > >> > >> Anyone is free to copy a working version from a previous Universe to a > >> new Universe. They have read/write permissions to all. > >> > >> This setup will avoid the problems we are having right now with the > >> in-image changes that are rendering the ConfigurationOfXXX unusable in > >> distinct releases of Pharo. > >> > >> What this means to the end user: > >> > >> - For released version of Pharo > >> > >> They will have to use gofer this way: > >> > >> Gofer new > >> squeaksource: 'UniverseForPharo10'; "Or UniverseForPharo11" > >> project: 'ConfigurationOfMagma'; > >> load. > >> ConfigurationOfMagma project latestVersion load. > >> > >> - For next releases of Pharo > >> > >> Gofer loadFromUniverse: 'Magma'. "Or with GoferProjectLoader" > >> ConfigurationOfMagma project latestVersion load. > >> > >> All this depends on conventions to find the appropriate universe for > >> each pharo release, and also in the support from tools (like gofer in > >> this example or the GoferProjectLoader if it is part of the core image). > >> The universe functionality of the tools right now rely on the > >> SystemVersion current majorMinorVersion string for deciding which > >> repository to connect to. This could be improved surely but for now it > >> works. > >> > >> I'm loading a new version of Gofer to PharoInbox with this functionality > >> added so if you want to load directly from the universes with gofer do: > >> > >> Gofer upgrade. > >> Gofer loadFromUniverse: 'YourPackageAlreadyInAUniverse'. > >> > >> But wait to this change to be treated by Stephane or Lukas before > >> attempt it. > >> > >> Right now there is only Magma in the three repositories, but it > >> shouldn't be hard for the maintainers of the other Configurations to > >> help populate the universes from Pharo1.0, Pharo1.1 and Pharo1.2. > >> > >> This will benefit us as a community because the universes for the > >> released pharo versions will be mostly untouched (only maintenance > >> releases) and people will have the freedom to modify the configuration > >> in the unstable (currently UniverseForPharo12) universe without > >> affecting the users of the stable versions. > >> > >> Also, this will avoid to have a lot of conditionals inside the > >> ConfigurationOfXXX classes, because a given class will target a specific > >> Pharo release (the version on the newest universes could even delete the > >> methods for the old universe, because will likely won't work in the new > >> universe, deleting unnecessary and legacy code from the configuration) > >> > >> Comments and improvements welcome > >> > >> -- > >> Miguel CobÃ¡ > >> http://miguel.leugim.com.mx > >> > >> > >> > >> _______________________________________________ > >> 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

Re: [Pharo-project] Telling the OS that the VM wants focus

by Miguel Enrique CobÃ¡ MartÃnez

El miÃ©, 04-08-2010 a las 11:55 +0200, StÃ©phane Ducasse escribiÃ³: > why not growl events? Or D-Bus on linux systems > > On Aug 4, 2010, at 10:38 AM, Max Leske wrote: > > > Ok, thanks. > > Would be nice if at some point in the future unhandled exceptions would notify the OS automatically (for instance). > > > > > > On 04.08.2010, at 00:34, John M McIntosh wrote: > > > >> Many things come to mind, one is to use some of the old text to voice features of squeak and have the computer yell at you when it's ready... That should work on all platforms that support sound. > >> > >> More subtle and complex would be to use Alien/FFI and talk to the operating system's notification/alert API. > >> > >> On 2010-08-03, at 12:51 AM, Max Leske wrote: > >> > >>> Hi folks > >>> > >>> The project I'm currently working on requires that I have to wait frequently for computations / operations to complete. To control the status I used progress bars wherever possible. Now, since the operations might take several minutes I like to sometimes switch to another Desktop, maybe read an e-mail or an article. > >>> I'd find it rather useful if the OS would notify me that the VM needs my attention as soon as the operations have completed or if there was an error during execution, so that I don't have to go and check every 30 seconds. Is there an existing way to do this? If not, I'd like to propose this as a feature for a future release (although I don't have an inkling how one would accomplish this...). > >>> > >>> Cheers, > >>> Max > >>> _______________________________________________ > >>> 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> Twitter: squeaker68882 > >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > >> =========================================================================== > >> > >> > >> > >> > >> _______________________________________________ > >> 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

Re: [Pharo-project] Gofer support for Universes

by Miguel Enrique CobÃ¡ MartÃnez

El miÃ©, 04-08-2010 a las 09:15 -0300, Esteban Lorenzano escribiÃ³: > Hi, > GoferProjectLoader does that, and I think it does it fine (althought is > my child, he)... and it is not at core versions because no body has > decided so, yet... but stef can change his mind :) Yes, I know. I mentioned GoferProjectLoader in the Universes announce. I know that maybe this functionality belongs to GoferProjectLoader and not to Gofer, but currently, Gofer is officially in PharoCore and GoferProjectLoader isn't. That is the only reason. If GoferProjectLoader is a core package I will the most happy to use it to access the pharo universes :) Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

Re: [Pharo-project] Gofer support for Universes

by Miguel Enrique CobÃ¡ MartÃnez

El miÃ©, 04-08-2010 a las 11:26 +0200, Lukas Renggli escribiÃ³: > I'll have a look when I am back from holidays. > > Two questions arise: > > - Is Universe still relevant and maintained by anybody these days? > Looks like all current code is managed with Metacello nowadays. > > - Gofer was designed to make Monticello scriptable. How do actions > like commit and merge map to Gofer? Sorry for the confusion. Indeed the Universes name is already overloaded and has a tradition in Squeak... But we are Pharo! :) I meant the Metacello Universes that I created in squeaksource.com UniverseForPharo10 UniverseForPharo11 UniverseForPharo12 UniverseForPharoXX that contains only Metacello Configurations of packages that are tested and working on the corresponding Pharo release. It has nothing to do with the old squeak universes. Cheers > > Lukas > > On Wednesday, August 4, 2010, Miguel Enrique CobÃ¡ MartÃnez > <miguel.coba(a)gmail.com> wrote: > > StÃ©phane, Lukas, > > > > I have uploaded > > > > Gofer-Core-MiguelCoba.124 > > Gofer-Tests-MiguelCoba.117 > > > > to PharoInbox repository on squeaksource. > > > > They are based on the versions of gofer in Pharo 1.0 > > Gofer-Core-MarkusDenker.117 > > Gofer-Tests-MarkusDenker.116 > > > > and add universes support to gofer. > > > > What do you think, are they worth integrating to mainstream gofer? > > Does this functionality belongs to Gofer? I know of GoferProjectLoader, > > but it isn't part of PharoCore, so that discards it right now. > > > > What is the procedure to merge it to trunk gofer, if so decided, so that > > a > > > > Gofer upgrade > > > > in any Pharo image gets this new version? > > > > Cheers > > -- > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

Re: [Pharo-project] Refactor source method is grayed out?

by Romain Robbes

> > > Message: 4 > Date: Wed, 4 Aug 2010 02:09:57 +0100 > From: Tim Mackinnon <tamackinnon(a)gmail.com> > Subject: Re: [Pharo-project] Refactor source method is grayed out? > To: Pharo-project(a)lists.gforge.inria.fr > Message-ID: <69EB6BBC-FA35-4168-A291-7E3C956DCEBF(a)gmail.com> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > Lucas - I can't repeat this in a Pharo 1.1 image - so maybe we should > put it down to some oCompletion/eCompletion bad interaction (or unload > weirdness). > > Tim > > On 3 Aug 2010, at 12:23, Lukas Renggli wrote: > >> I am using the images from hudson.lukas-renggli.ch. I don't know how >> oCompletion depends/overrides on eCompletion, so indeed it might make >> a difference. >> >> Lukas >> OCompletion is a fork of eCompletion. A while ago I think eCompletion was not really maintained so it made sense to just fork it. Romain -- Romain Robbes http://romain.robb.es rrobbes(a)dcc.uchile.cl

Aug. 4, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Miguel Enrique CobÃ¡ MartÃnez

El miÃ©, 04-08-2010 a las 11:46 +0200, Torsten Bergmann escribiÃ³: > Hi Miguel, > > hey, nice! If we follow this convention then it is easy to implement > a universe browser that selects the correct universe repo and > displays all loadable versions. Loading stuff should just be > a few clicks away - I personally hate all this MC/Gofer typing ... > > Attached is a quick/simple implementation of such a browser: > Mann, Sie sind Ã¼ber schnell! I tested it in PharoCore 1.0 and worked after a few changes, but the interface is cool. +1 to aim it be the default universe browser in 1.2. Simple, to the point. In Pharo 1.0 I had: - Open it with Universe open (doesn't register on menu because of the lacking pragmas) - UniverseBrowser pharoUniverse returns PharoCore1.0 instead of Pharo10 to build the universe name. This could be changed in two ways: - Add a system property that states the image repository: SystemVersion current universeName "Returns Pharo10 for image releases 1.0, 1.0.1, 1.0.5, etc) - Use the equivalent method in the gofer package I uploaded to PharoInbox (if it is approved, so there is only a unique source for converting image version string to universe names) Other than that, I like the browser. > - file in the attached changeset (I tried in Pharo 1.2) > - open via World menu -> "Universe Browser" > - select the configuration you want and from the context menu choose > -- "Load configuration" -> only the config is loaded > -- "Load configuration and latest version" -> the config and lates version is loaded > > Have fun! I used Pharo 1.2 - should work in Pharo 1.0 and 1.1 too > (havent tested). > > Bye > T. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010