We should have a standard way to collect information during the pipeline processing; e.g., when creating a tarball as an export_context (quintagroup.transmogrifier.writer), there is - correct me if I'm wrong - no way to access the resulting tarball in the end, or in later parts of the pipeline. (The GenericSetup creates the TarballExportContext itself). If there was, we could easily build user interfaces to create tarball exports from a Plone site, e.g. of a specified subtree and all referenced ressources.
As a first shot, my idea is to have an _collected_info attribute (a list); this could take dictionaries with keys for the category (e.g. export_context), section (the name), and info (for export contexts, this could e.g. be a dict with context_type and context keys).
The info could be added with an add_info method, and a get_info method could return a list (optionally filtered by category and/or section).
We should have a standard way to collect information during the pipeline processing; e.g., when creating a tarball as an export_context (
quintagroup.transmogrifier.writer), there is - correct me if I'm wrong - no way to access the resulting tarball in the end, or in later parts of the pipeline. (The GenericSetup creates theTarballExportContextitself). If there was, we could easily build user interfaces to create tarball exports from a Plone site, e.g. of a specified subtree and all referenced ressources.As a first shot, my idea is to have an
_collected_infoattribute (a list); this could take dictionaries with keys for thecategory(e.g.export_context),section(the name), andinfo(for export contexts, this could e.g. be a dict withcontext_typeandcontextkeys).The info could be added with an
add_infomethod, and aget_infomethod could return a list (optionally filtered by category and/or section).