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

Re: [Pharo-project] [OT] Ubuntu wallpaper

by Mariano Martinez Peck

2010/6/28 Henrik Johansen <henrik.s.johansen(a)veloxit.no> > > On Jun 28, 2010, at 4:10 45PM, Mariano Martinez Peck wrote: > > > > On Thu, Jun 24, 2010 at 3:42 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> >I have an error "'image format not recognized'" >> >> Check the correct URL: >> >> http://ubuntu.ecchi.ca/wallpapers/10.04//Maraetaibeforesunrise.jpg >> >> in a webbrowser and then try in Pharo 1.1. >> >> Which VM (Std/Cog?), which OS and which pharo image do you have? >> Do you have the same error in another image? >> >> > Pharo-1.1-11400-rc2 > Latest update: #11400 > VM: Squeak VM 4.2.2b1 > > What I evaluated: > > |form| > form := (Form fromBinaryStream: (HTTPSocket httpGet: > 'http://ubuntu.ecchi.ca/wallpapers/10.04/' , > 'Maraetaibeforesunrise.jpg')). > World backgroundImage: form layout: #scaled > > > I attach the PharoDebug.log generated. > > The problem is in #formFromStream: aBinaryStream > > Because none of "ImageReadWriter withAllSubclasses" understands the > format, and thus, it goes with the ifNone. > > Can you put a self halt and let me know which subclass in particular is > working for you? > > Cheers > > Mariano > > > Works just fine for me, with a variety of VM's, reader is > PluginBasedJPEGReadWriter. > Try inspecting just the get-stream, and see if you you actually get the > image data or something else. > (First line in streams collection should start with Ã¿ÃÃ¿Ã JFIF Z in ascii > mode ) > > Thanks Henry....Weird....Today, I cannot reproduce it anymore. In any image :( I don't know what was the problem then...anyway, forget it. Thank you very much mariano > Cheers, > Henry > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 29, 2010

[Pharo-project] How programatically collapse main pharo window?

by Denis Kudriashov

Hello. How programatically collapse main pharo window? How it can be done?

June 29, 2010

[Pharo-project] Fwd: Emploi Smalltalk

by StÃ©phane Ducasse

>> From: Franck BUDAIL <FBU(a)gconsept.com> >> Date: 28 juin 2010 15:35:28 HAEC >> To: "bouraqadi(a)ensm-douai.fr" <bouraqadi(a)ensm-douai.fr> >> Subject: smalltalk et forum entreprise >> >> Monsieur Bouraqadi, >> >> Suite Ã notre Ã©change tÃ©lÃ©phonique, je reviens vers vous sur nos recherches de profils Â« Smalltalk Â», >> Nous recherchons donc 3-4 personnes pour des projets de plusieurs annÃ©es basÃ©s au Mans. >> >> Les rÃ©munÃ©rations vont de 30 Ã 45kâ¬ suivant les profils (dÃ©veloppeurs, concepteurs, analystes, CP, architectes) >> NâhÃ©sitez pas Ã diffuser nos besoins auprÃ¨s de votre rÃ©seau, >> Les personnes intÃ©ressÃ©es peuvent me joindre directement par email ou sur mon portable. >> >> Jâattends vos Ã©lÃ©ments en parallÃ¨le sur le forum entreprise >> >> Dans lâattente de votre retour >> Cordialement >> >> >> >> Franck BUDAIL >> Directeur DÃ©veloppements >> >> >> >> Zac des hauts de CouÃ«ron. >> rue des forgerons >> 44220 COUERONwww.gconsept.com >> >> >> TÃ©l.: +33 (0)2 51 83 03 00 >> Fax: +33 (0)2 51 83 03 01 >> Mob: +33 (0)6 25 31 24 57 >> Email : fbu(a)gconsept.com >> >> Ã¼ N'imprimez ce mail que si nÃ©cessaire. >> Ce message peut contenir des informations confidentielles protÃ©gÃ©es par le secret professionnel. Au cas oÃ¹ il ne vous serait pas destinÃ©, nous vous remercions de bien vouloir nous en aviser immÃ©diatement et de le supprimer. >> >> >> > > > > Noury > http://csl.ensm-douai.fr/noury > ---- > -18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. > http://www.esug.org/Conferences/2010 > > -18Ã¨me JournÃ©es Francophones des SystÃ¨mes Multi-Agents (JFSMA), 18-20 october 2010, Mahdia, Tunisia. > http://www.ltim.org/jfsma10/accueil.php > > -4th Argentinian Smalltalks Conference November 11th - 13th, 2010, ConcepciÃ³n del Uruguay, Entre RÃos, Argentina > http://www.fast.org.ar/ >

