2009/3/5 Michael van der Gulik <[email protected]>:
>
>
> On Wed, Mar 4, 2009 at 9:51 PM, Jorge Ressia <[email protected]> wrote:
>
>>
>> 3.- Error messages: at least like in the old compiler.
>
>
> I would like to see a different way of editing code: any modifications in a
> code pane are assumed to be unsaved changes to the source code. This means
> that things like "Print it" and error messages should go to a separate text
> pane on the UI somewhere - maybe a pop-up at the location of the error, or
> in a status bar, or maybe a separate list of errors/warnings like other IDEs
> do???
>
> I haven't looked at the code for reporting error messages, but I'm assuming
> (and hoping) that the compiler just reports an error message and a character
> index, and the "presentation layer" does the notification?
>

I prefer a status line (or more complex morph) which appears at the
bottom of text area - there can be shown an error message ,  as well
as 'accept/cancel' buttons. We also could make it appear only if
source has changed.

> Gulik.
>
> --
> http://gulik.pbwiki.com/
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



-- 
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to