konakid wrote:

Bump!!!

????

best, Klaus

MikeMcFarlane wrote:

Hi, second question of the night. I'm finding Panotour Pro really useful for constructing large complex tours, but it is apparent from the outset that a lot of xml coding is necessary to produce something special. That's fine. I've got my head round creating themes which improve the look a lot. However, the full version of krpano offers a lot more control and plugins, such as google maps, which are really appealing.

Kolor has promised lots more 'plug-in' type functionality via the GUI in the next version, including Google maps support .

As you will be aware, PTP is essentially a command code generator for the krpano player and as such will support all the functionality of which ever version of the krpano player it incorporates; but not all that functionality can be accessed via the PTP GUI.

I'm interested in the sort of workflow people are using. Do people start in Panotour then 'polish' the xml using krpano plugins etc, or are the more complex tours just created from scratch in xml?

I think people here would use PTP to create the basic tour and then hand code to embellish it.

If you also have a krpano license I guess you could use a MAKE VTOUR droplet as an alternative starting point, although I think those droplets generate a very different structure of code than PTP, making heavy use of scenes.
http://krpano.com/docu/xml/#scene

If you are using Panotour to start, are there any pitfalls, problems, dubious code it produces etc?

The main thing to be aware of is that code added by any means other than editing templates will be overwritten (and lost) if you later rebuild the tour. But I'm sure you know that.

Can I add the full version plugin code into the themes xml to automatically generate the tour, or will I always need to edit xml at the end?

I don't know.