As John wrote: > Have you created a nice Frontend-layout, i think it should not only > be a big Dialog-Frame like the old avrdude-gui, or what i have now > for test purpose ?
I don't think my setup already satisfied any kind of aesthetical pleasure. If you want to start over from scratch, without being biased by whatever my ideas have been so far, that's fine. > There are parts of code which can only be used in CLI, and have to > be rewritten in/for the GUI to have the same functionality, [...] Just tell me. The major idea behind separating the backend library from the CLI frontend was to allow for a completely different (presumably GUI) frontend. If I missed anything there, it ought to be fixed. Feel free to file bug reports for that. I don't make any promises about the timeframe to handle then, but if the library/ frontend separation missed its purpose, it should be considered a bug anyway. > avrpart.c: avr_display(...) Something I apparently missed. Could probably be rewritten using the (ficticous) notification callback already discussed. > i rewrote this function in the GUI-project, but found further > problems, with i.e. reset_disp_str(), this function can only be > called inside avrpart.c but could be used from a GUI ! (I had to browse the code to see what you mean: reset_disp_str() is declared "static".) This should be resolved by using the notification callback instead of just firing an sprintf(stderr, ...) in the library. > ich hoffe das versteht jetzt irgendwer, genug verschiedene > engl. wörter wären enthalten :-) Gute Nacht! -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
