I'm planning to work on this tomorrow or the day after and I think that the first version will be a simple table with hardlinks on the images.
For the next versions what would you prefer I work on? Thumbnails, number of links per page, relative links, export to a directory with a copy of the files in a images dir for immediate use on a server web?
Have you any other requests?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the moment, export tools will remain as independant scripts, since I did not have
the time to include proper plugin support into VisLib. However, this is at the top of the todo list, and should be included, if not in the very next version, at least in 1.1.0. That is, something around two or three weeks.
As for the moment, my own priority job is to put *comments* into the whole bunch of code, since until that is done I am the only one to grok anything to it. Along this, I am writing the doc for the library structure API, that could be the first part of real code you may have to contend with while writing plugins. Should be available next week.
For the HTML export plugin, you will need parsing methods for VLB files. In C, almost everything is available (look up the Library.h file... or wait for the doc ^o^). But
I reckon you will probably prefer to write that sort of thing in Perl. As such, Perl parsing methods are still not available (though writing a .pm file with the needed constructs is
also on the todo list), but taking a look at the *reverse* methods in the directory import plugin could be useful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm planning to work on this tomorrow or the day after and I think that the first version will be a simple table with hardlinks on the images.
For the next versions what would you prefer I work on? Thumbnails, number of links per page, relative links, export to a directory with a copy of the files in a images dir for immediate use on a server web?
Have you any other requests?
For the moment, export tools will remain as independant scripts, since I did not have
the time to include proper plugin support into VisLib. However, this is at the top of the todo list, and should be included, if not in the very next version, at least in 1.1.0. That is, something around two or three weeks.
As for the moment, my own priority job is to put *comments* into the whole bunch of code, since until that is done I am the only one to grok anything to it. Along this, I am writing the doc for the library structure API, that could be the first part of real code you may have to contend with while writing plugins. Should be available next week.
For the HTML export plugin, you will need parsing methods for VLB files. In C, almost everything is available (look up the Library.h file... or wait for the doc ^o^). But
I reckon you will probably prefer to write that sort of thing in Perl. As such, Perl parsing methods are still not available (though writing a .pm file with the needed constructs is
also on the todo list), but taking a look at the *reverse* methods in the directory import plugin could be useful.