- Pharo-dev - lists.pharo.org

[Pharo-project] Making cr to autocomplete as well as tab (in Pharo 1.3)
by Igor Stasenko May 6, 2011

May 6, 2011

Hi, i just found inconvenient that for autocompletion i should press tab all the time while i tend to always hit enter, which instead of pasting suggestion, inserts cr into text. So i hacked a lil piece of code to make autocompletion to insert suggested text when you pressing either tab or cr -- Best regards, Igor Stasenko AKA sig.

11 17

[Pharo-project] Preferred way of removing slice from Inbox
by laurent laffont May 6, 2011

May 6, 2011

Hi, Once a SLICE is integrated in PharoCore, how do you remove it from PharoInbox ? Laurent

3 4

[Pharo-project] Popularity of Smalltalk in Software Industry
by sourav roy May 5, 2011

May 5, 2011

Hi All,I have just started my career in Software/IT industry and got into a project which involes enhancement/maintainance of product built in Smalltalk.I was never exposed to this language before and have no idea if it is used in the Industry as popularly as JAVA and .NET and looks like its a DEADlanguage for the industry. I may be wrong but i need some clarification about it. I just want to know that why smalltalk is not so popular as the other OOPs Languages and what is the future prospect of one if he/she is into Smalltalk development.Looking for some positive note so that it may give me some entho for working with Smalltalk. Thanks&Regards, Sourav RoyGet Yourself a cool, short @in.com Email ID now!

12 13

[Pharo-project] [update 1.3] #13183
by laurent laffont May 5, 2011

May 5, 2011

13183 ----- Issue #4132: - LongTest are run by default (so they will be run by Hudson) - Add a setting in System / Run Long Test to enable / disable them - Comment Laurent

2 2

[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