June 29, 2010

Re: [Pharo-project] [Vm-dev] Re: Tools to Build Cog on Win32

by laurent laffont

On Tue, Jun 29, 2010 at 5:16 AM, Rob Rothwell <r.j.rothwell(a)gmail.com>wrote: > > I have a good [rough draft] start on very detailed (too detailed?) steps to > properly install Cygwin and build the Cog VM on Windows. I just need to add > preparing the image for first time use, etc...: > > > http://book.pharo-project.org/book/Virtual-Machine/Building/BuildVMOnWindow… Thank you !! (I haven't started editing/revising yet). > > Anyway, if anyone could help me properly position my two topics, "Cog VM" > and "Traditional (Squeak) VM" underneath "The MS-Windows way," I would > greatly appreciated it. Although they are subsections, they are fully > "unindented" like a chapter in the table of contents... > It seems someone has done it ... Anyway, to move a page, click on the 'Move' link in the command line and the choose the parent section. Laurent > > Thank you, > > Rob > > On Mon, Jun 28, 2010 at 3:12 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> >> >> On Mon, Jun 28, 2010 at 1:47 AM, Rob Rothwell <r.j.rothwell(a)gmail.com>wrote: >> >>> >>> Disregard! I have found the magic incantation and even got Pharo 1.1 >>> running in a VM compiled on my own! >>> >> >> Cool, this is waiting for you :) >> http://book.pharo-project.org/book/Virtual-Machine/Building/BuildVMOnWindow… >> >> >> Laurent >> >> >> >>> >>> I will try to type up the formula for others to follow in terms of >>> installing cygwin and the required tools. >>> >>> Thank you, >>> >>> Rob >>> >>> On Sun, Jun 27, 2010 at 11:14 AM, Rob Rothwell <r.j.rothwell(a)gmail.com>wrote: >>> >>>> Is there some way to package the tools required to build Cog similar to >>>> the Squeak-Win32-Tools package that is available for the standard Squeak VM? >>>> >>>> I just don't seem to be savvy enough to choose all the proper cygwin >>>> options. I DID manage to get subversion loaded in cygwin and check out the >>>> sources, but I am sure I am doing the wrong thing by installing the 1.7.5 >>>> version of cygwin since HowToBuild references 1.5.24. Plus, I just can't >>>> seem to get the right gcc...I keep getting "gcc: The -mno-cygwin flag has >>>> been removed; use a mingq-targeted cross-compiler," and I just can't seem to >>>> get the right installation options selected in the "Devel" section. >>>> >>>> So...either a prebuilt bundle or very specific instructions for mere >>>> mortals would be very helpful! It would be nice to keep up with the fixes; >>>> this VM made a HUGE difference in some Binaural Beat generation code I have >>>> that writes very large audio files. I can actually fork the code now and >>>> keep using the image with very good responsiveness! Amazing! >>>> >>>> Thanks for any help, >>>> >>>> Rob >>>> >>> >>> >>> >> >> > >

June 29, 2010

Re: [Pharo-project] Bug in 1.1 RC2? Trait composition lost when loading a MC package

by StÃ©phane Ducasse

