- Pharo-dev - lists.pharo.org

[Pharo-project] [Urgent] Big problem with fix for issue 1293
by Damien Cassou Dec. 6, 2009

Dec. 6, 2009

Hi Bart, your fix for issue 1293 prevents OmniBrowser from being loaded in Pharo 1.1. Could you fix it rapidly or should we revert it? Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] StandardWindow Layout Help
by Rob Rothwell Dec. 6, 2009

Dec. 6, 2009

I just can't seem to figure this out from the UITheme examples. Can anyone give me some general pointers on building a plain old Window? I know there isn't a UI builder, but how do you control the placement of the child controls you create in the window? For example, the following will create a StandardWindow and add a button to it (in the upper left corner). Do you control placement [of the button] with LayoutFrame? How do you use LayoutFrame? | win btnOk | win := StandardWindow new. btnOk := win newButtonFor: nil action: #ok getEnabled: nil label: 'Ok' help: nil. win addMorph: btnOk . win themeChanged; openInWorld. Thank you. I am finally trying to understand how to build some typical applications without a GUI builder... Take care, Rob

3 4

[Pharo-project] Usability with too many Deprecation Warnings dialogs (Settings framework)
by HernÃ¡n Morales Durand Dec. 6, 2009

Dec. 6, 2009

I'm using latest Pharo-Core with OmniBrowser and it's unusable with so many warning dialogs raising all the time in every operation : Opening an OB browser for example requires 6 Proceed clicks from an user with messages like this one: "The method Preferences class standardButtonFont has been deprecated. now accessible via the new setting framework " To modify this setting you could change the default to false in Deprecation initialize: Preferences addBooleanPreference: #raiseDeprecatedWarnings category: #general "programming?" default: false balloonHelp: 'If enabled, use of a deprecated API raises a Deprecated warning.'. but this would modify the Deprecation behavior for all deprecations (not just those related with the Preferences-Settings migration). To me it sounds like one should to consider two kinds of deprecations: -Those which need to raise a dialogs -Those which doesn't want to because it would affect usability (like right now in Pharo with OB). I've just attached a specific message for deprecations requiring active interaction for the user (#deprecatedWithPopUp). This addition doesn't require to modify all the current #deprecated: senders, but you should explicit modify with the #deprecatedWithPopUp variant in those places you consider of enough importance to keep the user informed. The Transcript notification behavior keeps intact. Feel free to change it anyway you want :) Cheers, HernÃ¡n

3 4

Re: [Pharo-project] about sluggines on linux
by John M McIntosh Dec. 6, 2009

Dec. 6, 2009

On 2009-12-05, at 3:32 PM, Arturo Zambrano wrote: > '215851602 bytecodes/sec; 6194336 sends/sec' > > Machine: Linux donner2 2.6.28-tuxonice-r10 #8 SMP Sun Nov 8 09:50:51 ART 2009 x86_64 AMD Turion(tm) 64 X2 TL-60 AuthenticAMD GNU/Linux. 2GHz > That speed is 1/2 of my 2.33Ghz intel core 2 Duo '533333333 bytecodes/sec; 12157397 sends/sec' > > Try doing > Transcript cr;show: > [Display fillWhite. 1 to: 4 do: [:i | Pen new color: i; turn: 90*i; dragon: 14] ] timeToRun. > Display restore. > > report back how big the number is printed to the transcript > > 1897 This number is fine -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

2 1

[Pharo-project] mouse clicks not registered
by Sean Allen Dec. 6, 2009

Dec. 6, 2009

I installed the latest pharo vm and the 10492-rc1dev09.11.1 image on a ubuntu 8. fire up the image and it doesn't respond to mouse clicks. took a work setup from xubuntu, copied it over, same issue. this is on a 64 bit machine. any pointers on what might be the issue?

1 0

Re: [Pharo-project] [Moose-dev] Re: for mondrian designers
by Tudor Girba Dec. 6, 2009

Dec. 6, 2009

Hi, >>> So consider to have a look at the cairo package in PharoTaskForces >>> because it will not come to you alone :) What exactly should I load from PharoTaskForces to get Cairo? I see several Rome related packages, but which ones are needed? Is there a load script? Cheers, Doru -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

4 9

[Pharo-project] [update 1.1] #11072
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

11072 ----- - Issue 1437: Bitmap #decompress:fromByteArray:at: not wellformed - Issue 1252: Transparency Artifact - Issue 1363: should use selectorsDo: instead of selectors do:

1 0

[Pharo-project] Fwd: Issue 1298 in pharo: CrLfFileStream not properly initialized on Mac OS
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

Begin forwarded message: > From: pharo(a)googlecode.com > Date: December 5, 2009 9:56:30 PM GMT+01:00 > To: stephane.ducasse(a)gmail.com > Subject: Re: Issue 1298 in pharo: CrLfFileStream not properly initialized on Mac OS > > > Comment #2 on issue 1298 by nicolas.cellier.aka.nice: CrLfFileStream not properly initialized on Mac OS > http://code.google.com/p/pharo/issues/detail?id=1298 > > 1) I don't like to see these getSystemAttribute: 1001 spreaded like a plague. We have > clear messages that perfectly insulate these cryptic secret codes. > 2) As I changed these getSystemAttribute: senders recently in trunk, I think I saw > more subtle things like testing for 'Darwin' or something... Aren't OS-X linefeed > based ? (I don't own a Mac...) > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences at: > http://code.google.com/hosting/settings

1 0

Dec. 5, 2009

Begin forwarded message: > From: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: December 5, 2009 9:55:14 PM GMT+01:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: why OOP needs tails recursion article > > Hi Steph, > > can you forward my response to the Pharo list? I guess I do need to join the Pharo list :/ > > Eliot (from under an avalanche of email) > > On Sat, Dec 5, 2009 at 12:32 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Sat, Dec 5, 2009 at 2:00 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > http://lambda-the-ultimate.org/node/3702 > > > I want to return to the implementation and optimization implications of this later. But Steele's post refers to William Cook's excellent paper On understanding data abstraction, revisited. Onward! Essays, 2009 ACM OOPSLA. SIGPLAN Notices 44, 10 (Oct. 2009), 557-572. There's a freely available draft version. The quote I want to emphasise is > > The extensibility of objects does not depend upon inheritance, but rather is an inherent property of object interfaces. > > The paper proves this point eloquently and concisely. The implication is that isKindOf: is <shout>BROKEN</shout>. In the absence of something better isSomeInterface to query whether an object implements some interface SomeInterface is acceptable. isKindOf: (and the horror I found the other day isKindOf:orKindOf: (you see why it exists and where it leads?)) is not and should be expunged. > > My weekend rant. > > best, > Eliot >

1 0

Re: [Pharo-project] asBit
by Ralph Boland Dec. 5, 2009

Dec. 5, 2009

> I currently writing a code which looks like: > > a := some numeric expression + (someBoolean ifTrue: [1] ifFalse: [0]). > > And i get somewhat tired repeating the same pattern in multiple places. > So, i thinking , maybe #asBit convenience method could be useful? > > True>>asBit > Â ^ 1 > False>>asBit > Â ^ 0 > > so, then, in case of need like above, we could write much shorter expressions: > a := some numeric expression + someBoolean asBit. > > And its much less error prone comparing to #ifTrue:ifFalse:, since i > found its relatively easy to make a mess (swapping 1 with 0), > especially, when you having negations in expression, because once you see: > > (someBoolean not ifTrue: [1] ifFalse: [0]) > > you always tempted to write it as: > > (someBoolean ifTrue: [0] ifFalse: [1]). > > or as: > > (someBoolean ifFalse: [1] ifTrue: [0]). > > but once you start playing with it, its very easy to shoot into own > feet if you are not careful. > > But if we could add #asBit, then we could write: > > someBoolean not asBit > > which is much more: > a) concise & cleaner > b) error proof > > > -- > Best regards, > Igor Stasenko AKA sig. I use "someBoolean card" for this where card stands for cardinality. The cardinality of false is 0 and of true is 1. Method "card" can also be used for other classes of object that have cardinal values associated with them. Regards, Ralph Boland -- Volume * Density = Mass. Volume / Density = Intelligence. The latter equation explains the essentially equal intelligence of men and woman and the capabilities of some commonly used operating systems.

1 0