New versions, again... (for frame templates only, the list templates stayed the same)A "broken" image was displayed in the upper right corner on exported HTML pages when movie entries had no poster with them. Corrected that.Then I tidied up a little and "streamlined" the exported code. The stylesheets are in seperate files. The templates are a lot easier to maintain now and the seperate stylesheets offer new possibilities. Now there can be user selectable stylesheets (switching between stylesheets would even work without javascript). Therefore it will be possible with a single export template to provide different layouts (list only or fully detailed records, for example). I will implement that next week.

...and it worked! (I'm always amazed when the obvious works.) Maybe you could prepare a brief tutorial when you're done on how to use the templates provided, along with instructions for such modifications.

buah

Svenne, thank you for a really nice html export template. Don't blame me for not being clear enough to say that there should be only right (i)frame, while there wasn't actual need for a left one.Once again, really impressed with the result.

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.)

I see... The problem lies in the nature of iframes + some less than perfect browser behaviour:http://kb.mozillazine.org/Problems_printing_web_pages#Does_not_print_multiple_pagesInternet Explorer is not so different from Firefox. IE7 even printed a scrollbar (but it was of no use, I really tried hard but I only ripped the paper... At least I could prevent IE from printing scrollbars via CSS now...).Iframes (and frames) always where problematic when it comes to printing. One of two workarounds is what you did. The other is (at least in Firefox): right click into the iframe and tell the browser to print the current frame (choose "This Frame" -> "Print Frame").

I had quite a lot of other things to do, so it took a little bit longer... Here is the first version of an HTML export template for printing purposes. Since I really didn't have much time, consider this alpha...In Firefox you can choose between different print layouts: In the menu "View" go to "Page Styles" and you'll see a list to choose from. If your Database is huge it might take some time for the browser to reformat the whole thing (same with the browser's print preview). So be patient. Choosing different styles is possible in all common browsers and in IE8 or newer. It will work with IE7, too, but that'll need some javascript. I'm planning to add a menu to the exported HTML anyway, to make the different settings more obvious.

It became quite tricky, because both Internet Explorer 7 and 8 are buggy. With IE8 at least you can choose between alternate stylesheets and they will be rendered on screen, but while printing the whole thing alternate stylesheets are ignored... Ok, at last I found a workaround and now everything's fine in IE (as long as JavaScript is not deactivated, of course). Tested it with IE8, but with IE7 it should be ok, too, since problems of IE7 were the same.Firefox is fine anyway.Hope you like it...

I made some changes to the "HTML Print Layout" template:- fixed some problems with the browsers refresh button- in "no details"-view the information on genre now is ommitted. Replaced it with file properties (filesize, codec, languages)- added "show/hide movie id" and "show/hide file properties" to the "Print Layout" dialog

This is coming along nicely. Now I wonder what happened to all those who were looking for a "print" capability.

The print layout control doesn't seem to work properly in the "no details" view (in Firefox, if that matters)...

movie id appears whether selected or not

selecting movie id causes genre to disappear

show file properties doesn't work unless movie id is also selected

I think you should keep genre. It's still there, but your post implies you intended to remove it. It could be set apart from file properties by using a different font (or simply not italicizing)—should they both be selected.

It would also be nice if sequential numbers could be used instead of, or in addition to, id. A numbered "no detail" view could then be used as a table of contents for a detailed view.

I can't reproduce that behaviour, works fine here on Firefox 3.6.3... PVD never overwrites existing files (except the main html files and the poster images). Did you export to a directory where the subfolder "htmlprintfiles" already existed? Old versions of the stylesheets would be a problem. Try to delete "htmlprintfiles" and then do a fresh export with "HTML Print Layout". Please let me know if it works afterwards.

Ok, I will add sequential numbers soon.I added ID, cause you can use the ID to index your DVDs and stick the number onto the cover of every DVD. Makes it easier to find the right one...

Ok, no sequential numbers then. Would have been a little bit more difficult to achieve than just showing/hiding things. But if someone really wants this, I could add the feature to reindex within the exported file (so you won't loose your original IDs in PVD). By the way, if you sort your database alphabetically prior to export, there might be no real need for a table of contents with numbers. But if you'd like to have it, just tell me.

Yes, some poster images will span over two pages in Firefox as long as you don't choose "one page per record", but Internet Explorer for example handles this in a different way and avoids to split the images. So I don't want to force the "one page per record" setting, but instead let the user decide what to do. A CSS rule could be added to tell the browser never to split the DIV-tag containing the poster ("page-break-inside:avoid;"), but Firefox still ignores this. Might be implemented in near future though.