Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:Papyrus/Neon Work Description/Discussions/Development rules"
m |
|||
| Line 1: | Line 1: | ||
= Development Rules (Talk) = | = Development Rules (Talk) = | ||
| + | *NAME-06 | ||
| + | Patrick: according to me, the name must be understable. I dislike acronyms concatenations and abbreviations. | ||
| + | An exception has been done for ''gmfdiag'' | ||
| + | *NAME-22 | ||
| + | Patrick: I have the same point of view as Cedric, for boolean variable I prefer a prefix with ''is'' | ||
| + | |||
| + | *PRES-01 | ||
| + | Patrick: I prefer not to be so strict in the structuration of the code. In IDE, now you can order properties, operations as you want (alphabetic...) | ||
| + | Nevertheless: On remarks about inner class. I do like it. I someone add a ne inner class, it has to write a solid argumentation (if no a lot od developper will write the code in one files ;D ) | ||
| + | |||
| + | *PRES-18 | ||
* ARCH-12 | * ARCH-12 | ||
| − | The string externalisation is already in place, but most of the string are not placed into a specific file: <code>messages.properties</code>. | + | The string externalisation is already in place, but most of the string are not placed into a specific file: <code>messages.properties</code>. |
| + | |||
I don't know if this could be done in Papyrus for the warnings, labels or other text messages.--[[User:Celine.Janssens.all4tec.net|Céline Janssens [ALL4TEC]]] ([[User talk:Celine.Janssens.all4tec.net|talk]]) 09:29, 9 July 2015 (EDT) | I don't know if this could be done in Papyrus for the warnings, labels or other text messages.--[[User:Celine.Janssens.all4tec.net|Céline Janssens [ALL4TEC]]] ([[User talk:Celine.Janssens.all4tec.net|talk]]) 09:29, 9 July 2015 (EDT) | ||
Revision as of 05:33, 15 July 2015
Development Rules (Talk)
- NAME-06
Patrick: according to me, the name must be understable. I dislike acronyms concatenations and abbreviations. An exception has been done for gmfdiag
- NAME-22
Patrick: I have the same point of view as Cedric, for boolean variable I prefer a prefix with is
- PRES-01
Patrick: I prefer not to be so strict in the structuration of the code. In IDE, now you can order properties, operations as you want (alphabetic...) Nevertheless: On remarks about inner class. I do like it. I someone add a ne inner class, it has to write a solid argumentation (if no a lot od developper will write the code in one files ;D )
- PRES-18
- ARCH-12
The string externalisation is already in place, but most of the string are not placed into a specific file: messages.properties.
I don't know if this could be done in Papyrus for the warnings, labels or other text messages.--Céline Janssens [ALL4TEC] (talk) 09:29, 9 July 2015 (EDT)
- SONAR
Why not activate the sonar instance for our project?: https://wiki.eclipse.org/Sonar