Hi Peter and all, > > Recently there have been a lot of discussions about what should and should > not be in libgeda. In order to stimulate a debate about what libgeda is > really for, and what its future is likely to look like, I've created a > page on the wiki that tries to describe in a very abstract manner what > libgeda should **ideally** look like from the "outside". > > http://geda.seul.org/wiki/libgeda3 > > Feel free to add or change things: I've probably missed a lot out.
Nice page. A few comments: There is no such thing as libgeda1, or libgeda2 (other than the debian package names) from my perspective. The version of libgeda has always just been an increasing integer. This is just a silly nit. I'm certainly okay with changing libgeda or gschem a lot to improve the tools, but it does sound like a lot of work and I would hate to end up with something that is partially finished or unstable. This is all in context that gEDA/gaf works now. Maybe there should be a definite release of the existing architecture (say gEDA/gaf v1.0) and then the architecture of gEDA/gaf can be redesigned. -Ales _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
