I'd say go with standalone as well. It makes sense because Derby
itself is a database, not a development framework, so there is a good
chance that many potential users of the GUI won't be IDE users at all.
Andrus
On Jan 27, 2006, at 10:33 AM, Manyi Lu wrote:
A GUI for derby is a great idea. I have used SquirreL, but it lacks
some functionality, and it is under LGPL not Apache license.
A stand alone GUI would be better, people tend to use different IDEs.
Manyi
duminda wrote:
Hi,
What does the community most wanted, Eclipse or Stand alone?.
Duminda
----- Original Message -----
From: Satheesh Bandaram
To: Derby Discussion
Sent: Friday, January 27, 2006 12:59 PM
Subject: Re: Developing a UI for Derby
Sounds nice. Derby doesn't have its own GUI. This page at
Apache Derby lists several known GUI tools that work with Derby.
Are you thinking of a stand-alone tool or on some framework...
like Eclipse?
http://db.apache.org/derby/integrate/misc.html#Products+by+Type
Satheesh
duminda wrote:
Hi,
I'm interested in developing a GUI for Derby with Apache
licence.
Schema browser
alter table (column/constraint)
DML (insert/delete/update)
This will be something like "Toad" to "Oracle".
Is there any tool already exist?
Regards!
Duminda
