> If the export function is implemented in Subsurface, then all this data > should be available and can be included in the produced output. So the > plan > is to have this output possibility as part of the result on this GSOC > project. Even better, if the HTML/JS part is almost there.
If the target is to produce static HTML as a frame and the JS within it which then provides the 'dynamic' part, then yes. To be explicit, this means that we more or less contain the whole log book data in one file (JS-file can of course be compressed). > Looks good. We just need to produce the HTML/JS from Subsurface with easy > to use interface, and no additional packages or installations (like PHP > would be in your current implementation) The PHP is merely to provide the XML->JSON conversion. If this can be done in Subsurface, then it is not needed. And I'm willing to put some hours in this on the JS-side. Alas my C/C++-days are over, having degenerated from there to Java->Perl->PHP in the last couple of decades. >, all self contained in Subsurface > installation package. As Dirk remembers to state, our average user is not > computer specialist :D Indeed. This however opens the pandora's box ;-) My feeling is that this requirement will shortly result in need to have automated uploads to various blog-softwares such as Wordpress. But maybe that is a concern for later (and other people :-). Poltsi -- Paul-Erik Törrönen "When science and the Bible differ, [email protected] science has obviously misinterpreted +358 40 703 1231 its data" http://poltsi.fi/ Henry Morris, father of 'modern creationism' _______________________________________________ subsurface mailing list [email protected] http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
