Plomino is a powerful and flexible web-based application builder for Plone.

• create your own custom applications from a web interface without programming
• create and design forms in WYSIWYG mode
• easily embed charts or maps
• create specific actions with formulas (compute fields, send emails, ...)
• adapt the application behaviour depending on the user access rights and roles
• import/export your application structure and/or your application data, including replication between Plomino instances

Plomino is a through-the-web application builder, hence:

• it is not a through-the-web content-type builder like Dexterity, which is perfect to create a custom content type but that will always stick to the standard content management scenario, while Plomino allows any custom scenario,
• it is not just a form generator like PloneFormGen, as Plomino provides all the services (data storage, search, automation, import/export, etc.) to build an entire application. Regarding form generation itself, a major difference with PloneFormGen is that Plomino allows editing the form layout in its entirety, while PloneFormGen uses a fixed pre-defined form layout.

Screencasts and how-tos are available on http://www.plomino.net/ .

Plomino documentation is available on ReadTheDocs.

Note: if you think something is missing in the documentation, please send your pull request at https://github.com/plomino/PlominoDoc .

Plomino itself is internationalized and translated in seven languages. Applications built with Plomino can be internationalized (see the related documentation).

To deploy Plomino, you need to edit your buildout.cfg file and add the following in the eggs section:

eggs =
     ...
     Products.CMFPlomino

and also add the following in the versions block:

[versions]
...
collective.js.datatables = 2.0.1

Then you have to run buildout to realize your configuration:

bin/buildout -N

If you're using Plone version older than 4.2 you'll need to add some more directives to your buildout.cfg.

Plomino depends on plone.app.registry, and plomino.tinymce requires Products.TinyMCE>=1.2.13. To make Plomino work on pre-4.2 Plone sites you need to pin those versions in your versions.cfg section:

Products.TinyMCE=1.2.13
collective.js.jqueryui=1.8.16.9

and use a known good set for plone.app.registry.

This means extending your buildout from:

http://good-py.appspot.com/release/plone.app.registry/1.0b2?plone=4.0.9

replacing 4.0.9 with the actual version you need.

You can find support on the freenode IRC channel #plomino or using the GitHub issue tracker

Plomino is continuously tested on Travis _ and the code coverage is tracked on coveralls.io _.

• Eric BREHAULT <eric.brehault@makina-corpus.org>
• Jean Jordaan <jean.jordaan@gmail.com>
• Silvio Tomatis <silviot@gmail.com>

The complete list is available here <http://www.plomino.net/credits>.

_

• Planet Makina Corpus
• Contact us

_