Hi Pedro,
> So I am at a standstill as some "parts are missing"..
> Notably header.php is missing and other stuff for db connection. and
> obviously data..
> Which is understandable.. we dont want everyone to have access to a not db
> and the server is apache and probably configured in a custom way.. as is
> usual.
The whole data is not there, it's still getting prepared to be "gitted" (put
the passwords out of the git repositories, etc.). For me it's ok, so I think
there will be more data soon, as soon as Martin finds the time to push it.
> For all of us to play moving forwards, we need a db or a clone or some public
> access etc...ideal worls.. but
> Regardless of the server side.. and all its complications with code +
> access...and then downloading a huge DB...
We could possibly make the data scheme public, which could be something good to
understand how the FG tables are defined. However most of the DB (out of the
pure scenery site) - Martin please correct me - is based on mapserver, so it
depends on which part of the website you want to work.
> So Can I suggest we patch up the server simple and quick to do simple task of
> returning data in json format..
We are already pulling some info from the server in Ajax, maybe you can be more
precise in what you mean by "patching".
> To get started what would be idea would be a list of "types"/
What do you mean by "types" ?
> also a list of models
The list of models is here : http://scenemodels.flightgear.org/models.php
(mixing shared and static).
> and a list of authors...
The list of authors is here : http://scenemodels.flightgear.org/authors.php.
> eg with adodb..
> $models = $db->getAll("select * from models order by model")
> headers("Content-type: json")
> echo json_encode($models);
For the moment I wrote some simple PHP functions (not in git yet) to avoid
rewriting everything each time. However there are mostly two parts on the
scenery site (not talking of mapserver) : the part I wrote (adding, editing,
deleting positions) and I'm still working on, and the part Jon wrote.
Hopefully, putting all this to GIT will make things more coherent and easier to
update. This is still not perfect, but better than nothing.
> However atmo its an unknown "thing" happening in some "dark room" with some
> parts available..
As already said, this has been the case for many years, and the git data you
are seeing is a clear way to showing you that things are changing. There is not
enough people working on it, so you'll be welcome to help once the whole data
is published (it will make things a lot easier for you). But of course there is
a need for human validation on the data pushed back to the server.------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
