Community mailing list archives
Re: Why Open Object Framework?by
Certainly there was no IDE support, or even a decent python IDE comparable with say Eclipse for Java, they came much later. Built in Django support was when 2010 maybe later. in Pydev? and later again in Pycharm which really wasn't decent until a few years ago.
So to suggest that Odoo had a choice is a bit disingenuous and said, there are all these great frameworks, but we need to invent our own is very misleading. You want to start afresh, and do it in one of those frameworks, 2m lines of code to port, for possibly negative benefit.
We have what we have, I like it, introspection is improving and it is so simple that really while it would be nice, in truth given the choice between the modular inheritance and flexibility of the OO Framework and being nicely able to introspect MRO, I'd take the flexibility any day.
I think I was not clear enough, and I am really for that.
Well, I am not suggesting to change the framework. It is just a wondering "What if...?". let me explain by an example:
Imagine your have two choices to start your own ERP business and you have two choices@Ruben, You are right when you said:
- A good system with a good support through a big community, but no IDE can support it which makes it harder to be used or developed by your team. it has a medium learning sources, bad official documentation and it has its own issues ==> OOF
- A good system with better support through a greater community, almost all IDEs support it which makes it easier to be used and developed by your team. its learning sources are everywhere, great official documentation and for sure it has its own issues which is well known with its solutions ==> Django, Rails or Zend.Changing to another paradigm might bring advantages but also new problemsbut if you start with an existing framework, you will get new issues but it will be well-known issues
@Dave, Owning your framework to get the full control is a good point, but you still can form an existing framework and customize it to match your needs and get the full control of it. We all know Tryton which was a fork of Odoo (OpenERP) from its earlier versions.@OpenERP Master, it is not about what you like, it is about what is the best. ;)
I just wondering why not to get benefits from an existing framework (Django, Rails, Zend .....), exiting support (Tools like IDEs), existing community, existing documentation and learning sources, and well-known issues which can be fixed/customized in the new fork ?On Tue, Apr 21, 2015 at 9:57 AM, Rubén <firstname.lastname@example.org> wrote:
OOF has a very focused purpose, being the framework for Odoo. Changing to another paradigm might bring advantages but also new problems, so it might be best to put some community effort and try to improve OOF as much as posible.
What are the main things you would change, Mohamed Magdy? How can anybody lend a helping hand on that?
El 20/04/15 a las 16:52, OpenERP Master escribió:<blockquote cite="mid:CAENzJ3HNaQiE0Gx01yHbBzpa8O9ALfPG_3khqTqH8-avt12FVA@mail.gmail.com" type="cite">
There are a lot of people who do not like Django ORM, myself included. Some bigger sites that are powered on Django actually might use sqlalchemy because its better.I like openobject, but its ORM definitely has it's limitations and find myself occasionally having to do direct sql. Another discussion.
On Mon, Apr 20, 2015 at 9:12 AM, Dave Ellison <email@example.com> wrote:
Personally don't think this is an issue. Also, using Django expects
to following their paradigm. If this was to change, for worse or
better, it could affect how Odoo operates. To have its own
framework, means they have full control of their product. Right or
wrong, I don't believe it to be issue. I can see the advantages both
sides, but having their own seems better in my opinion.
On 20/04/15 14:48, Nhomar Hernández
2015-04-20 8:02 GMT-05:00 Mohamed
I found the model inheritance in Django's documentation, it is a
little bit different than what we found in Open Object
Framework. But I think the concept is the same.
Change the framework is change the
Django is "popular" but it do not
become it as "best" there are a lot of similaritites, but if
the core editor of the tool where do not have write permisions
to improve at the speed they need and protecting the job in
terms of branding it is too complicated make it evolve.
Django and OOF are similar framworks
done for different purpose.