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

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

by Noury Bouraqadi

Hi HwaJong, On which image should I try it. I used pharo-1.3-13315 and Pharo-1.4-14225, but I couldn't run the examples. Best, Noury On 17 dÃ©c. 2011, at 08:40, HwaJong Oh wrote: > Markus, > > Forget Ameba. Ani is here. > > Zini das Wuslon is implemented. It moves like a real one. > > > Gofer new > squeaksource: 'DaliotsPlayground'; > package: 'ConfigurationOfDaliotsPlayground'; > load. > > (Smalltalk at: #ConfigurationOfDaliotsPlayground) project lastVersion load: > 'Ani' > > http://appdal.com/groups/36442/wiki/9eee9/Ani.html > > Best Regards > HwaJong Oh > > -- > View this message in context: http://forum.world.st/Have-you-played-with-Ameba-tp3585624p4207593.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > Noury -- http://twitter.com/#!/NouryBouraqadi

Dec. 19, 2011

Re: [Pharo-project] Fuel serialzing not truncating files

by Martin Dias

Hi Norbert, Thank you, it was wrong. We will include your fix will in next version. After releasing Fuel 1.7, we have moved from squeaksource to http://ss3.gemstone.com/ss/Fuel.html, so the fix is there. We always appreciate the feedback, thanks! MartÃn On Mon, Dec 19, 2011 at 3:47 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Hi Martin, Mariano, > > I wanted to check the permissions on squeaksource for fuel but > squeaksource is about to die. So I drop you a note here (because I don't > know a better place). > In FLSerializer>>serialize:toFileNamed: > > you should use > > StandardFileStream > forceNewFileNamed: aFilename > ... > > instead of > > StandardFileStream > fileNamed: aFilename > ... > > Yours does not truncate the file. If your model is shrinking then the file > stays of same size with garbage trailing. I didn't test if this introduces > read problems but I think truncating is the way to go. > > Norbert > > > >

Dec. 19, 2011

Re: [Pharo-project] Christmas Greetings

by Mariano Martinez Peck

heheheheh nice :) On Mon, Dec 19, 2011 at 6:09 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks noury. > I saw the commits on squeak source :) so I was waiting for your announce > :). > What you could do next is a "boule en verge souvenir" where you first have > a storm of snow falkex and they could also go up > then fall :) > > On Dec 19, 2011, at 2:34 PM, Noury Bouraqadi wrote: > > > 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 > > > > > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

Dec. 19, 2011

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

by Mariano Martinez Peck

Hi Ben. Some offtopic, but be aware that ConfigurationOfSqueakDBX is deprecated. The whole project has been renamed to DBXTalk and what was SqueakDBX is now DBXTalkOpenDBXDriver. You can find ConfigurationOfOpenDBXDriver in DBXTalk repo or MetacelloRepository. On Mon, Dec 19, 2011 at 6:11 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Dec 19, 2011, at 5:04 PM, Ben Coman wrote: > > > 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? > > > The problem is that we did not push it to the point the repository for > 1.0, contains only 1.0 configuration. > We will check that when esteban will arrive. > > > > > 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 > >>> > >>> > >> > >> > >> > >> > > > > > > > -- Mariano http://marianopeck.wordpress.com

Dec. 19, 2011

[Pharo-project] Fuel serialzing not truncating files

by Norbert Hartl

Hi Martin, Mariano, I wanted to check the permissions on squeaksource for fuel but squeaksource is about to die. So I drop you a note here (because I don't know a better place). In FLSerializer>>serialize:toFileNamed: you should use StandardFileStream forceNewFileNamed: aFilename ... instead of StandardFileStream fileNamed: aFilename ... Yours does not truncate the file. If your model is shrinking then the file stays of same size with garbage trailing. I didn't test if this introduces read problems but I think truncating is the way to go. Norbert

Dec. 19, 2011

Re: [Pharo-project] Anyone want more timezones in the base image?

by Paul DeBruicker

Thanks for the feedback. Comments below. Sven Van Caekenberghe wrote > > > I had a quick look at your code and it seems like a logical addition > (given what TimeZone currently is and what you want to do: interpret tz > abbreviations). I have 3 remarks/comments: > > - the list is currently a dynamic array that is recreated on every access, > wouldn't a lazy initialized class variable be better ? > Yes of course I would love that but I don't know how to create a class variable when just using extensions on a class. Is there a way? > - one other goal of a list of timezones is to present them to the user to > pick one; for that TimeZone as it stands now is insufficient (there is no > country/city mapping, which is the most user friendly way to pick one, > IMHO). it seems a bit wastefull to have such a list and not be able to > support that goal as well. > I agree but that would entail mapping also when each timezone is in effect in each locale during different times of the year. My Something the Chronos (http://www.chronos-st.org) package does and I think the TimeZoneDatabase from Dave Lewis does. My solution is definitely much simpler and less useful. > - on Mac OS X and Linux, there is enough data in /usr/share/zoneinfo to > dynamically load/parse from, if something equivalent existed on Windows, > we could use that (and benefit from OS level updates to this DB); I know > it is more work, I'm just thing out loud. > I'm glad you are thinking about it. Dave Lewis's TimeZoneDatabase does this, I think not on windows but I'm not positive. . It also seems to me that adopting the TimeZoneDatabase is natural next step for the TimeZone/Chronology package to go if there's reason to make Pharo better able to handle cross-timezone issues. But it would need to have a source for Olson time zone data on Windows. Dave has created a primitive (primitiveUtcWithOffset) in the interpreterVM that would be good to port to the CogVM. Chronos is great and exact but also Big in the image. -- View this message in context: http://forum.world.st/Anyone-want-more-timezones-in-the-base-image-tp420639… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 19, 2011

Re: [Pharo-project] 1.3, PBE and lab setups

by StÃ©phane Ducasse

On Dec 19, 2011, at 6:30 PM, Dave Mason wrote: > For those following along at home, we are definitely doing the Advanced Algorithms course in Smalltalk using Pharo 1.3, cool ! > so this has become a critical path for me - see below. > > On Dec 15, 2011, at 2:24 AM, Serge Stinckwich wrote: > >> 2011/12/15 Dave Mason <dmason(a)mason-rose.ca>: >>> Additionally, the PBE book doesn't play well with 1.3 (things that the book >>> says die when you try them). >>> >>> is the PBE book getting updated to work with a vanilla 1.3/1.4 image? >> >> There is no plan at the moment to do that, but you could help adapt >> the Pharo Book to the new images. >> Maybe we can have branches for each version of Pharo ? pharo1.2, >> pharo1.3, etc â¦ > > I've imported the git repo into a local mercurial one, and we'll work from that. > > On Dec 15, 2011, at 05:17, Oscar Nierstrasz wrote: > >> Sure, that would be great, but please be aware that you must also check that the examples (and tests) work as advertised. >> >> If someone wants to do this please contact me, and I can give some advice and help ... > > I have 2 grad students who are working through PBE and will be TAs for the course. They will work through each of the examples in 1.3 and correct discrepancies. I'll check for language and wording, and commit the results. I'm hoping this will be nearly complete by early January. I'll commit the results back to github. in the read me you will see that you can run automatically the code of the book so that we can catch the discrepancies. I think that the problem is more at the level of the user interface than the libraries. > We'll be working on 1.3 only. If useful, someone could go through and decide whether the 1.1 or 1.3 version is more appropriate for each example in 1.2, but I presume that isn't as useful. Going forward, we'll probably update it for 1.4 when it's stable. > > ../Dave

Dec. 19, 2011

Re: [Pharo-project] 1.3, PBE and lab setups

by Dave Mason

For those following along at home, we are definitely doing the Advanced Algorithms course in Smalltalk using Pharo 1.3, so this has become a critical path for me - see below. On Dec 15, 2011, at 2:24 AM, Serge Stinckwich wrote: > 2011/12/15 Dave Mason <dmason(a)mason-rose.ca>: >> Additionally, the PBE book doesn't play well with 1.3 (things that the book >> says die when you try them). >> >> is the PBE book getting updated to work with a vanilla 1.3/1.4 image? > > There is no plan at the moment to do that, but you could help adapt > the Pharo Book to the new images. > Maybe we can have branches for each version of Pharo ? pharo1.2, > pharo1.3, etc â¦ I've imported the git repo into a local mercurial one, and we'll work from that. On Dec 15, 2011, at 05:17, Oscar Nierstrasz wrote: > Sure, that would be great, but please be aware that you must also check that the examples (and tests) work as advertised. > > If someone wants to do this please contact me, and I can give some advice and help ... I have 2 grad students who are working through PBE and will be TAs for the course. They will work through each of the examples in 1.3 and correct discrepancies. I'll check for language and wording, and commit the results. I'm hoping this will be nearly complete by early January. I'll commit the results back to github. On 15 Dec 2011, at 08:48, stephane ducasse wrote: > yes this would be really good to have a branch We'll be working on 1.3 only. If useful, someone could go through and decide whether the 1.1 or 1.3 version is more appropriate for each example in 1.2, but I presume that isn't as useful. Going forward, we'll probably update it for 1.4 when it's stable. ../Dave

Dec. 19, 2011

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

by StÃ©phane Ducasse

On Dec 19, 2011, at 5:04 PM, Ben Coman wrote: > 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? The problem is that we did not push it to the point the repository for 1.0, contains only 1.0 configuration. We will check that when esteban will arrive. > > 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] Christmas Greetings

by StÃ©phane Ducasse

Thanks noury. I saw the commits on squeak source :) so I was waiting for your announce :). What you could do next is a "boule en verge souvenir" where you first have a storm of snow falkex and they could also go up then fall :) On Dec 19, 2011, at 2:34 PM, Noury Bouraqadi wrote: > 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