March 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3913 in pharo: Fix in PluggableListMorph hierarchy

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Nautilus New issue 3913 by Benjamin...(a)gmail.com: Fix in PluggableListMorph hierarchy http://code.google.com/p/pharo/issues/detail?id=3913 - Fix PluggableIconListMorph to make it works with the new wrapping system - Create PluggableMorphListMorphOfMany, the copy of PluggableMorphLitMorph but which inherits from PluggableListMorphOfMany - Create PluggableIconListMorphOfMany, the copy of PluggableIconListMorph but which inherits from PluggableMorphListMorphOfMany Attachments: PluggableListMorphs.1.cs 6.6 KB

March 30, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by Patrick Barroca

My first look yesterday night taught me that different windows colour management is a basic behaviour of UITheme via #patchworkUIThemeColorFor:. If I simply subclass UITheme and do nothing more I get more or less a standard squeak theme with coloured windows minus some fills and borders styles. >From here I think I could try to make a simple theme with the look of Glamourous one with support for squeak windows colour management. Is this the right direction ? On Tue, Mar 29, 2011 at 11:17 AM, Patrick Barroca <patrick.barroca(a)gmail.com > wrote: > On Tue, Mar 29, 2011 at 9:38 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Yes! >> >> Partick if you want to extend the default theme to add color please do. We >> can create a repo >> PharoThemes and we are done. >> I would really like to remove the standard squeak because it is terrible. >> I set it up since some updates and >> I cannot work with it anymore. > > > Ok, I'll take a look at it. > > I'll try to make a default theme with the same color scheme as standard > squeak. > > -- > Patrick Barroca > -- Patrick Barroca

March 30, 2011

Re: [Pharo-project] Issue 3767 in pharo: We should add References to Pool Variable

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3767 by marcus.d...(a)gmail.com: We should add References to Pool Variable http://code.google.com/p/pharo/issues/detail?id=3767 Was added

March 30, 2011

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2

by StÃ©phane Ducasse

May be. Better is the enemy of good. Let's continue. If tomorrow we have two engineers in addition then somebody can do better. I like to think in terms of ratio and not absolute number. >> Thanks for reply. >> >> I should search mails first. >> > We should have added that fix to 1.2, not just 1.3.... > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. >

March 30, 2011

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image

by StÃ©phane Ducasse

Marcus no stress. Let us push 1.2 out and wait and see. We should not do a 1.2.2 now else it does not make sense. The fixes are available so we can batch them but not now. Stef >>> still in a circular dependency. >>> >>> Lukas >> >> Can you open a ticket? > > We can do a 1.2.2... and add the TextContstants at:put: fix, too. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 30, 2011

Re: [Pharo-project] Issue 3911 in pharo: Change updater to allow updating a release image

by pharo＠googlecode.com

Updates: Status: FixToInclude Labels: Milestone-1.2 Comment #1 on issue 3911 by marcus.d...(a)gmail.com: Change updater to allow updating a release image http://code.google.com/p/pharo/issues/detail?id=3911 fix attached Attachments: FixUpdatingRelease.1.cs 1.6 KB

March 30, 2011

Re: [Pharo-project] Progress bar design pattern

by Daniel Lyons

On Mar 29, 2011, at 6:17 PM, Martin Dias wrote: > I have a couple of algorithms and I want to show the progress while they run. I played with the progress bar and it's okay for my needs. > > The progress bar should be pluggable and decoupled of the algorithms. > > I am writing to you to ask about good designs for my problem. I hope I haven't expressed the problem in a too abstract way. > > The design I have in mind is a kind of observer pattern: the serialization algorithm publishes information about the run; a specific listener implements the progress bar for that serialization algorithm, interpreting the information published. I'm a newcomer here, so I'm sharing my experience with non-Smalltalk systems and my best guess what would constitute good designs. I hope other real Smalltalkers will poke some holes in this and point out the right way to do things! ;) The simplest design, IMO, would be this API: MyProgressBar>>percentComplete: aNumber MyProgressBar>>beIndeterminant MyProgressBar>>beDeterminant You would manually invoke percentComplete: with a new percent complete each time you want to advance the progress bar. I've seen this kind of thing in practice somewhere. Maybe it was Cocoa? The next level of abstraction would be to go a bit more jQuery UI and remove percentComplete: and use this instead: MyProgressBar>>maximum: anInteger MyProgressBar>>current: anInteger Now you'll calculate the progress bar based on some quantity of "tasks" you want to do. You could even go further and just have: MyProgressBar>>incrementProgress instead of letting your clients tell you which one they're on. That would prevent progress bar relapse. Either of these would be easy to implement on top of the above API using percent. The simplest observer-type pattern would be to rely on the built-in observer/event system and use the stuff from Object's updating protocol or events-registering or events-triggering. I don't know which one of these is modern or preferred. Anybody? :) At any rate, they make it possible to expose a simple object/message protocol as in Polymorph, where your progress bar widget would be listening for change notifications from your domain object. Then you can ask the same questions about your model as above, in terms of whether you want to work in terms of simply percent complete or N/M or what. Another question is whether or not you want to provide a string message status to go under the progress bar. Does this help at all, or did I miss the point? â Daniel Lyons

March 30, 2011

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

by pharo＠googlecode.com

Comment #9 on issue 3088 by vonbecm...(a)gmail.com: MNU Text>>withBlanksTrimmed http://code.google.com/p/pharo/issues/detail?id=3088 if you execute this query SourcedMethodReference allInstances select: [:each | each stringVersion class == Text ] it will give you these methods Announcement >> #asAnnouncement Announcement >> #open that have a Text as a string version. so, you get a Text for a Text when you invoke asStringOrText therefore, it produce a MNU in the following expression PluggableListMorph>>basicKeyPressed ... a asString withBlanksTrimmed asLowercase beginsWith: lastKeystrokes ...

March 30, 2011

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

by pharo＠googlecode.com

Comment #8 on issue 3088 by vonbecm...(a)gmail.com: MNU Text>>withBlanksTrimmed http://code.google.com/p/pharo/issues/detail?id=3088 neither in Pharo image: Pharo1.3a#13117 Virtual machine used: Squeak4.1 of 17 April 2010 [latest update: #9957] Platform Name: unix Class browser used (if applicable): Browser Attachments: PharoDebug.zip 130 KB

March 30, 2011

Re: [Pharo-project] [COTDC] 37 - MCPatcher

by HwaJongOh

2011. 3. 29., ì ë 3:46, laurent laffont ìì±: > > A new site about Pharo ? Cool ! > Yes. It is a wiki open to anonymous user. No sign in or sign up is required. So, anyone can cooperate on creating easy reference page. For now, no one is using ,except me, it is like public personal memo.

March 30, 2011