Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
* Melchior FRANZ -- Wednesday 09 August 2006 19:09: I think we should also save aircraft specific settings in this file An alternative would be to save aircraft specific stuff in getprop(/sim/fg-home)~/~aircraft_name~.xml, that is: each aircraft saves its settings in its own file. Would this be better? m. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
Melchior FRANZ wrote: * Melchior FRANZ -- Wednesday 09 August 2006 19:09: I think we should also save aircraft specific settings in this file An alternative would be to save aircraft specific stuff in getprop(/sim/fg-home)~/~aircraft_name~.xml, that is: each aircraft saves its settings in its own file. Would this be better? Well, I already use /sim/model/name/ for aircraft specific stuff just to keep things neat. I only put stuff outside there when I am dealing with a system that already has a place, like instruments. Most of my stuff however should not be saved. For that reason I like the latter idea, though i would use something more descriptive like /sim/ac-saved-states/~b29. Home sounds to me like you are talking about people, not planes. Josh - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
* Josh Babcock -- Wednesday 09 August 2006 20:03: Melchior FRANZ wrote: getprop(/sim/fg-home)~/~aircraft_name~.xml, that is: Well, I already use /sim/model/name/ for aircraft specific stuff just to keep things neat. Yes, it's a kind-of standard. For that reason I like the latter idea, though i would use something more descriptive like /sim/ac-saved-states/~b29. Home sounds to me like you are talking about people, not planes. Huh? Is this supposed to be a path on the hard-disk? You are aware that getprop(/sim/fg-home) resolves to the same path where autosave.xml is put? This is $HOME/.fgfs/ on Unices, and something ugly on MS Windows. And generating directories isn't possible with fgfs' nasal. So what makes most sense is: getprop(/sim/fg-home)~/~aircraft_name~.xml which resolves under Linux with the bo105 to: /home/foo/.fgfs/bo105.xml But this requires extra code in Nasal, while putting such settings in autosave.xml doesn't. m. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
* Josh Babcock -- Wednesday 09 August 2006 20:16: My point was that if you automatically store everything in /sim/model/name you may grab a lot of stuff that doesn't need to be stored. We need a way to designate what gets stored and what doesn't. I was actually suggesting the autosave.xml method. No, it shouldn't save all in /sim/model/name, and yes, there would be a designator, one that exists *already*: sim model bo105 variant type=int userarchive=y0/variant ^^^ Just try that, and you'll find the settings in autosave.xml, written on exit. This seems much saner than saving each aircraft's data in an extra file. Sorry, should have explained better from the beginning. :-) m. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
On Wednesday 09 August 2006 18:09, Melchior FRANZ wrote: If someone wants to save e.g. frequencies, then he should save them in /sim/model/foocopter/instrumentation/comm/frequencies/selected-mhz (or something) and on startup copy the frequencies to their respective addresses. That sounds fine to me. I am about to try and make the Lightning radios do what they should, and that would involve (user chosen) pre-set frequencies. Obviously it would be nice to avoid having to manually pre-set these frequencies every run... Like you suggested, liveries would be another obvious choice to remember, and stuff like seat height. Personally I don't think we need a separate file for each aircraft, but I don't have any particularly strong feelings either way on that one. I suppose it would make it very easy to return any aircraft model to standard state... Cheers, AJ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
Melchior FRANZ wrote: * Josh Babcock -- Wednesday 09 August 2006 20:16: My point was that if you automatically store everything in /sim/model/name you may grab a lot of stuff that doesn't need to be stored. We need a way to designate what gets stored and what doesn't. I was actually suggesting the autosave.xml method. No, it shouldn't save all in /sim/model/name, and yes, there would be a designator, one that exists *already*: sim model bo105 variant type=int userarchive=y0/variant ^^^ Just try that, and you'll find the settings in autosave.xml, written on exit. This seems much saner than saving each aircraft's data in an extra file. Ah, that seems like a very good way to do it. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autosave.xml -- aircraft specific settings
AJ MacLeod wrote: Personally I don't think we need a separate file for each aircraft, but I don't have any particularly strong feelings either way on that one. I suppose it would make it very easy to return any aircraft model to standard state.. It would be not too difficult to delete the settings corresponding to a specific aircraft from the autosave.xml either. As it's very easy to do we could just use the autosave.xml for now and when someone finds a good reason to do otherwise change it. I don't think it's wise to do much work and produce code that has to be maintained just because of a vague guess that it might be nice to have. Nine - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
