Vyper-Django™
Vyper-Django™ Leverages the Power of Django using concise Agile Development techniques:
- Maximize Code Reuse.
- Dynamic Page Rendering via a standard site template.
- DHTML Tab Bar for Navigation (integrated into the site template)
- A Common Site Template for each Django Applet.
- Uses OOHtml (no need to use the Django Tag Language)
- Uses Django 0.96.3 as the basis for Vyper-Django™ (there are far too many bugs in Django 1.0.x as of 04-01-2009)
- Partials and Sub-Partials just like Ruby on Rails only faster using less code.
- Renders partials just like Ruby on Rails, partials have file names that begin with "_" (underscore)
- Able to use Django Models or SQLAlchemy Models as-desired.
- Able to use Django Authentication or any Authentication Model as-desired.
- Not bound to the limitations found in Django
- Vyper-Django™ is far more friendly for Web 2.0 than Ruby on Rails.
Current Vyper-Django™ Features
- Vyper-Django™ allows many sub-sites to be plugged into a Vyper-Django™ Site.
- Vyper-Django™ leverages server resources by minimizing the RAM required to serve many Django sites.
- Vyper-Django™ can serve an unlimited number of sub-sites (limited only by the available disk space).
- Typically a Django site requires 50 MB RAM however Vyper-Django™ can serve an arbitrary number of Django sites using a single 50 MB footprint.
Future Vyper-Django™ Features
- Plug-In Templates with automatic site menu creation.
- Vyper-Django™ Ajax Powered CMS (Content Management System) with in-place editing.
Vyper-Django™ Facts
- Vyper-Django™ consists of pure Python code.
- Vyper-Django™ does not fork any existing Django version.
- Vyper-Django™ is not a derivation of the Django Framework.
- Vyper-Django™ uses the Django Framework like any Django App.
- Vyper-Django™ uses the "Django" name like any other Django App that needs to identity what it works with.