Re: [FreeWRL] EAI documentation question

[Dave J. <dav...@go...>]

On 10 May 2010 18:47, Ian Stakenvicius, Aerobiology Research
<ia...@ae...> wrote:
> On 10/05/10 01:34 PM, John A. Stewart wrote:
>> Dave;
>>
>>
>>> I would make three suggestions:
>>>
>>> a) Move the .doc files to .html files permanently

Do others have any comments about this ?
1) I always have access to a text editor,but only some of the machines
here run a word processor (and only one of them runs MS WORD)
2) CVS can genuinely track the document.

>>> b) Insert all the .html files into a new area in the CVS tree, say a
>>> subdir called webtree with the same tree structure as the website
>>> c) Bundle a couple of expect scripts into the CVS tree as well, to do
>>> the upload to the website (*)
>>>
>> I think Ian might have better ideas on this than I. (probably many others here, too)
>>
>
> This sounds pretty good to me.  s/expect/export/
>
>> Does the webserver where the pages currently are support Server Side
>>> Includes? If it does, then is is even easier to maintain a consistent
>>> look.
>>>
>> Unknown, but I'd expect so.
>>
No, they do not.

>
> I think probably not (iirc there were security issues with SSI that were
> never resolved and so is usually turned off on web servers), but I do
> expect that it supports either php or asp, and we can do the same thing
> with that.

Sure

> Alternatively, it's not too hard to make the export scripts
> handle inserting common header/footer/formatting info when the data gets
> published.  Alternatively (2), a properly-built CSS file can handle all
> of the look-and-feel stuff, leaving the html files essentially bare.
>

OK, tested this.
1) They have closed off SSI
2) PHP works OK, sample file djtest.php contains <?php include('djtest.html') ?>

So, a simple template system will be usable by everyone.

Dave