Re: gda-report and gnue

> > well, I've also been looking at Derek's proposal, and it's really GREAT.
> > And having a report server, as I've understood, is just a CORBA server
> > which will be activated when needed. For small applications, you just
> > have all the components on the same machine, and the user won't notice
> > any difference.
> That is correct.  I havent fully looked into libgda, but figured that is
> how it worked as well.  If necessary we could make it so you could
> encapsulate this w/o CORBA into a small application, but I am not sure I
> see the inherent value.
I don't see it neither. ORBit is very lightweight, and a user won't ever
notice he's using CORBA.

> > I think we should adopt Derek's ideas. The only thing I don't agree is
> > to have this out of GDA. I think it should go to GDA, for not having to
> > add another dependency out of it.
> This is my reason for not wanting in GDA.  Bloat.  There will be LOTS of
> projects that perhaps want GDA but not reporting why make them have
> both?  By separating it you get that.
well, I was thinking on making a separated CORBA server and client
library, which could go separated (that is, in a gda-report RPM or DEB).
Thus, users will install it only if needed.

> Also and possibly more importantly for GNUe is that while we plan to
> only use libgda at the current time, I think the tool should be able to
> in future allow it to be used with other data access methods if an
> author wants.
> By this I mean WE (GNUe) plans to use libgda, after all it would be dumb
> not too. :)  However a smaller project may want to just connect directly
> to postGRES w/o overhead abstration of libgda.  I think we would have
> more users and a better product if we allowed for this as well.
here you're right, but is it worth the extra work to make it like this?
I mean, in the report engine we're going to use the XML queries, which
are in GDA, so you'll have to code a substitution for this. Also, other
things will have to be reimplemented to allow what you say. Some things
could be moved from GDA to the report engine, but for example, the XML
queries can't, since they'll be used in GDA (clients and providers).

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