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

Re: [Pharo-project] Failing Gofer test in windows [WAS] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

Lukas...maybe MCSubDirectoryRepository >> description is wrong and it should be MCSubDirectoryRepository >> description ^ directory pathName, FileDirectory slash, '*' What do you think ? On Mon, Jan 25, 2010 at 10:30 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Ok, i passes now: > > Name: Gofer-Tests-lr.115 > Author: lr > Time: 25 January 2010, 10:30:34 pm > UUID: ec6e1ded-492e-470e-b41a-468265edfc9e > Ancestors: Gofer-Tests-lr.114 > > - killed a test > > 2010/1/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Lukas, it is still failing because when you ask the description to first, > it > > is -> > > > > 'C:\mariano\squeak\imagenes\Pharo1.0-10508-rc2dev10.01.2//*' > > > > Double slash. And that's due to > > > > MCSubDirectoryRepository >> description > > ^ directory pathName, '/*' > > > > > > Cheers > > > > Mariano > > > > > > On Mon, Jan 25, 2010 at 9:46 PM, Lukas Renggli <renggli(a)gmail.com> > wrote: > >> > >> Thanks for figuring out. The following change should fix that problem: > >> > >> Name: Gofer-Tests-lr.114 > >> Author: TestRunner > >> Time: 25 January 2010, 9:45:44 pm > >> UUID: 9dafc930-c2ed-4619-a7ce-d77984e17edd > >> Ancestors: Gofer-Tests-lr.113 > >> > >> - fixed a bug in gofer under windows > >> > >> 2010/1/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> > > >> >> I cannot reproduce the Gofer test failure. Can you debug it and/or > >> >> provide a stack trace? > >> >> > >> > > >> > Ok...I put off the dust from my virtual box image with windows and I > >> > could > >> > reproduce the problem. > >> > > >> > GoferApiTest >> testSubDirectoryRepository > >> > > >> > fails in > >> > > >> > self assert: gofer repositories: (Array with: FileDirectory default > >> > pathName > >> > , FileDirectory slash , '*') > >> > > >> > Because in assert: aGofer repositories: anArray I can see that: > >> > > >> > "first description" is -> > >> > 'C:\mariano\squeak\imagenes\Pharo1.0-10508-rc2dev10.01.2/*' > >> > > >> > and "second" is -> > >> > 'C:\mariano\squeak\imagenes\Pharo1.0-10508-rc2dev10.01.2\*' > >> > > >> > Notice the last slash. They are different. > >> > > >> > Cheers > >> > > >> > Mariano > >> > > >> > > >> >> > >> >> Lukas > >> >> > >> >> -- > >> >> Lukas Renggli > >> >> http://www.lukas-renggli.ch > >> >> > >> >> _______________________________________________ > >> >> 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 > >> > > >> > >> > >> > >> -- > >> Lukas Renggli > >> http://www.lukas-renggli.ch > >> > >> _______________________________________________ > >> 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 > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 26, 2010

Re: [Pharo-project] new mac menu code :)

by Adrian Lienhard

I think we should apply the patch to 1.0, but not add the host menu support again. Like this, if somebody really wants to use the menus, he can load them into 1.0. And I very much like the idea of making the host menu package *not* being part of the core but load it into the Pharo image! We just need a Metacello configuration and we load it into the dev image. Cheers, Adrian On Jan 26, 2010, at 09:30 , Michael Roberts wrote: > I think really it should go only into 1.1 if you mean the core. We do > a quicker 1.1 cycle and get it released and stable. Perhaps it could > be loadable as a package on top of the core anyway? > > Cheers mike > > On Tuesday, January 26, 2010, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> >> >> On Tue, Jan 26, 2010 at 12:26 AM, John M McIntosh <johnmci(a)smalltalkconsulting.com> wrote: >> >> Ok, I figured it out, well I think I did.. Mariano is confirming... But I'll post the expected fix in this email. >> >> >> >> wiiiiiiiiiiiiiiii !!!! At the end you made it!!! It worked :):):):):):):):):):):):):):):):):):):):):):):):):):) >> >> I also sent you in private what you ask me. >> >> >> >> >> >> >> As for the changes earlier posted, we should run with those. Michael altered them to make the logic cleaner, and >> I had to change the cmd-key to synthetic key generation to meet expectations based on changes done in the last 5 years. >> >> >> So...we need to integrate those two changes (michael one first, then your) and finally this changeset in peeckEvent ? >> >> Can me integrate this in 1.0 or only 1.1 ? >> >> >> On 2010-01-25, at 12:14 PM, StÃ©phane Ducasse wrote: >> >>>> File in Michael's change first, then mine >> >> -- >> =========================================================================== >> 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

Jan. 26, 2010

Re: [Pharo-project] Failing Gofer test in windows [WAS] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

On Mon, Jan 25, 2010 at 11:43 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > > Just make a bug report and put the version in the inbox (and make sure > it's mergable, that is, > > provide all nececary intermediate versions) > > It probably won't merge because I splitted the package into a Core and > a Test package, so the tests don't have to be present as well. > But in the latest images this is already merged. I mean, we have also those two packages. > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 26, 2010

Re: [Pharo-project] Failing Gofer test in windows [WAS] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Marcus Denker

On Jan 25, 2010, at 11:43 PM, Lukas Renggli wrote: >> Just make a bug report and put the version in the inbox (and make sure it's mergable, that is, >> provide all nececary intermediate versions) > > It probably won't merge because I splitted the package into a Core and > a Test package, so the tests don't have to be present as well. > I added two entries to the tracker (for 1.0 and 1.1) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 26, 2010

Re: [Pharo-project] help with removing a file

by Mariano Martinez Peck

2010/1/26 John M McIntosh <johnmci(a)smalltalkconsulting.com> > I *think* you can run into problems if your evil windows virus package has > the file OPEN has it's trying to figure out which of the 100 million viruses > could exist in the file. > This can cause your delete to fail. Maybe you have to wait 1000 > milliseconds? for Norton to catch up? > > Thanks John for the tip, but I don't have any antivirus or similar installed :( > The windows code runs the following code, and there is a FAIL check to see > if there is a duplicate file name based on case sensitivity. > > sqInt sqFileDeleteNameSize(char* fileNameIndex, sqInt fileNameSize) { > WCHAR win32Path[MAX_PATH+1]; > int sz; > /* convert the file name into a null-terminated C string */ > sz = MultiByteToWideChar(CP_UTF8, 0, fileNameIndex, fileNameSize, NULL, > 0); > if(sz > MAX_PATH) FAIL(); > MultiByteToWideChar(CP_UTF8, 0, fileNameIndex, fileNameSize, win32Path, > sz); > win32Path[sz] = 0; > if(hasCaseSensitiveDuplicate(win32Path)) FAIL(); > if(!DeleteFileW(win32Path)) FAIL(); > return 1; > } > > > > On 2010-01-25, at 2:07 PM, Mariano Martinez Peck wrote: > > Hi folks. I don't want other than green tests in dev images, thus, I > started to fix them as much as possible. There are a lot of failing tests of > Nile (only fail in windows). The test is NSCompressedSourceStreamTest and I > noticed something weird. If you look to tearDown method, it tries to remove > two files that it actually were created in the setUp method. > > But it is weird because it tries to remove a file that actually exist and > it is not being removed. > > If I debug in DosFileDirectory >> deleteFileNamed: localFileName ifAbsent: > failBlock > > everything looks ok, but the file is not removed and the failBlock is > executed :( > > localFileName -> 'testCompressedSourceStream.stc' > > (self fullNameFor: localFileName) asVmPathName -> > 'C:\mariano\squeak\imagenes\Pharo1.0-10508-rc2dev10.01.2\testCompressedSourceStream.stc' > > And that file exist, as you can see in screenshot that I attach. > > Can someone help me with this ? > > Cheers > > Mariano > <Picture 2.png>_______________________________________________ > 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 >

