Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Help in customization
Remi,

Thank you very much for your help.
You totally cleared my mind about these directories!!!
Your email was very helpful!

I can see clearly how the svn structure works! As I was insecure about what to download, I've downloaded all the three directories: branches, tags and trunk! Now, I know I must focus on trunk directory.

Well, when I've talked about adding some screens in the first email I meant I would like to provide to the user some options through some forms. 
I think the most likely directory


Currently, I am not totally sure yet about what options will be because I am still studying about UML profiles and OCL. For that reason, my email was so vague.

Among the options I've already known that I will want include there is OCL treatment (I know it's already possible to add OCL constraint in papyrus 1.12.3 but I would like to know if I can offer something new).

I really interested in knowing more about papyrus so much that I've studied about eclipse plugin creation and about OSGi.

As all of you have already noticed, I'm totally new to the project papyrus so I have some really basic questions. I imported the project though subclipse (the eclipse plugin for svn) and now I don't know how to launch it. In some eclipse plugin creation tutorials I've found in the internet, I just need to right click the project and choose the option <<Run as->Eclipse Application>> but in the papyrus project, more specifically in the trunk folder, the <<Run as>> option doesnt't give the option <<As eclipse application>>. Could you help in that ?

Thank you very much

Best regards!

On Tue, Mar 22, 2011 at 10:02 AM, SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:

Hi Paulo,

 

 

I’ll try to explain you the structure of the SVN:

-          As said by Sebastien, in the branches, you will find the branch 0.7.X, which is the current stable version of Papyrus. As done usually in the code projects, all bug fixes are pushed ‘or should be pushed) in the trunk. So the trunk itself should be quite stable.

-          In the trunk, you will currently find the sources on which the next version of Papyrus is build: the 0.8.0 version, that will be part of the Indigo simultaneous release train of Eclipse (Eclipse 3.7 to be more precise: http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan)

 

If you are in the branch/0.7.X or trunk, you will find the same structure:

-          Doc: contains some documentation for developers, for example meeting reports, coding style and rules, etc.

-          Examples: example projects

-          Extra plugins: the subfolders here contain some additional plugins for Papyrus, that are not always part of the official distribution : implementation of standard profile, projects that contribute to Papyrus for model transformation integration, etc. They are not required to be able to use Papyrus

-          Features : all features used to structure the set of plugins and to generate the Papyrus tool.

-          Incoming: temporary place holder to store plugins that will be added to Papyrus tool. Comitters can comment the code, the naming of the plugin, etc. After one week or two, plugins are added into the distribution, if there are no critical issues.

-          Plugins: The most interesting project for you. It contains all plugins that compose Papyrus tool. Several subfolders :

o   Core: contains the backbone of the tool. (required)

o   Developer: plugins that are used by commiters to generate code for the diagram editors mainly. Required only if you need to generate code for a specific editor

o   Marte: standard implementation of the MARTE OMG profile. (to be removed, as marte is located in extra plugins, so not necessary for you)

o   Others: 2 plugins that are required by the tool. Should be moved in other folders.

o   Profile tool: was used to generate diagram editor from specific profiles. No required

o   Sysml and uml: diagram editors and other views dedicated to UML world and SysML world. As far as I understand your needs, you require at least all UML plugins.

-          Releng: used for release engineering (build of the tool on the eclipse  servers). Not required for you

-          Tests: All plugins or fragments used to test the tool after compilation phase on the build server. Not required, but you can find there some code snippets that could be interesting.

 

I advise you to download stuff from the trunk, as this will be the next major version in a few months (June to be precise).

 

What do you mean exactly by : Basically, I intend to add some screens during a profile creation and write some code to change another ones. ?

Hope this helps!

Rémi

 

 

 

 

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Paulo Alexandre Costa
Envoyé : lundi 21 mars 2011 13:42


À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Help in customization

 

Thank you again for the helping.

 

When I said << I can write/change both the  Branch directory code as the Trunk directory code >>, I tried to figure it out where I can write the code to add the screens I've mentioned in the previous email.

 

For instance, in the <<Branches>> directory there are several directories ( 

 

 

On Fri, Mar 18, 2011 at 4:57 AM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote:

What do you mean by « , I can write/change both the  Branch directory code as the Trunk directory code » ?

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Paulo Alexandre Costa
Envoyé : jeudi 17 mars 2011 14:05
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Help in customization

 

 

 

Basically, I intend to add some screens during a profile creation and write some code to change another ones. 

At the moment, I'am not  sure yet about I'll really do but your help was helpful.

 

If I understand correctly what you said, I can write/change both the  Branch directory code as the Trunk directory code. Am I Right ? 

 

Anyway, I'm really grateful for your help!!!!

Thank you!

 

 

On Mon, Mar 14, 2011 at 6:09 PM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote:

Hi Paulo,

 

Trunk consist of the most up to date development. Branch is dedicated to “stable versions”. Trunk is on Indigo and will lead to 0.8.x version, whereas 0.7.x is on the branch and is helios-based.

 

What do you intend to add as functionalities?

 

Best… Sébastien.

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Paulo Alexandre Costa
Envoyé : lundi 14 mars 2011 18:14
À : mdt-papyrus.dev@xxxxxxxxxxx
Objet : [mdt-papyrus.dev] Help in customization

 

Hi, everybody.

 

I'm interested in knowing better the papyrus 4 uml. 

My objective is to add more functionalities but i have no clue where do I start. 

Searching for more informations in the site http://wiki.eclipse.org/MDT/Papyrus, I've found the svn address in which one there are three folders: branches, trunk and tags. So, my first doubt is which of these directories I should download. I'd like to ask all off you where do I Start.

 

Any help would be of great help!

 

Thank you!!!!



--
Paulo Alexandre da Silva Costa

GREat-UFC http://great.ufc.br/
Mestrando Ciência da Computação

Universidade Federal do Ceará

"While 2SAT is in P, 3SAT is NP-complete. This shows that innocent changes in a problem may lead to drastic changes in the complexity."

"A velocidade impressionante dos computadores é de utilidade limitada se os programas que neles rodam usam algoritmos ineficientes."

 


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




--
Paulo Alexandre da Silva Costa

GREat-UFC http://great.ufc.br/
Mestrando Ciência da Computação

Universidade Federal do Ceará

"While 2SAT is in P, 3SAT is NP-complete. This shows that innocent changes in a problem may lead to drastic changes in the complexity."

"A velocidade impressionante dos computadores é de utilidade limitada se os programas que neles rodam usam algoritmos ineficientes."

 


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




--
Paulo Alexandre da Silva Costa

GREat-UFC http://great.ufc.br/
Mestrando Ciência da Computação

Universidade Federal do Ceará

"While 2SAT is in P, 3SAT is NP-complete. This shows that innocent changes in a problem may lead to drastic changes in the complexity."

"A velocidade impressionante dos computadores é de utilidade limitada se os programas que neles rodam usam algoritmos ineficientes."

 


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




--
Paulo Alexandre da Silva Costa
GREat-UFC http://great.ufc.br/
Mestrando Ciência da Computação
Universidade Federal do Ceará

"While 2SAT is in P, 3SAT is NP-complete. This shows that innocent changes in a problem may lead to drastic changes in the complexity."

"A velocidade impressionante dos computadores é de utilidade limitada se os programas que neles rodam usam algoritmos ineficientes."


Back to the top