Re: [Openocd-development] OpenOCD GUI

[Austin, A. <Ale...@sp...>]

I would like to see openocd always start, even if the config
file is invalid. Then, it can be configured via telnet and,
hopefully, Have a command to dump a config file. If the telnet
interface supported completion a la Cisco routers (press ? to
list available completions), it would not be difficult to write
flexible GUIs that wrap around it, and it would be nicer to use
in and of itself.

> -----Original Message-----
> From: ope...@li... [mailto:openocd-
> dev...@li...] On Behalf Of David Brownell
> Sent: Tuesday, October 20, 2009 11:19 AM
> To: ope...@li...
> Subject: Re: [Openocd-development] OpenOCD GUI
> 
> On Tuesday 20 October 2009, Øyvind Harboe wrote:
> > The alternative is to create a complete API and stick to it.
> > We're not keen, nor do we see the need for the sort
> > of simple functionality that has been outlined.
> 
> Web access *IS* an API ... at least, as soon as
> any client starts to use it that way.
> 
> That's why there's been such a lot of interest
> in web programming interfaces that uplevel things
> from "screen scraping" to something that's more
> maintainable.
> 
> 
> IMO that's kind of moot until whatever non-commandline
> UI starts to get more users, though.  :)
> 
> _______________________________________________
> Openocd-development mailing list
> Ope...@li...
> https://lists.berlios.de/mailman/listinfo/openocd-development