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

Re: [Pharo-project] Smalltalk interactive tutorial in good English

by laurent laffont

> > > which I converted in a workspace. I used ShoutWorkspace for that because > you have colors and is nicer :) > Totally stupid question: how can I change the text inside a ShoutWorkspace once it's opened ? > > If you want to see what I did, download the package > ImageForDevelopers-pharo-MarianoMartinezPeck.212 > from http://www.squeaksource.com/ImageForDevelopers > > See the class methods of DEVImageWorkspaces class > > I will add this tutorial also to the getting started part. What do you > think ? > If you want :) Laurent > > Cheers > > Mariano > > > 2010/1/15 laurent laffont <laurent.laffont(a)gmail.com> > >> Hi >> >> I've written a sort of interactive tutorial based on (old) Stephane's >> screencasts about Smalltalk syntax. >> >> It's called PrStef ;). To load it: >> >> Gofer new >> squeaksource: 'PrStef'; >> package: 'PrStef'; >> load. >> >> and to run it: PrStef go. >> >> I'm looking for English-speaking people to check that the texts are >> written in a correct English before I make a screencast on it. Thank you ! >> >> Cheers, >> >> Laurent >> >> _______________________________________________ >> 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. 15, 2010

[Pharo-project] Smalltalk interactive tutorial in good English

by Torsten Bergmann

I would also show interesting snippets like: HandMorph attach: (SketchMorph fromStream: ('http://code.google.com/p/pharo/logo' asUrl retrieveContents contentStream) ) -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Jan. 15, 2010

Re: [Pharo-project] Regex regression?

by Schwab,Wilhelm K

Installing Seaside is how I hit it also. I also _suspect_ something wrong elsewhere. I use SIF to get my code out of Dolphin and into Pharo. Between those steps, I edit the "raw SIF" and began using regex for the task. It's not going well lately, and this increases my suspicion that it is not my doing. I will try to capture what I did as a test case. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Friday, January 15, 2010 10:53 AM To: Pharo-project(a)lists.gforge.inria.fr Cc: Lukas Renggli Subject: Re: [Pharo-project] Regex regression? On Fri, Jan 15, 2010 at 4:42 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: A lot is happening, so I could be off here. In the 10496 web image, I noted that there might be problems with the regex package. Now trying to build a new image I hit a walkback over '*username*' asRegex Any other takers? I am seeing this problem in both 10496 and the new RC1 on the download page. Yes!!! Is the same error I saw trying to install Seaside2.8 as it uses exatly that I already contact Dale few days ago to see if he could look at it. Lukas ? Cheers Mariano Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 15, 2010

Re: [Pharo-project] Regex regression?

by Mariano Martinez Peck

On Fri, Jan 15, 2010 at 4:42 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > A lot is happening, so I could be off here. In the 10496 web image, I > noted that there might be problems with the regex package. Now trying to > build a new image I hit a walkback over > > '*username*' asRegex > > Any other takers? I am seeing this problem in both 10496 and the new RC1 > on the download page. > > Yes!!! Is the same error I saw trying to install Seaside2.8 as it uses exatly that I already contact Dale few days ago to see if he could look at it. Lukas ? Cheers Mariano > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

[Pharo-project] Smalltalk interactive tutorial in good English

by Torsten Bergmann

It would be nice if the tutorial would take place in a syntax highlighted workspace (Shout). Just place the text in comments. While the reference to PrStef makes insiders smile I would rather name it "Tutorial" or "Intro". Thx Torsten -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

Jan. 15, 2010

Re: [Pharo-project] Smalltalk interactive tutorial in good English

by Mariano Martinez Peck

Hi Laurent! This is really cool. I am preparing welcome workspaces for the next dev image. I already wrote the one which is here: http://code.google.com/p/pharo/wiki/GettingStartedWorkspaces which I converted in a workspace. I used ShoutWorkspace for that because you have colors and is nicer :) If you want to see what I did, download the package ImageForDevelopers-pharo-MarianoMartinezPeck.212 from http://www.squeaksource.com/ImageForDevelopers See the class methods of DEVImageWorkspaces class I will add this tutorial also to the getting started part. What do you think ? Cheers Mariano 2010/1/15 laurent laffont <laurent.laffont(a)gmail.com> > Hi > > I've written a sort of interactive tutorial based on (old) Stephane's > screencasts about Smalltalk syntax. > > It's called PrStef ;). To load it: > > Gofer new > squeaksource: 'PrStef'; > package: 'PrStef'; > load. > > and to run it: PrStef go. > > I'm looking for English-speaking people to check that the texts are written > in a correct English before I make a screencast on it. Thank you ! > > Cheers, > > Laurent > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

[Pharo-project] Regex regression?

by Schwab,Wilhelm K

A lot is happening, so I could be off here. In the 10496 web image, I noted that there might be problems with the regex package. Now trying to build a new image I hit a walkback over '*username*' asRegex Any other takers? I am seeing this problem in both 10496 and the new RC1 on the download page. Bill

Jan. 15, 2010

[Pharo-project] Smalltalk interactive tutorial in good English

by laurent laffont

Hi I've written a sort of interactive tutorial based on (old) Stephane's screencasts about Smalltalk syntax. It's called PrStef ;). To load it: Gofer new squeaksource: 'PrStef'; package: 'PrStef'; load. and to run it: PrStef go. I'm looking for English-speaking people to check that the texts are written in a correct English before I make a screencast on it. Thank you ! Cheers, Laurent

Jan. 15, 2010

Re: [Pharo-project] MC case sensitity and sub-packages

by Schwab,Wilhelm K

Stef, It looks as though this might work as I had hoped, though I am giving careful consideration to your concern. I had both DolphCompatibility and Dolphincompatibility in package names; there were a few of the later form. I used PackageOrganizer to enumerate the package names, selected the incorrect ones, then unregistered them. After the above and fixing a couple of things in my Migrate pacakge names list, my suspect methods report is down to five methods that are expected to appear. The save of the enumerated top-level packages *appears* to have worked. I will need to try building an image from them before getting too full of myself. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Friday, January 15, 2010 9:17 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] MC case sensitity and sub-packages Stef, I am doing some housekeeping toward building a new image. Changes such as below have allowed me to get Migrate into an almost-releasable state. One of its jobs is to look for code that is at risk of being lost, and that feature is detecting a LOT of code that should be safe; it is probably due to the extra packages. I had hoped that I could safely avoid the "double save" problem, but this is even worse than that :( Absent a simple solution, the answer is to delete DolphinCompatibility and others. The next question is then: will I have problems with dependencies between the sub-packages? I am wondering whether there could be problems saving separate packages like DolphinCompatibility-Streams DolphinCompatibility-ODBC when DolphinCompatibility would be perfectly happy. Does that make sense? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Wednesday, January 13, 2010 2:40 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] MC case sensitity and sub-packages On Jan 13, 2010, at 1:39 AM, Schwab,Wilhelm K wrote: > Brian and others have told me that I could expect to define packages > such as > > DolphinCompatibility-ODBC > DolphinCompatibility-Streams > > and save them all using DolphinCompatibility, or save just one specific part by giving the full name, such as DolphinCompatibility-ODBC. I was unable to make it work reliably, and I think I might have just figured out why. I really encourage you to save them as separate packages if you want to load and save them all build a metacelloConfig (not difficult and worth). don;t define a package DolphinCompatibility in addition (else you will get in trouble because your classes will be saved somehow twice)., I hate this pattern matching behavior. > Assertion: package names and class names must agree up to case; method categories (*packageName-etc) appear to be more forgiving. > > It further appears that once one messes up by naming a category and package Dolphincompatibility instead of DolphinCompatibility, the only way to fix it is to delete the working copy of the package and re-create it with the correct case after renaming the category, or something like that. probably I do not like that part of the system > > Does that sound right? Am I missing something that might cost me later? > > Bill > > > _______________________________________________ > 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. 15, 2010

[Pharo-project] About RemoteString>>checksum:

by StÃ©phane Ducasse

in squeak trunk Can some of you double check this change from squeaktrunk Name: Files-jcg.27 In squeak checkSum: aString "Construct a checksum of the string. A three byte number represented as Base64 characters." | sum shift bytes | sum := aString size. shift := 0. aString do: [:char | (shift := shift + 7) > 16 ifTrue: [shift := shift - 17]. "shift by 7 to keep a change of adjacent chars from xoring to same value" sum := sum bitXor: (char asInteger bitShift: shift) ]. bytes := ByteArray new: 3. sum := sum + 16r10000000000. 1 to: 3 do: [:ind | bytes at: ind put: (sum digitAt: ind)]. ^bytes base64Encoded In pharo checkSum: aString "Construct a checksum of the string. A three byte number represented as Base64 characters." | sum shift bytes ss bb | sum := aString size. shift := 0. aString do: [:char | (shift := shift + 7) > 16 ifTrue: [shift := shift - 17]. "shift by 7 to keep a change of adjacent chars from xoring to same value" sum := sum bitXor: (char asInteger bitShift: shift)]. bytes := ByteArray new: 3. sum := sum + 16r10000000000. 1 to: 3 do: [:ind | bytes at: ind put: (sum digitAt: ind)]. ss := ReadWriteStream on: (ByteArray new: 3). ss nextPutAll: bytes. bb := Base64MimeConverter mimeEncode: ss. ^ bb contents Thanks

Jan. 15, 2010