On Sunday 23 October 2005 06:57 am, Carlos Nieves Ónega wrote: > - OK/cancel buttons: current GTK and Gnome widgets use to have the > cancel button on the left, and the ok button on the right.
The buttons should follow the platform style upon which they run. GTK under Linux like system is different than Windows, MAC, or PocketPC etc. > ok/cancel. I don't know people reaction to this change. Comments? People expect consistencies on their platform, subtle differences like swapping buttons is consider bad forum by GUI design gurus. Simple things like this can make a subconscious impression that can make your program a big seller or a big looser. > - Heavy/light symbols: I don't want to start another never-ending > discussion on this, so please be kind with your answers and respect > other people's opinion. For example, I'd like to have only one symbol > for all NPN transistors. This would be a generic transistor symbol. I'm in the Light Symbols camp myself. From a manufacturing point of view you can not have down stream changes peculating back up through the documentation stack. That cost real money to maintain for no real benefit. > - Heterogeneus parts: this is the hardest thing to code. Using the > symbol inheritance, we can define a per-slot symbol. The idea is that > gschem be aware of parts, and part slotting, keeping track of what slots > are currently used/unused, and changing the symbol if needed when you > change the slot attribute. I know heterogeneus parts can be used now, > assigning the same refdes to two different symbols, but I'd like a more > automated way. They assume that all parts are they same, like a 7400. Many newer parts have divers functions in one package. Say a A/D with a couple of embedded Op-Amps for example. > - Attributes for packaging/automated refdes assignation I find the current built in system totally useless myself. I like to number my reference designators with a prefix that shows what page of the schematic it belows to, this makes it much easier to make sure you get a bypass cap to match the part it goes to in the PCB rats nest. > - Autosaving: having gschem automatically save every unsaved schematic > every few minutes (user-defined). PCB's feature of doing this has saved me a few times. Only thing I don't like about it is that those autosave files are around forever unless I go delete them. Should be something like "delete all files older than X days". >These files should be deleted when saving the page. I disagree with that. I have had crashes trash files that I did not notice immediately, and a backup save from yesterday saved my butt. > - Autosaving when crashing: I know gschem shouldn't crash but, what if > it happens some day?. What about automatically saving the schematics > when crashing? It is already crashed all bets are off on the integrity of the data, relegate this to the Autosaving. -- http://www.softwaresafety.net/ http://www.unusualresearch.com/ http://www.bpaddock.com/
