Run interface

[Vladimir Prus]

On Monday 26 November 2007 03:20:31 Hamish Rodda wrote:
> On Mon, 26 Nov 2007 04:51:46 am Vladimir Prus wrote:
> > On Sunday 25 November 2007 19:57:51 Andreas Pakulat wrote:
> > > Hi,
> > >
> > > as commit messages don't include new files I think its worthwile to post
> > > the new files from Hamish in a new thread to do any discussion.
> > >
> > > So here are irun, irunprovider and runcontroller.
> >
> > It's hard to comment on files that have no comments ;-) In fact,
> > it would be establish a policy that all core interfaces should be
> > fully documented.
> 
> That is of course planned, but I thought most of it was self-documenting 
> anyway.
> 
> > What I had in mind is that we should have a collection of 'launches'. Each
> > launch is associated with
> >    - A class that performs the actual launch
> 
> == IRunController
> 
> >    - A generic store (independent of launch type) to keep launch properties
> 
> == IRun

It does not seem 100% generic to me:

- It does not allow to specify random (name, value) pairs
- It hardcodes 'arguments' and 'environment' thing, which don't apply to
some launch types.

> >    - A set of UI pages to edit the launch, for example, a page to
> >    edit native run properties (executable, options, environments)
> 
> == the config dialog I'm working on now
> 
> >    , or a 
> >    page to configure which remote GDB target to use.
> 
> Needs to be supplied by the gdb plugin.

Probably I should just shut up and write some code to illustrate my approach :-)

- Volodya