April 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Replacing all text in a code pane

by Sean P. DeNigris

stephane ducasse wrote > Then sean did you look at the new debugger model? I want to use this in 2.0, so it seems I'm stuck with the old debugger for now. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Replacing-all-text-in-a-code-pane-tp4680669p4680734.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 11, 2013

Re: [Pharo-users] Replacing all text in a code pane

by Andrei Vasile Chis

I've spent some time in the past in that part of the debugger but still can't say which approach is better. Anyway, in the new debugger you can say: aDebugger code pendingText: 'something' Cheers, Andrei On Wed, Apr 10, 2013 at 9:24 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Igor, couldn't agree more. Plus there are problems with both my > approaches... > > > Sean P. DeNigris wrote > > aDebugger getTextMorph textMorph editor selectAll. > > aDebugger getTextMorph textMorph editor zapSelectionWith: aString. > > "Works if wrapped in "sourcePane handleEdit: []", but warns that the method > has been edited elsewhere. Without the wrapping, it looks like it has > accepted, but keeps the old source (i.e. when I browse the method, the > source was not accepted). > > > Sean P. DeNigris wrote > > aDebugger getTextMorph textMorph contents: 'meaning: aString > > meaning := aString.' > > aDebugger getTextMorph textMorph editor userHasEdited > > Warns that the method has been edited elsewhere; if you click okay, it > looks > like it has accepted, but keeps the old source (i.e. when I browse the > method, the source was not accepted). > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Replacing-all-text-in-a-code-pane-tp4680669p4680679.h… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 10, 2013

Re: [Pharo-users] Replacing all text in a code pane

by stephane ducasse

Alain is rewriting textMorph so it will get better. Then sean did you look at the new debugger model? Stef On Apr 10, 2013, at 8:38 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 10 April 2013 20:08, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> I'm writing a little debugger extension and I want to replace the entire >> method source with another string. >> >> I thought of two ways: >> >> aDebugger getTextMorph textMorph editor selectAll. >> aDebugger getTextMorph textMorph editor zapSelectionWith: aString. >> >> or >> >> aDebugger getTextMorph textMorph contents: 'meaning: aString >> meaning := aString.' >> aDebugger getTextMorph textMorph editor userHasEdited >> >> They both work, but what is the best/correct way to do something like this? >> >> Thanks! >> > > + 1 i wanna know that too. > the problem with it, that the model is so diverse that you have no > clue, which object is actually > true holder (owner) of text, while others using it just for quick access. > > and also i don't like the expression length: > aDebugger getTextMorph textMorph editor userHasEdited > > (poor guy, Demeter, and his law ;) ) > it should not be like that.. (maybe we need to think about proper api there?) > > > -- > Best regards, > Igor Stasenko. >

April 10, 2013

Re: [Pharo-users] Replacing all text in a code pane

by Sean P. DeNigris

Igor, couldn't agree more. Plus there are problems with both my approaches... Sean P. DeNigris wrote > aDebugger getTextMorph textMorph editor selectAll. > aDebugger getTextMorph textMorph editor zapSelectionWith: aString. "Works if wrapped in "sourcePane handleEdit: []", but warns that the method has been edited elsewhere. Without the wrapping, it looks like it has accepted, but keeps the old source (i.e. when I browse the method, the source was not accepted). Sean P. DeNigris wrote > aDebugger getTextMorph textMorph contents: 'meaning: aString > meaning := aString.' > aDebugger getTextMorph textMorph editor userHasEdited Warns that the method has been edited elsewhere; if you click okay, it looks like it has accepted, but keeps the old source (i.e. when I browse the method, the source was not accepted). ----- Cheers, Sean -- View this message in context: http://forum.world.st/Replacing-all-text-in-a-code-pane-tp4680669p4680679.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 10, 2013

Re: [Pharo-users] Replacing all text in a code pane

by Igor Stasenko

