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

Re: [Pharo-project] Progress bar design pattern

by Martin Dias

On Wed, Mar 30, 2011 at 6:12 AM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> wrote: > > On Mar 30, 2011, at 7:13 23AM, Daniel Lyons wrote: > > > 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 > > I've used Announcements for this in the past, and liked it quite alot. > > I will take a look on that. > - Worker announces WorkCompleted or some such. > Announcement holds details of the work it's done, in my case different > properties of an analysis like leak rate, . > > - GUI/Client is set up before analysis starts, and initialized with the > total work to be done. > Annnouncement handling contains code to estimate how much progress the Work > indicated by it was of the overall total. > > I also used a different client which provided ETA based on a more > sophisticated analysis of the Work announcements. > Wow! I don't need to estimate time but it's very interesting think on that. > > Needless to say, there's no hard dependency on a UI in such a scheme, as > there simply won't be any clients instantiated if you run headless. (well, > unless you make one writing to stdout or something) > > Not sure what would be reasonable to put in a Work-annnouncement intended > as superclass for custom solutions... > In other words, the downside is that this approach doesn't lead to > something you can use out-of-the-box, you always have to do some > customization, either/both to what data you provide, or/and to how you give > feedback. > (In this case, a standard widget using the simplest design you described > is preferrable, btw, the pluggability is done at a different level than the > widget) > > In this moment I am interested in a simple solution, I will not write a framework, but I like the discussion. Thanks! > Cheers, > Henry >

March 31, 2011

Re: [Pharo-project] [Pharo-users] [OT] I've started blogging

by Janko MivÅ¡ek

Mariano wonderful! Don't forget to add your blog on http://planet.smalltalk.org/, so taht all Smalltalk world will follow you! Best regards Janko On 31. 03. 2011 22:25, Mariano Martinez Peck wrote: > Hi guys. Just in case someone is interested, I've have started blogging: > "Sending messages through small talks" > > The blog is here: http://marianopeck.wordpress.com/ > > Any kind of feedback is more than welcome. > > Mariano -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 31, 2011

Re: [Pharo-project] Progress bar design pattern

by Daniel Lyons

On Thu, Mar 31, 2011 at 04:58:04PM -0300, Martin Dias wrote: > > The simplest design, IMO, would be this API: > > > > MyProgressBar>>percentComplete: aNumber > > MyProgressBar>>beIndeterminant > > MyProgressBar>>beDeterminant > > > > Sorry, what is an indeterminant progress bar? On your Mac, it's the barber pole; on Windows, it's when the progress bar just sort of throbs. It's for when you initially are calculating how long the task is going to take, or for cleanup after the task is complete. -- Daniel

March 31, 2011

[Pharo-project] [OT] Blog sequence "Journey through the VM"

by Mariano Martinez Peck

Hi folks. I will start a sequence of VM related posts called âJourney through the VMâ, similar to what Igor did in Deep Smalltalk School<http://www.inria.fr/centre-de-recherche-inria/lille-nord-europe/agenda/smal…>. My main focus is that a regular Smalltalker, without any knowledge in VM stuff can understand the basis of it (ObjectMemory, Interpreter, etc). In addition, I expect the reader can download, change, compile, run, and debug (and why not fixing?) the VM. Later on in the journey, I would also like to talk about what the compiler does, what bytecodes are, how to read them, how they are mapped to the VM, etc. I will also show some hooks or tricks that the VM provides and that are not always known. Moreover, I will explain what a primitive is, how they are executed by the VM, how you can write your own primitives, etc. FFI and writing your own plugin are also in my plans. It is important to notice that all these posts are thought for VM newbies. I would appreciate if there can be some VM hackers paying attention that I don't say stupid things. http://marianopeck.wordpress.com/ Cheers

March 31, 2011

[Pharo-project] [OT] I've started blogging

by Mariano Martinez Peck

Hi guys. Just in case someone is interested, I've have started blogging: "Sending messages through small talks" The blog is here: http://marianopeck.wordpress.com/ Any kind of feedback is more than welcome. Mariano

