|
Re: Eclipse UA panel March 7 at EclipseCon 2007 [message #468990 is a reply to message #468965] |
Thu, 15 February 2007 14:36  |
Eclipse User |
|
|
|
Here's a list of questions / discussion topics we "How We Learned to
Stop Worrying and Love Eclipse User Assistance" panelists came up with.
Any additions or comments would be appreciated, whether or not you're
attending.
1) Writers are getting more engaged with not only the help content but
the cheat sheet content, to encourage consistent presentation of
instructions to users. Are there any plans to create tooling to allow
help content to be converted into cheat sheet content or vice versa? or
possibly other solutions to allow this type of single sourcing? Maybe a
shared dtd?
2) What is the standard filetype for help content files? html, xhtml, xml?
3) We have many requests from users to be able to print multiple help
pages at once. Is this feature on the horizon for Eclipse UA?
4) What one User Assistance feature, not implemented in the current
version, would you most like to see in a future version of Eclipse, and why?
5) What additional UA customization options (e.g., help preferences)
would you most like to see in a future version of Eclipse, and why?
6) What UA content development tool (e.g., cheat sheet editor in 3.3)
would you most like to see in a future version of Eclipse, and why?
7) Do you have any suggestions for additional documentation, sample
projects, or tools that would make it easier or faster to author and
develop Eclipse User Assistance projects?
8) Do you have any suggestions for ways to make Eclipse User Assistance
development more efficient, whether changes or enhancements to the
Eclipse UA components, or best practices for UA developers and authors?
9) What do I have to do to hook the context-sensitive help up to my GUI?
10) What already-existing UA feature is most under-used, either by
authors or by users? Why don't people know about it or use it? What's
the value of using it? How can we get more people using it?
|
|
|
Re: Eclipse UA panel March 7 at EclipseCon 2007 [message #560257 is a reply to message #468965] |
Thu, 15 February 2007 14:36  |
Eclipse User |
|
|
|
Here's a list of questions / discussion topics we "How We Learned to
Stop Worrying and Love Eclipse User Assistance" panelists came up with.
Any additions or comments would be appreciated, whether or not you're
attending.
1) Writers are getting more engaged with not only the help content but
the cheat sheet content, to encourage consistent presentation of
instructions to users. Are there any plans to create tooling to allow
help content to be converted into cheat sheet content or vice versa? or
possibly other solutions to allow this type of single sourcing? Maybe a
shared dtd?
2) What is the standard filetype for help content files? html, xhtml, xml?
3) We have many requests from users to be able to print multiple help
pages at once. Is this feature on the horizon for Eclipse UA?
4) What one User Assistance feature, not implemented in the current
version, would you most like to see in a future version of Eclipse, and why?
5) What additional UA customization options (e.g., help preferences)
would you most like to see in a future version of Eclipse, and why?
6) What UA content development tool (e.g., cheat sheet editor in 3.3)
would you most like to see in a future version of Eclipse, and why?
7) Do you have any suggestions for additional documentation, sample
projects, or tools that would make it easier or faster to author and
develop Eclipse User Assistance projects?
8) Do you have any suggestions for ways to make Eclipse User Assistance
development more efficient, whether changes or enhancements to the
Eclipse UA components, or best practices for UA developers and authors?
9) What do I have to do to hook the context-sensitive help up to my GUI?
10) What already-existing UA feature is most under-used, either by
authors or by users? Why don't people know about it or use it? What's
the value of using it? How can we get more people using it?
|
|
|
Powered by
FUDForum. Page generated in 0.28031 seconds