From: Richard T. <rjt...@th...> - 2007-01-19 11:02:42
|
On Friday 19 January 2007 10:56, ben...@ug... wrote: > Quoting Richard Taylor <rjt...@th...>: > [snip] > > > Benny > > > > Lets be clear, I can see the benefit of a High Level API for > > GrampsDB/RelLib. I think that it could reduce the barrier to people > > writting plugins and that would be a good thing. It might also reduce a > > certain amount of boiler plate code in the core GUI. > > > > I do not see the same benefit from an SQL database backend. Don has > > explained the reasons for this in great detail before and I agree with > > his reasoning. > > > > That being said, I think that a High Level API should concentrate on the > > best presentation of the Gramps data model to the programmer and should > > not concern itself with how it maps to SQL. > > > > So I think that when someone steps forward to implement and maintain > > this High > > Level API they should be thinking about the best API for the programmer, > > built on top of the existing database, and should ignore the SQL backend > > issues. > > > > Regards > > > > Richard > > Richard, > > I mean the interface like one of those api's. The high level api should be > transaction aware, database must be set, objects made, saved, ... > In short, it behaves like one of those api's and the same functionality > must be > present. > Then we are in violent agreement :-) Regards Richard |