On Thu, Oct 21, 2004 at 09:16:41AM +0200, Piotr Miarecki wrote: > Hi Stuart and All, > > at first - I compromize everything if you only agree to work together on gEDA > installer/setup, including Python. The only condition is that every step should > carry a new functionality, not rewriting the existing code nor writing everything > from scratch. > > Majority of gEDA tools are one-person-projects. If a developer has no time for gEDA, > temporarily or permanently, the tool is not maintained. A good example was setup and > gmanager during past time. If you look into setup.cfg you see that it supported pcb, > gwave, gtkwave and other tools - but in old, obsoleted versions. Because during past > three years I had only few time for gEDA. > > If you start a new installer project - this is what probably happens with your > installer in the future as well. I propose that we cooperate. There are many > features missing: updating support for non-gaf tools, porting to windows, creating a > tool for creating setup.cfg, supporting APT/RPM(/PKG) databases, etc. > > Answering your questions: > * setup HAS BEEN designed using glade, take a look into CVS: > ~/glade/setup/setup.glade, > * setup does support ALL gEDA tools (now in obsoleted versions, it needs to be > updated), > * setup is written in C, yes, because imo its a gaf standard, as well as guile > should be used for scripting (imo it means also: not python, perl, etc.) - but this > is a subject that should be separately discussed with Ales.
I appreciate the fact these tools are in C and not in Perl or Python. C is fast and there's no danger that some new version will come in which something will behave differently. Cl<
