Search results

python3-products-contentmigration-2.2.2-1.lbn36.noarch

This is a generic content migration framework, which should help you write your own content migrations. It has no UI and no value on its own, but makes it easy to write certain type of content migrations. This replaces the ATContentTypes migration framework, and provide three useful extensions: A CustomQueryWalker can be used to specify a more specific catalog query for a walker to use (e.g. which content to actually migrate). This can be used with any migrator. A BaseInlineMigrator is similar to BaseMigrator, but does not migrate by copying the old object to a temporary location, creating a new object and applying migration methods. Instead, migration methods are applied in-place. This simplifies the code significantly, because attributes, local roles etc. does not need to be copied over. Note that whereas BaseMigrator works in terms of self.old and self.new as the objects being migrated, BaseInlineMigrator only has a single object, stored in self.obj. This can be used with any walker. An extension of this class called FieldActionMigrator uses the action-based migration framework for Archetypes fields, found in field.py. Please refer to that file for full details, but briefly, you specify a list of attributes to migrate at the storage level, instructing the migrator whether to rename, transform, unset or change the storage for an attribute. Please see the docstrings in walker.py, migrator.py and field.py for full details. For examples, see tests/cmtc.py and tests/testATFieldMigration.py.

python3-products-contentmigration-2.2.2-1.lbn36.noarch

This is a generic content migration framework, which should help you write your own content migrations. It has no UI and no value on its own, but makes it easy to write certain type of content migrations. This replaces the ATContentTypes migration framework, and provide three useful extensions: A CustomQueryWalker can be used to specify a more specific catalog query for a walker to use (e.g. which content to actually migrate). This can be used with any migrator. A BaseInlineMigrator is similar to BaseMigrator, but does not migrate by copying the old object to a temporary location, creating a new object and applying migration methods. Instead, migration methods are applied in-place. This simplifies the code significantly, because attributes, local roles etc. does not need to be copied over. Note that whereas BaseMigrator works in terms of self.old and self.new as the objects being migrated, BaseInlineMigrator only has a single object, stored in self.obj. This can be used with any walker. An extension of this class called FieldActionMigrator uses the action-based migration framework for Archetypes fields, found in field.py. Please refer to that file for full details, but briefly, you specify a list of attributes to migrate at the storage level, instructing the migrator whether to rename, transform, unset or change the storage for an attribute. Please see the docstrings in walker.py, migrator.py and field.py for full details. For examples, see tests/cmtc.py and tests/testATFieldMigration.py.

python3-products-daterecurringindex-3.0.1-1.lbn36.noarch

Products.DateRecurringIndex A Zope 2 catalog index with support for indexing of recurring events, following the icalendar standard. It is a drop-in replacement for the Zope2 DateIndex and will produce the same results for non- recurring dates.The DateRecurringIndex accepts following parameters:id Required. The name of the field or object attribute to be indexed.recurdef Required. The name of...

python3-products-daterecurringindex-3.0.1-1.lbn36.noarch

Products.DateRecurringIndex A Zope 2 catalog index with support for indexing of recurring events, following the icalendar standard. It is a drop-in replacement for the Zope2 DateIndex and will produce the same results for non- recurring dates.The DateRecurringIndex accepts following parameters:id Required. The name of the field or object attribute to be indexed.recurdef Required. The name of...

python3-products-dcworkflow-2.7.0-1.lbn36.noarch

:target:

python3-products-dcworkflowgraph-0.4.1-1.lbn36.noarch

Introduction DCWorkflowGraph DCWorkflowGraph is a DCWorkflow graphic viewer now. It uses Graphviz. I want to make it a graphic editor for DCWorkflow, just like what OpenFlowEditor does. DCWorkflowGraph is at the collective: Product home: Graphviz - see install.txtHow to use it Go to ZMI portal_workflow/your_workflow, there is a new tab called 'graph', click it and you will see the workflow graph!

python3-products-dcworkflow-2.7.0-2.lbn36.noarch

:target:

python3-products-dcworkflowgraph-0.4.1-1.lbn36.noarch

Introduction DCWorkflowGraph DCWorkflowGraph is a DCWorkflow graphic viewer now. It uses Graphviz. I want to make it a graphic editor for DCWorkflow, just like what OpenFlowEditor does. DCWorkflowGraph is at the collective: Product home: Graphviz - see install.txtHow to use it Go to ZMI portal_workflow/your_workflow, there is a new tab called 'graph', click it and you will see the workflow graph!

python3-products-extendedpathindex-4.0.1-1.lbn36.noarch

Introduction This is an Zope Catalog index to query treeish structures in the ZODB by path. It supports depth limiting, and has the ability to build a structure usable for navtrees and sitemaps. The actual navtree implementations are not (and should not) be in this package. This is the index implementation only.Assumptions EPI makes an assumption about the catalog and index being in the same...

python3-products-extendedpathindex-4.0.1-1.lbn36.noarch

Introduction This is an Zope Catalog index to query treeish structures in the ZODB by path. It supports depth limiting, and has the ability to build a structure usable for navtrees and sitemaps. The actual navtree implementations are not (and should not) be in this package. This is the index implementation only.Assumptions EPI makes an assumption about the catalog and index being in the same...