Hi Carlos (and all),
Yes, people who want to stop by and chat can sometimes find
me awake in the channel #seul on irc.seul.org. No guarantee that I'm
awake as I'm always in there.
> - Noweb: I don't know anyone who has benefit of using it. If we want
>to change to plain C files, we should convert all noweb comments into
>doxygen (or whatever) comments. I think doxygen will improve code
>documentation too. Is anyone still using noweb? who wants to drop noweb?
>Any volunteers to do the work?
I am in favor of dropping noweb, just as long as _all_ the major
contributors agree. Patrick, what's your opinion on this? Naturally all
the useful code documentation that has been written will be preserved
(either in code comments and/or doxygen).
> - OK/cancel buttons: current GTK and Gnome widgets use to have the
>cancel button on the left, and the ok button on the right. Gschem have
>them reversed. Recently I implemented the file load/save in gschem using
[snip]
As other have said, the order of the buttons is a subtle yet
important thing. And also as other have pointed out, getting this wrong
will annoy people. At the very least it should be configurable and/or
should follow the native OS's order. In the very very short term (so
that I can get a release done), I will switch the order of the buttons
so that it is consistent throughout gschem. I will do this as part of
my preview widget work.
> - Unsaved schematics warning when exiting: I always have to read the
>text to know what button I should click on. I think it can be improved
[snip]
I'm pretty indifferent on this. Just as long as you can't exit
the app without being told of unsaved schematics and also, you should
not be attacked by hundreds of popup dialogs.
> - Heavy/light symbols: I don't want to start another never-ending
[snip]
Oh no, not again. :->
> - Heterogeneus parts: this is the hardest thing to code. Using the
[snip]
Oh no, not again. :-> However, I'm not opposed to anything
proposed, other than it can't break any existing behaviors.
> - Attributes for packaging/automated refdes assignation: currently if
[snip]
Oh no, not again. :-> Don't get me wrong, all good ideas, but
not easy to implement.
>
> - Autosaving: having gschem automatically save every unsaved schematic
>every few minutes (user-defined). gschem can use another filename, like
>#real_name.sch#, like emacs, or real_name.sch~.... These files should be
>deleted when saving the page.
Actually gschem does autosave right now (indirectly). As part
of a very early implementation of undo (which was never changed because
nobody complained), gschem writes a copy of the schematic to /tmp after
each action. Not pretty (read: hack), but quite effective solves the
"loss of data on crash". (Un)Fortunately, the undo files are removed
on a proper gschem exit. It might be useful to change where these undo
files are written, since /tmp is typically purged on reboot.
> - Autosaving when crashing: I know gschem shouldn't crash but, what if
[snip]
See above. :)
Just my random 2c.
-Ales
