Do you think? To get that working the PEAR community has to endorse it and have the package maintainers implement the interface in their own packages.
I'm not very keen to see dependancies on Interface files for packages, one of the goals is to 'try' and keep the package interdependancies down.
That said it has been discussed numerous times that it would be good to have a list of recommended method names, so you could start a RFC on it..
on the template ones, setTemplate is called compile($filename) in flexy, which in it's particular case is far more descriptive. the render (or display) may be an improvement on on outputObject($object_with_vars)
from what I remember the list started something like:
toString()
toHtml()
toXml()
to*()
outputHtml() or renderHtml() or displayHtml() or outputToHtml(), renderToHtml(), displayToHtml() ??
factory()
contruct() ??? == new when it may return an error ???
singleton()
set*() / get*() / it would be nice to have recommendations to stop 'over-use' of these..
add*()
remove*()
insert*()
is*()
setOptions() / getOptions() ?? or replace it with options(var_args) ?? - always thought the single/plural get/set added considerable bloat.
connect() /disconnect()
load*()
**********
you may have difficulty in building a large list and getting a consensus. - If you construct a list in an RFC, gather up all views, and on the more contensious ones, do straw polls each of them. (having summarized the various views)
Regards
Alan
-Philippe