July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Mac like editing?

by Fernando olivero

Right now they are hardcoded here TextEditor class, category: keyboard shortcut tables For example: TextEditor class>> initializeBasicCmdKeyShortcuts Wouldn't be hard to plug a customized mapping. And then do the same in TextEditor>>dispatchOn: aKeyboardEvent You could make this changes, and later test them easily using NewTextMorph. Fernando On Jul 22, 2010, at 8:59 PM, Max Leske wrote: > I checked Squeak 4.1 basic image (Damien's server didn't let me download the SqueakDev image). There are no preferences in the preferences browser for editing shortcuts. The only shortcut I could verify was cmd + -> and cmd + <- for skipping words (I have that in my list as alt + -> and alt + <-). There seem to be a couple of other nice shortcuts (e.g. advancing to the next argument when typing a multi argument message) but I's prefer the basic shortcuts would work... > > There is an Editor class with two sub classes that has replaced a former implementation (apparently TextMorphEditor). I couldn't figure out where the shortcuts are actually defined though. > > Max > > On 22.07.2010, at 20:14, StÃ©phane Ducasse wrote: > >> I guess that they did that in squeak can you check? >> >> On Jul 22, 2010, at 8:10 PM, Max Leske wrote: >> >>> No I haven't. I'll take a look at it later on. >>> Are you planning to replace Paragraph with Editor? >>> >>> Max >>> >>> >>> On 22.07.2010, at 20:05, StÃ©phane Ducasse wrote: >>> >>>> What I want is a real way to define, plug a shortcut table. >>>> Max did you check the new Editor class. >>>> >>>> Stef >>>> >>>> >>>>> Hi everyone. >>>>> >>>>> I have no idea what the status is on the editor in pharo and if there are any plans to do something to / with it. If there's some resource, could you point me to it? >>>>> In the meantime I thought I'd share my impressions with you; doesn't hurt at least. >>>>> >>>>> Since I started developing in Pharo I've struggled with the editor, in particular with the fact that I need to use the mouse a lot to position the cursor which, as all of you know, makes development quite a bit slower. >>>>> Before I came to Pharo I used to develop in Eclipse and Eclipse supports all shortcuts used inside OS X (and if not you can change the shortcut settings). My favorite shortcuts: >>>>> â¢ cmd + -> : go to end of line >>>>> â¢ cmd + <- : go to beginning of line >>>>> â¢ alt + -> : go to end of the current word >>>>> â¢ alt + -> : go to beginning of current word >>>>> â¢ alt + arrow up : switch the line above with the current line (current line has line number -1, line above has line number +1) >>>>> â¢ alt + arrow down : switch the line below with the current line >>>>> â¢ cmd + l : delete line (I know this shortcut is used to cancel changes at the moment. Still, I haven't found a shortcut yet that deletes a single line) >>>>> >>>>> I'd LOVE to see this in Pharo, or at least be able to configure the shortcuts myself. I think, being able to change the shortcuts is important anyway because each developer has an own style. >>>>> I'd try to come up with a solution myself but I just don't have the time at the moment. >>>>> >>>>> Thanks for listening to my yapping :) >>>>> >>>>> Max >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2010

[Pharo-project] Another RB engine change

by Fernando olivero

Hi Lukas, here is another change in the RB engine package. RBClass>>realName: aSymbol self realClass: (Smalltalk at: aSymbol) => self realClass: (Smalltalk globals at: aSymbol) Fernando

July 22, 2010

Re: [Pharo-project] Time Machine

by StÃ©phane Ducasse

http://www.st.cs.uni-saarland.de/dd/ you can get some papers but also the slides that go with the book Stef On Jul 22, 2010, at 11:36 PM, laurent laffont wrote: > > On Thu, Jul 22, 2010 at 11:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > did you read delta debugging from andreas Zeller? > > No. Where ? > > Laurent > > > > Stef > > On Jul 22, 2010, at 11:11 PM, laurent laffont wrote: > > > Hi, > > > > From a discussion I had with Kent Beck about Continuous Testing / Autotest (see http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), I would like to add a kind of Time Machine for Smalltalk code in Autotest. > > > > When a test fails, what I really want to know is why. Sometimes a test fails and I don't know why. So I have to go through a debugging session which distracts me from what I've been coding. > > > > So an idea is to diff backtrace before and after the test fails: > > - revert to last green > > - replay the test and save the trace > > - forward to current test and run (test fails) > > - compare execution paths in order to see the consequence of last change > > > > How would you do this ? Where should I look for materials which can help me coding this ? > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2010

Re: [Pharo-project] State of Sound in Morph

by StÃ©phane Ducasse

On Jul 22, 2010, at 10:14 PM, Hilaire Fernandes wrote: > Le 22/07/2010 21:11, Hilaire Fernandes a Ã©crit : >> Le 22/07/2010 20:53, StÃ©phane Ducasse a Ã©crit : >> >>>> >>>> Of course I took your latest commit. Do this latest commit include the >>>> patches Stephane mentioned? >>> >>> no I guess not. >>> Hilaire if you can have a look at the bugtracker and harvest the fixes into sound >>> it would be great. >> >> Sure > > The proposed pathes are not related to the problem. > I replace the clone by a copy, it helps but I don't know the eventual > side effects. clone was a shallow copy and we replaced it by shallowCopy, copy copy ^ self shallowCopy postCopy We removed clone from pharo because tired to have three times the same half way done. because only some parts of the system used clone and other shallow > > Hilaire > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2010

Re: [Pharo-project] State of Sound in Morph

by Levente Uzonyi

On Thu, 22 Jul 2010, Hilaire Fernandes wrote: > Le 22/07/2010 21:11, Hilaire Fernandes a Ã©crit : >> Le 22/07/2010 20:53, StÃ©phane Ducasse a Ã©crit : >> >>>> >>>> Of course I took your latest commit. Do this latest commit include the >>>> patches Stephane mentioned? >>> >>> no I guess not. >>> Hilaire if you can have a look at the bugtracker and harvest the fixes into sound >>> it would be great. >> >> Sure > > The proposed pathes are not related to the problem. > I replace the clone by a copy, it helps but I don't know the eventual > side effects. Why don't you use #shallowCopy? #clone and #shallowCopy do the same, but #clone is primitive only, while #shallowCopy has fallback code written in Smalltalk. Levente > > Hilaire > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 22, 2010

Re: [Pharo-project] Time Machine

by laurent laffont

On Thu, Jul 22, 2010 at 11:34 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > did you read delta debugging from andreas Zeller? > No. Where ? Laurent > > Stef > > On Jul 22, 2010, at 11:11 PM, laurent laffont wrote: > > > Hi, > > > > From a discussion I had with Kent Beck about Continuous Testing / > Autotest (see > http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), > I would like to add a kind of Time Machine for Smalltalk code in Autotest. > > > > When a test fails, what I really want to know is why. Sometimes a test > fails and I don't know why. So I have to go through a debugging session > which distracts me from what I've been coding. > > > > So an idea is to diff backtrace before and after the test fails: > > - revert to last green > > - replay the test and save the trace > > - forward to current test and run (test fails) > > - compare execution paths in order to see the consequence of last change > > > > How would you do this ? Where should I look for materials which can help > me coding this ? > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 22, 2010

Re: [Pharo-project] Time Machine

by StÃ©phane Ducasse

did you read delta debugging from andreas Zeller? Stef On Jul 22, 2010, at 11:11 PM, laurent laffont wrote: > Hi, > > From a discussion I had with Kent Beck about Continuous Testing / Autotest (see http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), I would like to add a kind of Time Machine for Smalltalk code in Autotest. > > When a test fails, what I really want to know is why. Sometimes a test fails and I don't know why. So I have to go through a debugging session which distracts me from what I've been coding. > > So an idea is to diff backtrace before and after the test fails: > - revert to last green > - replay the test and save the trace > - forward to current test and run (test fails) > - compare execution paths in order to see the consequence of last change > > How would you do this ? Where should I look for materials which can help me coding this ? > > Cheers, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 22, 2010

Re: [Pharo-project] Time Machine

by Alexandre Bergel

> - compare execution paths in order to see the consequence of last change Not easy to get. But yes, this is what the whole world wants :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 22, 2010

Re: [Pharo-project] Time Machine

by StÃ©phane Ducasse

sound cool. looks like a research topic on it own. > When a test fails, what I really want to know is why. Sometimes a test fails and I don't know why. So I have to go through a debugging session which distracts me from what I've been coding. > > So an idea is to diff backtrace before and after the test fails: > - revert to last green > - replay the test and save the trace > - forward to current test and run (test fails) > - compare execution paths in order to see the consequence of last change > > How would you do this ? Where should I look for materials which can help me coding this ? I would use MethodWrapper or the like (may be byetsurgeon when available) and you can also have a look at dynamix (a famix extension in the Phd of orla greevy) to model trace. then you keep track of what changed using a changeset and revert. Stef

July 22, 2010

[Pharo-project] Time Machine

by laurent laffont

Hi, >From a discussion I had with Kent Beck about Continuous Testing / Autotest (see http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), I would like to add a kind of Time Machine for Smalltalk code in Autotest. When a test fails, what I really want to know is why. Sometimes a test fails and I don't know why. So I have to go through a debugging session which distracts me from what I've been coding. So an idea is to diff backtrace before and after the test fails: - revert to last green - replay the test and save the trace - forward to current test and run (test fails) - compare execution paths in order to see the consequence of last change How would you do this ? Where should I look for materials which can help me coding this ? Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

July 22, 2010