Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 20093 invoked from network); 16 Jun 2002 06:32:18 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 16 Jun 2002 06:32:18 -0000 Received: (qmail 9441 invoked by uid 97); 16 Jun 2002 06:32:30 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 9425 invoked by uid 97); 16 Jun 2002 06:32:29 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 9414 invoked by uid 50); 16 Jun 2002 06:32:29 -0000 Date: 16 Jun 2002 06:32:29 -0000 Message-ID: <20020616063229.9413.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: ant-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 9898] New: - Ant UI proposal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9898 Ant UI proposal Summary: Ant UI proposal Product: Ant Version: 1.5Beta2 Platform: PC OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Core AssignedTo: ant-dev@jakarta.apache.org ReportedBy: miha@softhome.net Hello, We use ant operationally for the following: 1. build/development lifecycles (compile, jni links, continuus builds and so on) 2. db manipulation: create DBs, feed with data - many db operations that can be allowed to non-administrator users without giving them super-user rights 3. uniq application execution interface: provide same interface to application execution modes. 4. many more. We put attention that we very miss some simple but powerful UI for executiong ant tasks, i.e. due that fact that every ant declares its input parameters explicitly and provides task descriptive information - it is possible to create ant module that will build default UI per task. That UI will provide a textfield with defaults values (taken from task input params/properties) and "execute button"). Example: Imagine cmd line parameters: ant -ui dbpop_h The above command will start ant and will build default dialog that contains "textfields" for properties: dataref and datadir with default values and "execute" button. simple and powerful! -- To unsubscribe, e-mail: For additional commands, e-mail: