Hello. As I say yesterday, I am working on some more things for the html export
Now the current status (not yet pushed to my branch) - Verbose option: added. I added this option so it is possible to have a trace of the execution of the program. I think it is a good thing if the export is executed by a cron job, to have a complete report. - Template sistem: work in progress. It is feasible. I have a working solution based on the idea to put all the html related part in a separated directory, where every subdirectory is a template. The structure is like this: be |--libbe |--... |--template |--default |--template_1 |--... This approach is much better then my previous idea to have the possibility to pass just the css file as option, since: 1) it clearly split the application logic from the presentation logic 2) it keep the size of the source code small 3) it allow to change the look without the need to modify the source code 4) eventually it allow to have a more complex html output (like comment that can collapse via javascript and so on) The only showstopper is where to put the template directory once be is installed. Any suggestion ? It can be put in the interface directory to keep coherence i think. Once I finish the implementation of the template system, I think that for now the html export is complete and ready to be merged (if everyone agree). The next udpdate to the interface will be done once I finish the work on the target status and due date (as specified in bug 22b). bye Gianluca _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
