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

Re: [Pharo-project] Release Core?

by Lukas Renggli

> In summary, what needs to be done: > - Fix one failing Shout test I fixed that one by changing the assertions that fail. The shout test package contains one single huge test that checks the number parsing of Shout. I've never run this test before and I don't really understand why they are broken. To me numbers look highlighted correctly. Lukas -- Lukas Renggli www.lukas-renggli.ch

July 6, 2010

Re: [Pharo-project] Release Core?

by Adrian Lienhard

(moving this thread to pharo-dev) Context: green tests for Pharo 1.1 (currently at RC4). Thanks Mariano, I went through your list of tests. In summary, what needs to be done: - Fixes for Nile - Fix one failing Shout test - Adaptation/fixes of external packages: method wrappers, sound, morphic examples In detail: Needs fixing ----------- SHParserST80Test>>#testNumbers NSMultiByteBinaryOrTextStreamTest>>#testFileOut NSSmartRefStreamTest>>#testGlobal NSMCPseudoFileStreamTest>>#testFileOut NSMCPseudoFileStreamTest>>#testFileOutFileIn NSRWBinaryOrTextStreamTest>>#testFileOut NSRWBinaryOrTextStreamTest>>#testFileOutFileIn ReleaseTest>>#testUndeclared Undeclared classes and variables (these external packages need to be adapted or should not be loaded) --------- WatchMorph references ColorPickerMorph AbstractSound references FillInTheBlank EnvelopeEditorMorph, MidiInputMorph, and ScorePlayerMorph reference PopUpChoiceMorph KeyboardMorphForInput, MidiInputMorph, and ScorePlayerMorph reference SimpleSwitchMorph ArchiveViewer references StandardFileMenu ObjectAsMethodWrapper has undeclared variable named selector and wrappedClass Fixed, see attached cs (we had that already in 1.0 but apparently it was lost for 1.1) ----------- WeakSetInspectorTest>>#testSymbolTableM6812 Workes for me (when running each test alone)(?) ----------- ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory MCInitializationTest>>#testWorkingCopy WeakRegistryTest>>#testFinalization FileStreamTest>>#testPositionPastEndIsAtEnd AllocationTest>>#testOneGigAllocation Cheers, Adrian On Jul 5, 2010, at 22:06 , Mariano Martinez Peck wrote: > On Mon, Jul 5, 2010 at 8:00 PM, Adrian Lienhard <alienhard(a)netstyle.ch>wrote: > >> I updated the download page. >> >> > thanks > > >> Cheers, >> Adrian >> >> BTW, what is the state of the tests? Last time I run them, there were a lot >> of failures... >> >> > much better. I fixed a lot of Nile with your suggestion and further > problems/fixes. > > My results so far are these: > > 9764 run, 9697 passes, 53 expected failures, 8 failures, 6 errors, 0 > unexpected passes > Failures: > AllocationTest>>#testOneGigAllocation > NSMultiByteBinaryOrTextStreamTest>>#testFileOut > SHParserST80Test>>#testNumbers > ReleaseTest>>#testUndeclared > FileStreamTest>>#testPositionPastEndIsAtEnd > WeakRegistryTest>>#testFinalization > MCInitializationTest>>#testWorkingCopy > ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory > > Errors: > WeakSetInspectorTest>>#testSymbolTableM6812 > NSSmartRefStreamTest>>#testGlobal > NSMCPseudoFileStreamTest>>#testFileOut > NSMCPseudoFileStreamTest>>#testFileOutFileIn > NSRWBinaryOrTextStreamTest>>#testFileOut > NSRWBinaryOrTextStreamTest>>#testFileOutFileIn > > > > > >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> On Jul 5, 2010, at 18:26 , StÃ©phane Ducasse wrote: >> >>> Yes >>> >>>> I have just created the image RC4. It is in >> https://gforge.inria.fr/frs/download.php/27254/Pharo-1.1-11409-rc4dev10.07.… >>>> >>>> Adrian, do you think we should update the link of 1.1 from the website >> to this one? >>>> >>>> Cheers >>>> >>>> Mariano >>> >> >>

