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

Re: [Pharo-project] Issue 2844 in pharo: String>>#numArgs is broken
by Schwab,Wilhelm K Sept. 4, 2010

Sept. 4, 2010

Stef, Does that mean that 1.1 will be patched accordingly? I have been thinking of building a new 1.1 image but can safely postpone that until this is ready if that is the intent. Bill ________________________________________ From: pharo(a)googlecode.com [pharo(a)googlecode.com] Sent: Friday, September 03, 2010 3:23 PM To: Schwab,Wilhelm K Subject: Re: Issue 2844 in pharo: String>>#numArgs is broken Comment #5 on issue 2844 by stephane.ducasse: String>>#numArgs is broken http://code.google.com/p/pharo/issues/detail?id=2844 marcus will integrate it in the 1.1.1 batch he will do soon :) -- You received this message because you starred the issue. You may adjust your notification preferences at: https://code.google.com/hosting/settings

2 1

[Pharo-project] PharoKernel #12121
by Pavel Krivanek Sept. 4, 2010

Sept. 4, 2010

Hi, I uploaded the new version of PharoKernel #12121: https://gforge.inria.fr/frs/download.php/27438/PharoKernel-1.2-12121.zip The shrinking process is now based on packages. Cheers -- Pavel

8 19

[Pharo-project] Pharocasts: Deploy Seaside with Cherokee Web Server
by laurent laffont Sept. 3, 2010

Sept. 3, 2010

Hi, New screencast from Christoph: Learn how to - install Cherokee Web Server on Ubuntu Linux through Launchpad - configure Cherokee to serve static files for a Seaside application - start an headless Seaside image http://pharocasts.blogspot.com/2010/09/deploy-seaside-with-cherokee-web-ser… Note: If you have any suggestions for improvement, Cherokee + Seaside tips and tricks you want to share or saw something that is plain wrong or could be described in more detail to make it easier to understand, feel free to add a comment and we will update the screencast accordingly to improve it. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

1 0

[Pharo-project] [ANN] New 1.2 unstable
by StÃ©phane Ducasse Sept. 3, 2010

Sept. 3, 2010

https://gforge.inria.fr/frs/download.php/27445/PharoCore-1.2-12123.zip Stef

1 0

[Pharo-project] TestSprinter
by Benjamin Van Ryseghem Sept. 3, 2010

Sept. 3, 2010

Hello everybody I'm now working on a new Test Runner tool and I wonder which behaviours do you want me to implement. For now, I want the Test Sprinter to be able to : - search through packages and classes thanks to search fields. - browse the hierarchy from packages to test methods (with icons). - create groups of tests easily re-runnable. If you have any ideas, I'm waiting for them ;) Thank you Ben

6 13

[Pharo-project] [update 1.2] #12123
by StÃ©phane Ducasse Sept. 3, 2010

Sept. 3, 2010

12123 ----- - Issue 2890: Some isNil ifTrueifFalse -> ifNil:. Thanks Guillermo Polito. - Issue 2907: undeprecate Smalltalk os so that we can write Smalltalk os versionName and Smalltalk os platformName - Issue 2896: Make sure system notifications for Smalltalk are up-to-date. Thanks Eliot Miranda and Adrian Leinhard. - Issue 2893: Network bugs. Thanks Andreas Raab.

1 0

[Pharo-project] Native (OS-level) windows
by Evgeniy Philippov Sept. 3, 2010

Sept. 3, 2010

Hello folks and Todd Blanchard, I have three questions. First question is---what is the current status of Ffenestri, and where can I download some version of Pharo with the most up-to-date Ffenestri support? The second question is---what are the other Pharo OS-level windowing interfaces, and what is their status? And the last question is---what is more complete: Squeak's Ffenestri support, or Pharo's Ffenestri support? My intents. I plan to use some version of Squeak or Pharo system for my project (which is a hobby project), and I am mainly interested in OS-level windowing for Linux (Ubuntu) and to a lesser extent for Win32 too. I studied wxSqueak a bit, and concluded that Ffenestri is overall simpler to develop than wxSqueak, and guessed that Ffenestri moves/will move faster when considering the completeness of it, than wxSqueak. -- Evgeniy

