> > * Why not having a many2one widget, which is able to embed a form view > > of its target model, inside the enveloping original view. There is no > > switching between form and list view, because list view is not needed. > > With this we could have a company view with a tab party which > > includes the complete party form view. > > I don't think it is good because in this case user lost the ability to > understand that he is working on an other foreign record that could be > linked to many other records. I think the current Many2One widget > provides more affordance.
I agree with Udo here. We would like to avoid as much as possible to have to open the M2O in a pop-up for edition. I think the ideal way would be to allow the developers to use the fields from the m2o directly in the view of the main model. Jean CAVALLO Coopengo -- -- tryton-dev@googlegroups.com mailing list --- You received this message because you are subscribed to the Google Groups "tryton-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tryton-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