thanks simon Stef On Jun 28, 2010, at 10:45 PM, Simon Denier wrote: > > When loading a package with class definitions containing a trait composition like ClassX uses: TraitY - {#selector}, the composition is lost in the image. > > It seems closely related to previous issues 2477 and 2148 > But I am not sure if this is the same bug reappearing or a variant. > > To reproduce: > Gofer new squeaksource: 'MooseAlgos'; package: 'Moose-Algos-Graph'; package: 'Moose-Tests-Algos-Graph'; load > > Run tests in Moose-Tests-Algos-Graph: you should have 3 failures and 4 errors, all due to the missing trait composition in some classes. > > > After loading, you can make a diff changes in monticello, it will highlight the package as dirty and show you the lost trait compositions in two classes: > > MOGraphNode subclass: #MABfsNode > uses: MATEdgeNode - {#previousEdges. #from:edge:} > instanceVariableNames: 'nextEdges firstDepth' > classVariableNames: '' > poolDictionaries: '' > category: 'Moose-Algos-Graph' > > MODisjointSetNode subclass: #MANextNode > uses: MATNodeNode - {#from:. #previousNodes} > instanceVariableNames: 'nextNodes' > classVariableNames: '' > poolDictionaries: '' > category: 'Moose-Algos-Graph' > > > > The problem has been reproduced in 11383 and 11400 RC2. > > > -- > Simon > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 29, 2010

Re: [Pharo-project] [Vm-dev] Re: Tools to Build Cog on Win32

by Rob Rothwell

I have a good [rough draft] start on very detailed (too detailed?) steps to properly install Cygwin and build the Cog VM on Windows. I just need to add preparing the image for first time use, etc...: http://book.pharo-project.org/book/Virtual-Machine/Building/BuildVMOnWindow… (I haven't started editing/revising yet). Anyway, if anyone could help me properly position my two topics, "Cog VM" and "Traditional (Squeak) VM" underneath "The MS-Windows way," I would greatly appreciated it. Although they are subsections, they are fully "unindented" like a chapter in the table of contents... Thank you, Rob On Mon, Jun 28, 2010 at 3:12 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > > > On Mon, Jun 28, 2010 at 1:47 AM, Rob Rothwell <r.j.rothwell(a)gmail.com>wrote: > >> >> Disregard! I have found the magic incantation and even got Pharo 1.1 >> running in a VM compiled on my own! >> > > Cool, this is waiting for you :) > http://book.pharo-project.org/book/Virtual-Machine/Building/BuildVMOnWindow… > > > Laurent > > > >> >> I will try to type up the formula for others to follow in terms of >> installing cygwin and the required tools. >> >> Thank you, >> >> Rob >> >> On Sun, Jun 27, 2010 at 11:14 AM, Rob Rothwell <r.j.rothwell(a)gmail.com>wrote: >> >>> Is there some way to package the tools required to build Cog similar to >>> the Squeak-Win32-Tools package that is available for the standard Squeak VM? >>> >>> I just don't seem to be savvy enough to choose all the proper cygwin >>> options. I DID manage to get subversion loaded in cygwin and check out the >>> sources, but I am sure I am doing the wrong thing by installing the 1.7.5 >>> version of cygwin since HowToBuild references 1.5.24. Plus, I just can't >>> seem to get the right gcc...I keep getting "gcc: The -mno-cygwin flag has >>> been removed; use a mingq-targeted cross-compiler," and I just can't seem to >>> get the right installation options selected in the "Devel" section. >>> >>> So...either a prebuilt bundle or very specific instructions for mere >>> mortals would be very helpful! It would be nice to keep up with the fixes; >>> this VM made a HUGE difference in some Binaural Beat generation code I have >>> that writes very large audio files. I can actually fork the code now and >>> keep using the image with very good responsiveness! Amazing! >>> >>> Thanks for any help, >>> >>> Rob >>> >> >> >> > >

June 29, 2010

Re: [Pharo-project] [SPAM] Fwd: [Pharo-users] [SPAM] Re: WebClient

by GermÃ¡n Arduino

2010/6/19 Philippe Marschall <kustos(a)gmx.net>: > On 15.06.2010 10:19, Sven Van Caekenberghe wrote: >> >> On 14 Jun 2010, at 16:48, StÃ©phane Ducasse wrote: >> >>>> I will contact Andreas directly once I know your position on the last remaining item. >>> >>> Good >> >> I did contact Andreas Raab and he integrated both of my patch sets upstream so that WebClient-Core now load and works on Pharo 1.1rc2 without the need for any Pharo specific patches. > > I also sent him two patches. With the backported SocketStream fixes I > now have Seaside running on WebClient in Pharo 1.0. The only thing > missing is multipart POSTs (file uploads). > > Cheers > Philippe > Hi Philippe: I sent an example method to do the multipart post (file upload) on other mail. I'm developing a service to a customer using that and it works. The only problem to a full automation is that you need to know previously the name of the fields included in the form (The same happens with other multipart post operations (not only with file upload)). I'm doing for now a trace with Firebug, check the post data and implement the method as I need, but should be nice to automate all :) Cheers. GermÃ¡n. -- ================================================= GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================

June 28, 2010

Re: [Pharo-project] ESUG will sponsor the XMLRPC project!

by GermÃ¡n Arduino

2010/6/28 Philippe Marschall <philippe.marschall(a)netcetera.ch>: > On 06/28/2010 12:25 AM, GermÃ¡n Arduino wrote: >> As flickr, > > Besides REST and SOAP > >> blogger, > > Nope, not any more. > >> wordpress, > > ok > >> Joomla sites, > > ok > >> Google blog search, > > Couldn't find anything about it. Google is standardizing on GData and > "AJAX". Even SOAP is being phased out. > >> Drupal sites, > > Moving away from XML-RPC like anybody else. > >> delicious, > > Couldn't find anything XML-RPC related, seems to use "REST". > >> zope, > > OK. > >> products as SAP, > > Still? I would have assumed they moved on. > >> to mention a few that >> I have in mind now.... >> >> I means, not only web sites, also products and I think also that is a >> compact protocol that could permit to implement an API to servers / >> products easily. > > My impression is that people either moved from XML-RCP to SOAP or > abandoned the idea and went to REST. I don't know anybody who considers > it for new projects. > Blogger and Google in general yes, are moving to GData but xml-rpc is still suported. But I understand your point, you think that isn't worth to invest in this protocol. I need to think about. Cheers. GermÃ¡n.

June 28, 2010

[Pharo-project] Bug in 1.1 RC2? Trait composition lost when loading a MC package

by Simon Denier

