[snip] > I've found Guile features called Fluids and Dynamic Contexts. These will > allow me to put a real flexible, dynamically extensible configuration > mechanism into gEDA that works much more cleanly than the current one does.
Whoa. I'm not going to allow such a change (or any other significant changes that might break end users) unless the changes are written up in a comprehendable specification and a few of the core developers provide some comments on the written proposal. And by comprehendable specification I mean liberal use of bulleted lists, pictures (where they makes sense), and no dense paragraphs of text (that nobody has time to grasp; like this one :-). Also, silence or lack of feedback is *not* a blank check or approval for major changes. If the above proposal requirement slow development down a bit, that is okay since 1) gEDA users have really really really long upgrade cycles anyways and 2) the changes will be of higher quality and fit better into the overall gEDA/gaf philosophy. Anyways, if any new config mechanism comes into existence, the new config mechanism has to coexist with the old mechanism for a while. The old mechanism can be deprecated (then removed) at some later point, but not until a good chunk of the user base moves forward. I'm not going to comment on changing the guile or gtk+ minimal requirements just yet as I haven't made up my mind yet. However, I have heard the request (btw, making the same request over again doesn't help the cause). -Ales _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
