[Erp5-dev] optional actions

[Yoshinori Okuji]

On Wednesday 06 July 2005 00:08, Jean-Paul Smets wrote:
> Not always. Most print actions currently call a standard script which
> redirects to the current view of the portal_type and sets portal_skin=Print
> to get a PDF rendering of the current form. This is achieved by:
>
> 	Id: print
> 	Action: string:${object_url}/Base_printPdf
> 	Category: object_print
>
> Sometimes, we would like to override this behaviour. One way would be in
> this case to move the print action definition to the page template
> (efficient but neither very clean nor very flexible).

If you want to override the original, you must make a new portal type or a new 
layer. There is no other clean solution.

But usually you just modify existing actions manually and that's it. When you 
upgrade business templates, you need to take care of merging changes. This is 
not funny, but not difficult at all. Simply time-consuming.

Actually, the idea of layers do not solve all the problem in upgrade. It 
solves only the problem of "getting rid of customization". It does not solve 
the problem of how to merge important changes.

> I like optional actions (it is simple and efficient) but I am not sure it
> solves the upgrade issue for actions which have been overriden for a given
> customer site.

Of course, it does not solve such a complex issue, you know. My change was 
required urgently to make good accounting templates, since each localized 
accounting template wants to add new actions.

YO
-- 
Yoshinori Okuji, Nexedi Research Director
Nexedi: Consulting and Development of Free / Open Source Software
http://www.nexedi.com
ERP5: Free / Open Source ERP Software for small and medium companies
http://www.erp5.org
Storever: OpenBrick, WiFi infrastructure, notebooks and servers
http://www.storever.com