Modified items

All recently modified items, latest first.

grokcore.viewlet-1.11-1.lbn13.noarch: Grok-like configuration for zope viewlets

grokcore.view-2.8-1.lbn13.noarch: Grok-like configuration for Zope browser pages

grokcore.site-1.6.1-2.lbn13.noarch: Grok-like configuration for Zope local site and utilities

grokcore.security-1.6.2-2.lbn13.noarch: Grok-like configuration for Zope security components

grokcore.formlib-1.9-2.lbn13.noarch: Grok-like configuration for zope.formlib components

grokcore.component-2.5-2.lbn13.noarch: Grok-like configuration for basic components (adapters, utilities, subscribers)

grokcore.annotation-1.3-2.lbn13.noarch: Grok-like configuration for Zope annotations

graphviz-python-2.28.0-16.fc17.armv6hl: Python extension for graphviz.

graphviz-python-2.26.3-2.fc13.x86_64: Python extension for graphviz.

graphviz-2.28.0-16.fc17.armv6hl: A collection of tools for the manipulation and layout of graphs (as in nodes and edges, not as in barcharts).

graphviz-2.26.3-2.fc13.x86_64: A collection of tools for the manipulation and layout of graphs (as in nodes and edges, not as in barcharts).

google-perftools-1.7-1.fc13.x86_64: Perf Tools is a collection of performance analysis tools, including a high-performance multi-threaded malloc() implementation that works particularly well with threads and STL, a thread-friendly heap-checker, a heap profiler, and a cpu-profiler.

gomobiletheme.basic-1.0.9-2.lbn13.noarch: This product provides Go Mobile Default Theme mobile site theme for Go Mobile for Plone <http://webandmobile.mfabrik.com>. The theme look and feel resemble's Plone 4's Sunburst theme. The theme contains two optimized image resolutions * 48x48 based icon tiles for > 640 pixels wide mobile screens (based on Javascript screen width detection). * 24x24 based icon tiles for smaller screens CSS3 styles are used for WebKit based mobile browsers. Low-end phones, or non-webkit based proprietary mobile browsers, are also supported partially.

Products.DCWorkflowGraph-0.4-3.lbn13.noarch: 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.

Products.DCWorkflow-2.2.4-3.lbn13.noarch: This product provides fully customizable workflows for the CMF portal_workflow tool. Developing a workflow ===================== This tool is easiest to use if you draw a state diagram first. Your diagram should have: - States (bubbles) - Transitions (arrows) - Variables (both in states and transitions) Remember to consider all the states your content can be in. Consider the actions users will perform to make the transitions between states. And consider not only who will be allowed to perform what functions, but also who will be *required* to perform certain functions. On the "States" tab, add a state with a simple ID for each state on your diagram. On the "Transitions" tab, add a transition with a simple ID for each group of arrows that point to the same state and have similar characteristics. Then for each state choose which transitions are allowed to leave that state. Variables are useful for keeping track of things that aren't very well represented as separate states, such as counters or information about the action that was last performed. You can create variables that get stored alongside the workflow state and you can make those variables available in catalog searches. Some variables, such as the review history, should not be stored at all. Those variables are accessible through the getInfoFor() interface. Worklists are a way to make people aware of tasks they are required to perform. Worklists are implemented as a catalog query that puts actions in the actions box when there is some task the user needs to perform. Most of the time you just need to enter a state ID, a role name, and the information to put in the actions box. You can manage all of the actions a user can perform on an object by setting up permissions to be managed by the workflow. Using the "Permissions" tab, select which permissions should be state-dependent. Then in each state, using the "permissions" tab, set up the role to permission mappings appropriate for that state. Finally, you can extend the workflow with scripts. Scripts can be External Methods, Python Scripts, DTML methods, or any other callable Zope object. They are accessible by name in expressions. Scripts are invoked with a state_change object as the first argument; see expressions.stx. Once you've crafted your workflow, you hook it up with a content type by using the portal_workflow top-level "Workflows" tab. Specify the workflow name in the target content type's box.

Products.ContentTypeValidator-2.0b4-1.lbn13.noarch: Provides a archetypes field validator for content types of files

Products.ClockServer-0.2_Zope2.9dev-2.lbn13.noarch: The Zope ClockServer product provides a mechanism for users to call Zope object methods without the use of an external clock source (e.g. cron/wget). It operates by acting as a medusa "server", essentially coopting Zope's asyncore mainloop and injecting "fake" requests into Zope's ZPublisher. Despite the complicated description, it's rather easy to use.

Products.CacheSetup-1.2.1-2.lbn13.noarch: CacheFu is a collection of products which aggregate and simplify various caching settings, speeding up Plone sites using a combination of memory, proxy, and browser caching. CacheFu can be used by itself or with Squid, Varnish, and/or Apache. Configuration files can be generated for Squid, Varnish, Squid-behind-Apache, Varnish-behind-Apache, and Apache cache proxy (if you are using a non-caching Apache by itself or just Zope-only, no extra configuration files are needed).

Products.CMFUid-2.2.1-3.lbn13.noarch: CMFUid introduces a simple unique id implementation. Implementation ============== The supplied tools attach the unique ids to the objects. The objects do not have to be aware of unique ids. The current implementation depends on the portal catalog to find an object of a given unique id. The interfaces do not imply the use of the catalog (except the IUniqueIdBrainQuery). Which Tool does What? ===================== The 'portal_uidgenerator' tools responsibility is to generate unique ids. The 'portal_uidannotation' tool is responsible to attach unique ids to a content object, and enforce rules about what happens on object move/create/delete. The 'portal_uidhandler' manages registering and accessing unique ids. This design was chosen to allow users replacing only parts of the functionality without having to understand the whole thing. Unique Id API ============= 'portal_uidhandler' implementing 'IUniqueIdHandler' is the main API for playing with unique ids. Usage ===== 'portal_uidhandler' fully implements IUniqueIdHandler (IUniqueIdSet for registering/unregistering unique ids, IUniqueIdQuery for queries and IUniqueIdBrainQuery for more efficient queries by returning catalog brains instead of objects). The current implementation of get/queryBrain and get/queryObject do not return invisible objects (and brains of invisible objects). By invisible objects, we mean objects that would be filtered out by portal_catalog.searchResults due to expiry/effective date and/or user roles. It is often necessary to avoid this filtering in an application. To do this, use the unrestrictedGet/QueryBrain and unrestrictedGet/QueryObject as this will avoid 'None' results. Have a look at the interfaces. CMFUid's functionality is used by CMFDefault's favorite content type to follow linked objects. The favorite content type works as before if CMFUid is not installed.

Products.CMFTopic-2.2.1-3.lbn13.noarch: This product declares a topic content type for the Zope Content Management Framework (CMF).

« Previous 20 items Next 20 items » 1 ... 2374 2375 2376 2377 2378 2379 2380 ... 2425


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items