Import XML to XML

[mathrafal]

Hi folkets!

Just got another order for a 60+ panorama tour. I am not crowing there, but am terribly concerned about what happens a little down the line if and/or when I want to change things (which will happen).

With the Røros mega tour, I have changed my mind several times since publishing all 92 panoramas. These are little things that bug me, but which I am loathe to change since it means buggering around with FFC for 61 different folders.

What I want to know is if I can have the main elements (e.g. Load sequence, alpha, etc.) in a separate xml file which I can hand code (whoops! Sorry Mr T) when I want to alter small details.

If so, would anyone know the import coding?

Thanks in advance,

Jon

[mathrafal]

No ideas?

Jon

[Morten]

G'day Jon,

Have you looked at the FPP editor? I have very little experience with it but believe it may be a more economical way to edit your tour after it's initial build (in FFC). It think there are several users here that use it and may in fact provide a service to you. The fact is that once a tour becomes the monster size you have created, it is problematic to edit in FFC.

With bigger tours (not that I have anything that size) it may pay to square away all your design elements first (with the client) and let them know that from then on there will be a substantial cost to make changes.

Regards,

Morten

[mathrafal]

Heisann Morten!

Thanks for the reply, but I don't think I made myself clear.

The tour will be initially 60 or so panoramas that are separate, each of which will be launched from my Google Map interface.

This is quite a simple thing to so, since all I need is to Flashificate 60 individual panoramas.

However, I shall be using a uniform skin throughout, so there will be elements of each that will remain constant. The problem this brings to mind is the same as I found with the Røros tour, since if I want to change one single aspect of the skin or its functions, then I will need to do that 60 (or as in the case of Røros 101) times. This is a pain . . .

If all the skin elements and functions are contained in a master xml file, which is then imported to each individual xml, when such changes occur, it should be easy (lol) enough to just change the master file and everything else follows suit.

The question (I am not a programmer) I ask is how to achieve that import.

Best,

Jon

[Morten]

Ahhh sorry Jon.That is a different problem again.

One suggestion is that you name all the pano cubes the same and then just replace them in the tours. I imagine you could use an editor to find and replace any differences in the xml (i.e. google map references, start points etc.). If they are identical in all other aspects it should just be a matter of editing the template then replacing cubes and xml in each.

I hope this might be some help Jon.

Morten