1. Mailing Lists
  2. Contributors
  3. Re: OCA Coding Standards and recommended IDEs

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: OCA Coding Standards and recommended IDEs

Re: OCA Coding Standards and recommended IDEs

Avatar

Re: OCA Coding Standards and recommended IDEs

by
dar@devco.co
- 16/10/2015 21:30:49
>The only way to think to benefit to everybody, is think pythonistic. "Program Once and very good ;-)"

I disagree on this point and support Oleg's point. To understand his concerns you need to adopt a more holistic perspective. It's not a question about yet another python package.

I understand that many of you have objections about standard tooling, because you already use something. But this does not help anyone. You need to understand that such recommendation is not for you, the experienced programmer. The tremendous value lies in a more dynamic ecosystem. It's not about you, who is acquainted with OCA, it is about you, the one, who just heard about odoo two days ago. Outside-In perspective, not Inside-Out. More Contributors. Easyer onboarding. Better productivity. More dynamic. Who can seriously tell me that those are not VERY valuable goals, that can be easily achieved by this move?? Or did I miss something?

A "recommendation" or just a "hint" neither is binding. OCA is a soft authority. Everyone's free - you have been warned! :)

Best Regards, David

El vie., 16 oct. 2015 a las 14:53, Nhomar Hernandez (<nhomar@vauxoo.com>) escribió:
Hello Oleg.

Actually we have a huge job already done around a python package which include a huge set of tools IDE's agnostic, which you can include in your decided IDE as a normal python tool (like Flake8 or Pylint config files).

Recommend a tool is not correct, due to this is so so subjective and it do not add any value by itself whta really add value is the fact that you can improve such mqt project proposeing solutions with issues found in such IDES (but those solutions should be proposed without brake any actual feature with another tool).

The best technical way is think as "a python package" and not as a "plugin for X IDE", then if you want develop a plugin for the tool you use which use the features on mqt, then cool! we can considere have such project, BUT taking care that the python package is aways who makes the job.

In our team we have people that use several different IDE, by myself I use VIM and pycharm and tried sublime but we have a lot of others, ninja-ide is other very good one, gedit, etc, etc, etc....

The only way to think to benefit to everybody, is think pythonistic. "Program Once and very good ;-)"

Regards.




On Fri, Oct 16, 2015 at 5:37 AM, Oleg Kuryan <oleg.kuryan@xpansa.com> wrote:
Dear Contributors,

I would like to bring up discussion about coding standards and also recommended for developers IDEs. 
1. Regarding coding standards that is already well described here https://github.com/OCA/maintainer-tools/blob/master/CONTRIBUTING.md 
2. Additionally I would like to suggest to OCA to standardized development environment. Of course, not to force everybody to work in some particular IDEs, but define list of supporting one. So my recommendations for IDEs based on experience in my company are:
- PyCharm
- Sublime Text

Note that point 2 also requires development of standard helper configuration for IDE/Editors validator. And most likely snippets. 
Fr example, for Sublime there is plugin https://github.com/dreadatour/Flake8Lint that adds pep8 validator. And also for snippets there is https://github.com/sotogarcia/sublime-odoo-snippets 

How about creating OCA forks that will help developers to quickly install necessary addons to one of supported editors and start writing code according to standards? Are there already plans on doing this or some work in progress?




--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

Reference