> Aren't you effectively writing code when you create the XML by hand? Good question.
The Renaissance XML format was designed to be "a pleasure" to edit by hand; I personally like to edit the Renaissance XML files in emacs and find it very productive - very simple, short, logical, to the point, quick to edit, with all and only the relevant information displayed. :-) But I completely understand people who use Gorm which is a fantastic tool if you like visual editing. It's a different approach. The ideal scenario was to have a Renaissance/Gorm GUI builder (as we have discussed countless times, this would allow a lot of different approaches from an integrated app), but I have come to the realization that I'm not alone and there are other developers who actually like to edit the Renaissance XML files in their editor too! In fact the most exciting/excited users don't seem to care that much about the GUI builder. So I'm ignoring the GUI builder issue, and aiming for a stable, robust and complete Renaissance 1.0 release which will be complete but won't have a GUI builder. We'll work on the Gorm/Renaissance integration later, for Renaissance 2.0. :-) Btw, having different tools to build GUIs is great as it gives people a choice. Different tasks/developers are more or less suited to different tools. So it enriches GNUstep as a project to have various options available. :-) Also, we have two ways of attracting Apple developers to GNUstep / GNU; Gorm provides them with a free tool similar to the Apple one (attracting developers looking for something similar to Interface Builder); Renaissance provides them with something new/different (attracting developers looking for something different from Interface Builder). Thanks _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev