kicad-developers team mailing list archive

[Stefano Rossi <chimera.stefano@xxxxxxxxx>]

I concur with Chris. From my experience, status windows are just there for
when you are interested in some output, maybe to debug your scripts but log
files could serve that purpose. It does make sense to show it along a
command input window or messages from a DRC check.

Scripts should run in UI mode and not command line, get user inputs and
then generate the wanted output.

Just my two cents.
On Oct 24, 2015 10:46 AM, "Chris Pavlina" <pavlina.chris@xxxxxxxxx> wrote:

> On Sat, Oct 24, 2015 at 04:34:47PM +0200, jp charras wrote:
> > [[snip]]
> > This window is needed to show messages from python scripts, because
> > all
> > python scripts print info messages for users, and error messages about
> > erroneous parameters.
>
> There really should be another way to handle this. Users don't seed
> "Python scripts", they see "footprint wizards", and having to read console
> output is just going to scare them off. Scripts meant to be of a high
> enough quality to distribute should have a proper IO mechanism for
> interacting with the user without dumping to a console.
>
> It would be unacceptable for kicad proper to display error messages by
> fprintf'ing them to stderr, why is it acceptable for the bits written in
> Python?
>
>
> --
> Chris
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>