On 10 April 2013 20:08, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm writing a little debugger extension and I want to replace the entire > method source with another string. > > I thought of two ways: > > aDebugger getTextMorph textMorph editor selectAll. > aDebugger getTextMorph textMorph editor zapSelectionWith: aString. > > or > > aDebugger getTextMorph textMorph contents: 'meaning: aString > meaning := aString.' > aDebugger getTextMorph textMorph editor userHasEdited > > They both work, but what is the best/correct way to do something like this? > > Thanks! > + 1 i wanna know that too. the problem with it, that the model is so diverse that you have no clue, which object is actually true holder (owner) of text, while others using it just for quick access. and also i don't like the expression length: aDebugger getTextMorph textMorph editor userHasEdited (poor guy, Demeter, and his law ;) ) it should not be like that.. (maybe we need to think about proper api there?) -- Best regards, Igor Stasenko.

April 10, 2013

Replacing all text in a code pane

by Sean P. DeNigris

I'm writing a little debugger extension and I want to replace the entire method source with another string. I thought of two ways: aDebugger getTextMorph textMorph editor selectAll. aDebugger getTextMorph textMorph editor zapSelectionWith: aString. or aDebugger getTextMorph textMorph contents: 'meaning: aString meaning := aString.' aDebugger getTextMorph textMorph editor userHasEdited They both work, but what is the best/correct way to do something like this? Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Replacing-all-text-in-a-code-pane-tp4680669.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 10, 2013

Re: [Pharo-users] A demo video

by DeNigris Sean

Really cool video! I'm struck by how much I take for granted things that seemed magical when I discovered Smalltalk... thanks :)

April 10, 2013

A demo video

by Esteban Lorenzano

Hi, I made a small video to show how work the âlife environmentâ we pharoers (and every smalltalker) always talk. That adictive little thing I like to call: âImmediate feedback experienceâ. You can see the video here (in the same old ugly english you all know me :) http://www.youtube.com/embed/Hu_C0ldSqrs Cheers, Esteban

April 10, 2013

Re: [Pharo-users] [Pharo 2.0] ConfigurationOfSeaside30 problems

by Robert Shiplett

CC rider : config issues are as old as commercial Smalltalk ; I keep an entire mail bin of these (separate from 'user' or 'tips' conversations.) At least this is not eclipse+CVS+Java+open-source ! I work in a very advanced commercial OOP created by MIT Lisp gurus and THAT IDE has package circularity issues that have to be addressed by developers who push beyond the pre-tested envelope. Does the issue exist for commercial PROLOG implementations with packages ? That would be amusing .... (there had been SOUL and QSOUL projects for Squeak as well as a Prolog and then Lisp for Squeak ) I would not be surprised to find packaging issues with functors in Mozart/Oz ! And I could check the Mercury dev mailing list ... (Mercury - which can gen Erlang code ! ) The Puppy Linux folks have a real challenge in getting tools into their light Linux ... but so far so good (mostly) - I say "mostly" as I cannot get the ObjectIcon IDE to run in their JWM X ... but Icon with objects could be used to address that very config issue in a maintainable, readable fashion !!! Practical computing : tasks which keep our sense of irony well-honed ;-) (even without management)CC Needed : Pre-Factoring browsers ! ;-) and please do keep smiling ... but only if the crows' feet crinkle at the edges of the temples ... On 10 April 2013 03:55, jtuchel <jtuchel(a)objektfabrik.de> wrote: > Hi Marcus, > > there's nothing anybody should have to be looking for excuses for. Pharo > 2.0 > is brand new and it takes time to make all projects loadable... > > I was just curious if I had missed something, and if not, I wanted to let > people know it doesnt't work. No accusations intended. > > Also my questions about where to load code from and how to find out which > repositories may be of interest to a newbie pharoer who is not yet into > publishing code but just take a look was intended as both a question for > help to see the trees in the forest and an inspiration for improvements on > what could be described better. Once I've found my way and am confident > enough I might help with this... > > Joachim > > > > -- > View this message in context: > http://forum.world.st/Pharo-2-0-ConfigurationOfSeaside30-problems-tp4680360… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 10, 2013

Re: [Pharo-users] [Pharo 2.0] ConfigurationOfSeaside30 problems

by stephane ducasse

> Maybe all of this is already written down somewhere and I simply need a link >> to this placeâ¦ >> > What is missing is a real Catalog of packages to be installed. > This is just missing now, no excuses. We will get it but roma was not build in a single day ;)

April 10, 2013