To both rick and mgpw4me: That's how it should be.
I will prepare a brief tutorial, but I won't give an introduction to HTML and CSS. Concerning the HTML part you can copy and paste lines, change them and see what happens. I was trying to keep that as simple and compact as possible. Perhaps I should mention that the list templates have some headlines that you can't see with standard styles applied, so don't be surprised.
After you finished to change something you should test if the HTML is still valid (that every tag has its closing tag, and so on), especially if you're less experienced. You can do that here:
http://validator.w3.orgI tried it myself a few minutes ago and saw that I used XHTML syntax in one line and I'm into (barrier-free) web design for years now... I changed that now, but I'm shure you won't see any difference in this case, most browsers are kind enough and don't bother.
CSS is a bit more complicated, because the different browsers still (mis)interpret some things in different ways, but people could change colors or fonts quite safely. Nevertheless I would advice them to read one of the CSS tutorials you can find easily on the web. The majority of users won't even know about hexadecimal values or RGB colors, for example, and I don't want to write a documentation raising more questions than giving answers to those. Nevertheless, everyone who wants to should dare to mess with the source code. There's no reason not to try and if they do something wrong their computers won't explode afterwards... although in some cases I'd really like that.
You can validate CSS here:
http://jigsaw.w3.org/css-validator/To buah: Thanks, I like it that you like it (like it is, like).
And there only is one iframe, the list part is a simple <div></div> containing an unordered list (<ul></ul>). By the way, it would be possible to have a "real" frameset generated with templates (but the iframe looks nicer...). I just wasn't aware that nostra implemented a copy command that can be used. It's documented
here, but I overread that.
Since it is possible to store all the CSS in seperate files now, I can do more complex things with so called alternate styles (that have to be in different files).
Concerning PVD export templates in general, some stuff seems not to be documented. Nostra even introduced
something like functions, but I don't know if there are more, what they do and how they work. By the way, is there a possibility to define some kind of (constant) global variables in the %OPTIONS% part, that could be used throughout the template? Something like
#define in C++? It doesn't need to be that complex, simple string replacement would do (like {#StringReplace...}, just not applied to %values but to the template itself). Sometimes missed that, but just a little bit.
New versions of the templates... I only transformed the single occurence of XHTML into HTML, no big deal...
(The two language versions of the iframe template have some files in common. When extracting the second one to the same directory you surely will be asked if you want to replace files. You can safely click yes, those files are the same anyway. Both language versions will work properly afterwards.)
