20,741
edits
Initializing Nasal early: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
{{Portability Navbar}} | {{Portability Navbar}} | ||
{{Nasal Internals}} | {{Nasal Internals}} | ||
{{cquote|The primary goals are: | |||
* make startup more predictable and less hard-coded. | |||
* allow running flightgear in a server/test mode with only some subsystems, and no rendering | |||
Obviously supporting a standalone 'fgcanvas' would be quite a small extension from those. I'm not worrying about dynamic dependencies or automatic subsystem creation for the moment - I expect the user / defaults to have defined a set of subsystems that work without crashing You're correct of course that Nasal has many assumptions about subsystems, but I think that can be improved incrementally on the Nasal side. | |||
For the test mode, I really want to start Nasal-the-langauge very early, without loading all the modules in Nasal/ immediately. (Or maybe load a 'safe' subset). That's going to take some thought and I didn't get that far yet!<ref>{{cite web |url=http://forum.flightgear.org |title=incremental initialization of SGSubsystems|author=James Turner |date=Oct 01, 2012}}</ref>|James Turner}} | |||
This is a summary of all discussions relating to: | This is a summary of all discussions relating to: | ||