Running scripts

[Andreas Pakulat]

On 15.03.09 09:39:25, Niko Sams wrote:
> On Sun, Mar 15, 2009 at 1:27 AM, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 14.03.09 09:34:21, Niko Sams wrote:
> >> I started working on a php debugger and need a way to run scripts.
> >> I need the following possibilities:
> >> - run on commandline
> >>    can be accieved using the current run settings by settings executable to
> >>     "php /path/to/my/script.php"
> >> - run on commandline over ssh on external server
> >>    it is quite common that you have php only on a server, and you want
> >> to run it there.
> >>    currently possible with:
> >>     "ssh server php /path/to/my/script.php"
> >> - run in external browser (remote or local server)
> >>    "konqueror http://server/path/to/my/script.php?XDEBUG_START=$XDEBUGID"
> >>    ($XDEBUGID would be replaced by the debugger with an unique id)
> >> - run in internal browser
> >>   a WebKit OutputView should be opened, currently not possible
> >>
> >> So any ideas how we could improve the user interface for defining
> >> script targets?
> >> Especially "run in external browser" targets could be more user friendly.
> >
> > I just went through some of the mails in the last 2 months today and marked
> > the run-pref-change stuff for myself as I want to work on that soon(ish).
> > That will allow you to have custom target types with custom config UI (and
> > of course custom run-jobs), so should fulfill your needs. My current plan
> > is to write that in the next 1-2 weeks, but of course depends on my
> > motivation.
> great!
> Where will it be possible to have the custom UI? in IRunProvider?

No idea, haven't spent any time yet on thinking about API :)
 
> > Regarding the internal browser thing: A "OutputView" as in similar to the
> > ones we have right now is probably not an option due to its design, but
> > you're of course free to provide a custom toolview that embeds the
> > webkitpart and/or khtmlpart.
> You mean in my debugger plugin? For now the easiest way I guess - later when
> multiple plugins need this we could create a IBrowserOutputView or something.

Why? If there are two plugins that want such a browser toolview we can
simply move it into the util library. So any plugin can simply re-use the
toolview factory from the library.

Andreas

-- 
Be cheerful while you are alive.
		-- Phathotep, 24th Century B.C.