[cad-linux] Re: database access methods

Eric,
I guess I have assumed that the library to access the database is
integrated with the solid modelling kernel. I.e. these were actually
one and the same thing. The solid modelling kernel is itself only
concerned with modelling, i.e. parametric geometry, topology, etc.. 

CAD applications would build upon that. The libraries' main purpose is
to provide a 'downstream' API for CAD applications. 

The core of the system would therefore consist of a Parametric Solid
Modelling Kernel which interfaces with a SQL database. 

As the application grows, your cellphone would connect via a
webinterface and find out how many doors you have to order for your
building. The webapplication that finds out about that asks also a 
library, one that knows how many doors are in the building - again from
the same database though, since doors are connected to points which
mark openings in walls and so on. 

We are possibly talking about two different things. First we have to
have a kernel that enables us to build a parametric CAD system. Then
comes all the CAD infrastructure. 

From your other email I understand that we are mostly on the same page
already. 

Roland


--- Eric Wilhelm <ewilhelm@xxxxxxxxxxxxx> wrote:
> 
> > The following was supposedly scribed by
> > Roland Krause
> > on Thursday 15 May 2003 11:52 am:
> 
> >Eric,
> >I believe access library and solid modelling kernel should be
> reversed.
> >
> >The model should imo be
> >
> >Parametric Solid Modelling Kernel
> >  implements access to:          --> Database
> >  provides an interface for:     --> GUI
> >                                 --> "Spreadcheat"
> >                                 --> "PHBs' cellphone"
> >Providing the interface could be by means of C++ API, C-API, DCOP,
> COM,
> >Corba, .not... etc.
> 
> I was trying to illustrate that the database access and format are
> handled by 
> the library.  Should an application need graphics or high-level
> geometry 
> data, it would utilize the kernel which utilized the library to
> access the 
> database.  An application could also use the kernel for accessing
> some 
> entities and the library for accessing the database.
> 
> I'm not sure why you would reverse the positioning of the kernel and
> the 
> library.  The kernel would build against the access library and a 
> project-management (non-geometry) app would build against the access
> library.
> 
> The idea is that the library creates a standard method of read-write
> access to 
> the database.  Therefore, to make the kernel standards-compliant, you
> simply 
> use this library for the database access.  To make any other app
> standards 
> compliant, simply use the library for database access.
> 
> Sure, the kernel may be providing the interface for the cell-phone
> geometry 
> viewer, but I don't think it needs to provide that for the
> spreadsheet.
> 
> --Eric
> 

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

Other related posts: