December 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] setting Windows Application Title Bar

by Gary Chambers

For Windows (in this example), it is possible (nastily) to change as you like... (HostWindowProxy new instVarNamed: #windowHandle put: Win32Window getFocus; yourself) windowTitle: 'Title here'. Could add a class to startup to change based on various things, of course... Just mentioning as we are about to do deployed stuff based on a variable configuration running "fullscreen". Regards, Gary ----- Original Message ----- From: Ben Coman To: Pharo-project(a)lists.gforge.inria.fr Sent: Friday, December 16, 2011 1:29 PM Subject: Re: [Pharo-project] setting Windows Application Title Bar Sean P. DeNigris wrote: Ben Coman wrote These past few days I've had several images open at the same time to compare the operation of different versions, and found I quickly lost track of exactly which image was which. There is a lot of empty space on application title bar after "Pharo 1.3" where I'd like to display the directory where pharo.exe was started from. +1 on the confusion, but I would want it to show the directory of the image (because I use the same VM for all my images) :) Maybe it could be a setting? With some serendipity I noticed that the Croquet.exe I used to get ODBC working last night was displaying the image path in the Window Title Bar - pretty much just what I wanted. I discovered that removing the line "WindowTitle=Pharo 1.3" from "pharo.ini" replicated this. /*grin*/ Regarding the other thread discussing the "startup preferences" across multiple images, could the ability be provided the "delete" preferences already set in the "pharo.ini" that comes with the OneClick download ? cheers, Ben

Dec. 19, 2011

Re: [Pharo-project] Newbie observations on use of Metacello

by Sven Van Caekenberghe

On 19 Dec 2011, at 17:04, Ben Coman wrote: > I've been lurking this mail list for 6 - 9 months and had not picked that up. That is a big miss. I'm not usually so slow. Can you point me to the documentation that describes that process? I agree, the UX is not (yet) perfect; so your comments are valid. Metacello was written with many different design goals: one of them is that it solve the 'chicken/egg' problem by allowing configurations to be loadable in images that do not yet contain anything related to Metacello ! That is why you always see this boilerplate with Gofer and the Smalltalk at: #ConfigurationOf.. Sven

Dec. 19, 2011

Re: [Pharo-project] Newbie observations on use of Metacello

by Ben Coman

StÃ©phane Ducasse wrote: > ben thanks for your feedback. > > Normally we should use the monticello repository browser and just click on a ConfigurationOf > I've been lurking this mail list for 6 - 9 months and had not picked that up. That is a big miss. I'm not usually so slow. Can you point me to the documentation that describes that process? In the meantime, I unzip a fresh Pharo-1.3-OneClick, open Monticello Browser and look for ConfigurationOfSqueakDBX. I can't see it. I expected to since you seemed to indicate it was that simple. So I GUESS* my way through. I <Open> the http://www.squeaksource.com/MetacelloRepository repository (which actually requires a bit of fore knowledge about the url - which not all newbies will have) This did show ConfigurationOfSqueakDBX but the are many versions and so many buttons to choose from. A bit scary for a newbie. Anyhow, I'll ASSUME* to select the latest one ConfigurationOfSqueakDBX-MarianoMartinezPeck.27 and click <Load>. I still can't see any SqueakDBX or OpenDBX classes in System Browser. Do I need to follow up manually doing "ConfigurationOfSqueakDBX project latestVersion load." ? A mixed procedure part GUI and part non-GUI is not the best - and I've not seen it documented anywhere. I would have liked to have loaded the package with "just a single click on a ConfigurationOf" but there seems to be more to it than that. The following still seems easier: > Metacello package: 'SqueakDBX' load or perhaps some alternatives using existing tools... 1. To the Monticello Browser add a <Metacello> button that opens http://www.squeaksource.com/MetacelloRepository. If Metacello is "THE" package management tool then it should have a higher profile than just one of the 23 listed repositories, of which two others have "Metacello" in their title. 2. To the World Menu, add a <Metacello Browser> item that jumps straight to the Monticello Repository Browser for http://www.squeaksource.com/MetacelloRepository. 3. The Welcome Text of a fresh pharo-oneclick image should describe how to do either 1. or 2. above. cheers, Ben > than did you read the forthcoming chapter? > https://gforge.inria.fr/frs/download.php/28462/Metacello.pdf (old version) > > Yes I refer to it in point 4 below. Can you point me to where in that pdf it specifically describes that loading procedure using Monticello Browser. All the examples I can see are code b> below, except using (Smalltalk at:.....) rather than the class itself. Further, the Pharo-1.3-OneClick opening documentation says to execute the following line... > DEVImageWorkspaces openExternalProjectWorkspace. which shows several examples all of the same form as the code b> below. Also, from memory the examples given throughout this mail list tend to be of the same form as code b> below - rather than directing people to the GUI Monticello Browser - or I probably would have picked that up sooner. > Stef > > > > On Dec 19, 2011, at 5:15 AM, Ben Coman wrote: > > >> Some observations from the perspective of as a newbie on Pharo Package Management. I'm likely to me missing in the philosophy of the design, but from the narrow view of my own usage.... >> >> 1. When I read about Metacello being the package management system, I expected there to be a "command"(*) Metacallo but instead I see Gopher being used. This is a mixed message that lowers my comfort level feeling I understand the system as I'm trying to pick up a bundle of new ideas. As I now understand it Metacello is more about a system of backend configuration than a front end user interface. I am now more comfortable using Gopher direct - but I reflect on how I felt the first time. >> >> (*) While technically a "command" is like a verb, and Gopher is like a noun rather than a verb - I can't yet completely disengage my prior learning that considers the first part of the statement to be a "command" - and I expect other newbies might find the same. >> >> 2. The strong convention of naming things ConfigurationOfXXXX is somewhat redundant from a user perspective. >> >> 3. If copy-paste into the Workspace from a web site a sample package load (for example b> below) and then highlight the whole thing and execute, it tells me >> "Unknown variable: ConfigurationOfSqueakDBX, please correct, or cancel" Duh! What? Oh, I need to execute it in two parts. No one wrote that down anywhere.... >> The alternative "(Smalltalk at: #ConfigurationOfSqueakDBX)" adds further complexity in the eyes of a newbie. >> >> Based on the above points, it would be nice to have... >> >> a> Metacello configuration: 'SqueakDBX' load >> >> rather than... >> >> b> Gofer new >> b> squeaksource: 'MetacelloRepository'; >> b> package: 'ConfigurationOfSqueakDBX'; >> b> load. >> b> ConfigurationOfSqueakDBX project latestVersion load. >> >> While only a small saving in typing, I think it significant for newbies in terms of polish and the marketing message that Metacello really is the chosen package management system. >> A very rough implementation (with much of the syntax likely wrong) might be just... >> >> c> Metacello class >> package: aPackage >> c> | packageConfig | >> c> packageConfig := 'ConfigurationOf', aPackage; >> c> Gopher new c> squeaksource: 'MetacelloRepository'; >> c> package: packageConfig >> c> load >> c> ^((Smalltalk at: (packageConfig asSymbol)) >> >> >> Now after I've written the above I contemplate that there must have been an early design decision to not implement a separate Metacello class to avoid duplication/overlap with Monticello. However perhaps now that the system is implemented as it is, a thin shim can be put over the top to assist getting the ConfigurationOfXXX files downloaded. Additional things this Metacello class might later provide: a. Improved reliability by downloading from a system of package repository mirrors. SqueakSource was having some issues and I found [1] a fortunate backup. b. A GUI for browsing package versions >> c. A GUI for browsing compatibility tables from a continuous integration system that tries different permutations of Montecello packages together. >> >> >> 4. It seems that every ConfigurationOfXXX has its own category in the SystemBrowser. Each of these categories has only one class. This seems to me like unneeded clutter of the System Browser. It would be neater if Metacello specified its configurations to be grouped under a single category "MetacelloConfigurations" or similar. >> >> 5. The sample Metacello PBE is very good in the detail for developers to provide configurations. However there is not much directed clearly at a 'mere' user. Even though Smalltalk makes us all developers, newbies all start as mere users while exploring the system. >> [1] Gofer new url: 'http://dsal.cl/squeaksource/MonticelloRedirect'; package: 'MontiRedirect'; load. MRManager redirectFrom: 'http://www.squeaksource.com/' to: 'http://dsal.cl/squeaksource/'. >> >> Cheers, Ben >> >> > > > >

Dec. 19, 2011

Re: [Pharo-project] Have you played with Ameba?

by Alexandre Bergel

Many of us are working on graphical/animation engine for Pharo. We should have a workshop at the next esug on this. The workshop could be just a couple of hours long where people can - do a demo of their engine - show their library and tell us how they can be reused - do pair programming Cheers, Alexandre On 19 Dec 2011, at 11:28, Fernando Olivero wrote: > Nice indeed! > > Are you using a kind of spring layout for the big bang animation? > > Fernando > > On Mon, Dec 19, 2011 at 2:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Dec 17, 2011, at 8:40 AM, HwaJong Oh wrote: >> >>> Markus, >>> >>> Forget Ameba. Ani is here. >>> >>> Zini das Wuslon is implemented. It moves like a real one. >>> >> >> Very nice! >> >> Marcus >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 19, 2011

Re: [Pharo-project] Have you played with Ameba?

by Fernando Olivero

Nice indeed! Are you using a kind of spring layout for the big bang animation? Fernando On Mon, Dec 19, 2011 at 2:38 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Dec 17, 2011, at 8:40 AM, HwaJong Oh wrote: > >> Markus, >> >> Forget Ameba. Ani is here. >> >> Zini das Wuslon is implemented. It moves like a real one. >> > > Very nice! > > Â Â Â Â Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > >

Dec. 19, 2011

[Pharo-project] [update 1.4] #14262

by Marcus Denker

14262 ----- Issue 5120: Morph>>stepTime comment addition http://code.google.com/p/pharo/issues/detail?id=5120 Issue 5115: pluggableButtonMorph sensor cleaning http://code.google.com/p/pharo/issues/detail?id=5115 Issue 5110: Certain classes cannot be uncompact http://code.google.com/p/pharo/issues/detail?id=5110 -- Marcus Denker -- http://marcusdenker.de

Dec. 19, 2011

Re: [Pharo-project] xpath queries

by Tudor Girba

Hi, I tried this one, too, but it does not work :) But, just for your information, it is the grammar (not the parser) that fails on this one. Cheers, Doru On Mon, Dec 19, 2011 at 2:15 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > mmm... > this one should work: > > /top/*/second > > (this is also valid in xpath, but not usually used... I'll add the wildcard as expected to next version) > > > El 19/12/2011, a las 10:10a.m., Tudor Girba escribiÃ³: > >> Thanks. It works now :) >> >> Regarding the wildcard expression (//), is it correct to assume that >> it does not work for now, or is there some hidden trigger? :) >> >> I tried this: >> xml := '<root> >> Â Â Â <top> >> Â Â Â Â Â Â Â <second/> >> Â Â Â </top> >> </root>'. >> element := PPXmlParser parse: xml. >> element find: '/top/second'. "--> this works fine" >> element find: '/top//second'. "--> this does not" >> >> Cheers, >> Doru >> >> On Mon, Dec 19, 2011 at 1:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> Hi, >>> >>> >>> El 19/12/2011, a las 9:11a.m., Tudor Girba escribiÃ³: >>> >>>> Thanks, Esteban. >>>> >>>> I gave it a try, but I cannot seem to make it work (and there are no tests :)). >>> >>> yes... I know that :( >>> I will add them when I can spare some time... and a couple of examples too :P >>> >>>> >>>> Here is an example of what I tried: >>>> xml := '<root> >>>> Â Â Â <topChild/> >>>> </root>'. >>>> element := PPXmlParser parse: xml. >>>> element find: 'root/topChild' >>> >>> there is a "known" issue (known by me :( ): >>> PetitXPath is ignoring "document root element"... this is a stupid error and I will fix it (real reason is that when I coded it, I assumed "first element is always unique, so... let's get rid of it"... and yes I know it was a stupid assumption... but I needed this working really fast or my client would became upset) >>> >>> So... if you do: >>> >>> element find: '/topChild' >>> >>> It should work... good thing is other ppl using this stuff encourages me to make it work as it should be :) >>> >>> cheers, >>> Esteban >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 19, 2011

Re: [Pharo-project] Have you played with Ameba?

by Marcus Denker

On Dec 17, 2011, at 8:40 AM, HwaJong Oh wrote: > Markus, > > Forget Ameba. Ani is here. > > Zini das Wuslon is implemented. It moves like a real one. > Very nice! Marcus -- Marcus Denker -- http://marcusdenker.de

Dec. 19, 2011

[Pharo-project] Christmas Greetings

by Noury Bouraqadi

Best wishes for everyone and go Pharo :-) A greetings video is available online http://car.mines-douai.fr/noury/blog Cheers, Noury -- http://twitter.com/#!/NouryBouraqadi

Dec. 19, 2011

Re: [Pharo-project] xpath queries

by Esteban Lorenzano

mmm... this one should work: /top/*/second (this is also valid in xpath, but not usually used... I'll add the wildcard as expected to next version) El 19/12/2011, a las 10:10a.m., Tudor Girba escribiÃ³: > Thanks. It works now :) > > Regarding the wildcard expression (//), is it correct to assume that > it does not work for now, or is there some hidden trigger? :) > > I tried this: > xml := '<root> > <top> > <second/> > </top> > </root>'. > element := PPXmlParser parse: xml. > element find: '/top/second'. "--> this works fine" > element find: '/top//second'. "--> this does not" > > Cheers, > Doru > > On Mon, Dec 19, 2011 at 1:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> >> El 19/12/2011, a las 9:11a.m., Tudor Girba escribiÃ³: >> >>> Thanks, Esteban. >>> >>> I gave it a try, but I cannot seem to make it work (and there are no tests :)). >> >> yes... I know that :( >> I will add them when I can spare some time... and a couple of examples too :P >> >>> >>> Here is an example of what I tried: >>> xml := '<root> >>> <topChild/> >>> </root>'. >>> element := PPXmlParser parse: xml. >>> element find: 'root/topChild' >> >> there is a "known" issue (known by me :( ): >> PetitXPath is ignoring "document root element"... this is a stupid error and I will fix it (real reason is that when I coded it, I assumed "first element is always unique, so... let's get rid of it"... and yes I know it was a stupid assumption... but I needed this working really fast or my client would became upset) >> >> So... if you do: >> >> element find: '/topChild' >> >> It should work... good thing is other ppl using this stuff encourages me to make it work as it should be :) >> >> cheers, >> Esteban > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 19, 2011