March 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] fog monkey bugz

by Norbert Hartl

Yesterday I registered for an account on bugs.pharo.org. I enteres username (NorbertHartl) and email and assured I'm not monkey. I got to the fogbugz page but not logged in. I didn't receive an email to set a password or something like that. How is it supposed to work? Norbert

March 25, 2013

[Pharo-project] Squeak Community Hangout - now!

by GÃ¶ran Krampe

Hey! I think it would be nice to blend the Squeak and Pharo communities a bit more - thus I am forwarding this to the Pharo list. Hope some of you drop by! regards, GÃ¶ran -------- Original Message -------- Subject: [Newbies] Squeak Community Monday - today Date: Mon, 25 Mar 2013 08:46:52 +0100 From: Bert Freudenberg <bert(a)freudenbergs.de> Two weeks ago we had lots of fun talking about everything from the VM (several VM hackers stopped by) over OpenQWAQ / Immersive Terf (3D stuff is always fascinating) and tablet UIs (the next big thing is here already) to Metacello and git (with Dale, our cross-dialect hero). But mostly we had fun :) Today we're opening a hangout again for 24 hours so everyone worldwide can get their chance: https://plus.google.com/events/cgrv2ob01fsga5ppbunjdg55fnk Feel free to drop by and say hello! - Bert

March 25, 2013

Re: [Pharo-project] [pharo website] updated the issue tracking page

by Marcus Denker

>>> >>> >> Ok, then how would you fix that >> >> bugs.pharo-project.org >> >> points to the google tracker? Let me guess! :) >> > This is fixed now (thanks to Stefan Reichart). Marcus

March 25, 2013

[Pharo-project] [update 3.0] #30011

by Marcus Denker

30011 ----- 7578 Remove String asPacked/fromPacked: protocol https://pharo.fogbugz.com/f/cases/7578 7598 Nautilus>>class #cleanUpForProduction --> just cleanUp https://pharo.fogbugz.com/f/cases/7598/ 10117 remove class TestURI https://pharo.fogbugz.com/f/cases/10117 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Tools-MarcusDenker.1065 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/NetworkTests-MarcusDenker.81 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Nautilus-MarcusDenker.436 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Strings-MarcusDe…

March 25, 2013

Re: [Pharo-project] extra class category added in Pharo-2.0 for Monticello package

by Sven Van Caekenberghe

Hi Yanni, On 25 Mar 2013, at 04:42, Yanni Chiu <yanni(a)rogers.com> wrote: > When I load a Monticello package that was developed in Pharo-1.X, into a Pharo-2.0 image, I get an extra category created. For example, a package named "Some-Thing-author.n.mcz" originally contained class categories: > > Some-Thing-Model > Some-Thing-View > > In the Pharo-2.0 system browser, I see an extra category, like: > > Some-Thing > Some-Thing-Model > Some-Thing-View > > I thought it was just an artifact of the new browser. However, when I do a diff, before saving the changes to a Monticello version, I see that the "Some-Thing" is flagged as diff. > > Will this extra class category cause any trouble, if I want to load the new Monticello version into a Pharo-1.4 image? In your case, there will be a virtual/extra category in the browser called 'Some-Thing' to show the extension methods. For MC, the package is still 'Some-Thing', as far as diffs are concerned. This seems normal to me. That being said, sometimes strange things happen ;-) Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

March 25, 2013

[Pharo-project] extra class category added in Pharo-2.0 for Monticello package

by Yanni Chiu

When I load a Monticello package that was developed in Pharo-1.X, into a Pharo-2.0 image, I get an extra category created. For example, a package named "Some-Thing-author.n.mcz" originally contained class categories: Some-Thing-Model Some-Thing-View In the Pharo-2.0 system browser, I see an extra category, like: Some-Thing Some-Thing-Model Some-Thing-View I thought it was just an artifact of the new browser. However, when I do a diff, before saving the changes to a Monticello version, I see that the "Some-Thing" is flagged as diff. Will this extra class category cause any trouble, if I want to load the new Monticello version into a Pharo-1.4 image?

March 25, 2013

[Pharo-project] Password reset/reminder for SmalltalkHub

by Esteban A. Maringolo

