Re: [platform-ua-dev] BuildHelpIndex ant task problem in 3.2

["Curtis D'Entremont" <curtispd@xxxxxxxxxx>]

Hi Pierre,

Glad to hear things are working out.

What if xhtml documents with dynamic content had
a specific "dynamic 
content" meta tag in their head element:
ex: <meta name="DynamicContent" content="true"/>

Would it be better, performance wise?

It certainly would. This
is one option we thought about and we might use this in the future. For
now we're in end-game 3.2 so probably not enough time to do this.

I wonder if Internet Explorer is XHTML 1.0 compliant...

I don't think it's 100% but
it seems ok for most purposes. Everything I've thrown at it so far it seems
to accept, with the exception of a few things like having an XML declaration
at the top <?xml ...> (it shows the XML markup).

Thanks,
Curtis d'Entremont
Eclipse User Assistance
IBM Toronto Lab

Phone: (905) 413-5754
E-Mail: curtispd@xxxxxxxxxx

"pierre _" <pican123@xxxxxxxxxxx>
Sent by: platform-ua-dev-bounces@xxxxxxxxxxx

07/04/2006 03:25 AM

Please respond to
"Eclipse Platform User Assistance component developers list." <platform-ua-dev@xxxxxxxxxxx>

To	platform-ua-dev@xxxxxxxxxxx
cc
Subject	Re: [platform-ua-dev] BuildHelpIndex ant task problem in 3.2

Hi Curtis,
thank you so much for answering all my questions. I feel better already
:)
Integrating our doc plugin into Eclipse 3.2 won't be as complicated as
I 
first imagined.
I added some comments to your answers.
Regards,
Pierre

>Shouldn't you rather detect xhtml documents that use dynamic content
>specific markup?
>
>- It can, but there would be a significant performance cost. For example,
>if you only have one instance of dynamic content at the very end of
your
>long document, it has to scan through the entire document just to find
out
>whether it has dynamic content.

You're absolutely right.

What if xhtml documents with dynamic content had a specific "dynamic
content" meta tag in their head element:
ex: <meta name="DynamicContent" content="true"/>

Would it be better, performance wise?

>- While it is true that it now contains eclipse-specific content, browsers
>must still be able to handle the xhtml and ignore the extra
>eclipse-specific content. So it should not break any browsers as long
as 
>they're compliant.

I wonder if Internet Explorer is XHTML 1.0 compliant...

Btw, how are you gonna overcome the problem mentioned at the bottom of
this 
page:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-doc-home/docs/EclipseStyle.htm

>Can xhtml files and html files coexist in the same documentation plugin?
>
>- Yes.

Then the XHTML conversion tool will have to be really careful when (and
if) 
link updating is implemented:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=135069

So as to not change a link from a non-javadoc file to a javadoc file, for
instance.


_______________________________________________
platform-ua-dev mailing list
platform-ua-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ua-dev