March 31, 2011

Re: [Pharo-project] Issue 3926 in pharo: MorphTreeMorph autoSelet

by pharo＠googlecode.com

Updates: Status: closed Comment #1 on issue 3926 by stephane...(a)gmail.com: MorphTreeMorph autoSelet http://code.google.com/p/pharo/issues/detail?id=3926 in 13124 Now ben it would be good to: add comments to the methods you know, and do not hardCode Color red.

March 31, 2011

[Pharo-project] Probably stupid but why SimpleHierarchicalListMorph inherits from ScrollPane

by StÃ©phane Ducasse

Hi guys May be I stupid but why SimpleHierarchicalListMorph inherits from ScrollPane? Is it because ScrollPane is a stuff with scrollbar and SHLMorph also? Stef

March 31, 2011

Re: [Pharo-project] Issue 3928 in pharo: Add reciprocalModulo: support in Kernel

by pharo＠googlecode.com

Updates: Status: closed Comment #4 on issue 3928 by stephane...(a)gmail.com: Add reciprocalModulo: support in Kernel http://code.google.com/p/pharo/issues/detail?id=3928 (No comment was entered for this change.)

March 31, 2011

Re: [Pharo-project] Issue 3928 in pharo: Add reciprocalModulo: support in Kernel

by pharo＠googlecode.com

Comment #3 on issue 3928 by stephane...(a)gmail.com: Add reciprocalModulo: support in Kernel http://code.google.com/p/pharo/issues/detail?id=3928 in 13124

March 31, 2011

Re: [Pharo-project] [update 1.3] #13119

by Nicolas Cellier

I presume MC is not equipped to overwrite a global variable with a class, so result may depend on load order, and maybe loadOrder is depending itself on some random hash or something... Nicolas 2011/3/31 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > Yes I got a strange message too. > but marcus never got it and hudson neither. So I gave up and took the hudosn image. > > Stef > >> Very strange, I saved the image, closed the image, restarted and it >> now behaves differently asking me to proceed to overwrite >> Transcript... >> I can then update normally... >> >> Nicolas >> >> 2011/3/31 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>> I have update 13119 failing on this MCMethodDefinition: >>> >>> classIsMeta: Â Â true >>> source: Â Â Â Â 'addEntry: aString >>> Â Â Â Â "Add a new entrie to the entries circular list. If full, a new entry >>> will replace the oldest one." >>> Â Â Â Â | msg now | >>> Â Â Â Â logToFile ifTrue: [ >>> Â Â Â Â Â Â Â Â now := DateAndTime now. >>> Â Â Â Â Â Â Â Â msg := String streamContents: [ :strm | >>> Â Â Â Â Â Â Â Â Â Â Â Â now printWithMsOn: strm. >>> Â Â Â Â Â Â Â Â Â Â Â Â strm >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: '' process:''; >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: Processor activeProcess priority printString; >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPut: $ ; >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: Processor activeProcess hash printString; >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPut: $ ; >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â nextPutAll: aString; >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â lf ]]. >>> >>> Â Â Â Â self addEntry: aString logToFile: msg' >>> category: Â Â Â #private >>> selector: Â Â Â #addEntry: >>> className: Â Â Â #Transcript >>> timeStamp: Â Â Â 'jmv 2/18/2011 12:59' >>> >>> Since Transcript is not a class (it is an instance of ThreadSafeTranscript). >>> It cannot understand classSide then DNU... >>> >>> What's up >>> >>> Nicolas >>> >>> 2011/3/31 Marcus Denker <marcus.denker(a)inria.fr>: >>>> 13119 >>>> ----- >>>> >>>> Issue 3913: Â Â Fix in PluggableListMorph hierarchy >>>> Issue 3736: Â Â new Transcript from CUIS >>>> >>>> >>>> -- >>>> Marcus Denker Â -- http://www.marcusdenker.de >>>> INRIA Lille -- Nord Europe. Team RMoD. >>>> >>>> >>>> >>> >> > > >

March 31, 2011