- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Boring confirmation message...

by Schwab,Wilhelm K

Alexandre, There is a preference for confirm on close or something like that - I think. Your test for change in value is an interesting idea, but I am often willing/expecting to toss whatever I type into an inspector. I very much want the system to warn me if I am about to discard code in the debugger or browser source pane, and certainly in workspaces. Bill ---- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre Bergel [Alexandre.Bergel(a)inria.fr] Sent: Saturday, February 14, 2009 2:09 PM To: Pharo Development Subject: [Pharo-project] Boring confirmation message... Hi All, Often, I do a print-it in a debugger or browser. For some mysterious reason, I subsequently press the delete key that erases what was just print. Some changes occurred therefore. When I then select another method (or frame if I am in a debugger), a confirmation whether I want to save my changes is done. I find this very boring. Am i the only one ? A simple check whether the textual content has been modified would prevent this stupid question. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 14, 2009

[Pharo-project] Boring confirmation message...

by Alexandre Bergel

Hi All, Often, I do a print-it in a debugger or browser. For some mysterious reason, I subsequently press the delete key that erases what was just print. Some changes occurred therefore. When I then select another method (or frame if I am in a debugger), a confirmation whether I want to save my changes is done. I find this very boring. Am i the only one ? A simple check whether the textual content has been modified would prevent this stupid question. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 14, 2009

Re: [Pharo-project] Debugging with morphic

by Gary Chambers

More often than not the emergency evaluator can save you from having to reload changes... Otherwise, save often after careful consideration and before likely dangerous changes. Not a huge hassle to relaunch and load the last changes either though. Regards, Gary ----- Original Message ----- From: "Alexandre Bergel" <alexandre(a)bergel.eu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, February 14, 2009 6:29 PM Subject: Re: [Pharo-project] Debugging with morphic >I was just wondering how you guys debug your morphic programming. > There is probably something wrong in the way I do. I cannot imagine > people have been doing some morphic for so long without having a > simple way to debug it. > > Cheers, > Alexandre > > > On 14 Feb 2009, at 18:26, Gary Chambers wrote: > >> I'm sure I can come up with something... you obvioulsy want some >> kind of >> debugger if an error occurs. >> The taskbar works effectively synchronously with the display and >> should >> handle self inflicted errors. >> Other display errors *should* get managed by the #errorOnDraw thing, >> but not >> always it would seem. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Alexandre Bergel" <Alexandre.Bergel(a)inria.fr> >> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Saturday, February 14, 2009 4:53 PM >> Subject: [Pharo-project] Debugging with morphic >> >> >>> Hi All (and especially the Pinesoft crew), >>> >>> When an error is triggered by a displayOn: method, the bottom bar is >>> being filled with debugger windows. It then become hardly debuggable. >>> Ideally, the system should not display a window if an error is >>> triggered in the displayOn. >>> >>> Do you have any recommandation/conviention/enhancement to prevent the >>> image to hang when an error is signaled in a displayOn. This is >>> really >>> annoying. >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 14, 2009

Re: [Pharo-project] Sends unknown message to global

by Gary Chambers

Thanks. Spotted and refactored. Regards, Gary ----- Original Message ----- From: "Lukas Renggli" <renggli(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, February 14, 2009 5:55 PM Subject: Re: [Pharo-project] Sends unknown message to global >> I do not know >> It would be good if lukas could improve the quality of the report of >> SmallLint. > > If you select the rule and click on browse, it lists all the > occurences and also highlights the offending code. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 14, 2009

Re: [Pharo-project] Debugging with morphic

by Alexandre Bergel

I was just wondering how you guys debug your morphic programming. There is probably something wrong in the way I do. I cannot imagine people have been doing some morphic for so long without having a simple way to debug it. Cheers, Alexandre On 14 Feb 2009, at 18:26, Gary Chambers wrote: > I'm sure I can come up with something... you obvioulsy want some > kind of > debugger if an error occurs. > The taskbar works effectively synchronously with the display and > should > handle self inflicted errors. > Other display errors *should* get managed by the #errorOnDraw thing, > but not > always it would seem. > > Regards, Gary > > ----- Original Message ----- > From: "Alexandre Bergel" <Alexandre.Bergel(a)inria.fr> > To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, February 14, 2009 4:53 PM > Subject: [Pharo-project] Debugging with morphic > > >> Hi All (and especially the Pinesoft crew), >> >> When an error is triggered by a displayOn: method, the bottom bar is >> being filled with debugger windows. It then become hardly debuggable. >> Ideally, the system should not display a window if an error is >> triggered in the displayOn. >> >> Do you have any recommandation/conviention/enhancement to prevent the >> image to hang when an error is signaled in a displayOn. This is >> really >> annoying. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 14, 2009

Re: [Pharo-project] Fwd: A question about hardcoded class names

by Lukas Renggli

The class CUCastingExample in the following Pharo image <http://scg.unibe.ch/Research/DSL/diesel-languageaspects.zip> contains some language experiments along these lines. For example the keyword "this" starts the lookup of in the class the method is defined in. Similar receivers of message sends can be casted to any superclass using #cast:. Lukas On Sat, Feb 14, 2009 at 6:43 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > 2009/2/14 Keith Hodges <keith_hodges(a)yahoo.co.uk>: >> StÃ©phane Ducasse wrote: >>> Hi guys >>> >>> some days ago with alex we wanted to identify the methods containing a >>> reference to their class (Lint does it too). >>> Now we thought that replacing them with self class is not equivalent >>> since we could imagine >>> >> st/x uses >> >> here class >>> that hardcoding the class name make sure that subclass cannot redefine >>> methods. >>> Now this is a bit against Smalltalk late bindinness and probably most >>> of the time an newbie error. >>> >> I doubt it. >> >> isAbstract >> >> self class = here class. >> > If i understood, st/x > > here class > > is equivalent to squeak > > thisContext method methodClass > > right? > >> Keith >>> But I wanted to know what was your experiment to that regards. >>> >>> Stef >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 14, 2009

Re: [Pharo-project] [ANN] 10234 SmallLint cleaning

by Igor Stasenko

2009/2/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > addressed or tagged as addressed > > Issue 523: [SmallLint] Undeclared variables > This check is similar to the "References an undeclared variable" > check, but it looks for variables that > are not defined in the class or in the undeclared dictionary. You > probably had to work hard to get > your code in this state. > > PasteUpMorph>>#makeNewDrawing:at: > Project>>#storeSegmentNoFile not sure about the rest methods, but these two showing that people worked hard to get code in this state. or maybe its my brain is too small to fit such amount of code in attempt to understand it. > CollectionRootTest>>#nonEmpty > ScriptLoader>>#update10196 > ScriptLoader>>#update10074 > > Issue 525: useless boolean checks on Morphic extras > MorphicExtras Check for a =, ==, ~=, or ~~ message being sent to true/ > false or with true/false as the argument. > SqueakPage>>#write > URLMorph>>#mouseUp: > ClockMorph>>#addCustomMenuItems:hand: > ClockMorph>>#step > ClockMorph>>#toggleShowingSeconds > ClockMorph>>#toggleShowing24hr > MorphObjectOut>>#doesNotUnderstand: > SketchEditorMorph>>#verifyState: > SketchEditorMorph>>#deliverPainting:evt: > FlapTab>>#inboard > FlapTab>>#flapShowing > FlapTab>>#tabSelected > ReferenceMorph>>#isHighlighted > SimpleSliderMorph>>#truncate > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Feb. 14, 2009

Re: [Pharo-project] Sends unknown message to global

by Lukas Renggli

> I do not know > It would be good if lukas could improve the quality of the report of > SmallLint. If you select the rule and click on browse, it lists all the occurences and also highlights the offending code. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 14, 2009

Re: [Pharo-project] Sends unknown message to global

by StÃ©phane Ducasse

I do not know It would be good if lukas could improve the quality of the report of SmallLint. Sometimes I have to think to spot the problem stef On Feb 14, 2009, at 5:31 PM, Gary Chambers wrote: > What is the unknown message for > UITheme..#newColorPresenterIn:for:getColor:setColor:help: > ? Looks ok here. > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, February 14, 2009 1:23 PM > Subject: [Pharo-project] Sends unknown message to global > > >> same here: would be good to define bugfix entries for each of them. >> >> Stef >> >> TTSampleStringMorph>>#initializeToStandAlone >> Character>>#storeBinaryOn: >> EFontBDFFontReaderForRanges >>>> #override:with:ranges:transcodingTable:additionalRange: >> InstallerMonticello>>#unloadCleanUp >> ServerDirectory>>#createDirectory: >> ServerDirectory>>#deleteDirectory: >> CompiledMethod>>#searchImageForHomeMethod >> SMSimpleInstaller>>#fileIntoChangeSetNamed:fromStream: >> UITheme>>#newColorPresenterIn:for:getColor:setColor:help: >> SystemDictionary>>#unbindExternalPrimitives >> UIMonticello>>#installFileNamed:fromURL: >> TabSorterMorph>>#acceptSort >> MCPackageLoader>>#useChangeSetNamed:during: >> InstallerFile>>#basicView >> InstallerFile>>#basicBrowse >> URI>>#mimeType >> StrikeFont>>#readEFontBDFFromFile:name:rangeFrom:to: >> StrikeFont>>#readEFontBDFForJapaneseFromFile:name:overrideWith: >> StrikeFont>>#readEFontBDFForKoreanFromFile:name:overrideWith: >> StrikeFont>>#readEFontBDFFromFile:name:ranges: >> Morph>>#showActions >> OBTreeFanTests>>#makeTreeFanStructure >> MczInstaller>>#useNewChangeSetDuring: >> TranslatedReceiverFinder class>>#makeJapaneseTranslationFile >> SARInstaller class>>#newChanges: >> SARInstaller class>>#currentChangeSet >> Transcripter class>>#startTranscriptProcess >> RxParser class>>#doHandlingMessageNotUnderstood: >> NaturalLanguageTranslator class>>#default >> Utilities class>>#authorNamePerSe >> >> >> _______________________________________________ >> 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 >

Feb. 14, 2009

[Pharo-project] [ANN] 10234 SmallLint cleaning

by StÃ©phane Ducasse

addressed or tagged as addressed Issue 523: [SmallLint] Undeclared variables This check is similar to the "References an undeclared variable" check, but it looks for variables that are not defined in the class or in the undeclared dictionary. You probably had to work hard to get your code in this state. PasteUpMorph>>#makeNewDrawing:at: Project>>#storeSegmentNoFile CollectionRootTest>>#nonEmpty ScriptLoader>>#update10196 ScriptLoader>>#update10074 Issue 525: useless boolean checks on Morphic extras MorphicExtras Check for a =, ==, ~=, or ~~ message being sent to true/ false or with true/false as the argument. SqueakPage>>#write URLMorph>>#mouseUp: ClockMorph>>#addCustomMenuItems:hand: ClockMorph>>#step ClockMorph>>#toggleShowingSeconds ClockMorph>>#toggleShowing24hr MorphObjectOut>>#doesNotUnderstand: SketchEditorMorph>>#verifyState: SketchEditorMorph>>#deliverPainting:evt: FlapTab>>#inboard FlapTab>>#flapShowing FlapTab>>#tabSelected ReferenceMorph>>#isHighlighted SimpleSliderMorph>>#truncate

Feb. 14, 2009