Hi,
Yep!
Using ArrayMaker, this is possible, and would work very well.
https://hutonggames.fogbugz.com/default.asp?W715Using XML and XPath would be even better:
http://hutonggames.com/playmakerforum/index.php?topic=2583.0Now, the problem with any of the above solution is that PlayMaker doesn't support any internal translation of strings. This would be very useful indeed to flag a string variable or any variable really to be "pre processed" when a fsm needs it.
So currently, you will have to have extra steps manually performed to translate.
Else, you can modify the actions you are using to implement a translation. Actually, if your project has a serious budget, I would even consider writing a framework specifically for that, that you wold use in all your actions, so that querying for a fsm variable, would be done via this framework and it would simply check if there is a translation and return it if present.
something like:
string myString = TranslateMaker.TranslateString(MyFsmString.Value);
instead of
string myString = myFsmString.Value
If you take this approach, you completly remove the need for any Fsm to do the translation, it's all done within the actions themselves ( and will be a lot more efficient as well)
Now, you will find that sometimes you want a string to be translated, and sometime you don't.. for this, you will have to implement this in your fsm design ( like any other scripting environment), again, if playmaker would implement a translation system, we would likely be given a specific UI to flag a string for translation, within the action UI. That would be so great!
Hopefully in a near future, Playmaker will open it's action UI interface, and this kind of implementation will become possible for use developers, to redesign the string field and add more features in it.
bye,
Jean