No, it's different from polls. Polls actually have several templates mixed in 1 file. What we propose here is having 1 template (1 MAIN block) for both adding and editing. Which is less work for coders.

@Macik

Yes, support for pade.add.tpl still should be there if the template exists. But by default it would fall back to page.edit.tpl otherwise.

As for hooks, I think they still should be different because some actions are done when a page is added for the first time but not when editing, and vice versa. But e.g. page.add.tags and page.edit.tags can be merged. In other words, each hook needs individual consideration.

Is there ability to use one function with different TPLs?  I speak about using 2 tpl - one for add and one for edit.

Or some compromise solution to pass TPL path as a parameter, so (when we adding a page) first we can check is there separate «add» template, otherwise use standart «edit» one.

By the way, is this merge consider any «add/edit.first/tags» hooks? Would it be backwards compatible so old plugins still works?

Pros:

• Maintain just page.edit.tpl instead of page.add.tpl and page.edit.tpl.
• Reduces code redundancy.

Cons:

• If you need different sets of fields for adding and editing a page, you need to use IFs in the template or still make 2 different templates for add and edit.

What do you think?