Dweba: Distributed and Web Application Framework for Python
Project description
Dweba is a framework and work environment
to develop and run distributed and web applications using
the python programming language. It contains SPyRO and DOM3K (the libraries for
Distributed applications and AJAX framework).
In this package you will find packages (named objects in SPyRO) as follows:
+ Useradmin: Management of users and groups
+ Packadmin: Package manager and editor. You can update, upload, pack, unpack, backup,
files and packages, and connects the objects pools to GuiGo!
+ ProxyKong: A Simple and flexible http proxy, with support for authentication
+ GuiGo!: The Graphical User Interface Object Generator, it uses databases to create
object GUIs that can be easy customizables.
+ forum: A simple forum
======
- Guigo:
+ Foreign fields now are shown with preview_<table>, so pretty names are shown
+ Interface with minor changes
- Packadmin:
+ Modifications to frames and viewweb
- Configuration:
+ A simpler configuration
+ More documentation
- db3k
+ manager sqlite3, sqlite2 are now just aliases of sqlite
and we try to use first sqlite3, and then sqlite2
to develop and run distributed and web applications using
the python programming language. It contains SPyRO and DOM3K (the libraries for
Distributed applications and AJAX framework).
In this package you will find packages (named objects in SPyRO) as follows:
+ Useradmin: Management of users and groups
+ Packadmin: Package manager and editor. You can update, upload, pack, unpack, backup,
files and packages, and connects the objects pools to GuiGo!
+ ProxyKong: A Simple and flexible http proxy, with support for authentication
+ GuiGo!: The Graphical User Interface Object Generator, it uses databases to create
object GUIs that can be easy customizables.
+ forum: A simple forum
======
- Guigo:
+ Foreign fields now are shown with preview_<table>, so pretty names are shown
+ Interface with minor changes
- Packadmin:
+ Modifications to frames and viewweb
- Configuration:
+ A simpler configuration
+ More documentation
- db3k
+ manager sqlite3, sqlite2 are now just aliases of sqlite
and we try to use first sqlite3, and then sqlite2