August 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Blinking Cursor - (WAS: Enhanced StrikeFonts (antiAliasing , subPixel AA))
by Torsten Bergmann Aug. 5, 2009

Aug. 5, 2009

Hi there, attached is a "blinking cursor" implementation for Pharo ported/inspired from/by the Morphic Text improvements done by Andreas [1]. The more general question I have is: is it "legally" possible to port and include stuff like this from the new "squeak trunk" into pharo? Andreas is not (yet) on the list of License Agreement Signers. Does anyone know if the new "squeak trunk" is already MIT license? Thanks Torsten [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-August/138025.h… -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

4 4

[Pharo-project] [ANN] Pharo 1.0 Beta
by Adrian Lienhard Aug. 5, 2009

Aug. 5, 2009

Hi all, We are excited to announce the first Pharo 1.0 beta release. A new Pharo image (and also Pharo-web image) can be downloaded from the website: http://pharo.cmsbox.ch/pharo-download The corresponding version number of Pharo-core is #10401. I'd like to thank all the people that have contributed to Pharo so far! Have fun, Adrian BTW, I also wrote about Pharo and the beta release on http://www.adrian-lienhard.ch/blog ___________________ http://www.adrian-lienhard.ch/

10 25

[Pharo-project] Pharo responseless when debugger steps into DNU in Seaside app
by Johan Brichau Aug. 5, 2009

Aug. 5, 2009

Hi everyone, I'm getting a problem debugging Seaside applications in latest Pharo. When stepping with the debugger through the execution of a seaside application and encountering a message not understood, the entire Pharo system freezes and is totally unresponsive. It does not show that a DNU occurs, it simply becomes unresponsive when trying to step over the message that does not exist. I have to force quit. The problem can easily be recreated by changing a seaside component's render method such that a DNU occurs. Next, choose to debug the problem and restart the context. Now start stepping through the method and the system freezes when you try to step into the message that is not understood. The system freezes and does not show you a DNU. It seems to be a Pharo-Seaside problem since I do not have the same problem when doing this outside of Seaside applications. I'm using Pharo 09.7.5 (with seaside) and did a system update just now. I'm trying to drill down to the source of the problem but if anyone has any ideas.... ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

3 5

[Pharo-project] preferences?
by StÃ©phane Ducasse Aug. 5, 2009

Aug. 5, 2009

This is nice to see that we are also copied :) At ESUG it would be good to see the next step in preference cleaning. Stef From: Andreas Raab <andreas.raab <at> gmx.de> Subject: Preference Pragmas redux Newsgroups: gmane.comp.lang.smalltalk.squeak.general Date: 2009-08-05 04:52:16 GMT (3 hours and 7 minutes ago) Folks - I've just pushed a version of preference pragmas into the trunk. With preference pragmas, you no longer need to litter Preferences with loose methods that confuse Monticello and don't get uninstalled. With preference pragmas, you define your preferences locally (for example as class variables) and provide an annotation that can be discovered automatically. A sample preference looks like here: MyClass>>samplePref <preference: 'Sample Preference' category: 'My Application' description: 'A sample preference in my application' type: #Boolean> ^SamplePref The following types of preferences are currently supported: #Boolean, #String, #Number, and #Color. When a preference is changed, the accompanying setter method is called. Preference pragmas will help us get rid of most of the dependencies between Preferences and the rest of the world. New preference browsers or entire implementations can easily be written without introducing unnecessary dependencies by virtue of discovering the annotation. Cheers, - Andreas

1 0

[Pharo-project] table widget
by Tudor Girba Aug. 5, 2009

Aug. 5, 2009

Hi, Is there a table widget in Morphic/Polymorph? I would features like: - add columns - sort the rows based on a column - select a row Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

3 4

[Pharo-project] Pharo name format
by Miguel Enrique CobÃ¡ Martinez Aug. 4, 2009

Aug. 4, 2009

Now that the release date for pharo is close, I propose to use the following sintax for the pharo core products PharoCore-x.y-#####-TagName.zip where x.y is the version of pharo (0.1, 1.0, 1.1, 2.0, 2.1, etc) ##### is the number of image release in that version (10449, 10450, 10451, etc) TagName is a tag for better explain some specific feature of the image (closure, RELEASE, STABLE, beta, etc) e.g. For a normal daily release, say 10450, in the 0.1 branch: PharoCore-0.1-10450.zip For the image that has all tests in green: PharoCore-0.1-10456-AllTestGreen.zip For the image that it is the first stable 1.0: PharoCore-1.0-10478-RELEASE_1_0.zip For the next image with the NewCompiler code integrated, after the 1.0 release: PharoCore-1.0-10490-NewCompiler.zip For a subsecuent 1.1 release, that includes NewCompiler: PharoCore-1.1-10511-RELEASE_1_1.zip When, for example, 1.1 is the current branch, and 1.0 has fixes support and a new emergency release for the old 1.0 branch: PharoCore-1.0-10512-UPDATE_1.zip Release for pharo 2.0: PharoCore-2.0-10890-RELEASE_2_0.zip Other fix in the 1.1 branch (brach 1.0 is out of support): PharoCore-1.1-10915-UPDATE_1.zip Notes: We can also reset the number in each mayor release (0.1, 1.0, 1.1, etc) so that the updates to the old supportes branches can be a continuous. For example, the previous names would be (in the same order of release as the examples above): PharoCore-0.1-10450.zip PharoCore-0.1-10456-AllTestGreen.zip PharoCore-1.0-10001-RELEASE_1_0.zip PharoCore-1.0-10002-NewCompiler.zip PharoCore-1.1-10001-RELEASE_1_1.zip PharoCore-1.0-10003-UPDATE_1.zip PharoCore-2.0-10001-RELEASE_2_0.zip PharoCore-1.1-10002-UPDATE_1.zip etc Also, the PharoCore-1.0-10001-RELEASE_1_0.zip would be a copy of the last image of 0.1 branch (in this example PharoCore-0.1-10456-AllTestGreen.zip) But this is mostly estetic and can potentially confuse new users. What do you think?

7 10

[Pharo-project] [update] #10405
by Marcus Denker Aug. 4, 2009

Aug. 4, 2009

10405 ----- Issue 1017: Some packages are dirty in the core version 400 Issue 1020: Rename TSetAritmetic in TSetArithmetic -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

1 0

Aug. 4, 2009

From: Juan Vuletich <juan <at> jvuletich.org> Subject: Cuis updated to #0250 Newsgroups: gmane.comp.lang.smalltalk.squeak.general Date: 2009-07-31 22:05:02 GMT (3 days, 19 hours and 58 minutes ago) A new release of Cuis is available at http://www.jvuletich.org/Cuis/Index.html . It includes some bugfixes and more cleanup. Biggest news is a lot of cleanup in the Text system. Gone are the ugly TextConstants pool and the old Paragraph class. TextStyle lost over half its instance variables and over 80% of its methods. I also added a TextEditor to the World menu that is not a Smalltalk Workspace and may be useful especially for end users. As usual, all the updates starting at #0001 are available separately, and described in http://www.jvuletich.org/Cuis/CategoriesAndChangeSets.txt . This could be useful for users of other Squeak images wanting some of the bug fixes and enhancements included in Cuis. Comments welcome. Cheers, Juan Vuletich

1 0

Re: [Pharo-project] Custom user Interrupt handling
by Dale Henrichs Aug. 4, 2009

Aug. 4, 2009

Michael, What's the approved method for unregistering the current user interrupt handler? InputEventFetcher default eventHandlers copy do: [:hndlr | (hndlr isKindOf: UserInterruptHandler) ifTrue: [ hndlr unregister]]. Looks like it would work, but seems a bit fragile. Dale ----- "Michael Rueger" <m.rueger(a)acm.org> wrote: | Dale Henrichs wrote: | | > The class UserInterruptHandler is tantalizingly close, however, | there | > is no obvious way to insinuate myself as an interested | party....It's | > pretty much hard-wired to open a debugger on the interrupted | > process.... | | Just write your own class (e.g. subclass UserInterruptHandler) and | replace the handler (unregister the current one and register your | own). | | That's why I designed it the way it is :-) | | michael

3 2

[Pharo-project] Debbuging problems, FFI
by Javier PimÃ¡s Aug. 4, 2009

Aug. 4, 2009

Hi, I'm having problems with the debugger. Every time I try to debug code that uses FFI, if I step over a message that internally does an FFI call, I get an externalCallFailed error and then I land in MethodContext(ContextPart)>>runUntilErrorOrReturnFrom: If I run the code without debugging, then I have no problems at all. I'm using SqueakPharo v3.11.2 with pharo0.1-10373web09.07.2. To reproduce it you can try this: ScriptLoader loadFFI. then load latest GLMorphic from squeaksource, and uncomment the "self break." in GLCanvas>>displayString:from:to:at:strikeFont:kern: doit World fullDrawOn: GLDisplayScreen testCanvas hit debug and step over until you reach ogl glTexImage2D: GLTexture2d with:... also you'll see wrong values for local vars, like aPoint which will look as #(nil nil nil nil nil) when it'll actually have a point. Is there any other way to set up a break point instead of adding self break to the code?? Thanks, Javier. -- Javier PimÃ¡s Ciudad de Buenos Aires

5 14