Re: The Tutorial That Would Not Die
>The common content file would be for example an enhanced HTM, or other
>format we create to hold the actual tutorial. The user will download a
>viewer specific to it's OS and the content file. Contents can be then
>actualized independent of the viewer and vice-versa. The viewer can also
>exploit all the funcionality of the target OS. Thing like Windows
>winhelp.exe (the viewer) and the .hlp files (the content files).
>
Probably HTML would be the best choice, so it can be viewed by any sort of
tutorial or a browser, regardless of platform. We would need to create an
editor that would make maintaining this large file painless, in case we need
to update it as new features of Euphoria comes in.
David Gay
|
Not Categorized, Please Help
|
|
