Bugzilla – Full Text Bug Listing
| Summary: | [General] Papyrus shall provide a welcome page | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Tatiana Fesenko <tatiana.fesenko> |
| Component: | Core | Assignee: | Tatiana Fesenko <tatiana.fesenko> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | Patrick.Tessier, rschnekenburger, sebastien.gerard, tatiana.fesenko, vincent.lorenzo, yann.tanguy |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 317587 | ||
|
Description
Tatiana Fesenko
I have just renamed the title of the task. The welcome page should be put into Doc Plugin. There is a org.eclipse.papyrus.doc project which holds documentation. It has a name as it is a plugin project, but it's not a _plugin_ project, it's just a project. I would like to make it a Doc Plugin for papyrus, defining all extension points and xmls for out documentation. As this is an important decision which could influence everybody I want to know your opinion. So, I can 1. Convert an existing org.eclipse.papyrus.project into our doc plugin. pros: In this case all doc files will stay there. This is a place that every developer knows. contras: It's a huge project where obsolete documentation could be stored. 2. Make another plugin to serve as our doc plugin pros: we will be sure that documentation stored there is up to date. (At least first several month =)) contras: we will have two projects for documentation, what is confusing we will have to either copy documentation from old plugin to a new one, or reference files from one plugin to another. Either choice is not good. I personally prefer choice 1 - to convert an existing oep.doc project into our doc project. But I am open to listen to your arguments. And for now I will keep my changes for the Welcome page in patches instead of committing it into SVN. It was decied to keep org.eclipse.papyrus.doc plugin as Papyrus doc plugin. All documentation not related to user doc will be moved to SVN /doc folder. Initial version of Papyrus Welcome page has been committed to HEAD. At the moment it contains defualt items (tutorals, samples, etc) and Papyrus labels and icons. Now I am inverstigating a way to integrate NewPapyrusProject Wizard into the welcome page (In reply to comment #4) > Initial version of Papyrus Welcome page has been committed to HEAD. At the > moment it contains defualt items (tutorals, samples, etc) and Papyrus labels > and icons. It also opens Papyrus perspective as default NewPapyrus Project was added to Getting Started subpage of the Welcome page NewPapyrusProject wizards closes Welcome page now before opening the WizardDialog The Create NewPapyrus Project action was added to Overview subpage of the Welcome page Fixed in Helios |