- Pharo-dev - lists.pharo.org

[Pharo-project] [update] #10516

by Marcus Denker

10516 ----- Issue 2215: testFontFullName recursively deletes all files in the image directory -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 29, 2010

Re: [Pharo-project] squeakToUTF-8 and related?

by StÃ©phane Ducasse

Thanks john. >>> You should ask Sophie team, their knowledge certainly is far more >>> advanced than mine. >> >> The problem is that most of them disappeared after the java rewrite announce. > > Ok, well it's not as if we disappeared from the planet... > > The UTF8 work came out of work done on the OLPC/eToys, check with Bert > > You need to carefully check that some of the UTF8 encoders/decoder methods, or classes actually DO make UTF8 > One of them lied and did a UTF8ToMacRoman or was that UTF8ToLatin1 conversion when it claimed a UTF8ToUnicode32. Argh! So we should really find a way to rescue what was done in sophie. > In Sophie because we wrote it's own storage subsystem we could ensure that all textual data going to storage was UTF8, and > all text coming in was UTF8->WideStrings. Also all references to external resources were made into URI that were UTF8 and http encoded safe. > Mind we did have a tiny disagreements at times about unicode characters and encoding in URLs between Safari and FireFox, never was quite > sure who had the bug. > > -- > =========================================================================== > 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

March 29, 2010

Re: [Pharo-project] Pharo 1.0 fixing tests

by Adrian Lienhard

On Mar 29, 2010, at 09:22 , Mariano Martinez Peck wrote: >> - I assume Mariano is going to build a Pharo RC4 when we have a new >> PharoCore RC4 (there have been some updated packages like Metacello and OB >> if I understood correctly). >> >> >> > PharoCore RC4 or PharoDev RC4 ??? because Metacello and OB are for > Dev...not core :) > Or there will be a PharoCore RC4 ? Yes, since we have to do something to fix the situation with the tests we'll have to do an update, which will be declared PharoCore RC4. Adrian > > > >> [...] >> >>> I think that theses tests do not show bugs but probably badly designed >> tests. >>> So why don't you move them to expected failures and we release 1.0? >> >> Then there would be a failure when these tests don't fail, which happens >> every second run. So we would need to remove them. But if somebody has some >> cycles to figure out why they fail we could probably fix them. >> >> Adrian >> _______________________________________________ >> 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

March 29, 2010

Re: [Pharo-project] how to contribute test to pharo

by Adrian Lienhard

On Mar 29, 2010, at 09:07 , laurent laffont wrote: > 2010/3/28 Mariano Martinez Peck <marianopeck(a)gmail.com> > >> Hi Hilaire. I dont understand your question. >> >> If you want to contribute to test, just download the image you want, and >> test. If you find bugs, you report it. >> To submit an issue: http://www.pharo-project.org/community/issue-tracking >> >> If you are talking about submitting new tests or fixes to current tests, is >> the same process as submitting any code: >> >> http://code.google.com/p/pharo/wiki/HowToContribute >> > > > And there's the screencast :) > http://pharocasts.blogspot.com/2010/03/how-to-contribute-to-pharo.html I added a FAQ entry with both links. Adrian > Laurent Laffont > > > >> >> I know this link was pointed from somewhere in the pharo website...but I >> don't find it. >> >> Adrian? >> >> Cheers >> >> Mariano >> >> >> >> On Sun, Mar 28, 2010 at 5:34 PM, Hilaire Fernandes < >> hilaire.fernandes(a)gmail.com> wrote: >> >>> I can't find any information in the website >>> >>> Hilaire >>> >>> >>> _______________________________________________ >>> 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

March 29, 2010

Re: [Pharo-project] Squeak VM+FT2Plugin, all Pharo 1.0 rc3 tests green

by Adrian Lienhard

Hi Laurent I used the awk gnuification as it is automatically done with cmake. The problem I run into was that the line end chars of the interp.c file generated from Squeak were cr instead of lf and hence awk failed with the same error like the one you posted below. I've explained how to fix this in my blog post (http://www.adrian-lienhard.ch/blog) Cheers, Adrian On Mar 27, 2010, at 20:41 , laurent laffont wrote: > I've tried gnuification on rev 2151. cmake/configure OK. But while building: > > /home/lol/sandbox/squeakvm/Squeak-3.11.3.2151-pharo-src/build/gnu-interp.c:25104:2: > erreur: #error GNUIFICATION FAILED ( 0 ) > > > Laurent Laffont > > > On Sat, Mar 27, 2010 at 6:47 PM, laurent laffont > <laurent.laffont(a)gmail.com>wrote: > >>> Does it mean latest SVN source is already "Gnuified" ? With latest rev. >>> I >>>> have a little drop in benchmarks. However I'd rather put a stable >>> release >>>> for Pharo 1.0 than latest trunk. What do you think ? >>> >>> The so-called "gnuification" is a transformation of the interp.c file. So >>> this is done after generating the sources with VMMaker. The cmake >>> configuration that comes with revision 2135 does not have this step enabled, >>> and the more recent version that I used, revision 2151, has it. The magic is >>> in the awk script in unix/cmake/gnuify.awk which produes gnu-interp.c. >>> >> >> OK thanks. I will take a look. >> >> Laurent Laffont >> >> >> >>> >>> Cheers, >>> Adrian >>> >>>> >>>> Laurent Laffont >>>> >>>> >>>>> >>>>> Adrian >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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

March 29, 2010

Re: [Pharo-project] The Pharo Linux Vm [WAS] Squeak VM+FT2Plugin, all Pharo 1.0 rc3 tests green

by Mariano Martinez Peck

On Mon, Mar 29, 2010 at 4:23 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > 2010/3/29 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > >> > >> > >>> > >>> - In the README.TXT we also have to put links for help: squeakvm site, > >>> posts like Laurent or Adrain > >>> - Gunification > >>> - It needs to have a name of PharoXXX. Not squeak. This is VERY > confusing > >>> for newcomers. > >> > >> I agree we need to explain better the distinction between the VM and the > >> image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a > fork. I > >> tend to think it will bring higher confusion. > > > > I don't agree. Image you are a new comer. For you, Pharo is Pharo. You > > probaly have no idea what Squeak is. So...you go to Pharo website, and > > download the image, and the VM. Imagine when you go to download the VM > and > > it says "SqueakVM". I would say "WTF?????" "WTF is squeak?" > > I am not saying forking the VM. Just to rename it. Actually, the windows > VM > > has that name: > > "http://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip" > > And the same with exupery: > > " > http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip" > > Yes and also having a Pharo icon and not a Squeak one. > > Yes! The windows VM has already that. The MacVM, I sent an email few months ago to explain how to do it. If you want, I can upload a Squeak 4.2.2beta1U.app but with the Pharo icons and named Pharo 4.2.2beta1U.app Then we link from the website to that VM. What do you think ? I know there are newer MacOS VMs, but they are still in beta and for the Pharo 1.0 I think the best VM is the 4.2.2.beta1 What do you think ? Cheers Mariano > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 29, 2010

Re: [Pharo-project] The Pharo Linux Vm [WAS] Squeak VM+FT2Plugin, all Pharo 1.0 rc3 tests green

by Serge Stinckwich

2010/3/29 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> >>> >>> - In the README.TXT we also have to put links for help: squeakvm site, >>> posts like Laurent or Adrain >>> - Gunification >>> - It needs to have a name of PharoXXX. Not squeak. This is VERY confusing >>> for newcomers. >> >> I agree we need to explain better the distinction between the VM and the >> image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a fork. I >> tend to think it will bring higher confusion. > > I don't agree. Image you are a new comer. For you, Pharo is Pharo. You > probaly have no idea what Squeak is. So...you go to Pharo website, and > download the image, and the VM. Imagine when you go to download the VM and > it says "SqueakVM". I would say "WTF?????"Â Â Â "WTF is squeak?" > I am not saying forking the VM. Just to rename it. Actually, the windows VM > has that name: > "http://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip" > And the same with exupery: > "http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip" Yes and also having a Pharo icon and not a Squeak one. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

March 29, 2010

Re: [Pharo-project] Pharo 1.0 fixing tests

by Mariano Martinez Peck

> - I assume Mariano is going to build a Pharo RC4 when we have a new > PharoCore RC4 (there have been some updated packages like Metacello and OB > if I understood correctly). > > > PharoCore RC4 or PharoDev RC4 ??? because Metacello and OB are for Dev...not core :) Or there will be a PharoCore RC4 ? > [...] > > > I think that theses tests do not show bugs but probably badly designed > tests. > > So why don't you move them to expected failures and we release 1.0? > > Then there would be a failure when these tests don't fail, which happens > every second run. So we would need to remove them. But if somebody has some > cycles to figure out why they fail we could probably fix them. > > Adrian > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 29, 2010

Re: [Pharo-project] The Pharo Linux Vm [WAS] Squeak VM+FT2Plugin, all Pharo 1.0 rc3 tests green

by Mariano Martinez Peck

> > > >> - In the README.TXT we also have to put links for help: squeakvm site, >> posts like Laurent or Adrain >> - Gunification >> - It needs to have a name of PharoXXX. Not squeak. This is VERY confusing >> for newcomers. >> > > I agree we need to explain better the distinction between the VM and the > image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a fork. I > tend to think it will bring higher confusion. > I don't agree. Image you are a new comer. For you, Pharo is Pharo. You probaly have no idea what Squeak is. So...you go to Pharo website, and download the image, and the VM. Imagine when you go to download the VM and it says "SqueakVM". I would say "WTF?????" "WTF is squeak?" I am not saying forking the VM. Just to rename it. Actually, the windows VM has that name: " http://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip" And the same with exupery: " http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip" > > > > >> - Pass all PharoRC3 tests in green >> - The process has to be repeatable. Someone has to be able to came in 1 >> year, donwload the same VM and repeat the steps without major problems. >> - The readme.txt has to include the SVN revision where the C code was >> taken. >> - It would also be good to said which ConfigurationOfVmMaker version was >> used. >> >> > Agree. > > Maybe you can open a git repository on INRIA servers so we can keep track > of patches + README included in the VM for Pharo. I've used Javier and > Levente patches and these are not included in squeak-vm svn. I sent a mail > last week on vm-dev but no answers. > This way builders can do: > git clone git://......squeak-vm > cd ..squeak-vm../build > ... configure && make && make install. > For packagers it would be cool. > Developpers can have their own branches and submit patches more easily, add > more visibility. > With git-svn we can synchronize from official Squeak-VM svn (until they > switched to git or another DVCS :) > > What do you think ? > > I like the idea....but what about the sync with the public/official SVN repo ? how we will be able to merge ? or the GIT repo will be only for patches ? Cheers Mariano > Laurent Laffont > > >> Cheers >> >> Mariano >> >> >> >> >>> >>> >>>> Ok.....but not only plugins. For exaple, if I don't want UTF-8 ? >>>> >>>> >>> errr... maybe it's time to ask to the vm-dev list :) >>> >>> >>>> >>>> >>>> ufff.....what an idiot...thanks! did you already discovered I am a >>>> newbie here ? :) >>>> >>> >>> >>> Me too, but a little less every day :) >>> >>> Laurent Laffont >>> >>> _______________________________________________ >>> 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 >

March 29, 2010

Re: [Pharo-project] Pharo 1.0 fixing tests

by Adrian Lienhard

On Mar 27, 2010, at 20:56 , StÃ©phane Ducasse wrote: > Hi adrian > > who is working on what? - I was working on the website and change log, and checked the tests. I can also check the workspace contents in the Pharo image. I plan to put the changes log on the website and simply link from the workspace to that page. - Marcus said he would do a one-click image - I assume Mariano is going to build a Pharo RC4 when we have a new PharoCore RC4 (there have been some updated packages like Metacello and OB if I understood correctly). [...] > I think that theses tests do not show bugs but probably badly designed tests. > So why don't you move them to expected failures and we release 1.0? Then there would be a failure when these tests don't fail, which happens every second run. So we would need to remove them. But if somebody has some cycles to figure out why they fail we could probably fix them. Adrian

March 29, 2010