3 5

[Pharo-project] FSPlatformResolver class>>forCurrentPlatform use a deprecated method
by Cyrille Delaunay Sept. 3, 2010

Sept. 3, 2010

In the package Filesystem, FSPlatformResolver class >> forCurrentPlatform | platformName | platformName := SmalltalkImage current platformName. ^ (self allSubclasses detect: [:ea | ea platformName = platformName]) new should be replaced by FSPlatformResolver class >> forCurrentPlatform | platformName | platformName := OSPlatform platformName. ^ (self allSubclasses detect: [:ea | ea platformName = platformName]) new

4 4

Re: [Pharo-project] [squeak-dev] Experimental Cocoa OS-X based Squeak Cog JIT VM 5.8b4.
by John M McIntosh Sept. 3, 2010

Sept. 3, 2010

On 2010-08-29, at 11:10 AM, stephane ducasse wrote: > John > > What I want to understand is what does it means to use open/GL. > This means that you use open/GL to implement the primitive? > Now I thought that opengl was more vector graphics than bitblt so how does it fit together. > Is it because the mac UI is opengl based too? > > Stef Ok let me give you some background, then talk about open/GL The Squeak drawing logic invokes: http://isqueak.org/displayioShowDisplay Which is to say copy this rectangle of data from the Squeak Display Oops data pointer to something that visually shows the user what is going on, since drawing can require a few Smalltalk based calculations resulting in draw events to compose a final image then we also have, http://isqueak.org/ioForceDisplayUpdate To help the process a bit by allowing the drawing subsystem to compose the bits until we are done, then perform the expensive step of visualization. In general the displayioShowDisplay is really fast but the ioForceDisplayUpdate is slow, displayioShowDisplay may not show the bits, but displayioShowDisplay may now (or later... ) Depending on which VM source code (version and platform dependent) you may find that ioForceDisplayUpdate does nothing, or a operating system flush is done to the hardware on every displayioShowDisplay. Where you can see this issue is if you try. Transcript cr;show: [| b | b _ Pen new. Display fillWhite. b place:(Display boundingBox bottomLeft). b hilbert: 9 side: 2 ] timeToRun. Display restore. If this crawls, like taking 30 seconds, then the implementation is flushing every bit draw to the operating system. Well or if you don't see the bits then maybe neither displayioShowDisplay or ioForceDisplayUpdate does any flushing, and all you see is the Display restore results. Now just to make life harder for the VM implementor the Smaltalk code might not call ioForceDisplayUpdate. Then the VM has to do the ioForceDisplayUpdate internally in order not to leave bit's dangling. How this is done again is different from VM to VM. Usually this shows up as a double menu selection highlight. For the 4.2.x series of Macintosh VM we would trigger a operating system flush if more than 20 ms (a settable value) had elapsed, and I did nothing for ioForceDisplayUpdate. But I change this in 5.x and for the iPhone to make ioForceDisplayUpdate the trigger, with a timer that pops if a ioForceDisplayUpdate is not done within 20ms of the last executed displayioShowDisplay. Now about Open/GL, in the past for os-x carbon VM 4.2.X and earlier we used System 7.5.x technology to draw bits, which was quickdraw and quickdraw quartz. When I moved the logic to the iPhone that is not supported technology, because of the interesting drawing logic on the iPhone it took 6 attempts and a long chat with a graphics engineer at Apple. That resulted in using Core Animation to divide the screen into 16 tiles so when a draw happens we note which Tile(s) are dirty based on the rectangle intersections, then on the ioForceDisplayUpdate we generate images for each of the dirty tiles from the Display Oops and tell Core Animation redraw the new tiles. Bert said this seemed slow on OS-X. At this point the next step in our OS-X/iOS drawing path is drop one step lower down and consider Open/GL. I must admit I've not done any open/GL work before so it was a learning opportunity. Although you think of Open/GL as a vector based graphic language it does support what is know as Textures. So instead of providing vectors, you supply bits. So a chunk of data, stating it's RGB, at this depth and pixel layout and size, etc make a chunk of screen glow that is showing the open/GL viewport. Now there are lots of restrictions but the GPUs and drivers have become more friendly so you can supply arbitrary sized rectangles, this was at one time slow, but GPUs have become extremely fast, so slow is fast... In fact on the mac you can supply a arbitrary sized rectangle taken from a much larger rectangle of data, which fits perfectly into the displayioShowDisplay logic. The only hassle is that you need to figure out how the flush should work. So after 3 days of intense effort I can say the algorithm is... displayioShowDisplay collects the union of the rectangles that are being drawn. Nothing more happens... It's pointless to do the glTexImage2D here because 'b hilbert: 9 side: 2' will kill you. Mind we do still watch for a missing ioForceDisplayUpdate. ioForceDisplayUpdate Then takes the union of the rectangles, set a GL viewpoint, and does the glTexImage2D based on figuring out the start point of the top/left pixel of the rectangle to draw, then setups up the coordinate system and finally flush the data. glViewport( subRect.origin.x,subRect.origin.y, subRect.size.width,subRect.size.height ); char *subimg = ((char*)lastBitsIndex) + (unsigned int)(subRect.origin.x + (r.size.height-subRect.origin.y-subRect.size.height)*r.size.width)*4; glTexImage2D( GL_TEXTURE_RECTANGLE_ARB, 0, GL_RGBA, subRect.size.width, subRect.size.height, 0, GL_BGRA, GL_UNSIGNED_INT_8_8_8_8_REV, subimg ); glBegin(GL_QUADS); // The -1 is so we flip the coordinate system as os-x and squeak have different views of where (0,0) is... glTexCoord2f(0.0f, 0.0f); glVertex2f(-1.0f, 1.0f); glTexCoord2f(0.0f, subRect.origin.x.size.height); glVertex2f(-1.0f, -1.0f); glTexCoord2f(subRect.origin.x.size.width, subRect.origin.x.size.height); glVertex2f(1.0f, -1.0f); glTexCoord2f(subRect.origin.x.size.width, 0.0f); glVertex2f(1.0f, 1.0f); glEnd(); glFlush() // Ask the hardware to draw this stuff, don't use the more aggressive glFinish() reset the union of draw rectangles. Hint (a) Oddly some people feel they should re-configure the open/GL graphic context on *every* draw cycle, why? (b) People don't read the Apple guidebooks for best practices for doing glTexImage2D, this I know based on Google searches using certain Apple open/GL extension keywords. Notes: This assumes the Squeak display is 32 bits, other resolutions are an exercise for the reader. Actually if the row width is a multiple of 32 bytes then on the Mac things are *much* faster and no copy is made. This is enforced in 5.7b5 by ensuring window size is divisible by 8. When the graphic context is setup when the window is built there is a bunch of cmds to execute, one important one is glPixelStorei( GL_UNPACK_ROW_LENGTH, self.frame.size.width ); and when the window is resized there are a few things to do to indicate how the context has changed. Some platforms like the iPhone might need to do this instead because it doesn't support the GL extension GL_TEXTURE_RECTANGLE_ARB glTexImage2D( GL_TEXTURE_2D, 0, GL_RGBA, subRect.size.width, subRect.size.height, 0, GL_RGBA, GL_UNSIGNED_INT_8_8_8_8_REV, NULL ); for( int y = 0; y < subRect.size.height; y++ ) { char *row = ((char*)lastBitsIndex) + ((y + subRect.origin.y)*subRect.size.width + subRect.origin.x) * 4; glTexSubImage2D( GL_TEXTURE_2D, 0, 0, y, subRect.size.width, 1, GL_RGBA, GL_UNSIGNED_BYTE, row ); } -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

6 15

[Pharo-project] FSPlatformResolver class>>forCurrentPlatform use a deprecated method
by Torsten Bergmann Sept. 3, 2010

Sept. 3, 2010

Lukas wrote: >Why? OSPlatform doesn't even exist in Pharo 1.1. Pharo includes this class in Pharo-1.1-11411 Bye T. -- GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 fÃ¼r nur 19,99 €/mtl.!* http://portal.gmx.net/de/go/dsl

1 0