20,741
edits
(→Modified tanker.nas version using ai.nas: new section) |
|||
| Line 142: | Line 142: | ||
Like I said, before you told me you were interested in exploring this, I already started some work related to this - I'd suggest you wait until I have committed those changes so that you can take a look - it's mainly structural stuff ensuring that the existing GUI dialog can be used to instantiate a new tanker using ai.nas - everything else is "as is" and still needs to be adapted, but I thought this could help lower the barrier to entry. It's up to you obviously to decide if you want to use or discard those changes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:19, 2 November 2014 (UTC) | Like I said, before you told me you were interested in exploring this, I already started some work related to this - I'd suggest you wait until I have committed those changes so that you can take a look - it's mainly structural stuff ensuring that the existing GUI dialog can be used to instantiate a new tanker using ai.nas - everything else is "as is" and still needs to be adapted, but I thought this could help lower the barrier to entry. It's up to you obviously to decide if you want to use or discard those changes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:19, 2 November 2014 (UTC) | ||
Ok, I've committed those additions[https://gitorious.org/fg/hoorays-fgdata/commit/c61effba1a8e0f80b4acf5c48de8c19d94218fbc] - it isn't yet using ai.nas though, it's just a slightly modified version of tanker.nas that is loaded into a different namespace, and integrated via the tanker.xml GUI dialog, so that the actual file doesn't need to be modified. We can now easily replace existing functionality without there being any chance to break anything. Even though reset/re-init handling may still need some work/tweaking, because I haven't reviewed tanker.nas for any hard-coded namespace references yet.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:14, 2 November 2014 (UTC) | |||