Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] ISV guide for WTP


Eclipse help usually has two audiences, end users, and ISVs. The end users will be using WTP to create 'web artifacts'. ISVs will be extending the tools provided in WTP. The docs written for the different audiences are distinguished in the Eclipse projects with the extensions .doc.user and .doc.isv so companies using the docs can easily choose which plug-ins they want to provide to their users.

There are three possible formats for providing the ISV information for WTP. I would like to discuss which is the most appropriate for this project.
1. Provide a single guide for WTP
2. Separate the information for ISVs into WST and JST guides
3. Create separate guides for each component

I'm not sure if companies will use or deliver WTP as a whole, or if they will be able to choose which tools for extending components that they will provide in a product. I'd like to decide the format at today's WTP meeting.


The user documentation will be componentized as is standard for Eclipse projects.

Thanks,
Susan Yeshin

Rational Tools Information Development
IBM Toronto Lab
D3 - 446
syeshin@xxxxxxxxxx
(905) 413-3662
t/l 8-969-3662


Back to the top