When loading a package with class definitions containing a trait composition like ClassX uses: TraitY - {#selector}, the composition is lost in the image. It seems closely related to previous issues 2477 and 2148 But I am not sure if this is the same bug reappearing or a variant. To reproduce: Gofer new squeaksource: 'MooseAlgos'; package: 'Moose-Algos-Graph'; package: 'Moose-Tests-Algos-Graph'; load Run tests in Moose-Tests-Algos-Graph: you should have 3 failures and 4 errors, all due to the missing trait composition in some classes. After loading, you can make a diff changes in monticello, it will highlight the package as dirty and show you the lost trait compositions in two classes: MOGraphNode subclass: #MABfsNode uses: MATEdgeNode - {#previousEdges. #from:edge:} instanceVariableNames: 'nextEdges firstDepth' classVariableNames: '' poolDictionaries: '' category: 'Moose-Algos-Graph' MODisjointSetNode subclass: #MANextNode uses: MATNodeNode - {#from:. #previousNodes} instanceVariableNames: 'nextNodes' classVariableNames: '' poolDictionaries: '' category: 'Moose-Algos-Graph' The problem has been reproduced in 11383 and 11400 RC2. -- Simon

June 28, 2010

Re: [Pharo-project] [Metacello] Re: [Seaside] New structure for Seaside30, Magritte2, and Pier2 Metacello configurations

by Dale Henrichs

Mariano, Yes that's what I was thinking. I plan on updating the Seaside config and workspace ... but I wanted to make sure I wasn't headed off in some wild direction first:) I think that the minimum is to have a deployment group that loads just what is needed ... Development becomes a stickier issue, because it isn't always clear what should be included ... I think that with Metacello, one can be very explicit about what pieces one wants to load...it would be nice to have a minimal development group that adds just what is needed to do development (i.e., trying to debug a sticky production problem you'd like to load only what you need and getting examples and a bunch of other stuff isn't something you'd want to load into a production environment ... ). I think that one can leverage groups in Metacello which means that in an application one can afford to use _more_ mcz files...providing fine granularity on what can be loaded (even down to the level of a class per mcz file for things like independent components)...I wouldn't think that everything should be reduced to that fine of a granularity...but there are advantages to breaking things up into smaller loadable chunks... Dale Mariano Martinez Peck wrote: > Hi Dale. I didn't test it, but from the theorical point of view, I > really like it. I hope other people too. I think we have to take > advantage of Metacello features to do this kind of stuff. > > It is very interesting to have two groups: one for the core (and > probably deployment) and one for development. > > If you do this changes, please update the workspace of > ConfigurationOfSeaside explaining this :) > (sorry if you already did it) > > Cheers > > mariano > > On Sun, Jun 27, 2010 at 7:54 PM, Dale Henrichs <dhenrich(a)vmware.com > <mailto:dhenrich@vmware.com>> wrote: > > I am looking for a little feedback on the changes that I have made > to the latest configurations of Seaside30, Magritte2, and Pier2. I > have new versions for each of these configurations queued up for > release (#development blessing), but before releasing them I'd like > to hear if the changes I've made will cause trouble for folks using > Magritte2 and/or Pier2 in their applications. > > In the past, when you referenced Seaside30 from a configuration, the > entire Seaside3.0 release would be loaded, including development > tools, examples, both adaptors (on Squeak/Pharo and > GemStone)...basically the whole kitchen sink. > > With the 3.0.0-alpha5.15 release I've defined several groups for > Seaside3.0 (with feedback from the Seaside devs:): Base, Base Tests, > Development and Development Tests. I will also add a One-click group > to shdow the one-click release. Without going into too much detail, > the Base group defines the set of packages that are needed for a > production release, while the Development group defines the set of > packages that are useful in development (on top of the Base). > > To see how these new groups work out, I have created new versions of > the configurations for Magritte2 and Pier2 that reference the Base > group (plus any other packages that were needed) instead of bringing > in the entire Seaside3.0 release...This is the big change. After > loading the Magritte2 or Pier2 configuration you will need to load > from the Seaside30 configuration any and all packages that you may > need for your own application. > > I haven't released the changes yet, but if you are curious or > concerned you can try out the releases ahead of time ... depending > upon feedback I may go with a different scheme. > > In a fresh image, you can see what will be loaded for production by > executing one or more of the following expressions (note you need to > get the latest version of each of the configs from the SqueakSource > MetacelloRepository...oh and for best results use Metacello > 1.0-beta.27.1): > > (ConfigurationOfMagritte2 project version: '2.0.5') load. > (ConfigurationOfPier2 project version: '2.0.6') load. > (ConfigurationOfPierAddOns2 project version: '2.0.6') load. > > Once you've loaded one of these configs, there will be no > development tools nor any adaptors so at a minimum you'll need to > load one of the following depending upon which adaptor you want to use: > > "All platforms" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-Swazoo'). > "Squeak and Pharo" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-Comanche'). > "GemStone" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-FastCGI'). > > If you want to load in the Seaside development environment then you > would evaluate the following expression: > > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Development'). > > So at this point you can see the direction I'm going with this ... > the Magritte2 and Pier2 configurations are currently aimed at > loading the bare minimum needed for functionality from Seaside3.0 > for Magritte2 and Pier2 with the idea that you'd load the additional > functionality that you want by dealing directly with Seaside30 > configuration (like loading adaptors and development)... > > Pier2 already depends upon the following javascript packages: > > 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-UI' > > but if you're currently using Magritte2 and javascript, then you'll > need to explicitly load the javascript package(s) that you are using. > > There are other ways that the configs could be structured. This > approach minimizes the coupling between the Seaside3.0 and > Magritte2/Pier2 configurations, which I think is a good thing. > > I've taken the bare minimum step: loading what is required... it > would be reasonable to add 'Dev' groups to both Magritte2 and Pier2 > that would bring in Seaside30 dev support on the other hand, I don't > think it is reasonable to add support for loading the various > Adaptors to Magritte2 and Pier2, so if you're going to have to deal > with the Seaside30 config directly anyway why bother with adding dev > groups ... > > Anyway this is what _I_ think and I am interested in what you folks > think... > > For GemStone folks ... the answer is yes, Magritte2 and Pier2 have > been ported to GemStone/S 64 2.4 finally:). If you've been working > with Seaside3.0 already, you can load the > Magritte2/Pier2/PierAddOns2 configs into a fresh > 1.0-beta.8....otherwise I'll ask you to wait until I announcement. > > Dale > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > <mailto:seaside@lists.squeakfoundation.org> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >

June 28, 2010