i understand that there are two types of xml files we're dealing with when working with ptp: the template xml files and the resulting krpano xml files.
plz correct me if i'm wrong: the template xml file are ptp specific and are parsed during build process to assemble the output krpano xml files. sometimes the template xml files contain krpano code chunks which are only copied into the result krpano xml file (e.g. menu button plugins).
ptp is absolutely great preparation tool for further code fine tuning by hand. especially arranging the panos, setting up the hotspots and keeping an overview about the whole project is a huge timesaver with ptp. alone setting all this hotspots by hand coding in krpano xml files is a pain.
but ptp (by now) only supports a basic set of features available in krpano. @photokina i talked with alexandre about e.g. integrating the google maps plugin in ptp. such a feature must be integrated in a project after
exporting all panos and by modifying the exported krpano xml files manually. if i need to re-export the project e.g. after an image editing on the panos, the ptp export naturally is overwriting all manually modified files. fortunately it doesn't replace the whole folder and additional custom files are left in place and untouched.so now my question, suggestion, request is:
is it possible to place a specially tagged area in the ptp template xml files where i can define e.g. includes or plugins for my own customization. the only requirement should be wellformed xml to not disturb what ptp is parsing during build process.
it would be ideal to have such an area at least at the beginning and at the end of the main template xml file. let me illustrate this with some fictional sample code based on Templates/menu/navigation-fullscreen-help.xml
<!-- this code block will be copied unchanged to the resulting main xml file -->
<include url="plugins/google_maps_and_some_other_own_stuff.xml" />
<plugin name="editor" url="tools/editor.swf" />
<plugin name="options" url="tools/options.swf" />
<!-- go on with usual ptp template code -->
of course every url path should be existing in the folder to where the project is exported. perhaps it can be treated in the same way you implemented [font=courier]$(STYLEDIR)[/font] in a kind like [font=courier]$(EXPORTDIR)[/font].
up to now all custom code inside the template xml file is ignored during the build process.
as i've some experience with code parsing / assembling (and with manual krpano coding as well) i think this shouldn't be too much work to implement this feature which makes ptp even more interesting for advanced users who want to tweak their projects without losing the possibility to re-edit the project without the need to re-integrate their own adjustments after each new ptp export.
this would allow ptp to rebuild the project as often as needed and at the same time to keep the manual custom code tweaking independent from these exports. ptp would get no notice from my own xml files, which are only important for the final project.
can i be of some hope to see this in the release?
thanx for listening
thomas bredenfeld - viennahttp://panorama-blog.com