July 6, 2010

Re: [Pharo-project] System vs System-support package

by StÃ©phane Ducasse

On Jul 5, 2010, at 10:32 PM, Michael Roberts wrote: > I can create a bug entry, but i was wondering what the fix was? In the > image the System package does not correctly know about its > repositories. I guess anyway we have to remove it programmatically in > an update. Do you know that it doesn't contain any changes that are > not also in its children? there are none I imagine. Not sure :) Stef > > thanks, > Mike > > On Sun, Jul 4, 2010 at 3:01 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> there is probably a problem since we worked with pavel on reorganization at the package level. >> >> Stef >> >> On Jul 4, 2010, at 3:53 PM, Michael Roberts wrote: >> >>> I am about to post a deprecation of SystemVersion>>version: to 1.2 but >>> once i have made my changes i see something odd in MC browser: >>> >>> dirty packages >>> * System (System-StephaneDucasse.6) >>> * System-Support (System-Support-StephaneDucasse.317) >>> >>> Stef, have you started to publish System as a whole? did you mean to? >>> My changes therefore hit two packages. System is still packaged in 1.2 >>> at its sub-level of ~20 packages. >>> >>> thanks, >>> Mike >>> >>> _______________________________________________ >>> 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

July 5, 2010

Re: [Pharo-project] DateAndTime>>asUnixTime should ignore timezones?

by StÃ©phane Ducasse

Thanks did you run the tests after your fixes? Because I tried to integrate another fixes related to date = string as proposed in Squeak by chris but a lot of date related tests break. and we should be cautious. Stef On Jul 5, 2010, at 7:31 PM, Nick Ager wrote: > I've filed a new issue: #2644 _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 5, 2010

Re: [Pharo-project] I updated the how to contribute web page

by StÃ©phane Ducasse

thanks hernan. I will not have the time to edit the changes but this is important that we keep this information upto date and that people can understand it. Stef On Jul 5, 2010, at 4:34 PM, HernÃ¡n Morales Durand wrote: > Ok, > > ================ > Here: "First and foremost, you must be aware that the Pharo project > only accepts code published under the MIT license. By publishing your > code in the SqueakSource Pharo or PharoInbox repositories, you are > agreeing to this condition. With that out of the way, here are the > steps to submit your contributions. " > > Please provide a link which explain the implications of code published > under the MIT license. Or better, a little comparison table between > different licensing schemes. > > ================ > Here: "If your change is directly related to a Mantis report, add the > label "Type-Mantis" and add the Mantis ticket number in front of the > subject. Else choose another appropriate label " > > Please clarify or link to. Manits is the bugs.squeak.org right? It > should be named by what it is, and not by the tool which is used for > bug tracking (if they change their tool 10 times, you must update the > page 10 times) > > ================ > Here: "Announce your contribution by sending a mail to the mailing > list and herewith ask to have somebody review your change. This person > should change the state of the issue to "Verified". " > > Provide a link to the mailing list. Note "herewith" is most used and > understood as a legal term. > > ================ > Here: "For complex changes use a slice since there is a much better > merging support. " > > What is a complex change? (please include this information in the page too) > > ================ > "Prepare a changeset with your changes. File it out. Important: Put > your Full name instead of your initials, it will help up to contact > you as it is often necessary. Do not use space and only alphabetical > characters. " > > 1) This is killing more than 50% of the habitants of the world :) What > happens with contributors without latin alphabet? how they setup their > system? (that should be included) > > 2) What is the problem with using space? If it is a limitation imposed > by a tool then the tool should be responsible of trimming all blanks, > not the users. > > 3) How do you distinguish between two John Smith? And how do you > contact contributors? (I've never wrote my e-mail or gmail user name > in a Pharo image). > > 4) Some brief explanation on how to create a changeset would be nice. > > ================ > Finally, this information should be in all images. Better, provide a > wizard to guide this process, it sounds like a nice excercise to do a > standard window flow with Morphic. > > Cheers, > > HernÃ¡n > > 2010/7/5 stephane ducasse <stephane.ducasse(a)free.fr>: >> please comment :) >> http://code.google.com/p/pharo/wiki/HowToContribute >> >> Stef >> >> _______________________________________________ >> 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

July 5, 2010

Re: [Pharo-project] Three little fixes for 1.2.

by StÃ©phane Ducasse

thanks. Today travel without connection. Tomorrow the same :) but to a really nice place in france where it can be great to have holidays: golfe du Morbihan first time I went there but it is gorgeous... Stef On Jul 5, 2010, at 5:26 PM, Torsten Bergmann wrote: > Three little fixes for 1.2 > > http://code.google.com/p/pharo/issues/detail?id=2640 fixed > http://code.google.com/p/pharo/issues/detail?id=2641 fixed > http://code.google.com/p/pharo/issues/detail?id=2643 fixed > > Ready for inclusion. > > Bye > T. > -- > GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. > Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 5, 2010

