Re: gnome-db/TOAD/gASQL (was Re: [gnome-db]Access-like prkect)



On Thu, Jul 26, 2001 at 04:58:36PM +0200, Rodrigo Moya wrote:
> Hi!
> 
> want in GNOME-DB. And this reminded me of another thing, which I've been
> thinking for a while, Vivien, which is to merge the functionality in
> gASQL into GNOME-DB, and make one killer app instead of 2 good apps.
> Also, if we support some of the things that are in gASQL in GNOME-DB,
> we'll make a big pain to gASQL, since I suppose people won't install an
> app that does the same that GNOME-DB, and which itself depends on
> GNOME-DB. I know this means some extra work, and please note that by no
> means do I want to "kill the competition" :-) by merging gASQL into
> GNOME-DB, of course not, but I really think there should be a good app
> for DB access in GNOME (like there is in Windows, with Access, Paradox,
> etc) instead of 2 with redundant functionality, or with stuff supported
> in one and not supported in the other one
> 
> so, should I shut up or is there something interesting in what I say?
> 

No, I think this is worth thinking about.

When I started gASQL (before I knew about GNOME-DB), I had the same need as you (and I
still have). I decided to use GNOME-DB because it offers a solid foundation and allows
to connect to many databases in the same way.

About a possible merging, I agree with you about the fact that we should not duplicate 
our work. I've thought about the respective positions of gASQL and GNOME-DB, and I think
the two products are complmentary. Let me explain:
* about the archutecture: for the two, libgda is the common engine
* 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).
* 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 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.

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
* 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 manipulate 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.

So, here is my point of view on the situation. I'm of course open to any comments and
discussions.

Tell me what you think about all this.

Cheers,

Vivien

> cheers
> --
> Rodrigo Moya <rodrigo gnome-db org> - <rodrigo ximian com>
> http://www.gnome-db.org/ - http://www.ximian.com/
> 
> _______________________________________________
> gnome-db-list mailing list
> gnome-db-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-db-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]