Hi Fred/Gijs,
________________________________
De : Frederic Bouvier <fredfgf...@free.fr>
À : Olivier <acom...@yahoo.com>; FlightGear developers discussions
<flightgear-devel@lists.sourceforge.net>
Envoyé le : Samedi 18 août 2012 16h23
Objet : Re: [Flightgear-devel] 3D models import webform in production.
> . AC3D and XML
Done (not multiple yet however)
> . PNG
> . JPG
Done
> . OSG (several variants)
> . RGB
> . EFF (effect)
> . FRAG/VERT/GEOM (shaders)
> You cover a wide range of needs if you allow any number of files in this
> set of formats
This list is great, we now just have to think about what is to be parsed in
those file, this means, what checks have to be done in them so we're sure the
model is OK when submitted. For instance, in AC3D file, we currently check that
the format is OK (file starting with AC3D header) and that all the textures
named in the AC3D file are shipped with the submission. Else, we report an
error automagically. So, if for each of those 4 types, we're able to tell what
format they must be like, and where they're to be defined (XML, for instance),
then a good part of the job is done.
For Gijs:
> The webform cannot handle updates yet for example,
No, because we had to set the priority on the insertion tool. Note the update
feature is in the todo list (xiii has been asking for it for a while, and we
intended to do so). However, now it's done, creating the update script is
easier. However, the first step will still be on updating current 3D models
(this means with one single AC file, with optional XML and PNG files).
> but all my and Fred's
Rembrandt edits are updates to existing models. You'll have to come up
with a way to handle those exceptions.
We will. But your updates are not "simple" ones, they differ from the majority
of existing models we have. We should first make sure the Terrasync export from
the scenemodels DB can handle this type of models (for instance, for now we
have 1 ID for 1 model having 1 thumbnail, 1 XML file and n textures). We have
to test it: 1 ID for 1 model having 1 thumbnail, n XML files and n textures and
n of the above file formats. (Martin tell me if I say something wrong).
> Models that don't fit the
webforms could be send directly to an email address, just like we used
to do.
This has shown some limitations lately. While this is possible for testing
purposes (and we'll have to do it in that case), don't think it's the best way
to do on a long term basis, I think we all agree on this. As I had the same
questionning lately on another point, is it possible to create @flightgear.org
email addresses, which would get redirected to a few emails or to a mailing
list (I had this question for eventual spam reports).
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