Jan. 26, 2010

Re: [Pharo-project] new mac menu code :)

by Michael Roberts

I think really it should go only into 1.1 if you mean the core. We do a quicker 1.1 cycle and get it released and stable. Perhaps it could be loadable as a package on top of the core anyway? Cheers mike On Tuesday, January 26, 2010, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Tue, Jan 26, 2010 at 12:26 AM, John M McIntosh <johnmci(a)smalltalkconsulting.com> wrote: > > Ok, I figured it out, well I think I did.. Mariano is confirming... But I'll post the expected fix in this email. > > > > wiiiiiiiiiiiiiiii !!!!Â At the end you made it!!!Â It worked :):):):):):):):):):):):):):):):):):):):):):):):):):) > > I also sent you in private what you ask me. > > > > > > > As for the changes earlier posted, we should run with those. Michael altered them to make the logic cleaner, and > I had to change the cmd-key to synthetic key generation to meet expectations based on changes done in the last 5 years. > > > So...we need to integrate those two changes (michael one first, then your) and finally this changeset in peeckEvent ? > > Can me integrate this in 1.0 or only 1.1Â ? > > > On 2010-01-25, at 12:14 PM, StÃ©phane Ducasse wrote: > >>> File in Michael's change first, then mine > > -- > =========================================================================== > 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 > >

Jan. 26, 2010

[Pharo-project] About ScriptManager [ WAS] How do I save the contents of a Workspace?

by Mariano Martinez Peck

Hi: I didn't know ScriptManager, but seems to be very cool. I remember having something VERYYYY similar in VAST. However, in this case it was cooler becuase it was stored in the "user slot" of ENVY. So, it doesn't matter which image to take you always have it there. But here I can export it to a file...so it is cool. I think that with a bit of work and test, we can include it in future Dev images. What do you think ? Torsten: I would be cool to fix the underscore assignments on it. I also found a little bug: - Choose a folder, put export, and then cancel. You will have a DNU beep. You already pointed that here: http://code.google.com/p/pharo/issues/detail?id=410 So....you can just change it to Beeper beep :) Cheers Mariano ---------- Forwarded message ---------- From: HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> Date: Tue, Jan 26, 2010 at 2:55 AM Subject: Re: [Pharo-project] [newbee] How do I save the contents of a Workspace? To: Pharo-project(a)lists.gforge.inria.fr Hi Alex, Notice that you don't need files to save workspaces, you may like the ScriptManager package, to install simply evaluate: Gofer new squeaksource: 'DeveloperWorkspace'; package: 'ScriptManager'; load. and open it from Tools -> More -> Script Manager Cheers, HernÃ¡n 2009/12/16 alesch <alex(a)schenkman.info>: > > I remember I used a menu item in Squeak, but I cannot find in Pharo. > > Thanks! > -- > View this message in context: http://n2.nabble.com/newbee-How-do-I-save-the-contents-of-a-Workspace-tp417… > Sent from the Pharo Smalltalk mailing list archive at Nabble.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

Jan. 26, 2010

Re: [Pharo-project] new mac menu code :)

by Mariano Martinez Peck

On Tue, Jan 26, 2010 at 12:26 AM, John M McIntosh < johnmci(a)smalltalkconsulting.com> wrote: > Ok, I figured it out, well I think I did.. Mariano is confirming... But > I'll post the expected fix in this email. > > wiiiiiiiiiiiiiiii !!!! At the end you made it!!! It worked :):):):):):):):):):):):):):):):):):):):):):):):):):) I also sent you in private what you ask me. > > As for the changes earlier posted, we should run with those. Michael > altered them to make the logic cleaner, and > I had to change the cmd-key to synthetic key generation to meet > expectations based on changes done in the last 5 years. > > So...we need to integrate those two changes (michael one first, then your) and finally this changeset in peeckEvent ? Can me integrate this in 1.0 or only 1.1 ? > > On 2010-01-25, at 12:14 PM, StÃ©phane Ducasse wrote: > > >> File in Michael's change first, then mine > > -- > =========================================================================== > 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 >

Jan. 26, 2010

Re: [Pharo-project] Monticello diff between chosen revisionsisbroken

by StÃ©phane Ducasse

gary what would be great is to have a label on top of the two methods shown I never now what I'm reading Incoming InWorkingCopy New Current would be so great! Stef On Jan 25, 2010, at 7:25 PM, Gary Chambers wrote: > Yes, in this case it is a bug with Polymorph. > > Try with > > MCVersionInspector>>changes > "Open a patch morph for the changes." > > self viewChanges: self version changes > > > Hopefully no bad side-effects... > > With a bit more work it may be possible to show both versions between which the changes apply (unlike the old MC tools) ;-) > > Regards, Gary > ----- Original Message ----- > From: Gary Chambers > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Monday, January 25, 2010 6:05 PM > Subject: Re: [Pharo-project] Monticello diff between chosen revisionsisbroken > > > MCVersionInspector>>diff > | ancestorVersion | > self pickAncestor ifNotNil: > [:ancestor | > ancestorVersion := self version workingCopy repositoryGroup versionWithInfo: ancestor. > (self version asDiffAgainst: ancestorVersion) open] > > > Regards, Gary > ----- Original Message ----- > From: Gary Chambers > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Monday, January 25, 2010 5:50 PM > Subject: Re: [Pharo-project] Monticello diff between chosen revisionsisbroken > > Needs looking at since it is confusing. IIRC the Diff button creates a .mcd file of the changes between some versions... > > Regards, Gary > ----- Original Message ----- > From: Mariano Martinez Peck > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Monday, January 25, 2010 5:34 PM > Subject: Re: [Pharo-project] Monticello diff between chosen revisionsisbroken > > > > 2010/1/25 Gary Chambers <gazzaguru2(a)btinternet.com> > The "Diff" button on the Monticello repository browser does what its balloon help says... > > 'Create an equivalent version based on an earlier release'. This is a diff version. I never use them as they can be confusing :-) > > > Ok...I never used before...but something is clear: the second ask about a version, has no sense, and even is wrong if it compares to the last version. See step 6 of Stefan. Then, we have to options: > > - Or we remove that second prompt, as it always will use the last version > - Or we change the diff implementation so that it uses the selected version instead of the last. > > What do you think ? > > Does someone really know what this "diff" should do ? > > Cheers > > Mariano > > If you want to compare two existing versions you should: > > 1. Open Monticello Browser > 2. Select a repo > 3. click open > 4. Select a revision, not the latest one > 5. Click HISTORY > > 6. chose an ancestor from the list > > > Regards, Gary > ----- Original Message ----- > From: Mariano Martinez Peck > To: Pharo-project(a)lists.gforge.inria.fr > Cc: Lukas Renggli > Sent: Sunday, January 24, 2010 12:59 PM > Subject: Re: [Pharo-project] Monticello diff between chosen revisions isbroken > > > > On Sat, Jan 23, 2010 at 9:51 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > Hi: > > In the current dev image (10508), Monticello is broken with respect to showing the differences of between chosen revisions. > > However, that seems to be broken already in 10496. (and maybe earlier) > > To reproduce: > > 1. Open Monticello Browser > 2. Select a repo > 3. click open > 4. Select a revision, not the latest one > 5. Click diff > 6. chose an ancestor from the list > Now you got a window 'Version: ...5' > Saying (Diff against ...2) > Here I would expect the changes button to open a window showing the changes between the chosen revisions, but it always diffs against the latest version. > > > Yes, I could reproduce the problem. Can you open a ticket ? > > Maybe Lukas Monticello guru can help us ? hahaha > > Cheers > > Mariano > > > Best > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 3956 > Fax: +32 2 629 3525 > > > _______________________________________________ > 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 > > > > _______________________________________________ > 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 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 26, 2010

Re: [Pharo-project] Monticello diff between chosen revisionsisbroken

by StÃ©phane Ducasse

Yes let us remove that. Stef On Jan 25, 2010, at 7:10 PM, Lukas Renggli wrote: >> Needs looking at since it is confusing. IIRC the Diff button creates a .mcd >> file of the changes between some versions... > > No this has nothing to do with .mcd. The .mcd thing was an experiment > (that should probably better be removed again) that did not always > safe a complete package but only a delta to the ancestor. I think it > has never been used in production and is quite buggy. > > Lukas > > > >> Regards, Gary >> >> ----- Original Message ----- >> From: Mariano Martinez Peck >> To: Pharo-project(a)lists.gforge.inria.fr >> Sent: Monday, January 25, 2010 5:34 PM >> Subject: Re: [Pharo-project] Monticello diff between chosen >> revisionsisbroken >> >> >> 2010/1/25 Gary Chambers <gazzaguru2(a)btinternet.com> >>> >>> The "Diff" button on the Monticello repository browser does what its >>> balloon help says... >>> >>> 'Create an equivalent version based on an earlier release'. This is a >>> diff version. I never use them as they can be confusing :-) >>> >> >> Ok...I never used before...but something is clear: the second ask about a >> version, has no sense, and even is wrong if it compares to the last version. >> See step 6 of Stefan. Then, we have to options: >> - Or we remove that second prompt, as it always will use the last version >> - Or we change the diff implementation so that it uses the selected version >> instead of the last. >> What do you think ? >> Does someone really know what this "diff" should do ? >> Cheers >> Mariano >> >>> >>> If you want to compare two existing versions you should: >>> >>> 1. Open Monticello Browser >>> 2. Select a repo >>> 3. click open >>> 4. Select a revision, not the latest one >>> 5. Click HISTORY >>> 6. chose an ancestor from the list >>> >>> Regards, Gary >>> >>> ----- Original Message ----- >>> From: Mariano Martinez Peck >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Cc: Lukas Renggli >>> Sent: Sunday, January 24, 2010 12:59 PM >>> Subject: Re: [Pharo-project] Monticello diff between chosen revisions >>> isbroken >>> >>> >>> On Sat, Jan 23, 2010 at 9:51 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: >>>> >>>> Hi: >>>> >>>> In the current dev image (10508), Monticello is broken with respect to >>>> showing the differences of between chosen revisions. >>>> >>>> However, that seems to be broken already in 10496. (and maybe earlier) >>>> >>>> To reproduce: >>>> >>>> 1. Open Monticello Browser >>>> 2. Select a repo >>>> 3. click open >>>> 4. Select a revision, not the latest one >>>> 5. Click diff >>>> 6. chose an ancestor from the list >>>> Now you got a window 'Version: ...5' >>>> Saying (Diff against ...2) >>>> Here I would expect the changes button to open a window showing the >>>> changes between the chosen revisions, but it always diffs against the latest >>>> version. >>>> >>> >>> Yes, I could reproduce the problem. Can you open a ticket ? >>> >>> Maybe Lukas Monticello guru can help us ? hahaha >>> >>> Cheers >>> >>> Mariano >>> >>>> >>>> Best >>>> Stefan >>>> >>>> -- >>>> Stefan Marr >>>> Software Languages Lab >>>> Vrije Universiteit Brussel >>>> Pleinlaan 2 / B-1050 Brussels / Belgium >>>> http://soft.vub.ac.be/~smarr >>>> Phone: +32 2 629 3956 >>>> Fax: +32 2 629 3525 >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> ________________________________ >> >> _______________________________________________ >> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 26, 2010