Re: [Pharo-project] I updated the how to contribute web page

by StÃ©phane Ducasse

thanks hernan. I will not have the time to edit the changes but this is important that we keep this information upto date and that people can understand it. Stef On Jul 5, 2010, at 4:34 PM, HernÃ¡n Morales Durand wrote: > Ok, > > ================ > Here: "First and foremost, you must be aware that the Pharo project > only accepts code published under the MIT license. By publishing your > code in the SqueakSource Pharo or PharoInbox repositories, you are > agreeing to this condition. With that out of the way, here are the > steps to submit your contributions. " > > Please provide a link which explain the implications of code published > under the MIT license. Or better, a little comparison table between > different licensing schemes. > > ================ > Here: "If your change is directly related to a Mantis report, add the > label "Type-Mantis" and add the Mantis ticket number in front of the > subject. Else choose another appropriate label " > > Please clarify or link to. Manits is the bugs.squeak.org right? It > should be named by what it is, and not by the tool which is used for > bug tracking (if they change their tool 10 times, you must update the > page 10 times) > > ================ > Here: "Announce your contribution by sending a mail to the mailing > list and herewith ask to have somebody review your change. This person > should change the state of the issue to "Verified". " > > Provide a link to the mailing list. Note "herewith" is most used and > understood as a legal term. > > ================ > Here: "For complex changes use a slice since there is a much better > merging support. " > > What is a complex change? (please include this information in the page too) > > ================ > "Prepare a changeset with your changes. File it out. Important: Put > your Full name instead of your initials, it will help up to contact > you as it is often necessary. Do not use space and only alphabetical > characters. " > > 1) This is killing more than 50% of the habitants of the world :) What > happens with contributors without latin alphabet? how they setup their > system? (that should be included) > > 2) What is the problem with using space? If it is a limitation imposed > by a tool then the tool should be responsible of trimming all blanks, > not the users. > > 3) How do you distinguish between two John Smith? And how do you > contact contributors? (I've never wrote my e-mail or gmail user name > in a Pharo image). > > 4) Some brief explanation on how to create a changeset would be nice. > > ================ > Finally, this information should be in all images. Better, provide a > wizard to guide this process, it sounds like a nice excercise to do a > standard window flow with Morphic. > > Cheers, > > HernÃ¡n > > 2010/7/5 stephane ducasse <stephane.ducasse(a)free.fr>: >> please comment :) >> http://code.google.com/p/pharo/wiki/HowToContribute >> >> Stef >> >> _______________________________________________ >> 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

July 5, 2010

Re: [Pharo-project] bug with documentation link

by StÃ©phane Ducasse

I would just have a small text and a link to the pharocast web page On Jul 5, 2010, at 12:01 PM, Adrian Lienhard wrote: > I exchanged the tutorial/books page with the FAQ page so that the former gets displayed by default. We don't have a Screencasts page; what content would such a page contain? Would we list available screen cast or just link to http://pharocasts.blogspot.com/? > > Adrian > > On Jul 5, 2010, at 11:47 , StÃ©phane Ducasse wrote: > >> Hi all >> >> when I go to the pharo web site and click on documentation I go to faq (and I do not care of FAQ) >> I want to see screencast >> adrian could it be possible to get >> >> Documentation >> tutorialBooks >> screencast >> faq >> >> >> by the way somebody told me that lighthouse in portuguese is farol and not faro (which means smelling). >> >> Stef >> _______________________________________________ >> 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

July 5, 2010

Re: [Pharo-project] bug with documentation link

by StÃ©phane Ducasse

not only we really like the idea of the lighthouse and this is a mixture between french and the rest :) On Jul 5, 2010, at 12:19 PM, Mariano Martinez Peck wrote: > > > On Mon, Jul 5, 2010 at 12:07 PM, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > > StÃ©phane Ducasse wrote: > > > > by the way somebody told me that lighthouse in portuguese is farol and not > > faro (which means smelling). > > > > I don't speak Portuguese nor Spanish but the good old Google Translate > confirms that lighthouse is indeed Farol and not Faro .... however > lighthouse does still translate as Faro in Spanish :) > > Yes, in Spanish, it is Faro. > Marcus told me he chose Pharo just to be easily indexed by search engines like Google. It doesn't mean lighthouse in any language. Just a deformation for google ;) > > cheers > > mariano > > > -- > View this message in context: http://forum.world.st/bug-with-documentation-link-tp2278198p2278220.html > 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

