Export templates: variable for filename chosen in filter dialog

[svenne]

A feature request for export template development (http://www.videodb.info/help/hlp_export.html)...

When developing export templates, in %OPTIONS% section there seems to be no way to access the filename that was chosen by the user in the "save as" dialog. It would be neat to have the filename without extension for additional processing:

As it is now, all static files (stylesheets, background images, etc.) may be copied to a subfolder (which can go by a name like "HTML-files" or whatever). The subfolder would be created along with the exported file. I'd like the name of this folder to depend on the name of the exported file. So what I want to do: If the user chooses "peter's database.html" as export filename, I'd like to copy all static files to a subfolder called "peter's database_files". Hence it would be obvious that both belong together. In addition to that, Windows would automatically link files and folders named that way and treat them as a pair:
http://paulelso.wordpress.com/2006/09/20/xp-folder-option-managing-pairs-of-web-pages-and-folders/

Maybe you can add a new variable for the %OPTIONS% section providing the users chosen filename without extension and perhaps, just in case, also a second one providing the full filename (or the extension alone)?

If %fname% would be the variable for the filename without extension, something like this shall work:

Code: [Select]

filter="HTML Files|*.html;*.htm"
copyfile="template\style.css<->"%fname%_files\style.css"
imagepath="%fname%_files\images\"
Would be really great.
And by the way, thanks a lot for all your efforts, of course!!

[nostra]

Added to TODO list

[svenne]

Great, I just saw that it made its way into the newest version of the export plugin!  

It works well with copyfile, but when used with recordfilename and imagepath no records or images are exported...  
recordfilename="%fname%_files\movie%id%.html"
imagepath="%fname%_files\images\"

And I just didn't consider until now: I will need another thing to be able to use it properly...
I need to have access to %fname% outside the %OPTIONS%-part of the template, too. I need it for links to subpages and to be able to include the stylesheets, for example. Something like this:
<link rel="stylesheet" type="text/css" href="./{%value=fname}_files/css/main.css">

Would that be possible? Thanks in advance, of course!!

[nostra]

recordfilename="%fname%_files\movie%id%.html"

It is not support for recordfilename

imagepath="%fname%_files\images\"

Should work actually, but I will recheck it

And I just didn't consider until now: I will need another thing to be able to use it properly...
I need to have access to %fname% outside the %OPTIONS%-part of the template, too. I need it for links to subpages and to be able to include the stylesheets, for example. Something like this:
<link rel="stylesheet" type="text/css" href="./{%value=fname}_files/css/main.css">

Would that be possible? Thanks in advance, of course!!

No problem

[svenne]

Ok, just checked it... it works fine with imagepath!! Sorry...
It didn't work if used with both imagepath and recordfilename, but the problem was solely the use in recordfilename...

I just saw you didn't add %fname% to recordfilename but recordtemplate. I can't imagine any use in recordtemplate, because the path in recordtemplate is the source path in the Plugins\Templates folder of PVD and that can never be dependend on the filename chosen in the "save as" dialogue. Am I wrong?
Would be great to have that in recordfilename to be able to store all exported files in the subfolder "%fname%_files".

[nostra]

Done.

Now you can use %fname% and %fext% in recordfilename as well and you have special values

Code: [Select]

FileName {%value=233}
File Extension {%value=234}

[svenne]

Just perfect!    Thanks!

I modified my export templates now...

[nostra]

You are welcome. Thx for the great templates

[rick.ca]

Thx for the great templates.

They are nice, aren't they? I think you should add a "Print" item to the File menu that simply calls HTML Print Layout. That will be the answer to any tree-killer who asks for a print capability.

[nostra]

You know what, why not. Maybe I will do this in 1.0

[svenne]

That you like 'em that much truly feels good...  

Maybe it would be strange if you click on "print" in PVD and a "save as..." dialogue opens up instead of a printer dialogue...
So if you decide to add a print item that calls my export template (would be kind of a great honour to me, of course ), you might want to override the "save as..." dialogue and just export the file to temporary files instead... after clicking "print" the page would pop up in the user's default browser. I added a "Print" button to the exported page to make things more obvious.

By the way, and completely apart from this, I almost can't await PVD version 1. I'm sure it's quite a lot of work, though...

[nostra]

Yes, I would need a special handling for your templates

By the way, and completely apart from this, I almost can't await PVD version 1. I'm sure it's quite a lot of work, though...

I hope it will be great. Unfortunately the work is not going too fast because of the lack of time :/

[rick.ca]

Yes, I would need a special handling for your templates

What have I started?

I suggest the template configuration include a "Use as default print template" button. And yes, using the "Print" command should bypass the "save as" dialog and use a temporary location. The same template could still be used from the Export menu if one wants to print and save the report.

[nostra]

What have I started? Lips sealed

As always