On Mon, 2005-11-14 at 17:35 +1300, Dene Maxwell wrote:
> George,
> What might be an idea is to post some source code so people with a more
> intimate knowledge of *nix and SQL can provide some suggestions (psuedo
> code). What I know about *nix can be written on the back of a very small
> postage stamp, I do know a little more about SQL but not much.
> 

Dene, 

I think you'll find that if you have provided the algorithms (if only in
VB code can be re-worked back to pseudocode then to the required
language with littler grief. The Target language might be php for a web
based flight planner or gtk+ based programming language for a graphical
user interface.

> My approach for connection to different database engines would be to have a
> registry flag that, if not present would invoke a routine to specify a
> database file name, location and type and then once a successful connection
> has been established to write the appropriate value into the registry for
> use then on.... but does *nix have a registry equivalent or is it done by
> "ini" files.

There are some "normal" places that a unix program *can* look for
configuration files (ini if you like). Examples include
/etc/program_name/, /usr/local/etc/program_name/ or under the user's
home directory. This "policy" it up to the program in question and can
take a bit to work out where the config file is being loaded from.
> 
> It might be easier to create an object(s) that sits between the FG Navaid
> table and the application to make it look like a series of related flat
> tables.
> 
> This of course begs the question; does *nix have a windows environment
> emulator?


Yes, it does have have a windows "emulator" called Wine and WineX but
doen't always emulate the windows system calls sufficiently. 

> 
> If so this gives another option to have a "Jet" connection for Windows users
> and a generic SQL connection for *nix users. This could use the OS ID to
> switch between the two....(or 3 if I include OS/2 support ;->)
> 

What about Mac OS X? :-P You could also use an rpc like routines where
you request some data from the server and the server replies with a
pre-formatted file containing the answer to that request. See xml-rpc
for one generic example.


George Patterson


_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to