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

[Pharo-project] Personalized systems with Treated
by Chris Muller May 5, 2011

May 5, 2011

To support Magma 1.2, I introduced some changes to OrderedCollection into the Squeak trunk some time ago. To deliver Magma to Pharo users, I needed to have these same enhancements in Pharo 1.1 and 1.2. But they were already released, so how was this solved? My first instinct was to deliver a change-set; the classical way to modify the system. But I know dirty packages are unattractive, and besides that the only way to achieve one-click load of something involving a change-set + MC-packages in Pharo is with a SAR - overkill since Magma is just MC packages; no resources. I really wanted to release Magma 1.2 to Pharo with just a Gofer script. So, I decided to import the same changes I made to Squeak's OrderedCollection into Pharo's and then save that new version to the Inbox and adjusted my Gofer script for loading Magma to merge that version of Collections from repositories: Pharo, Inbox, TreatedInbox. I knew they would accept it, thank you Pharo, BUT it's nice to know that I could actually deliver my application without having to wait for it to be integrated, or worry even if it didn't get accepted; that chain of repositories should work immediately and forever, no matter the outcome of acceptance. Thanks to MC merging, this is as unintrusive as it can be; in case someone runs with their own "personalizations" to the Collections package, loading Magma won't clobber them; nor will updating with official Pharo-released patches, because those are merged too. With the context of this experience, I came to view the "Treated" repository with a new respect; enabling a non-core developer to personalize system packages for my application.. - Chris

4 7

[Pharo-project] [COTDC] 59 - HierarchicalURI
by laurent laffont May 5, 2011

May 5, 2011

Today: HierarchicalURI Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

2 2

[Pharo-project] Just starting out
by Torsten Bergmann May 5, 2011

May 5, 2011

http://omasko.wordpress.com/2011/05/02/just-starting-out "Ultimately, we ended up in Pharo, an environment I havenât really had the opportunity to spend much time with. After some bad experiences with Squeak a few years ago, Iâve tended to stick with the old standards, but I was pleasantly surprised with the current state of Pharo, and given that much of the current innovation in the Smalltalk world is coming from Pharo, itâs not a bad place to start a newcomer." -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

9 11

[Pharo-project] [COTDC] 58 - TextPrinter
by laurent laffont May 4, 2011

May 4, 2011

Today: TextPrinter Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

2 2

[Pharo-project] [update 1.3] #13182
by laurent laffont May 4, 2011

May 4, 2011

