Albrecht Schlosser wrote:
>> In that doc it could link to the local and/or website docs,
>> eg:
>>
>> FLTK Docs:<A
>> HREF="file://path/to/localdocs/html/index.html">(local)</A>
>
> The above would be an autoconfigured path, or optional an expanded
> environment variable?
Good question, I'm not sure.
Since this could tie into the build system, which I know little
about, I'll just write the HTML, and leave this detail to one
of our build system experts ;)
Perhaps relative links would work; I assume fluid currently
'knows' the absolute path to the local index file, and if
relative links work relative to that, then that could work.
>> <A HREF="http://fltk.org/path/to/fltkdocs";>(website)</A>
> I guess, this would be fix for a particular FLTK version...
Yes, that would have to somehow be automatically managed,
or be a fixed link to a non-version specific fluid document
on the website.
I'm not sure autoconf is a good solution unless there's a
way to make it work on windows too. I think VS files can
refer to batch scripts, and DOS bat could be invoked to
update this info. DOS is a little clunky for file editing,
but I'll bet I could at least provide a script that does that.
Perhaps the substitution could happen as part of the script
that builds the tar balls? This would 'bake' the version# into
the html, so that nothing would need to be done at build time.
Otherwise, maybe just a 'generic' link to non-version specific
docs on the website for fluid that always lives in the same
location on fltk.org, and it could be a 'general usage' page,
with a link that points to the general FLTK docs page for all versions.
> You said that you wanted to write such a simple HTML file, right?
I can certainly write the simple fluid document.
That's a good start, and I can leave stubs, and we can iron
out the details later.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
