>> 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. >> For now the consensus(Duane and I have mostly discussed this >> in the past) is a built in web server for basic operations and >> special pages for target specific peripherals. >> >> Take the builtin httpd server for a spin. > > Does the httpd server support PHP, database access, sessions, cookies, etc, > etc? > Without that the functionality of a builtin webserver is extremely limited > because it > is very cumbersome to make active web-pages. It doesn't sound like you've had a look at the stuff that's already done. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
