Architecture not clear

Since you have installed an extra chapter in the forum in which users are encouraged to give their feed-back to the way you explain everything about SPi-V - and obviously everyone seems to be happy with it I must be the only exception (which I cannot really believe).

I will be giving my feed-back because I do have difficulties in understanding und I do have proposals how people like me (photographers with limited knowledge of dealing with programming) could be helped.
And since not every person who produces 360° panoramas and would love to present them with Spi-V has the necessary background in programming I could imagine that there are quite a few who give up, missing tutorials for dummies.

CONTENT OF DOCUMENTATION
I believe to understand how this documentation started and grew. You explained some basics and then added links here and there as time went by, explaining more and more.
This is fine - but I feel that all these information (from documentation and the information in the Downloads chapter) need to be brought into logical order and this order should be shown in a detailed directory.

Like that I find the structure rather confusing and it is hard to find an article I have once read and want to read again.

FEED BACK OF USERS
I find it very positive and helpful that users can directly add their comments, problems and proposals next to an article.

UNDERSTANDING BASIC ARCHITECTURE
EXAMPLES
Even though I managed to create my own websites, using many Flash elements, and I managed to embed my panoramas in QuickTime and using Java players - I did not manage to find access to the architecture of the different type of files and elements which you use in the SPi-V world.
(Honestly, I have spent quite some time and tried hard. I read and read and read and in the end I am totally confused.)

What would help?

1. Since those who are have no problems working in the SPi-V world should not be bored with new articles that particularly take care of people with only little experience in working with HTML, PhP, Java etc. - a special section might be fine.

2. I would love some graphics which explain the architecture (what are the basic files and elements, and how new files and elements are embedded when new functions are added.

And if there were functioning examples (downloadable folders with all the necessary files) for different constructions it would be great.

I know, you do have these downloadable examples but I do not find access to them because I am missing basic understanding.
e.g. I have downloaded the "simple tour folder". Inside I find files and folders which obviously need to be combined with others - but which ones? And how combined?
At least I cannot play the simple tour by only using the files provided in the "simple tour folder".
What is inside that folder certainly is fine and sufficient for many users. But please provide additional downloads with folders which contain EVERYTHING necessary for running. Then the entire structure would become clear.

In the download section / Minimal XML demo I can click on the "minimal.xml" button and the panorama opens. When I download the file and klick on the "minimal.xml" file (trying to open it with the same Netscape 7.2 browser on my Intel Mac) the panorama does not open but the browser shows me the script of the xml file.
I have no idea why is that so.

3. I can see how in some parts of your documentation you do explain step-by-step. That is very well done and works fine. In other sections I get entirely lost. No step-by-step guide. And many new vocabulary I have never heard. (by the way, a glossary would be fine).

4. An idex would be also very helpful, listing different features (e.g. FOV, hot-spots, sound, ...) and providing links to the individual articles and tutorials and downloads, containg examples.

I do understand that you rather like to dedicate your time to still improving and extending SPi-V - than to work on documentations and tutorials.
But maybe someone else could do that job for you. Someone who sufficiently understands the SPi-V technology and who, at the same time, has the ability to explain most clearly.

Now, after having complained so much: your SPi-V engine indeed is a wonderful tool to present panoramas. Thank you for this great developement!