June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 30181 Kernel package Dirty

by Marcus Denker

On Jun 6, 2013, at 7:22 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > 1. Download a fresh 30181 > 2. In MC Browser, view "Changes" on Kernel > > The package will show a handful of changes and be marked dirty > When I do it , it does not find any changes. Marcus

June 7, 2013

Re: [Pharo-dev] Problem with setting class comments

by Marcus Denker

On Jun 6, 2013, at 5:54 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. > > I think I found a problem with class comments. The default method #classComment: in TClassAndTraitDescription does the following: > > classComment: aString > "Store the comment, aString or Text or RemoteString, associated with the class we are orgainzing. Empty string gets stored only if had a non-empty one before." > ^ self classComment: aString stamp: '<historical>' > > Why it puts a '<historical>' stamp instead of say "Author changeStamp" ? > > Nautilus uses this message. So as a consequence, when you edit and save a class comment with Nautilus, to get a <historical> stamp.... > > I am using Pharo 2.0. > > Bug? > Yes! Marcus

June 7, 2013

Re: [Pharo-dev] Necessity of TDD with Smalltalk

by Paul Davidowitz

Thanks all for the feedback. TDD is for me! - Paul

June 6, 2013

Global initialization for new inst vars

by Sean P. DeNigris

From https://pharo.fogbugz.com/f/cases/10856/Global-initialization-for-new-inst-… : > When adding an instance variable which should be given a default value > e.g. in #initialize, you have a problem if there are existing instances of > the class. Instead of the proper default, they will have a nil value. Also > (although less importantly), you have to stop what you're doing to add the > statement to #initialize. In the mean time, I started implementing it in Pharo 2.0 and ran into a little issue... If you: 1. Load the changeset from the issue 2. Debug a method e.g. "RBAbstractCondition new doSomething" 3. Type the name of a non-existence inst var and accept 4. In the dialog, type 4, and accept the dialog The source will appear to have been accepted, but if you browse the method, the statement with the inst var name was not added. n.b. it works fine when editing in a browser instead of the debugger ----- Cheers, Sean -- View this message in context: http://forum.world.st/Global-initialization-for-new-inst-vars-tp4692042.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 6, 2013

taking a custom screenshot of a submorph

by Tudor Girba

Hi, Just in case you want to take a screenshot of a submorph, here is a description + video of how you can do it using the GTInspector: http://www.humane-assessment.com/blog/custom-morph-screenshot-with-gtinspec… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

June 6, 2013

Re: [Pharo-dev] Sunbursts are coming in Roassal

by Tudor Girba

Very cool :) Doru On Thu, Jun 6, 2013 at 10:38 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com>wrote: > Cool! :-) > > > 2013/6/6 Alexandre Bergel <alexandre.bergel(a)me.com> > >> Hi! >> >> Milton, an excellent engineer from Object Profile, just produced the >> following: >> >> >> Sunburst is a visualization particular efficient at visualizing >> hierarchical domain. >> It naturally uses Athens. >> >> We will show more at esug :-) >> >> Milton & Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

June 6, 2013

Re: [Pharo-dev] Sunbursts are coming in Roassal

by Juraj Kubelka

Cool! :-) 2013/6/6 Alexandre Bergel <alexandre.bergel(a)me.com> > Hi! > > Milton, an excellent engineer from Object Profile, just produced the > following: > > > Sunburst is a visualization particular efficient at visualizing > hierarchical domain. > It naturally uses Athens. > > We will show more at esug :-) > > Milton & Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

June 6, 2013

Re: [Pharo-dev] Adding a statement programmatically

by Sean P. DeNigris

Norbert Hartl wrote > method := (AbstractSound>>#initialize) parseTree. > method body addNode: (RBParser parseExpression: 'envelopes := nil'). > method formattedCode > ... > Does not work? What do you mean by saying "same result"? It did work (one year later, lol)! My last statement was mistakenly "body formattedCode" instead of "method formattedCode" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Adding-a-statement-programmatically-tp4454447p4692030… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 6, 2013

Sunbursts are coming in Roassal

by Alexandre Bergel

Hi! Milton, an excellent engineer from Object Profile, just produced the following: Sunburst is a visualization particular efficient at visualizing hierarchical domain. It naturally uses Athens. We will show more at esug :-) Milton & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 6, 2013

Re: [Pharo-dev] [Screencast]: Pharo Smalltalk's New TxText: The Power of Clean Code

by Tudor Girba

This is elegant :) Doru On Thu, Jun 6, 2013 at 9:21 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > So cool :) > > > > something like that ? :) > > > > smalltalkCodeWithStabilo > > "self smalltalkCodeWithStabilo" > > | area seg code | > > area := RubEditingArea new > > beWrapped; > > width: 400; > > updateTextWith: (code := self someSmallSmalltalkCode). > > area addSegment: (seg := RubPlainSegmentMorph inTextArea: area > from: 3 to: code size). > > seg color: (Color yellow). > > seg borderColor: (Color orange alpha: 0.5). > > seg beSmoothCurve. > > area openInWorld > > > > Alain > > > > <stabilo-selection.png> > > > -- www.tudorgirba.com "Every thing has its own flow"

June 6, 2013