Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Austin, Alex
20, 2009 11:19 AM > To: openocd-development@lists.berlios.de > 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

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread David Brownell
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 w

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Øyvind Harboe
>> Cross platforms w/dependencies during compilation or running >> is not great either. > > The GUI doesn't need to be part of OpenOCD. 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.

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Nico Coesel
> -Original Message- > From: Øyvind Harboe [mailto:oyvind.har...@zylin.com] > Sent: dinsdag 20 oktober 2009 9:33 > To: Nico Coesel > Cc: openocd-development@lists.berlios.de > Subject: Re: [Openocd-development] OpenOCD GUI > > > IMHO a GUI is a good idea but it

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Øyvind Harboe
> IMHO a GUI is a good idea but it has to be cross-platform. I have been > using WxWidgets for cross platform development for several years and I > must say the transfer between Windows and Linux is seemless. Cross platforms w/dependencies during compilation or running is not great either. For no

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Nico Coesel
> -Original Message- > From: openocd-development-boun...@lists.berlios.de [mailto:openocd- > development-boun...@lists.berlios.de] On Behalf Of Michael Schwingen > Sent: dinsdag 20 oktober 2009 8:48 > To: openocd-development@lists.berlios.de > Subject: Re: [Openocd-develo

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Øyvind Harboe
OpenOCD has started some work on a GUI using a web interface, look at the httpd server in the development section, the builtin web server works today. It should include some memory browsing, flash programming page, simple small scale production page for non-engineers, etc. A web interface is great

Re: [Openocd-development] OpenOCD GUI

2009-10-20 Thread Michael Schwingen
Dean Glazeski wrote: > Another thing of interest is a feature list. I've started a feature > list in this email and additions are welcome. I don't see how a GUI will improve my work in any of these areas: > > 1. OpenOCD server configuration > a. Telnet Port > b. GDB Port > c. TCL Port

Re: [Openocd-development] OpenOCD GUI

2009-10-19 Thread Dirk Behme
Dean Glazeski wrote: > Hi list, > > I've been sort of bothered by the lack of a GUI for OpenOCD. I've seen this > project: http://openocd-gui.sourceforge.net/, but I'm not entirely certain > if I like their direction. My main concern is the lack of activity and the > goal of using C++ or TCL/Tk.

Re: [Openocd-development] OpenOCD GUI

2009-10-19 Thread David Brownell
On Monday 19 October 2009, Dean Glazeski wrote: > Hi list, > > I've been sort of bothered by the lack of a GUI for OpenOCD. In what respect(s) ... what tasks do you find awkward today that a *Graphical* UI would help with? I think there's likely improvement to be made by noticing ways that, for

[Openocd-development] OpenOCD GUI

2009-10-19 Thread Dean Glazeski
Hi list, I've been sort of bothered by the lack of a GUI for OpenOCD. I've seen this project: http://openocd-gui.sourceforge.net/, but I'm not entirely certain if I like their direction. My main concern is the lack of activity and the goal of using C++ or TCL/Tk. At any rate, I was going to sta