Primarily @ Robby

At present when using Tellico's "Export to HTML" it creates a rather odd ( sorry Robby ) directory structure, would it be possible to have more control over this. (Even if it's a "hack" of some of the xsl files.)

Ideally, I would like to be able to separate the individual html files from the associated image (cover/poster) files.

Best illustrated by example...

This is the existing directory structure (export to individual files).



This an example of how I would like to be able to structure it. The actual sub-directory names are not important, it's the ability to separate html from fixed icons (pic) and the image files.



At the moment I'm manually moving the image files, then running kfilereplace on the html files to amend the image source and href paths...

I've looked at tellico2html.xsl and tellico-common, but to no avail, xsl is all rather foreign to me.


As an aside, what's the approximate release date of 2.3.9 likely to be?

metzman wrote:At present when using Tellico's "Export to HTML" it creates a rather odd ( sorry Robby ) directory structure, would it be possible to have more control over this. (Even if it's a "hack" of some of the xsl files.)

Ideally, I would like to be able to separate the individual html files from the associated image (cover/poster) files.

Your example has a lot of merit. But the HTML export is a mishmash of the C++ code and the xsl files. You can't get what you want without changing parts of the source code and recompiling. It's quintessential spaghetti code...

metzman wrote:As an aside, what's the approximate release date of 2.3.9 likely to be?

I wanted to get it out this past weekend, but I ran out of time. There are still a couple of minor bug fixes for some of the data sources.

robbystephenson wrote:But the HTML export is a mishmash of the C++ code and the xsl files. You can't get what you want without changing parts of the source code and recompiling. It's quintessential spaghetti code...

Just had a quick glance through "exportdialog.cpp" and "htmlexporter.cpp" for starters... First thought was maybe just hard code the path/filenames as I need them... You were fairly generous with the comments in the source code; always of help. Need to give this a bit more thought, my programming skills are extremely rusty I'm afraid. Likely I'll take the easy way out; write a bash script to just automate my current routine.

robbystephenson wrote:I wanted to get it out this past weekend, but I ran out of time.

Didn't realise it was that imminent - good news - many thanks indeed.

metzman wrote:

robbystephenson wrote:But the HTML export is a mishmash of the C++ code and the xsl files. You can't get what you want without changing parts of the source code and recompiling. It's quintessential spaghetti code...

Just had a quick glance through "exportdialog.cpp" and "htmlexporter.cpp" for starters... First thought was maybe just hard code the path/filenames as I need them... You were fairly generous with the comments in the source code; always of help. Need to give this a bit more thought, my programming skills are extremely rusty I'm afraid. Likely I'll take the easy way out; write a bash script to just automate my current routine. .

Right, it's pretty much all in htmlexporter.cpp