| 1016 |
|
|
| 1017 |
|
|
| 1018 |
|
|
| 1019 |
<h3></h3> |
<h3> Q&A </h3> |
| 1020 |
|
|
| 1021 |
|
<pre> |
| 1022 |
|
(Q) I am curious about the fact that infoviews have gone away. How will |
| 1023 |
|
different views of the infoset work now? |
| 1024 |
|
(A) We need to gather more feedback from the users to understand what is really needed |
| 1025 |
|
to accomplish by using views. This document deals mostly with building TOC's, without |
| 1026 |
|
making too many assumptions about their visual representation in the help view. |
| 1027 |
|
We have been discussing some ways to include/exclude certain TOC's under certain |
| 1028 |
|
conditions, for a role-based presentation of help, but we're still looking for input |
| 1029 |
|
from the users of the technology. |
| 1030 |
|
|
| 1031 |
|
(Q) And if infosets are gone, will there be any way of titling a doc web? |
| 1032 |
|
(A) What is the meaning of a doc web? Is it all the docs provided by an eclipse-based |
| 1033 |
|
product? Theoretically, all the plugins contributing |
| 1034 |
|
help are part of a doc web (that of the current eclipse session). If you think that |
| 1035 |
|
you may install two eclipse-based products then what kind of scenario are you looking |
| 1036 |
|
at that you need to differentiate between the two "doc webs"? |
| 1037 |
|
|
| 1038 |
|
(Q) I am also a little confused about the statement that properties files, both doc.properties and |
| 1039 |
|
contexts.properties, go away. What are they replaced by? |
| 1040 |
|
(A) The assumption here is that the xml files (toc.xml and context.xml) will be sent to |
| 1041 |
|
translation and packaged in their own fragments just like the translated html content. |
| 1042 |
|
This also allows for having different tables of contents on different languages. The |
| 1043 |
|
drawback is that last minute changes in a TOC will have to be propagated to all |
| 1044 |
|
the translated toc.xml files. |
| 1045 |
|
</pre> |
| 1046 |
|
|
| 1047 |
|
|
| 1048 |
|
|
Parent Directory
| 
Revision Log
| 
Patch