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

[Pharo-project] Thanks for license agreement :)
by StÃ©phane Ducasse April 7, 2010

April 7, 2010

Hi Justin and Yanni I checked my mailbox today and saw your license agreement. Thanks

2 2

Re: [Pharo-project] Redline Smalltalk
by Dan Ingalls April 7, 2010

April 7, 2010

James Ladd <<mailto:james_ladd@hotmail.com>james_ladd(a)hotmail.com> wrote... >>Hi Pharo-ites, >> >>I'm working on a port of Pharo to the Java Virtual Machine called >>Redline Smalltalk. >>(read more >>here: <http://jamesladdcode.com/?p=323>http://jamesladdcode.com/?p=323) >> >>I'm wanting to port every single class over time, but initially >>enough to get the >>compiler working and have a minimum runtime. >> >>Of the 1600+/- classes which are those necessary to make a small >>workable compiler >>and runtime environment? Hi, James - Bert Freudenberg forwarded this along to me, as I'm not on a Pharo mailing list. I think you know of my JSqueak project (a.k.a. Potato) -- a Squeak VM written in Java. The image that I used with it, is the same that I always use for this kind of experiment -- mini.image built in Squeak 2.2. The reason it is so cool is that it includes browser, editor, compiler, inspector debugger, and files -- everything you need for self-support. Plus it has the decompiler, and special temp-name hack, so you can actually browse sources with temp names before any file system works. My favorite thing about this image is that although it is only 600k, if you decompile all its sources, it comprises over 850k of Smalltalk, so it's like a compressed version of the sources with a full-function IDE thrown in for free ;-). As I said, the image is about 600k, of which 240k is code -- 202 classes (x2 if you count the metas) with 4590 methods. This should be a good guide for you in choosing classes to start with. You can actually run this image live in JSqueak on the web if you have Java installed and the planets are aligned correctly... http://Weather-dimensions.com/Dan/JSqueak.jnlp Another interesting statistic is that the Java .jar file is only 433k, including not only the VM, but also the entire image! This is possible because the image is so small that the pointers in it are mostly zeroes, so it compresses nicely. I just checked that this runs, and was happy to see that it putts along at 21 million bytecodes/sec on my laptop. I haven't looked recently, but I think you'll find Mini2.2.image or something like it in the same place where all the historical releases of Squeak are kept. Let me know if you can't find it. Have fun with your project! I hope this helps - Dan

4 8

[Pharo-project] Bug or new feature in RB?
by Mariano Martinez Peck April 7, 2010

April 7, 2010

Hi Lukas. I was playing around RB (actually, looking at your screencasts) and I found something weird. Steps done: 1) Go to AST, "refactoring scope" -> "package" 2) There, took class RBReplaceRule and "refactor method" -> "rename" to the method initialize 3) Proceed -> yes There you will see the list of the initialize methods that it will apply the refactor. As you can see, all classes affected are RB, BUT Behavior and CompiledMethod. This is because the package AST has extensions to both classes. But NONE of those extensions are with the initialize method, but with parseTreeFor: and parseTree, So, my question is, shouldn't only apply the refactor to the initialize method of extended packages ONLY if that method is extended ? Because otherwise I think it is a bit dangerous. What do you think ? I attach screenshot also. Cheers Mariano

2 2

[Pharo-project] Issue 2279: [BUG]MultiByteFileStream(Object)>>error: on changes file throwing ***System Error Handling Failed*** running test coverage
by Stan Shepherd April 7, 2010

April 7, 2010

VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Image: Pharo-1.0-10517-rc4 [Latest update: #10517] Steps to reproduce: 1.In TestRunner, select Tests-Traits , TestTraits 2.Select Run Coverage button. 3.In dialog, select Files stack trace attached ** to issue ** http://code.google.com/p/pharo/issues/detail?id=2279 -- View this message in context: http://n4.nabble.com/Issue-2279-BUG-MultiByteFileStream-Object-error-on-cha… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 2

[Pharo-project] Linux Pharo VM on Pharo website
by laurent laffont April 7, 2010

April 7, 2010

Hi, I've prepared the following archive. It may replace the "Unix (3.11-3)" download link. http://lolgzs.free.fr/pharo/squeak-vm/squeak-3.11.3.2151-pharo-src.tar.gz In this archive: - patched squeak-vm rev. 2151. (The 2 patches are for FT2Plugin build and multiple options in CFLAGS to work. Patchs in archive). - awk gnuification - README with instructions to build and regenerate this source from VMMaker - All Pharo-1.0 tests green (on my machine ...) - it has been built/tested by several people in order to send me tinyBenchmark results :) The tinyBenchmarks are not as good as Exupery one, but this vary a lot depending on the CPU. Cheers, Laurent Laffont

4 7

[Pharo-project] who is maintaining shout?
by StÃ©phane Ducasse April 7, 2010

April 7, 2010

Because I would like to change the default color of comments. Green is really ugly for the release. Stef defaultStyleTable "color can be a valid argument to Color class>>colorFrom: , or nil to use the editor text color. Multiple emphases can be specified using an array e.g. #(bold italic). If emphasis is not specified, #normal will be used. if pixel height is not specified , then the editor font size will be used. " ^#( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default black ) (invalid red ) (excessCode red ) (comment (gray muchDarker) italic) (unfinishedComment (red muchDarker) italic) (#'$' (red muchDarker) ) (character (red muchDarker) ) (integer (red muchDarker) ) (number (red muchDarker) ) (#- (red muchDarker) ) (symbol (blue muchDarker) bold) (stringSymbol (blue muchDarker) bold) (literalArray (blue muchDarker) bold) (string (magenta muchDarker) normal) (unfinishedString red normal ) (assignment nil bold ) (ansiAssignment nil bold) (literal nil italic) (keyword (blue muchDarker) ) (binary (blue muchDarker) ) (unary (blue muchDarker) ) (incompleteKeyword (gray muchDarker) underlined) (incompleteBinary (gray muchDarker) underlined) (incompleteUnary (gray muchDarker) underlined) (undefinedKeyword red ) (undefinedBinary red ) (undefinedUnary red ) (patternKeyword nil bold) (patternBinary nil bold) (patternUnary nil bold) (#self (red muchDarker) bold) (#super (red muchDarker) bold) (#true (red muchDarker) bold) (#false (red muchDarker) bold) (#nil (red muchDarker) bold) (#thisContext (red muchDarker) bold) (#return (red muchDarker) bold) (patternArg (blue muchDarker) italic) (methodArg (blue muchDarker) italic) (blockPatternArg (blue muchDarker) italic) (blockArg (blue muchDarker) italic) (argument (blue muchDarker) italic) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 (green muchDarker) ) (rightParenthesis1 (green muchDarker) ) (leftParenthesis2 (magenta muchDarker) ) (rightParenthesis2 (magenta muchDarker) ) (leftParenthesis3 (red muchDarker) ) (rightParenthesis3 (red muchDarker) ) (leftParenthesis4 (green darker) ) (rightParenthesis4 (green darker) ) (leftParenthesis5 (orange darker) ) (rightParenthesis5 (orange darker) ) (leftParenthesis6 (magenta darker) ) (rightParenthesis6 (magenta darker) ) (leftParenthesis7 blue ) (rightParenthesis7 blue ) (blockStart black ) (blockEnd black ) (blockStart1 (green muchDarker) ) (blockEnd1 (green muchDarker) ) (blockStart2 (magenta muchDarker) ) (blockEnd2 (magenta muchDarker) ) (blockStart3 (red muchDarker) ) (blockEnd3 (red muchDarker) ) (blockStart4 (green darker) ) (blockEnd4 (green darker) ) (blockStart5 (orange darker) ) (blockEnd5 (orange darker) ) (blockStart6 (magenta darker) ) (blockEnd6 (magenta darker) ) (blockStart7 blue ) (blockEnd7 blue ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black bold ) (primitiveOrExternalCallEnd black bold ) (methodTempBar gray ) (blockTempBar gray ) (blockArgsBar gray ) (primitive (green muchDarker) bold) (pragmaKeyword (green muchDarker) bold) (pragmaUnary (green muchDarker) bold) (pragmaBinary (green muchDarker) bold) (externalFunctionCallingConvention (green muchDarker) bold) (module (green muchDarker) bold) (blockTempVar gray italic) (blockPatternTempVar gray italic) (instVar black bold) (workspaceVar black bold) (undefinedIdentifier red bold) (incompleteIdentifier (gray darker) (italic underlined)) (tempVar (gray darker) italic) (patternTempVar (gray darker) italic) (poolConstant (gray darker) italic) (classVar (gray darker) bold) (globalVar black bold) )

2 1

[Pharo-project] todo after 1.0 is released
by StÃ©phane Ducasse April 7, 2010

April 7, 2010

Hi Adrian Once 1.0 is released we should check that all the fixes that went in 1.0 after the fork to 1.1 are integrated in 1.1. Would be nice also to remove the testsexpected to break so that we give them a chance to be fixed in 1.1. Stef

3 3

[Pharo-project] [For Testing] RC3 One-Click
by Torsten Bergmann April 7, 2010

April 7, 2010

>- splash.bmp says release candidate 2. It should be release stable 1.0 or RC3. Use the attached one. >This comes from the vm package. I personally honestly don't understand >spash-screens. Is windows so slow in loading an image file? There is no reason to have one to fill load time since this is fast as on any other platform. It is more or less a short intro screen to display version info and show the logo. It is very common to provide one and often you can already guess the version from the style of the splash without reading the provided version info. As a developer you would ask "why" - wearing a marketing hat you should say "absolutely necessary". Smalltalk should not only evolve in programming features but also learn some marketing/branding so people will remember it. Read the german entry on Wikipedia for more infos: [1] http://de.wikipedia.org/wiki/Splash_Screen Another bonus is that if one takes the one-click to develop a commercial application he just has to replace the splash with a custom one. If you dislike it, then just delete/rename the splash.bmp after unzipping the one click and you are done. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

3 2

[Pharo-project] Splash for 1.0...Torsten ? Re: [For Testing] RC3 One-Click
by Mariano Martinez Peck April 7, 2010

April 7, 2010

On Wed, Apr 7, 2010 at 3:04 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 3, 2010, at 1:10 PM, Mariano Martinez Peck wrote: > > > Hi Marcus. I have been testing a little the one click image and I found > the following things: > > > > - splash.bmp says release candidate 2. It should be release stable 1.0 > or RC3. > > This comes from the vm package. I personally honestly don't understand > spash-screens. Is windows so > slow in loading an image file? > > Torsten, I don't have the background image neither the tools handly...can you make a new .bmp that says only Pharo 1.0 instead of "Pharo 1.0 Rlease candidate 2" Thanks! mariano

1 0

[Pharo-project] [For Testing] RC3 One-Click
by Marcus Denker April 7, 2010

April 7, 2010

Here is a one-click image (for easy starting for newbies). I only tested this under macos, so it needs a testrun on Linux and Windows https://gforge.inria.fr/frs/download.php/26774/Pharo-1.0-10515-rc3dev.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

6 9