Search results

mobile.sniffer-1.0.0-2.lbn19.noarch

Mobile browser feature detection using multiple backends

mod_wsgi-3.4-8.fc19.armv6hl

The mod_wsgi adapter is an Apache module that provides a WSGI compliant interface for hosting Python based web applications within Apache. The adapter is written completely in C code against the Apache C runtime and for hosting WSGI applications within Apache has a lower overhead than using existing WSGI adapters for mod_python or CGI.

mod_wsgi-4.5.15-2.lbn19.x86_64

The mod_wsgi adapter is an Apache module that provides a WSGI compliant interface for hosting Python based web applications within Apache. The adapter is written completely in C code against the Apache C runtime and for hosting WSGI applications within Apache has a lower overhead than using existing WSGI adapters for mod_python or CGI.

numpy-f2py-1.7.1-7.fc19.armv6hl

This package includes a version of f2py that works properly with NumPy.

plone-4.3.20-1.lbn19.noarch

Plone is ideal as an intranet and extranet server, as a document publishing system, a portal server and as a groupware tool for collaboration between separately located entities. A versatile software product like Plone can be used in a myriad of ways. Look through the sites that use Plone section to see a variety of ways people have implemented Plone and Zope solutions.

plone-server-4.3.20-1.lbn19.noarch

Plone is ideal as an intranet and extranet server, as a document publishing system, a portal server and as a groupware tool for collaboration between separately located entities. A versatile software product like Plone can be used in a myriad of ways. Look through the sites that use Plone section to see a variety of ways people have implemented Plone and Zope solutions. This is a a minimal version of Plone that does not require X and other GUI-based software.

plone-vs.org-1.1.1-1.lbn19.noarch

Using vs.org almost any organization including its institutions, departments and employees may be represented within a Plone site. Even complex organizational structures can be made accessible and displayed, structered by business area, specialization and region. Features vs.org offers the following content types: Institution Telephone numbers An institution can hold an arbitrary number of telephone numbers. The vocabulary for descriptions can be assigned such that common declarations telephone, fax and mobile can be used, as well as reception, ward and others. Each number may be marked as externally visible. This way it is possible to administer internal numbers in vs.org, even if the page for the institution is published. Address Any number of addresses may be assigned to an institution. Provide details of street address, P.O. box, a delivery address and others. The first address given is used to generate a map using Google maps services. If the automatic mapping is not precise enough you may provide geo coordinates. With the generated map you may also display directions in RichText. An optional photograph or image of the institution is also helpful. Business area Any institution may show its business area. Editors may administer the business area vocabulary. Employees Employees of an institution are referenced from entries in an employee folder. The order of employees is freely assignable. Department A department can hold an arbitrary number of telephone numbers, described by custom vocabulary. Each number may be marked as externally visible. Building section / floor / room no. Departments are always part of an institution, so have no address of their own. Instead you provide building section, floor or room number details. Specialization Any department may be assigned a specialization. Employee Any employee can be described using Position Salutation Title (academic or other) Firstname Surname Telephone numbers Email URL Portrait Notes Again, any number of telephone number is possible. Each may carry arbitrarily assigned vocabulary for description. For each employee a business card in vcard format is generated that can be imported into address books and contacts. Views The institution homepage view makes specific institutions, departments accessible using their business areas, specializations and regions. Portlets Institution portlet This portlet shows name and image of the institution, the addresses linking to Google maps, the telephone numbers and employees. Department portlet Very similar to the institution portlet, showing building section, floor and room number instead of an address. Similar institutions, similar departments Shown in the context of an institution, this portlet provides other institutions sharing the same business area. In the same way, a portlet shows other departments having the same specialization. Employee search Searching for employees is using the employee's surnames. This search can be adapted to specific institutions. Use cases Websites of organizations having a complex organizational structure. Intranets and extranets that are used by employees and/or partner organizations who need to find contact information quickly.

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.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.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.