Niels Huylebroeck-2 wrote
Hi,
>
> We've been writing some modules here that most of our
customers seem to
> enjoy. It ranges from changes such as showing customer
references on the
> picking and invoices (also being able to search on them
immediately) and
> other such trivial changes.
>
> Up until now most of these changes we've been doing via the
customization
> approach (ie: create view records in a database without
using xml in a
> module). This has (as you all probably now) the advantage that any
> updates/upgrades/removals/migrations of other modules will
not affect
> these
> views. At the same time this is it's drawback, any changes on the
> inherited
> view can break and it's hard to maintain.
>
> When the community reviewer process and associated branches
were birthed
> one of the agreed policies was that we avoid very minimal
modules that do
> such simple tweaks. This mainly to avoid having a cluster
of modules that
> are very tiny, hardly documented and relatively hard to run
automated
> tests
> on.
Hello Niels, did you upload something to launchpad?
--
View this message in context:
http://openerp-community.2306076.n4.nabble.com/Openerp-community-Usability-features-branches-tp4642941p4643160.html
Sent from the OpenERP Community mailing list archive at Nabble.com.
_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp