Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] RE: Papyrus Themes for organizaing the Plan

I must admit, I'm a little fuzzy on these categories, but I see the backbone as an infrastructure for integrating editors for various "language" editors, e.g., for UML, SysML, etc., and so it seems to be somewhat related to extensibility. I'm open to putting either or both of these under (a) different theme(s), but preferably something other than "General" which seems too... general. :)

Kenn

On Mon, Sep 28, 2009 at 10:54 AM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote:

What is the link between Backbone, Metatooling and the theme extenssibility ?

 

For usability, why not.

 


De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Kenn Hussey
Envoyé : lundi 28 septembre 2009 16:39
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] RE: Papyrus Themes for organizaing the Plan

 

Sebastien,

 

Personally, I'd prefer to see some of the categories under "General" be left as themes unto themselves. For example, something more like this:

 

Extensibility

 

    - [Backbone]

    - [Metatooling]

 

Scalability & Performance

 

Usability

 

    - [Team Working]

    - [Model Explorer]

    - [Sash Editor]

    - [Property View]

    - [Palette]

 

 

Cheers,

 

Kenn

 

 

On Mon, Sep 28, 2009 at 10:13 AM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote:

So I propose the 4 following themes and for each theme, I include a list of prefixes for bug name:

UML Diagrams

-          [All diagram]

-          [Class diagram]

-          [Composite structure diagram]

-          [Component diagram]

-          [Profile diagram]

-          [Use case diagram]

-          [State machine diagram]

-          [Protocol state machine diagram]

-          [Activity diagram]

-          [Sequence diagram]

-          [Communications diagram]

-          [Interactions overview Diagram]

-          [Timing diagram]

Customization

General

-          [Extensibility]

-          [Scalability & Performance]

-          [Usability]

-          [Team working]

-          [Papyrus metatooling]

-          [Model explorer]

-          [Sash editor]

-          [Property view]

-          [Palette]

-          [Backbone]

Documentation

-          [Documentation - User]

-          [Documentation - Developer]

 

 


De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Kenn Hussey
Envoyé : lundi 28 septembre 2009 15:58
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] RE: Papyrus Themes for organizaing the Plan

 

Guys,

 

While I think that these are great categories for organizing Bugzilla items, e.g., as a prefix to the Bugzilla subject, for project planning purposes the themes tend to be coarser grained. For example, you might consider grouping all of the diagram-related categories under one "UML Diagrams" theme, or perhaps even use the "Compliance" theme that other projects are using. Based on this list, I'd suggest the following themes (or something similar) be used for the plan:

 

UML Diagrams

Customization

Extensibility

Scalability & Performance

Usability

Collaboration

 

Note that the "final" plan is actually due this Wednesday, September 30, so I'd suggest moving a little more quickly with regards to getting the Bugzilla items updated to be part of the plan, even if it's just a "first pass" at this point.

 

Cheers,

 

Kenn

 

On Mon, Sep 28, 2009 at 6:09 AM, TESSIER Patrick 202707 <Patrick.TESSIER@xxxxxx> wrote:

it lacks:

[Profile diagram]

[Customization]

[All diagrams]

 

[General]

[General - Usability]

[General - Scalability&Performance]

[General - Team working]

[Documentation - User]

[Documentation - Developer]

[Model explorer]

[Sash editor]

[Papyrus metatooling]

[State machine diagram]

[Protocol state machine diagram]

[Class diagram]

[Composite structure diagram]

[Component diagram]

[Activity diagram]

[Sequence diagram]

[Communications diagram]

[Interactions overview Diagram]

[Timing diagram]

[Property view]

[Palette]

---------------------------------------------------------

Patrick Tessier

Research Engineer

DRT LIST/DTSI/SOL/LISE CEA-Saclay

91191 Gif sur Yvette Cedex

Tel: 01 69 08 48 63

www.papyrusuml.org

---------------------------------------------------------

 

 


De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : lundi 28 septembre 2009 09:50
À : Papyrus Project list
Objet : [mdt-papyrus.dev] RE: Papyrus Themes for organizaing the Plan

Oupps, I forgot to put item for the property view.

 

[General]

[General - Usability]

[General - Scalability&Performance]

[General - Team working]

[Documentation - User]

[Documentation - Developer]

[Model explorer]

[Sash editor]

[Papyrus metatooling]

[State machine diagram]

[Protocol state machine diagram]

[Class diagram]

[Composite structure diagram]

[Component diagram]

[Activity diagram]

[Sequence diagram]

[Communications diagram]

[Interactions overview Diagram]

[Timing diagram]

[Property view]

[Palette]

 


De : GERARD Sebastien 166342
Envoyé : lundi 28 septembre 2009 09:47
À : 'Papyrus Project list'
Objet : Papyrus Themes for organizaing the Plan

 

Hi all,

 

The development plan of Papyrus (as all Eclipse plans) needs to organized in different themes. Here is a preliminary list of themes. Please modify/complete it if necessary. The deadline for that is Wednesday. After that I will reorganize accordingly the bugzilla, then I will asked you to look in the items of the bugzilla and to affect to you the items you think  you will deal with and to add a milestones accordingly. I will come back to you next Thursday for the procedure to update each items of the bugzilla that is intended to be part of the plan.

 

Preliminary list of themes:

 

[General]

[General - Usability]

[General - Scalability&Performance]

[General - Team working]

[Documentation - User]

[Documentation - Developer]

[Model explorer]

[Sash editor]

[Papyrus metatooling]

[State machine diagram]

[Protocol state machine diagram]

[Class diagram]

[Composite structure diagram]

[Component diagram]

[Activity diagram]

[Sequence diagram]

[Communications diagram]

[Interactions overview Diagram]

[Timing diagram]

 

Cheers… Sébastien.


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



Back to the top