El lun, 11-12-2006 a las 22:48 -0500, Ales Hvezda escribió: [snip] > Okay, so now the question is how to proceed. I need to look at > Patrick's code changes first. Sorry to say this, but let's hold off > merging glist_dev for a little bit till I've looked at them.
[snip] > Carlos, what's your thoughts on all this? I am still very interested > in getting your GList changes into HEAD. The glist-dev branch contains two main changes: the first one (and the older) is to convert the SELECTION into a GList. Since we all agree this is fine, and some future development depends on that, at least I'd merge these changes asap into HEAD. The most recent changes in glist-dev are the ones dealing with zooming while panning. I haven't seen Patrick's proposal. IIRC (it's almost one month since I don't deal with the glist-dev source code), the undo is only used when moving objects (keeping the old behaviour of gschem), but not when copying (changed completely to use the complex place list). Having said this, and without having seen Patrick's proposal, a natural improvement could be to use the complex place list for moving objects, and to store the current view somewhere at the beginning of the copy/move actions, thus avoiding the use of the undo. This is a huge patch already, and changing more gschem and libgeda's internals could be "dangerous". I had to do the work twice due to the change from noweb to plain C, and it will be a wasteful work if the changes were not merged (as it seems now), so I think I stopped at the right point: having changed only the necessary parts of libgeda and gschem to make it work. After discovering CVS branches, I strongly think anyone wanting to refactor the libgeda or gschem internals should start a branch in the official CVS server, and work on it. This allows to be able to sync whenever he wants, while letting others to see the development. Patrick, I feel there is a lack of communication here. This is the first time I hear any technical comment (i.e.: more than "this is not working") about this patch since I started it (long before the transition from noweb to plain C). I appreciate your work and your comments, however I'd like to hear them _before_ coding is started (whenever someone ask for comments about a new feature), or _while_ the development is going on. At least, I'd like to hear something like: "I don't like this, so I'm going to try a new way". Just share your thoughts, and give all people the chance to give their opinions and what I think it's most important: to know it. FMPOV waiting until the very last moment is not good. I think we will feel more comfortable if we know what other people is doing, specially if there are several developers working on the same feature, or if someone is basing his work on top of other's. This raises a new question to all the development group: what's the reason to have a private versioning system for developing? Why don't use the official server? Something is not properly working here... Best regards, Carlos P.S.: I tried to explain my feelings politely. If you think these words are rude, it was _not_ my intention, but my lack of (enough) english knowledge. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
