[Eric] running python-dialog scripts

[Detlev Offenbach]

On Samstag, 14. Februar 2009, Christof Hanke wrote:
> Ok, thanks for the explanation.
> Then, the only point I have, how to make the solution clear to other users,
> who might stumble on this problem ?
> In KDE the option is actually hidden behind a button "Options".
> So doing something like this would not necessarily clobber the interface.

That could be the solution. I'll add it to the wishlist.

>
>
> ________________________________________
> From: Detlev Offenbach [detlev at die-offenbachs.de]
> Sent: Saturday, February 14, 2009 1:48 PM
> To: Christof Hanke
> Subject: Re: [Eric] running python-dialog scripts
>
> On Samstag, 14. Februar 2009, Christof Hanke wrote:
> > Hi Detlev,
> >
> > no, I'm perfectly happy with eric as it is now.
> > I now know how to run python-dialog scripts in an external terminal using
> > the debugger. So that is fine for me.
> > I just wanted to suggest to have this option of external terminal in a
> > more obvious place. Compare it to e.g. pressing ALT+F2 in KDE, I have an
> > option to run this specific command in a separate terminal. Something
> > like this, if this does not fit into the codepath of eric or you think it
> > is not of general interest, just forget it.
>
> It could be done. That is not the problem. The problem actually is, that I
> don't want to clobber the interface. In eric4 the user would be required to
> enter the konsole command (e.g. konsole) to be used (like in the
> configuration dialog). That is neccessary because eric4 is platform
> neutral. KDE does have a much easier job because checking this option means
> "Run with konsole".
>
> > Thanks,
> >
> > Christof
> >
> > ________________________________________
> > From: Detlev Offenbach [detlev at die-offenbachs.de]
> > Sent: Saturday, February 14, 2009 1:22 PM
> > To: Christof Hanke
> > Subject: Re: [Eric] running python-dialog scripts
> >
> > Hi Christof,
> >
> > now I understand what you mean. However, if that feature is of general
> > interest or a specific requirement to solve your problem. Do you often
> > start scripts, that need an individual configuration? Maybe you will
> > describe the circumstances a bit more for me to understand. Maybe eric
> > already offers a solution that is just not that obvious.
> >
> > Regards,
> > Detlev
> >
> > On Samstag, 14. Februar 2009, Christof Hanke wrote:
> > > Hi Detlev,
> > >
> > > I just meant it would be nice to have the option of using an external
> > > terminal in the "run script" dialog.
> > > Not sure if that fits into the internal design of eric.
> > >
> > > Thanks,
> > >
> > > Christof
> > > ________________________________________
> > > From: Detlev Offenbach [detlev at die-offenbachs.de]
> > > Sent: Friday, February 13, 2009 7:17 PM
> > > To: Christof Hanke
> > > Subject: Re: [Eric] running python-dialog scripts
> > >
> > > On Mittwoch, 11. Februar 2009, Christof Hanke wrote:
> > > > Hi,
> > > >
> > > > sorry for the late reply. Yes, it works fine with the external
> > > > terminal and the debugger. Is it possible to have this kind of option
> > > > for running a script ?
> > >
> > > ???
> > >
> > > There is no difference. It is just an internal thing. The backend is
> > > always started. It is just a different code path, that gets executed
> > > depending on the selected action (run, debug, profiling, ...).
> > >
> > > Detlev
> > >
> > > > Thanks,
> > > >
> > > > Christof
> > > > ________________________________________
> > > > From: Detlev Offenbach [detlev at die-offenbachs.de]
> > > > Sent: Saturday, February 07, 2009 2:33 PM
> > > > To: eric at riverbankcomputing.com
> > > > Cc: Christof Hanke
> > > > Subject: Re: [Eric] running python-dialog scripts
> > > >
> > > > Hi,
> > > >
> > > > the Python shell window is not a terminal. It is built using a
> > > > QScintilla widget. That's, why you see the raw escape code been
> > > > print. Howver, you may start the debugger backend in a console. Just
> > > > go to the configuration dialog, Debugger->General page and enable the
> > > > option "Start debugger in console window" and give it a valid console
> > > > command (e.g. konsole -e). You may override this setting on a per
> > > > project basis using
> > > > Project->Debugger->Debugger Properties and enabling the console
> > > > debugger.
> > > >
> > > > I hope, that helps to solve your issue.
> > > >
> > > > Regards,
> > > > Detlev
> > > >
> > > > On Freitag, 6. Februar 2009, Christof Hanke wrote:
> > > > > Hi,
> > > > >
> > > > > I try to write some python-dialog-stuff, but the
> > > > > Shell-Window somehow prints out the Terminal-codes
> > > > > (stuff like "<ESC>[23;") instead of  actually applying it.
> > > > > The shell itself claims to be of terminaltype "xterm".
> > > > >
> > > > > I haven't really found something useful in the settings about this.
> > > > > (I am not saying it's not there, because 80% of the time Detlev
> > > > > just points people  to the correct place ;-)
> > > > >
> > > > > Or is it in general possible to run scripts in a real external
> > > > > Terminal (xterm/Konsole/whatever) ?
> > > > >
> > > > > Many thanks,
> > > > >
> > > > > Christof
> > > > >
> > > > > _______________________________________________
> > > > > Eric mailing list
> > > > > Eric at riverbankcomputing.com
> > > > > http://www.riverbankcomputing.com/mailman/listinfo/eric
> > > >
> > > > --
> > > > Detlev Offenbach
> > > > detlev at die-offenbachs.de
> > >
> > > --
> > > Detlev Offenbach
> > > detlev at die-offenbachs.de
> >
> > --
> > Detlev Offenbach
> > detlev at die-offenbachs.de
>
> --
> Detlev Offenbach
> detlev at die-offenbachs.de



-- 
Detlev Offenbach
detlev at die-offenbachs.de