July 5, 2010

Re: [Pharo-project] [SPAM] Re: ESUG will sponsor the XMLRPC project!

by GermÃ¡n Arduino

Thanks Hernan, Sven said the same in private mail. Thanks both. 2010/7/5 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > GermÃ¡n, > Seaside 3 includes the JSJsonParser > > HernÃ¡n > > 2010/7/4 GermÃ¡n Arduino <garduino(a)gmail.com>: > > Hi Sven: > > > > Which JSON are you using? > > > > The package I know from Squeaksource ( > http://www.squeaksource.com/JSON.html) > > doesn't includes the class JSJsonParser. > > > > Cheers. > > GermÃ¡n. > > > > > > 2010/6/28 Sven Van Caekenberghe <sven(a)beta9.be> > >> > >> And REST+JSON is easy to do with what is available in > >> Pharo/Seaside/WebClient: > >> > >> client := WebClient new. > >> client authCredentialsBlock: [:client :realm :fail | > >> client username: '680'; password: ((MD5 new hashMessage: > 'secret') > >> hex) ]. > >> response := client httpGet: 'http://api.t3-platform.net:9000/users/680 > '. > >> JSJsonParser parse: response content. > >> > >> Sven > >> > >> PS: Only HTTPS is missing ;-) > >> > >> On 28 Jun 2010, at 13:35, StÃ©phane Ducasse wrote: > >> > >> > Thanks. > >> > May be german should have a look at this solution instead of XML-RCP. > >> > > >> > Stef > >> > > >> >>> My impression is that people either moved from XML-RCP to SOAP or > >> >>> abandoned the idea and went to REST. I don't know anybody who > >> >>> considers > >> >>> it for new projects. > >> >>> > >> >> > >> >> As Philippe stated, many projects are moving to REST. > >> >> REST/JSON webservices are getting all the hype these days... > >> >> > >> >> > >> >> _______________________________________________ > >> >> 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 > > > > > > > > -- > > ================================================= > > GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > > Arduino Software & Web Hosting http://www.arduinosoftware.com > > PasswordsPro http://www.passwordspro.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 > -- ================================================= GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================

July 5, 2010