Search results

plone-wc.pageturner-1.2.3-3.lbn13.noarch

This package is a Plone product that will add a Page Turner view to the PDF File content type. The result is that you'll be able to view PDFs much in the same way you can view them on scribd.com. It uses the open source project, Flex Paper, to display the PDFs. You can find information about it at http://flexpaper.devaldi.com/.

plone-wc.pageturner-1.2.3-3.lbn19.noarch

This package is a Plone product that will add a Page Turner view to the PDF File content type. The result is that you'll be able to view PDFs much in the same way you can view them on scribd.com. It uses the open source project, Flex Paper, to display the PDFs. You can find information about it at http://flexpaper.devaldi.com/.

plone-wc.pageturner-1.2.3-3.lbn25.noarch

This package is a Plone product that will add a Page Turner view to the PDF File content type. The result is that you'll be able to view PDFs much in the same way you can view them on scribd.com. It uses the open source project, Flex Paper, to display the PDFs. You can find information about it at http://flexpaper.devaldi.com/.

plone.alterego-1.0-2.lbn13.noarch

Now you see it, it now you don't! This package defines a dynamic module type that lets you create objects in the dynamic module on demand. Usage To use this package, you should: * Identify an appropriate parent module where the dynamic module will live. * Ensure that plone.alterego.dynamic.create() is called with this module and a dynamic module name. Typically, you'd do this in the parent module itself, so that the dynamic module is instantiated as soon as the parent module is imported. * Register a named utility providing IDynamicObjectFactory. The name should be the same as the full dotted path to the dynamic module. This utility will be responsible for creating the objects that inhabit the dynamic module.

plone.alterego-1.1.5-1.lbn19.noarch

Now you see it, it now you don't! This package defines a dynamic module type that lets you create objects in the dynamic module on demand. Usage To use this package, you should: * Identify an appropriate parent module where the dynamic module will live. * Ensure that plone.alterego.dynamic.create() is called with this module and a dynamic module name. Typically, you'd do this in the parent module itself, so that the dynamic module is instantiated as soon as the parent module is imported. * Register a named utility providing IDynamicObjectFactory. The name should be the same as the full dotted path to the dynamic module. This utility will be responsible for creating the objects that inhabit the dynamic module.

plone.alterego-1.1.5-1.lbn25.noarch

Now you see it, it now you don't! This package defines a dynamic module type that lets you create objects in the dynamic module on demand. Usage To use this package, you should: * Identify an appropriate parent module where the dynamic module will live. * Ensure that plone.alterego.dynamic.create() is called with this module and a dynamic module name. Typically, you'd do this in the parent module itself, so that the dynamic module is instantiated as soon as the parent module is imported. * Register a named utility providing IDynamicObjectFactory. The name should be the same as the full dotted path to the dynamic module. This utility will be responsible for creating the objects that inhabit the dynamic module.

plone.api-1.1.0-1.lbn13.noarch

The plone.api is an elegant and simple API, built for humans wishing to develop with Plone. It comes with cookbook-like documentation and step-by-step instructions for doing common development tasks in Plone. Recipes try to assume the user does not have extensive knowledge about Plone internals. The intention of this package is to provide clear API methods for Plone functionality which may be confusing or difficult to access. As the underlying code improves some API methods may be deprecated and the documentation here will be updated to show how to use the improved code (even if it means not using plone.api) Some parts of the documentation do not use plone.api methods directly, but simply provide guidance on achieving a task using Plone's internal API. For example, using the portal catalog (see 'Find content objects'). The intention is to cover 20% of the tasks any Plone developer does 80% of the time. By keeping everything in one place, the API stays introspectable and discoverable, important aspects of being Pythonic.

plone.api-1.10.2-1.lbn19.noarch

The plone.api is an elegant and simple API, built for humans wishing to develop with Plone. It comes with cookbook-like documentation and step-by-step instructions for doing common development tasks in Plone. Recipes try to assume the user does not have extensive knowledge about Plone internals. The intention of this package is to provide clear API methods for Plone functionality which may be confusing or difficult to access. As the underlying code improves some API methods may be deprecated and the documentation here will be updated to show how to use the improved code (even if it means not using plone.api) Some parts of the documentation do not use plone.api methods directly, but simply provide guidance on achieving a task using Plone's internal API. For example, using the portal catalog (see 'Find content objects'). The intention is to cover 20% of the tasks any Plone developer does 80% of the time. By keeping everything in one place, the API stays introspectable and discoverable, important aspects of being Pythonic.

plone.api-1.10.2-1.lbn25.noarch

The plone.api is an elegant and simple API, built for humans wishing to develop with Plone. It comes with cookbook-like documentation and step-by-step instructions for doing common development tasks in Plone. Recipes try to assume the user does not have extensive knowledge about Plone internals. The intention of this package is to provide clear API methods for Plone functionality which may be confusing or difficult to access. As the underlying code improves some API methods may be deprecated and the documentation here will be updated to show how to use the improved code (even if it means not using plone.api) Some parts of the documentation do not use plone.api methods directly, but simply provide guidance on achieving a task using Plone's internal API. For example, using the portal catalog (see 'Find content objects'). The intention is to cover 20% of the tasks any Plone developer does 80% of the time. By keeping everything in one place, the API stays introspectable and discoverable, important aspects of being Pythonic.

plone.app-1.0.0-1.lbn13.noarch

plone.app module