- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Doodle for Christmas Smalltalk Parties

by StÃ©phane Ducasse

Would be nice to try before hand. I do not have the time for that but this would be fun. Stef On Dec 6, 2009, at 11:10 AM, Lawson English wrote: > Mariano Martinez Peck wrote: >> Ok, here I created the event: http://www.doodle.com/mn4e6anmskwpd5s7 >> >> I put from 18 of December until 4 of January, as Stef suggested. >> >> Now, you can subscribe yourself and put the days you can. Then, >> depending of the people subscribed for each day, we decide which days >> to do it. >> >> Best, >> >> Mariano > If you can provide an external video/audio connection for passive > viewers, it might be possible to set up that Second Life audience > participation thing with kibbitzers also contributing via text chat. > > Lawson > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 6, 2009

Re: [Pharo-project] Usability with too many Deprecation Warnings dialogs (Settings framework)

by StÃ©phane Ducasse

no stress alain. We really appreciate all the work you do :) Stef On Dec 6, 2009, at 11:02 AM, Alain Plantec wrote: > StÃ©phane Ducasse a Ã©crit : >> Hi hernan >> >> 1.1 is under work. Alain told me that he will kill all the call to deprecated methods soon >> > yes but only inside the core. > I will also change deprecation messages. They have to give the new > equivalent method if any (current message is stupid) > but, i will not check external packages... > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 6, 2009

Re: [Pharo-project] Doodle for Christmas Smalltalk Parties

by Lawson English

Mariano Martinez Peck wrote: > Ok, here I created the event: http://www.doodle.com/mn4e6anmskwpd5s7 > > I put from 18 of December until 4 of January, as Stef suggested. > > Now, you can subscribe yourself and put the days you can. Then, > depending of the people subscribed for each day, we decide which days > to do it. > > Best, > > Mariano If you can provide an external video/audio connection for passive viewers, it might be possible to set up that Second Life audience participation thing with kibbitzers also contributing via text chat. Lawson

Dec. 6, 2009

Re: [Pharo-project] Usability with too many Deprecation Warnings dialogs (Settings framework)

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : > Hi hernan > > 1.1 is under work. Alain told me that he will kill all the call to deprecated methods soon > yes but only inside the core. I will also change deprecation messages. They have to give the new equivalent method if any (current message is stupid) but, i will not check external packages...

Dec. 6, 2009

Re: [Pharo-project] [squeak-dev] AST-Core for Pharo and Squeak?

by Lukas Renggli

Did you run the tests, especially RBParserTest? They do all pass on Pharo. Does Squeak implement #isVariable on Object? Lukas 2009/12/6 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi guys, > I've noticed a different behavior relating the RBParseTreeSearcher > between Pharo and Squeak, using AST-Core-lr.33, the following code: > > | rbMethodNode | > rbMethodNode := RBParser parseMethod: 'test [ ]'. > ( RBParseTreeSearcher new > matches: '`{:node | node isVariable }' > do:[: aNode : answer | answer add: aNode; yourself ] ) > executeTree: rbMethodNode initialAnswer: Set new. > > gives an empty Set in Pharo-Core (#11072) and a Set(RBSequenceNode()) > in Squeak 3.10.2 > Does anybody know if I should use a different AST-Core version for > Squeak? An alternative repository maybe? > > HernÃ¡n > > -- Lukas Renggli http://www.lukas-renggli.ch 2009/12/6 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi guys, > Â I've noticed a different behavior relating the RBParseTreeSearcher > between Pharo and Squeak, using AST-Core-lr.33, the following code: > > | rbMethodNode | > rbMethodNode := RBParser parseMethod: 'test [ Â ]'. > ( RBParseTreeSearcher new > Â Â Â Â matches: '`{:node | node isVariable }' > Â Â Â Â do:[: aNode : answer | answer add: aNode; yourself ] ) > Â Â Â Â Â Â Â Â executeTree: rbMethodNode initialAnswer: Set new. > > gives an empty Set in Pharo-Core (#11072) and Â a Set(RBSequenceNode()) > in Squeak 3.10.2 > Does anybody know if I should use a different AST-Core version for > Squeak? An alternative repository maybe? > > HernÃ¡n > > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 6, 2009

Re: [Pharo-project] Usability with too many Deprecation Warnings dialogs (Settings framework)

by Alain Plantec

Hi all, Sorry, sorry, sorry, I'm the author. But please consider two things, it's the alpha 1.1 and that package maintainers must be warned. Anyway, you can already avoid having deprecation popup and redirect deprecation warning to the Transcript with the help of two existing preferences: #raiseDeprecatedWarning #showDeprecationWarning (accessible with the old preference browser). Sorry again. cheers Alain HernÃ¡n Morales Durand a Ã©crit : > 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 > > ------------------------------------------------------------------------ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 6, 2009

Re: [Pharo-project] Usability with too many Deprecation Warnings dialogs (Settings framework)

by StÃ©phane Ducasse

Hi hernan 1.1 is under work. Alain told me that he will kill all the call to deprecated methods soon. I was planning that too. Good idea for the PopUp Stef On Dec 6, 2009, at 5:46 AM, HernÃ¡n Morales Durand wrote: > 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 > <Deprecation.st><Object-deprecatedWithPopUp.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 6, 2009

Re: [Pharo-project] StandardWindow Layout Help

by StÃ©phane Ducasse

Hi hernan It would be great to have some nice litte examples; if you get some moment could you clean them from nebraska I will have a look later today for the sound in RC we load the package Sound and the extra Morphic examples. Because examples are IMPORTANT Stef On Dec 6, 2009, at 5:58 AM, HernÃ¡n Morales Durand wrote: > Hi Rob, > Besides the StÃ©phane's example, you will find attached a cool > Morphic example to start experimenting with Layouts. Possibly it's > non-functional because of some Nebraska dependencies with the Sound > package (I don't know the status of Sound in Pharo) but it would be > sufficient for your purposes. To open it: > > ChatNotes new openAsMorph. > > and play with the implementation of #openAsMorph > Cheers, > > HernÃ¡n > > 2009/12/5 Rob Rothwell <r.j.rothwell(a)gmail.com>: >> 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 >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > <ChatNotes.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 6, 2009

Re: [Pharo-project] about sluggines on linux

by StÃ©phane Ducasse

Hola Arthuro Here this is raining and windy :) (and cold) > '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' 2.56 Ghz intel core 2 Duo with latest 1.1 image '576901408 bytecodes/sec; 12762744 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 1676 The conclusion is that we should continue to work on making it faster. Arthuro using 1.1 changing the theme using StrikeFont installDejaVu and setting up the fonts give a better feel Does anybody know a software slowing down a mac (because the problem is that I'm not sure that I can run a closure VM on a old mac I have) so that we could do some tests on slow machines? Stef

Dec. 6, 2009

Re: [Pharo-project] squeak VM 5.0

by John M McIntosh

On 2009-12-05, at 9:46 PM, Laval Jannik wrote: >> I added >> object class = BlockClosure ifTrue: >> [(object instVarAt: 3) ifNotNil: >> ["May need to adjust PC and startPC if changing wordSize..." >> results at: 2 put: (block value: (object instVarAt: 2)+(self pcDeltaForMethod: object method) value: 2)]]. Oops should be object class = BlockClosure ifTrue: ["May need to adjust PC and startPC if changing wordSize..." results at: 2 put: (block value: (object instVarAt: 2)+(self pcDeltaForMethod: object method) value: 2)]. Post your current change set so we can see However that just gives me, which is where I was earlier. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Dec. 6, 2009