Re: [gnome-db] Future characteristic



On Thu, 28 Oct 2004 14:40:27 +0200, Rodrigo Moya <rodrigo gnome-db org> wrote:

> >
> > Because a simple GdaDataModel is a list of data, with no way of
> > knowing where the data comes from, which is a pre-requisite if you
> > want to update that data in the database.
> >
> but since GdaDataModel is fully extensible, we can add anything we want
> to derived classes.
> 
> Also, GdaDataModel already has methods for updating the data in the
> model, so I guess it makes sense to reuse/extend that

I see. I'll update the merge plan for that.

> 
> >  The idea is to modify the
> > data in the GdaDataModel and make sure the data is actually modified
> > in the database as well (in a correct way).
> > 
> this is what the append_row/update_row/append_row methods on the data
> models do. We just are missing the implementation of those methods in
> all providers.
> 
> If we need anything extra, GdaDataModel offers the base on which we can
> extend to anything we want.

Ok.

> 
> > >
> > > > However we could create an interface which both GnomeDbGrid and
> > > > MgWorkGrid will implement, so the API can be the same for both
> > > > widgets.
> > > >
> > > the data model one :)
> >
> > I was thinking of an interface for the following functions:
> > _set_titel(), _get_title(), _set_column_title, etc
> > 
> again, if we reuse the GdaDataModel, there is no need to have 2 widgets.
> A single widget can support both read-only models and full featured data
> dictionaries, and adapt itself to whatever it is using.

Yes, one widget is better.


> 
> > I'll update the proposal document and send it again for comments.
> > 
> I think this document would be better placed in the website, so that
> anyone can see it. Would you like to put it in the
> gnome-db-web/docs/white-papers directory, please?

I will as soon as I've updated it.



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