Rapid application builder
Project description
rapido.core
rapido.core allows to run Rapido applications.
rapido.core can run on Zope or Pyramid. The initial target is Plone (using rapido.plone), but a POC has been successfully implemented on Substance D.
Database design
A Rapido application can be built from Plone using rapido.plone or provided from sources (read from the local file system).
Anyhow, at the end, the database design is just a set of YAML/HTML/Python files.
The rapido.plone documentation gives a good overview of Rapido features.
Record storage
Storage is not handled directly by rapido.core.
By default, we use rapido.souper which allows to store records in a soup.
Using ZODB is not mandatory, different storages could be easily implemented (SQL-based storage, remote storage services, etc.).
Changelog
1.0.6 (2016-09-19)
Breaking changes:
Use ‘/blocks/’ in Rapido URLs (instead of ‘/block/’)
New features:
Allow regular GET and POST on elements (action elements make a redirect, other elements just return the result). [ebrehault]
on_display event [ebrehault]
Manager vew permissions on blocks [ebrehault]
1.0.5 (2016-04-09)
Allow REST POST to element [simon-previdente]
Raise compilation and execution errors [ebrehault]
Support callable layout [ebrehault]
Allow safe modules (datetime, random, time) [ebrehault]
1.0.4 (2016-03-02)
No rendering on basic element to allow {elem.attr} or {elem[item]} in templates
compute elements only once
Fixes
1.0.3 (2016-01-06)
Allow redirection after action, save, or delete [ebrehault]
REST endpoint to compute a block element [ebrehault]
1.0.2 (2015-11-17)
set_block() method
fix datetime
fix permissions
1.0.1 (2015-11-08)
More pythonic access to record items
1.0 (2015-11-07)
Initial release
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.