erendrake

I have created a new ticket in github for adding the features we have been talking about. We dont have to just hijack this thread https://github.com/erendrake/KOS/issues/40 Lets make this an awesome feature togfox I would love to get your input as to what tools you would like to have.

If you find out how, I would be interested to know. it would cut down on development time! Have you tried the new version of kOS? this release is much faster

I think its a great idea, if someone wants to make a model and texture for it i would be happy to add it to the backlog @togfox This is really cool and im really excited when someone makes such an interesting project thank you for sharing!

This is a pretty compelling idea. I was very interested in using the description until i could not find a way to actually get at it through the API Faced with the idea of having to persist that data in the craft file, I decided to work on some lower hanging fruit first.

I think that my preference with something like this would be to let each of you register an external to run on boot, something like REGISTER BOOTSTRAPPER TO <FILENAME> And maybe even one for when you are losing power like: REGISTER POWERLOSS TO <FILENAME> And so on. I can think of a bunch of events that we might want to listen for. I also like giving control to you rather than just saving all state and magically restore it back to you.

I agree with Steven. What has the new keyword ever done to you? I think it makes for clearer code when you are explicitly creating new structures. However, I have no plans for adding that keyword to KOS. the example in the wiki is pseudocode. Do we think that a timespan structure would be useful for scripters?

It can surely be implemented, Right now im working on Direct flight, rcs control so we can accomplish docking missions more easily. Having some kind of bootstrapper should be doable Actually what i have been working on most lately has been the documentation site http://erendrake.github.io/KOS/, I think im ready for the community to review and tell me where i messed up.

I have a similar problem with slumbering threads like this. So I use the forum subscription feature. It emails me when they get updates. BTW this is a great challenge, I hope to submit my own entry once i get the docking release finished.

Something like that sounds great! i would do the same for something like DN/AN too. The biggest challenge I have right now is documentation and the Github wiki is not really making me happy. The reason I mention documentation is that this could be harder for people to just know how to use. Would you mind moving that ticket over to the new repo? I split it from Kevins so github would let us search the code in it

you are welcome, most of the time i try to lock new features so close to a release but it was so small that i even forgot to add it to the notes

New full release v0.11 Spaceport Changelog - Thanks to enkido and jwvanderbeck for your help. - BREAKING: BODY, SHIP:BODY, TARGET:BODY now all return a Body structure rather than the name of the body - BREAKING: Removed NODE:APOAPSIS and NODE:PERIAPSIS. They are now available in NODE:ORBIT:APOAPSIS - Basic RemoveTech Intergration - Added VOLUME:NAME to getting the current volume - Lists can now be populated with basic data that you can loop over or index [Full Info](/wiki/List/) - Bodies (eg Kerbin, Mun, Duna) - Targets - All Vessels other than current - Engines - Engines on the craft - Resources - All Ship Resources - Parts - All Ship Parts (slow) - Sensors - (eg Pres, Grav, Accel) - Elements - All flights connected to the active vessel - A Lot of bug fixes and refactoring - Constants (eg G, E, PI) are now retrieved using CONSTANT() rather than spreadout. - Commands resolve in order of descending specificity, rather than in the pseudorandom order they were in before - Added Math operators LN, LOG10, MIN, MAX.

New full release v0.11 Spaceport Changelog - Thanks to enkido and jwvanderbeck for your help. - BREAKING: BODY, SHIP:BODY, TARGET:BODY now all return a Body structure rather than the name of the body - BREAKING: Removed NODE:APOAPSIS and NODE:PERIAPSIS. They are now available in NODE:ORBIT:APOAPSIS - Basic RemoveTech Intergration - Added VOLUME:NAME to getting the current volume - Lists can now be populated with basic data that you can loop over or index [Full Info](/wiki/List/) - Bodies (eg Kerbin, Mun, Duna) - Targets - All Vessels other than current - Engines - Engines on the craft - Resources - All Ship Resources - Parts - All Ship Parts (slow) - Sensors - (eg Pres, Grav, Accel) - Elements - All flights connected to the active vessel - A Lot of bug fixes and refactoring - Constants (eg G, E, PI) are now retrieved using CONSTANT() rather than spreadout. - Commands resolve in order of descending specificity, rather than in the pseudorandom order they were in before - Added Math operators LN, LOG10, MIN, MAX.

Once i heard what the symptoms were, i was pretty sure it was a problem with execution contexts. It would have taken me much longer to find if enkido hadn't squashed it i love pull requests!

This is exactly what i was thinking about doing. As for compatibility with RSS, i think i should be able to retrieve these values and respect them.

If you are running the pre-release of v0.11 yes! I have some examples here: https://github.com/erendrake/KOS/wiki/List

Speaking of forgetting stuff. I had an excellent pull request from enkido that addressed this issue. https://github.com/erendrake/KOS/commit/38a54e08e78d5768d41f5f40d8814fd2eae4196a So i gladly deny credit for this fix.

This was an intentional change. I should have marked it with BREAKING in the changelog, in the future i will try to have smaller releases that i can remember everything i break

Ask and you shall receive: https://github.com/erendrake/KOS/commit/2c61c0919eb68a52555a24fafb4e83f56a85be88 There is a little more work to do to make it better but we should be able to use it in v0.11.1

Of course I have to head to work but if you keep coming up with cool features like that would you mind adding them to the backlog on github?

Understood, good luck with graduation! I am hoping to recruit a few people to help me promote and support the mod in ways that dont require direct code submission which is not for everyone. Gotya, I think i know why that would be and that is going to be a bear to fix. Ill add an issue in github.

That should be fixed now. I really dislike the wiki feature in github because it is not integrated into GIT you only get one wiki and keeping the readme linked to it apparently breaks once you branch.

@erbmur Sorry i crossed over to the other thread I have it listed as a bug https://github.com/erendrake/KOS/issues/27 let me know if that wording is correct

We have an upcoming milestone that will address this exact issue. To allow for docking we will have to add more direct access to the FlightCtrlState API.

Thank you very much for testing! So i assume you are using RemoteTech? I Keep forgetting to test manned kOS missions Here is my proposed compromise: If you dont have a connection through RemoteTech but you have a crew. You can issue local commands and write code locally but you can not copy from the archive?

Thank you everyone for letting me know that sounds fine to me. How cool! i am particularly excited to see what people do with Lists. You are welcome. If anyone wants to contribute to that documentation for content or examples. i would be very happy to accept pull requests