As usual, I forgot my SmalltalkHub password. At the third attempt, I entered the right one. However, before that I was about to click on a "forgot password?" or similar option. But I couldn't find it. Is there a way to reset it or email it back to me? Regards Esteban A. Maringolo

March 25, 2013

Re: [Pharo-project] [ANN] Phratch: Scratch on Pharo2.0

by Frank Shearar

On 24 March 2013 19:56, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hi Pharoers, > > I am porting Scratch and BYOB on Pharo 2.0. The name of the project is Phratch. > To begin, I took Scat (a port of Scratch on Pharo1.3) and modify it to make it work on Pharo 2.0. For that I integrated FileSystem. > Then, I took BYOB and port it in the project. > > I have some bugs, but the main features are working. > The main issue is that it is slow. I will investigate that too. > > The goal for me is to use it for teaching software engineering and robotics. > I hope to use Phratch and Pharo 2.0 to create new features. > > The project is on SmalltalkHub, and a google code page is available, mainly for reporting issues: https://code.google.com/p/phratch/ > > To download Phratch, just run this code: > > Gofer it > url: 'http://smalltalkhub.com/mc/JLaval/Phratch/main'; > package: 'ConfigurationOfPhratch'; > load. > (Smalltalk at: #ConfigurationOfPhratch) loadBleedingEdge. > > Cheers, > Jannik Cool! Tim Rowledge is hackin on Scratch directly, with the aim of improving its code, particularly performance wise. You might want to drop him an email and see if you can make use of his efforts. frank

March 24, 2013

Re: [Pharo-project] Loading webdoc

by stephane ducasse

