yes it is very close to the final idea that i have.
Good - the trade-off is (always) going to be between quick-n-easy (in this case, creating the map navigation via the APT/PTP GUI) and incorporation of additional features which will require learning of krpano commands and command syntax and hand editing XML command files.
There is currently a further potential 'downside' to adding features by editing the XML files produced by APT/PTP.
If you re-export the tour after editing the XML files then either your edited XML files will be overwritten and you'll lose all your customisation, or you will save under another name and have to add your customised code all over again.
The only exceptions to this are if you can incorporate your custom code by editing the template files, but of course if you do this the customising will be applied to all tours created using those modified templates.
i understand that i don't understand the "krpano Flash Panorama Viewer" relationship.
but i am on the way.
2 days ago i didnt know what krpano is ...
It took me a while to get my head around it in the beginning too. And I'm still very much in learning mode.
But without the development of Autopano Tour and now Panotour I doubt I'd ever have managed to get to grips with krpano at all. I am not a programmer and, although I greatly admire those with such talents, I have never aspired to be one. Instead I lobby for more features to be added to APT and PTP.