I'm working on a new release of collective.imagetags
(pypi.python.org/pypi/collective.imagetags) in which all the
functionality that was carried by a browser view (@@imagetags-manage)
is now moved to a new adapter (not commited yet) which provides almost
the same interface that the browser view::
class IManageTags(Interface):
"""
imagetags-manage view interface
Tag management browser view
"""
def get_tag(id, create_on_fail=True):
""" Gets / creates a specific tag """
def get_tags():
""" Gets all the tags for the object """
def get_sorted_tags():
""" Sorted list of tags
"""
def save_tag(data):
""" Saves a tag with the passed data """
I really don't know if anybody is using this product in a project,
however, I think it would be a sensible idea to provide some backward
compatibility mechanism, in case anyone is using the browser view
methods outside the out-of-the-box functionalities.
What should I do? Keep the interface for the browser view with stub
methods that relay on the new adapter? Any suggestion?
Regards
--
Marcos F. Romero
Responsable de Desarrollo
Inter-Cultura
[email protected]
www.inter-cultura.com
+54 11 4542-8299
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
