Hey guys, I had some questions on how you both think the functionality of the 'Sources' Tree View should act.
1) Should we allow the user to position any file where they want in the tree? That is, should we allow the user to drag and drop different nodes wherever they want? The reason I don't have it implemented this way right now is b/c I know that certain files do not have children and/or are not related to other files in the project. I didn't want files that were not related to other files to become the children (child nodes) for those files. For example: Say we have test.sch and it has files that were generated from it...such as BOM and NETLIST (I am using generic names here) The tree would looks something like this for the test.sch node-- test.sch | |__ BOM | |__ NETLIST Other nodes . . . This actually brings up another question. 2) I know that schematic files are usually associated with certain PCB files. However, would we really want something like: test.sch | |__ BOM | |__ NETLIST | |__ test.pcb ????? Basically my question boils down to what should the node precedence be for the different files in the gEDA suite? Do we want to make one (such as test.sch in the above) to have the highest precendence? Let me know your thoughts. I am cc'ing the list as well to see what they think...so anyone please feel free to comment. -- Newell Before enlightenment, chop wood and carry water After enlightenment, code and build circuits
_______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
