Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312236 - [General] Papyrus shall provide a welcome page
Summary: [General] Papyrus shall provide a welcome page
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Tatiana Fesenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 317587
  Show dependency tree
 
Reported: 2010-05-10 06:50 EDT by Tatiana Fesenko CLA
Modified: 2011-01-03 03:33 EST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tatiana Fesenko CLA 2010-05-10 06:50:21 EDT
Create a Welcome page for Papyrus. It should be opened when the user opens Eclipse with installed Papyrus first time. The Welcome page sh. contain a button that creates 'New Papyrus Project'.
Comment 1 Sébastien Gérard CLA 2010-06-16 02:58:14 EDT
I have just renamed the title of the task.
Comment 2 Tatiana Fesenko CLA 2010-06-18 09:19:57 EDT
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.
Comment 3 Tatiana Fesenko CLA 2010-06-21 10:20:21 EDT
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.
Comment 4 Tatiana Fesenko CLA 2010-06-21 10:22:11 EDT
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
Comment 5 Tatiana Fesenko CLA 2010-06-21 10:22:58 EDT
(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
Comment 6 Tatiana Fesenko CLA 2010-06-24 05:06:33 EDT
NewPapyrus Project was added to Getting Started subpage of the Welcome page
Comment 7 Tatiana Fesenko CLA 2010-06-24 05:46:49 EDT
NewPapyrusProject wizards closes Welcome page now before opening the WizardDialog
Comment 8 Tatiana Fesenko CLA 2010-06-25 10:43:31 EDT
The Create NewPapyrus Project action was added to Overview subpage of the Welcome page
Comment 9 Tatiana Fesenko CLA 2011-01-03 03:33:52 EST
Fixed in Helios