Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 2441 invoked from network); 15 Nov 2001 19:45:28 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Nov 2001 19:45:28 -0000 Received: (qmail 28500 invoked by uid 97); 15 Nov 2001 19:45:18 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 28459 invoked by uid 97); 15 Nov 2001 19:45:17 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 28400 invoked from network); 15 Nov 2001 19:45:16 -0000 From: "Bernard D'Have" To: "Avalon Developers List" Subject: RE: [RT] Avalon Developer Tools Date: Thu, 15 Nov 2001 20:44:55 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3BF4187A.8080306@apache.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Berin Loritsch [mailto:bloritsch@apache.org] > Sent: Thursday, 15 November, 2001 20:33 > To: avalon-dev@jakarta.apache.org > Subject: [RT] Avalon Developer Tools > > > It would be handy to have some developer tools that don't cost an > arm and a leg. My question is first, "Does anyone know if these tools > exist?", and second, "If not, are we interested in a subproject to > house them?". Until we upgrade, we can use the Avalonia project that > we have at SourceForge to handle these things. > > 1) Database definition managment. It would be Really Great (TM) to > have a tool that took an XML representation of a group of tables > and views, and spat out the DB specific SQL commands to generate > the database. It would be even better if this tool could be > embedded in ANT! The other side of the tool would be the GUI that > you used to create the XML markup. Another Really Great (TM) thing > would be to handle the initial values that needed to be inserted > into the database to make it useable. there is a sub-project of jakarta-turbine for that: Torque Bernard > > 2) Configuration GUI. Let's face it, building a configuration file > by hand is only enjoyable by people who know what they are doing. > For the rest of us, we need a GUI to help out. One particular > utility we can use is Xybrix (http://jbrix.org/kits/xybrix). It > takes XForms (or a close proximation) and generates the GUI > dynamically. That way, components can have the XForms definition > with them and Xybrix can generate the entry for it. > > 3) Component Server. When you want to really make something a bit > easier to maintain, you want your tools to manage the monitoring > and notifications of updates. That way you can always have the > most current version of a Component. This may work better for > Blocks, but it's an idea we had a long time ago (hense the > blockinfo descriptor files, etc.) > > To me, the first one is the most important--esp. since the last > couple of days has been spent tediously taking an Informix schema > dump, and massaging the output to work with PostgeSQL. PAINFUL > AND BEST TO BE AVOIDED IF POSSIBLE. Commercial tools that manage > all that for you are more than $1000 USD, and many times are quite > clunky to use. > > -- > > "Those who would trade liberty for > temporary security deserve neither" > - Benjamin Franklin > > > -- > To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: