openerp-expert-framework team mailing list archive

[Raphaël Valyi <rvalyi@xxxxxxxxx>]

Hello,

I confirm I made the modules "sale_invoices_link" and "sale_packings_link"
for that in the trunk-addons-community branch (I use them with the
sale_simple pos module to make sale+picking+invoice the most straightforward
possible in small shop that do not require a true POS such as OpenbravoPOS
but can't risk the dubious and "sale modules incompatible" (such as
sale_tax_include or product_variant_configurator) official pos module.

It sounds that we can't make links for anything to anything that are related
in the right side menu by default because else there would be a
combinatorial explosion of the right side links.

A solution could be to improve the framework in such a way at configuration
time would could enable/disable of of those most direct possible links.
Notice that because domains now works with o2m and m2m related fields and
recursively in 5.2, the possibilities are even much larger. That's very
welcome but that makes the links candidates much more numerous.

Else we continue with the philosophical choices to decide which links should
be in or not be default. And I agree to say the cited links and/or those I
made in that 2 modules are very easily required.

I suggest that we put all the links we think that are very useful and
improve the framework/ensure it's easy to remove them when configuring the
ERP.


Also, for those cited links specifically, there is also an other point we
might want to deal with: currently you can see most of the picking/invoice
information in tabs of the sale order (order line history tabs). But those
links require clicks, don't offer an overview and most importantly don't
enable jumping to the invoice or picking in simple click. Adding links on
the right side menu of the sale order is good, but in a way they are
redundant with the info in those history tabs, no? What would be a more
unified presentation? Also, as default right side menus, we may want to
display all those from related objects present in the current view, so that
would include them; not sure...

Finally, if the framework can't be improved significantly here, I suggest we
move my 2 modules and possibly "account_customer_ref" (changing the name?)
to at least stable 5.2 extra addons and may be even addons.


Thank you for bringing that issue on the table.


Raphaël Valyi
htt://www.akretion.com




On Wed, Dec 16, 2009 at 6:50 AM, Albert Cervera i Areny
<albert@xxxxxxxxxxx>wrote:

> A Dimecres, 16 de desembre de 2009, Ferdinand Gassauer va escriure:
> > currently (branch 5.0)  navigation paths are  only partly implemented, in
> > https://code.launchpad.net/~openerp-commiter/openobject-
> > addons/chricar_price_unit
> > I have tried to add some navigation (quick and dirty and not reliable
> >  because it its based on the assumption of unique numbering which is not
> >  enforced) using available data fields (name, ref, ...) but IMHO
> navigation
> >  should/must be implemented using m2m relations
> >
>
> There are already modules that do that. See "account_customer_ref" (the
> name
> is absolutely unfortunate) and "sale_invoices_link". Though I agree this
> should be in the starndard modules.
>
> --
> Albert Cervera i Areny
> http://www.NaN-tic.com
> Mòbil: +34 669 40 40 18
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-framework
> Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-framework
> More help   : https://help.launchpad.net/ListHelp
>