[Pharo-project] getting rid of these boring questions and popup
bschwab at anest.ufl.edu
Sat Sep 12 16:37:25 EDT 2009
... And selecting an item from that log highlights the offending code. The context menu for the log includes help on the violated rule.
From: pharo-project-bounces at lists.gforge.inria.fr [mailto:pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse
Sent: Saturday, September 12, 2009 2:38 PM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] getting rid of these boring questions and popup
yeap good idea.
A kind of log console.
>>> Yes, the popups should go away - far away :) A code mentor pane
>>> with lint rule violations would be greatly appreciated, but the
>>> modal messages are too much. Sometimes I want to save code that I
>>> know will generate errors, with reasons ranging from "I'll let it
>>> blow up and choose to implement it from the debugger" to "don't want
>>> to lose this, so let's get it accepted before I do something
>> same here!
>> At least we have a common vision and we can go slowly there.
> I having the same vision. Browser should not prevent you from
> accepting the badly crafted code. It should allow it unless there is
> syntax errors.
> All warnings, like unused temps, use of unassigned temps etc, should
> pop-up in a list pane below the code pane, so user could see it and
> react, or just ignore and go & do something else. Btw, this pane could
> be reused for more deeper/complex code analyzing tools, like lint etc.
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
> Best regards,
> Igor Stasenko AKA sig.
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev