Allow buttons to call client actions.

With @ModelView.button_action we can reference an action form the ir.action model.

With this new behaviou we can aslo call client actions. Something like:

@ModelView.button_action('timesheet_line.new')

or

@ModelView.button_action('timesheet_line.duplicate')

added type::feature + 1 deleted label

* Sergi Almacellas Abellana [2013-08-22 17:07 +0200]:
>With @ModelView.button_action we can reference an action form the
>ir.action model.
>
>With this new behaviou we can aslo call client actions. Something
>like:
>
>@ModelView.button_action('timesheet_line.new')
>
>or
>
>@ModelView.button_action('timesheet_line.duplicate')

Can you be more specific about what you call client actions.
I think this issue might be related to an issue that Jean has.

added 1 deleted label and removed 1 deleted label

>Nicolas Évrard <nicoe@b2ck.com> added the comment:
>
>* Sergi Almacellas Abellana [2013-08-22 17:07 +0200]:
>> With @ModelView.button_action we can reference an action form the
>> ir.action model.
>>
>> With this new behaviou we can aslo call client actions. Something
>> like:
>>
>> @ModelView.button_action('timesheet_line.new')
>>
>> or
>>
>> @ModelView.button_action('timesheet_line.duplicate')

>Can you be more specific about what you call client actions.

For me a client action is and action that is done from the client. For example
click the button to create a new record, or click de button to delete de current
record.

So @ModelView.button_action('timesheet_line.new')

will execute de code of the function and when finished the client will perform
the new action, so the new form for the model will be presented to the end user.

Let me know if it isn't clear enought.

I don't think it is necessary to have "timesheet_line" as parameter but just
"new", "copy" etc. because button are on a form so there will be any ambiguity
about the action to perform.
I think now we must collect all the actions that should be implemented:

- new
- delete
- copy
- next
- previous
(- search ?)
- close

IMHO search is not needed as If you want to open some records you can open a new
window with the search in the pyson_domain.

Agree on all the others.

On 17/11/13 21:37 +0100, Sergi Almacellas Abellana wrote:
> IMHO search is not needed as If you want to open some records you can open a new
> window with the search in the pyson_domain.

Yes but I could imagine some cases where you would not want to open a
new tab for example to limit the number of tab opens.

Other possible actions we thought of:
- switch the view
- set focus (to discuss)

I really like the idea of creating a new instance in a list, that looks useful.

Another think we thought about was the possibility to chain actions.

I think we miss refresh also. See

#3519 (closed)

There is no need of a refresh because design should take care of it.

assigned to @ced

added 1 deleted label and removed 1 deleted label

Please test patches at review3241002, review3221003 and review3231002

added sao tryton trytond + 1 deleted label and removed 1 deleted label

Tested 'close' with / without wizard, no problem so far.

New changeset 1d06851c5d41 by C?dric Krier in branch 'default':
Manage client actions from button and wizard
http://hg.tryton.org/tryton/rev/1d06851c5d41

New changeset fc46f1ab2d36 by C?dric Krier in branch 'default':
Client side actions on button and wizard
http://hg.tryton.org/trytond/rev/fc46f1ab2d36

added 1 deleted label and removed 1 deleted label

closed

mentioned in issue #3519 (closed)

mentioned in issue #7364 (closed)