[no subject]
>* AFAIK, GNOME-DB is composed of some low level widgets (to manage libgda
>connections, to connect to a database, a tabular view of a recordset, etc),
>and of some higher level applications like gnomedb-fe and the rolodex (which I
>believe does not evolve a lot anymore). gASQL uses the GNOME-DB "low level
>widget" and is also a high level application (like gnomedb-fe).
My conception is of GNOME-DB as providing a GUI configuration process, a very
simple tool for blasting out arbitrary SQL statements, and a widget set (much
like Borland provides for its development platforms). Under the theory that a
great DB-aware widget set + good development tools (GLADE, etc...) will yield
abundant and good database applications. I think this formula has worked very
well for that other operating system.
>* now, about gnomedb-fe and gASQL: in my point of view, the two do not
>cover the same area: I see more gASQL like an "acces like" application, and
>gnomedb-fe like a swiss army knife for the databases. They do however have
>some functionnalities in common. I do use gnomedb-fe sometimes when I want
>to do some things without all the constrains gASQL imposes.
I don't view them as competing. GDA + GNOME-DB provides infrastructure.
gnomedb-fe = "ODBC Driver Manager" with a few enhancements (SQL editor /
executor). I can see someone wanting to run a GNOME-DB app (say an accounting
package) and installing GNOME-DB, using gnomedb-fe to setup the connection,
installing the GNOME-DB app. Maybe occasionally using the gnomedb-fe to
diagnose/fix a few problems now and then, but otherwise just using the app.
Said user may have no intrest in something like gASQL.
gASQL is an Access/Paradaox/dBase-ish tool. For people who spend their day
plowing about inside database, populating tables, searching data, etc...
>I agree that at the moment gnomedb-fe lacks some functionnalities that
>gASQL has (or will have): the queries designer, the forms edition mode.
>The trouble is that to have these functionnalities, a lot of overhead
>is needed (keep gASQL informed of the possible datatypes, functions,
>relationships between tables' fields, etc) which is too much if a user wants
>to make a simple SQL query and get a result fast.
Exactly. I had not really expected much more in the way of features to be added
to gnomedb-fe. Something like gASQL would pick that up, providing forms, a
report composer, etc... using the widget set that GNOME-DB provides. And, of
course, GNOME-DB apps would allow users to execute said reports, etc....
>So, to summarize, I would say that we need the two applications. However
>what could be nice is:
>* show the two applications as part of GNOME-DB: we could say that
>GNOME-DB is made of two applications that are gnomedb-fe and gASQL and has a
>GNOME-DB-devel package to make your own applications using parts of
>gnomedb-fe or gASQL
Yes. I'd almost classify gnomedb-fe as a "utility" rather than an "application".
>* work on gASQL to make different components reusable, and bind
>gnomedb-fe and gASQL more closely.
>Just to give you an idea of what I have in mind for gASQL in the
>future: gASQL composed of 3 main components:
>* a core component with no GUI
>* controls components composed of all the current GUI to manipulat data
>stored within the core
>* bonobo controls to get tabular and form views of the data.
>This architecture is not for tomorrow either because it requires a lot
>of work.
Sounds great!
Systems and Network Administrator
Morrison Industries
1825 Monroe Ave NW.
Grand Rapids, MI. 49505
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]