November 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] Debugger problem
by Michael Roberts Nov. 6, 2008

Nov. 6, 2008

Before I go digging too much, has anyone seen these symptoms? In executing some sunits I hit an error, so go poking around up the stack and try and restart a method or block to walk through the sequence of sends again. If I am inside a block I don't get prompted for the "restart the method or block?" type question. Squeak used to do this, no? I can't exactly work out what the exact sequence of events is, but I end up with multiple "unwind error during termination" notifiers popping up which I can't kill the process. This used to really wind me up in squeak so it might not be a new problem. any thoughts? Mike

1 0

[Pharo-project] Too much updates without an image
by Damien Cassou Nov. 6, 2008

Nov. 6, 2008

Hi, could you please release an image with the latest changes so that I can base the new pharo-dev on them? -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

4 6

[Pharo-project] ArrayedCollection, Boolean SmallInteger>>ccg: cg generateCoerceToOopFrom: aNode on: aStream
by StÃ©phane Ducasse Nov. 6, 2008

Nov. 6, 2008

I have the impression that we could remove these methods from the images. It seems that this is related to the VM generation? Does someone know more about them? Stef ccg: cg generateCoerceToOopFrom: aNode on: aStream self instSize > 0 ifTrue: [self error: 'cannot auto-coerce arrays with named instance variables']. cg generateCoerceToObjectFromPtr: aNode on: aStream

5 8

[Pharo-project] exportSegmentWithChangeSet: aChangeSetOrNil fileName: aFileName directory: aDirectory
by StÃ©phane Ducasse Nov. 6, 2008

Nov. 6, 2008

is worth reading :) I'm removing some players related code from there and others Stef

1 0

[Pharo-project] About Pharo - text to go with version 1.0
by Torsten Bergmann Nov. 6, 2008

Nov. 6, 2008

What about a "Pharo/Smalltalk Beginners Workspace" with colored text and some interesting expressions to evaluate (or just hyperlink-click for a simple doIt/printIt) This should start with simple expressions, unary, binary and keyword intro up to some high level code or cool demos (turtle graphics, ....). Ivan Tomek provided such a workspace (see http://lists.squeakfoundation.org/pipermail/squeak-dev/2000-April/013808.ht…) and I once started to adapt it to Squeak (see below). Bye Torsten ------------------------------------------------------------------------------------------- ************************************************************* * INTRODUCTION TO SMALLTALK IN x EASY STEPS ************************************************************* This workspace introduces some of the concepts of Smalltalk - the language behind Pharo. It''s contents is executable and you should try all our suggested exercices. There is much more to Smalltalk and the references listed at the end provide additional information. ================================= Part 1: Objects and messages ================================= --------------------------------------------------------------------------------------------------------- -- 1. EVERYTHING IN SMALLTALK IS AN OBJECT, AND ALL WORK IS DONE BY -- SENDING MESSAGES TO OBJECTS --------------------------------------------------------------------------------------------------------- To send a message we just have to enter text representing the object itself (which is the receiver of the message) and after that the message we want to send. To execute the following examples, - select the colored code text using the left mouse button (as in a word processor) - we can execute the text and print the result by selecting ''print it'' from the right mouse button <operate> menu - alternatively you can select the text and press ALT + p " 3 negated. "receiver is small integer 3, the message we send is ''negated'' " "The period is not necessary - it just preserves the color in this text since it marks the end of a Smalltalk statement. Note that if we send a message the object always responds by either returning a new object or by returning itself. In our example the object 3 responds with a new object -3 when we send the message ''negated''. When evaluating code using ''print it'' the responded object is printed. " "Now lets send a different message" 3 squared. "receiver is 3 again - the message is now squared" "Lets try some more examples" ''abc'' asUppercase. "receiver is string ''abc'' " ''HelloWorld'' reverse. "Lets reverse a string" 200 factorial. "1 * 2 * 3 * 4 ... * 199 * 200 returns a large number which is no problem for Smalltalk" "Simple message send can be used to ask an object. Note that the response is always an object" #(a b c) size. "lets ask an array for its size" ''123456'' isAllDigits. "is the string composed entirely of digits" "Instead of printing the result using the print it we can also open an inspector window on the result. This is done" "Note that compared to other languages even mathematical functions are handled by sending a message. instead of writing sin(x) we just have to send the message #sin to a number" 1 sin. "Converting objects is also typically done by sending messages" 123 asString. "you can convert an object to a string by sending #asString" 12.33 asInteger. "convert a float object into an integer object" ''12.34'' asNumber. "returns a number - here a float" "So the Smalltalk syntax simply is: Object always comes first (receiver), message follows. --------------------------------------------------------------------------------------------------------- -- 2. THERE ARE EXACTLY THREE KIND OF MESSAGES: Unary, binary and keyword messages --------------------------------------------------------------------------------------------------------- 2.1. Unary messages ======================== We already know this type of message from the above examples. The message we send to an object is just a word, there are no arguments." 3 negated. "We already know this " ''Hello World'' subStrings. "This returns an array of substrings" "2.2. Binary messages ======================== As the name implies we have two objects playing a role in this message type - the receiver and exactly one argument object. Each binary message is a binary selector, constructed from one or two characters followed by the argument object." 3 + 4. "send the message + to the receiver object 3 with the argument 4 " "Take care: compared to other languages where both sides of such an expression are treated equally in Smalltalk the objects in a binary message are clearly separated into the receiver of the message (the object in front of the binary message selector) and the argument (the object behind the message selector). Note the difference: " 3 + 4.0. "here we send the message + to an integer with a float as argument object" 4.0 + 3. "here we send the message + to a float with an integer as argument object" "Binary messages are typically used for arithmetic and comparing objects. Some more examples: " 1 = 2. "we know it should return false" 2 * 3. "ohhh ... it''s so simple" 1 < 2. "The object 1 should tell us if it is smaller than 2 (the argument)" ''Hello'', ''World''. "Concatenating string is done by sending the message , (comma) with another string as argument" "---------------------------------------------------------------------------------------------------------- ======================================== Part 2: Classes and their instances ======================================== --------------------------------------------------------------------------------------------------------- -- 1. AN OBJECT MAY HAVE PROPERTIES (state) --------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------- -- 2. EVERY OBJECT IS AN INSTANCE OF A CLASS --------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------- -- 3. A CLASS IS A TEMPLATE FOR CREATING ITS INSTANCES --------------------------------------------------------------------------------------------------------- ... Free Books on Smalltalk (available as PDF) http://www.iam.unibe.ch/~ducasse/FreeBooks.html -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

3 2

[Pharo-project] some minor tuning
by John M McIntosh Nov. 5, 2008

Nov. 5, 2008

I posted lessMethodSendsInFontUsage-JMM.4.cs to http://bugs.squeak.org/view.php?id=2144 to avoid excessive msg sends to font data entities as you resolve what to do character by character. Most of the changes described in #2144 were in Pharo but not all. I see we still do the forgetAllGrabCommandsFrom: dance across all objects in the image at startup time, not sure if this issue was ever resolved. Lastly I note PluggableListMorph>>getList runs quite a bit when we display a browser window. I'm wondering here if there should be a subclass where you know the list elements are strings and you just make a copy of the collection, versus doing a collect: asStringOrText -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

2 1

Re: [Pharo-project] FreeType
by Gary Chambers Nov. 5, 2008

Nov. 5, 2008

It would be a start, though, as I indicated, the major problem is the large computational expense of rendering the cached glyphs. Regards, Gary. ----- Original message ----- _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] [OT] A True Pluggable Look-and-Feel
by Torsten Bergmann Nov. 5, 2008

Nov. 5, 2008

see http://blog.3plus4.org/2008/11/04/a-true-pluggable-look-and-feel/ -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

3 2

[Pharo-project] KI diff package
by Pavel Krivanek Nov. 4, 2008

Nov. 4, 2008

This package http://squeak.cz/public/pub/KernelImage/temp/Remove-pavel_krivanek.1.mcz contains classes and methods that were removed in the KernelImage variant with Morphic but without Etoys. It may be used as referential material during Etoys removing. KI renames most of class initialization methods so they figure here as removed ones. -- Pavel

2 1

[Pharo-project] Pharo 1.0 release plan
by Adrian Lienhard Nov. 4, 2008

Nov. 4, 2008

Hi everyone, Last week in Bern, Marcus, Stef, and I have been discussing a plan for a first release of Pharo. Overall, the goal is to produce a valuable, stable "product" within reasonable time. Is there anything important we missed? Any suggestions? FUNCTIONAL REQUIREMENTS -------------------------------------------- Integrate Polymorph Integrate TrueType Main EToys removal Refactor Traits API NON-FUNCTIONAL REQUIREMENTS -------------------------------------------- All tests green License clean (check OLPC changes) First consistent version of the website (work in progress) INFRASTRUCTURE -------------------------------------------- Increase efficiency of producing new updates (work in progress) Prepare second update stream to maintain released version TENTATIVE SCHEDULE -------------------------------------------- Going beta in January Release of version 1.0 in February Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

16 29