On Mar 24, 2013, at 10:43 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > it does not load and fails on the strange statement: > > spec configuration: 'Swazoo2' with: [ > spec version: #stable; > loads: #( 'Swazoo'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > > dunno, to me this looks strange and should read rather > > spec project: 'Swazoo2' with: [ > spec version: #stable; > loads: #( 'Swazoo'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > > no? me too. You should add className: 'ConfigurationOfâ¦. May configuration: was introduced I wrote that this is optional in the chapter because I thought that dale changed it but no. spec project: 'CoolBrowser default' with: [ spec className: 'ConfigurationOfCoolBrowser'; ''this is optional'' loads: #('default'); ''this is optional'' repository: 'http://www.example.com/CoolBrowser' ]. > > On 2013-03-24, at 21:01, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> On the seaside dev list I asked if there was a conf and was pointed to: >> >> http://www.squeaksource.com/Seaside31/ >> >> and told to look at the config class comment. >> >> FWIW, loading packages as told by Sven worked, Seaside runs on my 2.0 >> >> Phil >> >> 2013/3/24 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> On 24 Mar 2013, at 20:15, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> On 2013-03-24, at 20:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>> On 24 Mar 2013, at 19:37, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>> >>>>>> On 2013-03-24, at 19:33, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>>> >>>>>>> Hi Camillo! >>>>>>> >>>>>>> I was trying to load webdoc but there are a lot of not loading dependencies >>>>>>> (Seaside, grease, Omnibrowser...)... The configuration does not load for >>>>>>> 1.4 nor for 2.0... I was using this snippets: >>>>>>> >>>>>>> for 2.0 >>>>>>> >>>>>>> Gofer new >>>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>>>>>> configurationOf: 'WebDoc'; >>>>>>> loadDevelopment. >>>>>>> >>>>>>> for 1.4 >>>>>>> >>>>>>> Gofer new >>>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>>>>>> package: 'ConfigurationOfWebDoc'; >>>>>>> load. >>>>>>> >>>>>>> ConfigurationOfWebDoc loadDevelopment. >>>>>>> >>>>>>> Any hint? How did you bypass them in a safe way? >>>>>>> tx, >>>>>>> Guille >>>>>> >>>>>> for 1.4 it should work out of the box. >>>>>> >>>>>> for 2.0 I can only make it work after there is a valid Configuration for >>>>>> seaside :/. >>>>>> So for now under 2.0 you have to follow this stupid manual process: >>>>>> - get a 2.0 seaside image: >>>>>> https://ci.inria.fr/pharo-contribution/job/Seaside-2.0/ >>>>>> - manually install the dev version of PPMarkdownParser from: >>>>>> http://smalltalkhub.com/#!/~dh83/petitmarkdown >>>>>> - then load the latest package from for 2.0 from here: >>>>>> http://smalltalkhub.com/#!/~dh83/webdoc >>>>>> >>>>>> Maybe I missed that there is now a 2.0 config for seaside, if that is so >>>>>> let me know and I will create a proper configuration for webdoc, beacuse >>>>>> this process here is plain stupid :D. >>>>> >>>>> It seems like the whole world is waiting for this elusive configuration, what a messâ¦ >>>>> >>>>> It is just a question of making some decisions and going forward. >>>> >>>> I guess I missed the point, but can't we just make the configuration do >>>> whatever the jenkins job does and declare it as the development version >>>> for 2.0? >>> >>> We (as the Pharo community) will most probably have to do that, but it is not the right way or the best for the future. >>> >>> Seaside has currently two main versions 3.0.x and 3.1 and targets many platforms, that is what Metacello is for, but it makes the config complex. Normally, the main Seaside developers should have to do this, it is their (communities') code. >>> >>> Sven >>> >>> >> > >

March 24, 2013

Re: [Pharo-project] Loading webdoc

by Camillo Bruni

it does not load and fails on the strange statement: spec configuration: 'Swazoo2' with: [ spec version: #stable; loads: #( 'Swazoo'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. dunno, to me this looks strange and should read rather spec project: 'Swazoo2' with: [ spec version: #stable; loads: #( 'Swazoo'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. no? On 2013-03-24, at 21:01, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > On the seaside dev list I asked if there was a conf and was pointed to: > > http://www.squeaksource.com/Seaside31/ > > and told to look at the config class comment. > > FWIW, loading packages as told by Sven worked, Seaside runs on my 2.0 > > Phil > > 2013/3/24 Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> On 24 Mar 2013, at 20:15, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> On 2013-03-24, at 20:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> On 24 Mar 2013, at 19:37, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>>> On 2013-03-24, at 19:33, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>> >>>>>> Hi Camillo! >>>>>> >>>>>> I was trying to load webdoc but there are a lot of not loading dependencies >>>>>> (Seaside, grease, Omnibrowser...)... The configuration does not load for >>>>>> 1.4 nor for 2.0... I was using this snippets: >>>>>> >>>>>> for 2.0 >>>>>> >>>>>> Gofer new >>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>>>>> configurationOf: 'WebDoc'; >>>>>> loadDevelopment. >>>>>> >>>>>> for 1.4 >>>>>> >>>>>> Gofer new >>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main'; >>>>>> package: 'ConfigurationOfWebDoc'; >>>>>> load. >>>>>> >>>>>> ConfigurationOfWebDoc loadDevelopment. >>>>>> >>>>>> Any hint? How did you bypass them in a safe way? >>>>>> tx, >>>>>> Guille >>>>> >>>>> for 1.4 it should work out of the box. >>>>> >>>>> for 2.0 I can only make it work after there is a valid Configuration for >>>>> seaside :/. >>>>> So for now under 2.0 you have to follow this stupid manual process: >>>>> - get a 2.0 seaside image: >>>>> https://ci.inria.fr/pharo-contribution/job/Seaside-2.0/ >>>>> - manually install the dev version of PPMarkdownParser from: >>>>> http://smalltalkhub.com/#!/~dh83/petitmarkdown >>>>> - then load the latest package from for 2.0 from here: >>>>> http://smalltalkhub.com/#!/~dh83/webdoc >>>>> >>>>> Maybe I missed that there is now a 2.0 config for seaside, if that is so >>>>> let me know and I will create a proper configuration for webdoc, beacuse >>>>> this process here is plain stupid :D. >>>> >>>> It seems like the whole world is waiting for this elusive configuration, what a messâ¦ >>>> >>>> It is just a question of making some decisions and going forward. >>> >>> I guess I missed the point, but can't we just make the configuration do >>> whatever the jenkins job does and declare it as the development version >>> for 2.0? >> >> We (as the Pharo community) will most probably have to do that, but it is not the right way or the best for the future. >> >> Seaside has currently two main versions 3.0.x and 3.1 and targets many platforms, that is what Metacello is for, but it makes the config complex. Normally, the main Seaside developers should have to do this, it is their (communities') code. >> >> Sven >> >> >

March 24, 2013