Tactical AI Kit - Best way to release an update?
by Bryce · in Torque 3D Professional · 01/14/2014 (8:40 pm) · 8 replies
Hey guys, looks like I'm alive and back on the face of the earth after all!
I'm finalizing the long overdue TAIK update right now, and while I hammer away at updating the documentation, I'm met with a big question:
HOW?
Now, I could take the easy way out and just dump the new code out there. But what about existing users? How do I handle users that bought the original AI Kit, merged it into their code, and probably changed a lot since then? Is there any sort of merge utility, or something along those lines, that can make the update process easier for users?
I have no idea if I'm saying anything useful right now. Help is appreciated!
-Bryce
I'm finalizing the long overdue TAIK update right now, and while I hammer away at updating the documentation, I'm met with a big question:
HOW?
Now, I could take the easy way out and just dump the new code out there. But what about existing users? How do I handle users that bought the original AI Kit, merged it into their code, and probably changed a lot since then? Is there any sort of merge utility, or something along those lines, that can make the update process easier for users?
I have no idea if I'm saying anything useful right now. Help is appreciated!
-Bryce
#2
As for code stuff - what's the kit's API like? (Actually I could check it since I own the thing, but anyway, you have to ask yourself this.) What will users have to change? Surely on some level they just need to replace the TAIK files. If they do that, what methods will no longer exist? Have any changed names? Or do they work differently? Ah the world of software maintenance.
Anyway, I encourage you to think about your kit in terms of its 'public' API. What bits should users be actually using, and how have those bits changed? The most useful form of help might be notes about what these changes are and what users need to do differently with the new code.
New features, document as usual and people may start using them.
01/15/2014 (3:32 am)
HOLY BLUE SMOKE, BATMAN! Bryce's back! My word it's good to see you. You had us worried :).As for code stuff - what's the kit's API like? (Actually I could check it since I own the thing, but anyway, you have to ask yourself this.) What will users have to change? Surely on some level they just need to replace the TAIK files. If they do that, what methods will no longer exist? Have any changed names? Or do they work differently? Ah the world of software maintenance.
Anyway, I encourage you to think about your kit in terms of its 'public' API. What bits should users be actually using, and how have those bits changed? The most useful form of help might be notes about what these changes are and what users need to do differently with the new code.
New features, document as usual and people may start using them.
#3
01/15/2014 (3:45 am)
Great to see you back..I agree with Jolinar one of those he suggested would be a good choice. 
#4
That's exactly what a shapeshifting Reptoid impersonating Bryce would want us to believe! ;)
01/15/2014 (6:33 am)
Quote:
Hey guys, looks like I'm alive and back on the face of the earth after all!
That's exactly what a shapeshifting Reptoid impersonating Bryce would want us to believe! ;)
#5
Its these small hiccups in the shapeshifter's conversations that allow us to be one step ahead of their machinations.
Bryce,
It is an awesome thing to see a developer concerned with all of the things that you posted. I hope the best of luck to your product and the recognition that should follow.
01/15/2014 (9:52 am)
Excellent point Steve,Its these small hiccups in the shapeshifter's conversations that allow us to be one step ahead of their machinations.
Bryce,
It is an awesome thing to see a developer concerned with all of the things that you posted. I hope the best of luck to your product and the recognition that should follow.
#6
It's great to see you alive and well, although as Steve as suggested. A shapeshifter as I like to think possibly a snatcher...
I hope all is well in your life. T3D has changed a bit we got a few different branches of the engine happening, the GREED engine, and Winterleaf's OMNI. That changes the field a fair bit.
I am really keen to see the new update for TAIK.
Glad to see some concern and thoughts for users to upgrade their existing code base. WinMerge etc is normally the way to go in my opinion.
01/15/2014 (3:25 pm)
Welcome back Bryce!It's great to see you alive and well, although as Steve as suggested. A shapeshifter as I like to think possibly a snatcher...
I hope all is well in your life. T3D has changed a bit we got a few different branches of the engine happening, the GREED engine, and Winterleaf's OMNI. That changes the field a fair bit.
I am really keen to see the new update for TAIK.
Glad to see some concern and thoughts for users to upgrade their existing code base. WinMerge etc is normally the way to go in my opinion.
J0linar
welcome back
Regarding the changes in T3D 3.5 MIT, navmesh was updated for the latest MIT Version, however i doubt that you will have issues to port your stuff over, anyways here are some tools for diff/merg.
There is meld
meldmerge.org/
there is a precompiled beta for windows
and it works straight forward
and i think you know WinMerge
winmerge.org/
well whats left to say, actually nothing
just nice to see you back and we all look forward to the update
On a side note, you will notice that i was a bit harsh in one of your blogs - however time passed, noone got harmed and you are back and that is all that matters, right?