13182 ----- COTDC integration - 49 - ClassFactoryWithOrganization - A.Bergel - 50 - LongTestCase (fix waiting for review - issue #4132) - L.Laffont - 51 - TestCaseAnnouncement, TestCaseStarted, TestCaseEnded - A.Bergel - 52 - PCXReadWriter (deprecated) - G.Polito - 53 - AnimatedGIFReadWriter - L.Laffont - 54 - BMPReadWriter - L.Laffont - 55 - IdentityGlyphMap (removed) - L.Laffont - 56 - HostFont (removed) - C.Cunningham - 57 - ColorMap - F.Olivero - 58 - TextPrinter (deprecated) Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

2 1

Re: [Pharo-project] [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style persistence....
by laurent laffont May 4, 2011

May 4, 2011

On Wed, May 4, 2011 at 7:00 PM, Ramon Leon <ramon.leon(a)gmail.com> wrote: > My general approach would be this sequence of steps, let's assume his > class is called Person in collection var name people. > > If Person has an initialize method, rename it to initializeOld. > Change superclass of Person to SDActiveRecord. > Person warmUp. to setup the store for this new class. > people do: [:e | e initialize ] to invoke active records initialize > setting up it's necessary inst vars and marking all people as new > rename Person>>initializeOld back to Person>>initialize. > people do: [:e | e save ] > > Migration complete. > > Thanks a lot Ramon, I add this to Pharocasts. Laurent > -- > Ramon Leon > http://onsmalltalk.com > > > On Wed, May 4, 2011 at 4:58 AM, laurent laffont > <laurent.laffont(a)gmail.com> wrote: > > > > Someone knows ? > > Laurent > > > > > > ---------- Forwarded message ---------- > > From: Bernat Romagosa <noreply-comment(a)blogger.com> > > Date: Wed, May 4, 2011 at 1:37 PM > > Subject: [Pharocasts] New comment on SandstoneDb, simple ActiveRecord > style > > persistence.... > > To: laurent.laffont(a)gmail.com > > > > > > Bernat Romagosa has left a new comment on your post "SandstoneDb, simple > > ActiveRecord style persistence...": > > > > I was trying to migrate a simple image-based persistence app into > Sandstone, > > so I just recompiled my biz objects to be subclasses of SDActiveRecord, > but > > of course the objects I want to save are already created and "floating" > in > > the image, so when I try to save them I get an error as many instvars > > haven't been initialized upon creating these objects (as they were > already > > there). > > > > Is there a way to automatically do this? > > > > Thanks! > > > > Bernat. > > > > > > > > Posted by Bernat Romagosa to Pharocasts at May 4, 2011 4:37 AM > > >

2 1

[Pharo-project] [ANN] PHANtom: A modern Aspect Language for Pharo
by Lemuus May 4, 2011

May 4, 2011

Hello all, We are happy to announce the release of PHANtom: a modern aspect language for Pharo. PHANtom was built taking into account recent advances in aspect language features such as dynamic advice rescheduling, reentrancy management, and scoping strategies for deployment. The advanced features are not all implemented yet, but the 'normal' features work and are well-tested (about 130 unit tests) so we are relasing it to the world for you to try out. We hope PHANtom can help you to solve some cross-cutting code problems. An overview of the language can be found at http://pleiad.cl/PHANtom Please try it out, see if it works for you, all your comments are welcome! More details: I am doing this as my engineering thesis, under the guidance of Prof. Johan Fabry. PHANtom works in Pharo 1.2.1 and in 1.3, and also in PharoCore. Right now, PHANtom uses Method Wrappers in its' implementation, just like the AspectS language did. But the plan is once we have all features implemented, that we will start compiling using the Opal compiler of Pharo, to make everything go faster. I just put one example from the website here so you can see what it looks like: asp := PhAspect new add: (PhAdvice new pointcut: (PhPointcut new receivers: 'SystemWindow+'; selectors: 'position:'; context: #(#receiver #arguments)); advice: [:context | Transcript show: context receiver. Transcript show: ' moved to: '. Transcript show: context arguments; cr.]; type: #after). asp install. Note: the unit tests of pointcuts take a large amount of time to execute, as some of them match on everything in the image. For more info and how to download PHANtom see http://pleiad.cl/PHANtom

3 3

[Pharo-project] right click on PluggableTreeMorph doesn't select
by Guillermo Polito May 4, 2011

May 4, 2011

Hi! Let's say I have a PluggableTreeMorph with some options(a,b and c). Each option may show a menu when I do a right click. Buuut, If I have selected item a, and do a right clic on c, the menu shown is for a, not for c :(. I expect the right click to work on the item the click is done, not in the selected one :(. Is there a way to have this tree morph working as I want? Thanks in advance! Guille

1 1

[Pharo-project] PharoCore 1.3 built stalled
by laurent laffont May 4, 2011

May 4, 2011

Last built started more than 1 day ago and not finished .... Laurent.

5 12

Re: [Pharo-project] Pharocast ContactManager using SandstoneDb
by laurent laffont May 4, 2011

May 4, 2011

On Tue, May 3, 2011 at 10:09 PM, Doug Edmunds <dougedmunds(a)gmail.com> wrote: > Hello, > > I took the ContactManager code from your Pharocast at > http://www.pharocasts.com/2011/02/pharo-gui-with-polymorph.html > and modified it to run with SandstoneDb, using the ideas from > > http://www.pharocasts.com/2010/04/sandstonedb-simple-activerecord-style.html > > Go ahead and use it for a future Pharocast if you want, or figure out > some place to put it. > > Because Contact is an SDActiveRecord, the database is constructed from > the SandstoneDb records: > > Contacts class >>database > |db| > db := Contact findAll asOrderedCollection. > ^ db > > and so it is portable, so long as the Contacts records are put in the > correctly named Pharo subdirectory. > > > Opening the ContactListEditor uses an initialization which is supposed > to avoid the need to close/reopen Pharo after creating the Contacts class. > > Tested on Pharo 1.3 using SandstoneDb-RamonLeon.135.mcz > > Thanks a lot Doug. May be the next step would be to create a ConfigurationOfContactManager :) Laurent > > -- Doug Edmunds >

4 3