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"
| Line 7: | Line 7: | ||
Patrick: I have the same point of view as Cedric, for boolean variable I prefer a prefix with ''is'' | Patrick: I have the same point of view as Cedric, for boolean variable I prefer a prefix with ''is'' | ||
| + | globally for all presentation rules, i think that is to strict. | ||
*PRES-01 | *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...) | 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...) | ||
| Line 13: | Line 14: | ||
*PRES-18 | *PRES-18 | ||
Patrick: Interesting, but I do know if it can be applicable to papyrus: the code that has been generated is greater than 2000 lines of code per files in some classes. | Patrick: Interesting, but I do know if it can be applicable to papyrus: the code that has been generated is greater than 2000 lines of code per files in some classes. | ||
| + | |||
| + | *PRES-10 | ||
| + | Patrick: 250 characters is better, screens are greaters than in the past. | ||
| + | |||
| + | *PRES-16 | ||
| + | Patrick: as Cedric I prefer in the same line | ||
* ARCH-12 | * ARCH-12 | ||
Revision as of 05:39, 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
globally for all presentation rules, i think that is to strict.
- 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
Patrick: Interesting, but I do know if it can be applicable to papyrus: the code that has been generated is greater than 2000 lines of code per files in some classes.
- PRES-10
Patrick: 250 characters is better, screens are greaters than in the past.
- PRES-16
Patrick: as Cedric I prefer in the same line
- 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