It is envisaged that version 3 will be a rebuild that will not necessarily be fully backwards compatible with versions 1 and 2.
EVOKE version 3 is currently a blue sky conceptualisation It is envisaged that version 3 will be a rebuild that will not necessarily be fully backwards compatible with versions 1 and 2.
It is envisaged that version 3 will be a rebuild that will not necessarily be fully backwards compatible with versions 1 and 2.
distributed
evoke to be remodelled to operate as a distributed system: i.e. a system of nodes, instead of server/browser.
Each node will store data locally, and will sync local content with other nodes. Users will then be able to use evoke apps and data when their web connection is sporadic or absent.
This implies packaging the system for easy installation on posix systems (including OSX) and (if we must..) Windows
Each node will store data locally, and will sync local content with other nodes. Users will then be able to use evoke apps and data when their web connection is sporadic or absent.
This implies packaging the system for easy installation on posix systems (including OSX) and (if we must..) Windows
python 3
EVOKE 3 will be written in python 3, giving full unicode support (not just utf8)
sqlite database
sqlite to replace (or as a default alternative to) mysql. This will make evoke nodes more lightweight, and simpler to package and install. It also allows greater flexibility and simplicity in the use of the database (if mysql is no longer supported), as sqlite has a more simplistic design.
web server
Twisted may be replaced with another python web server, if it does not support python 3 in time for our purposes.
open ID
open ID logins to be supported, including Google federated logins