|Version 233 (modified by 9 years ago) ( diff ),|
Table of Contents
We define requirements:
Designs should focus on Usability:
Designs should fit within our overall architecture:
We write Tests:
We keep code conventions to maximise readability & consistency:
Code should be documented:
Code should be able to perform well at scale:
- Database Synchronization
- GIS - Mapping
- PrePopulate- initialising the database with lookup lists &/or demo data
- SVG - One way of producing Charts
- Templates for instance configuration
- Save Search and Subscription
- Scheduler - push long-running tasks async as well as have tasks run to a schedule (e.g. recurring daily)
- User Management
- Web Services
Browsers default to only downloading 2 files from the same origin at a time, so many files is very slow on high latency links.
We therefore consolidate into fewer, larger files when running in Production mode.
Although, note that iPhone 3.x cannot cache files larger than 15kb and in iPhone 4 the limit is 25kb. And this is the size before gzipping.
Since GIS is a specialised app which requires many files, it's JS is loaded separately when required.
The build script is
It needs to be run as a web2py script:
python web2py.py -S eden -M -R applications/eden/static/scripts/tools/build.sahana.py
There is also a convenience wrapper for Windows to run this:
You must have an internet connection to run the build script unless you have a local version of the Compiler.
Our build process is based on the one used by OpenLayers
This uses Google's Closure compiler to compress the JS. This is done using their web service, however for OpenLayers itself we need to download the jar file & place in the tools folder since this is over 1Mb:
ToDo: Investigate using other options instead:
ToDo: Download/execute scripts asynchronously:
- Android - Android clients
- Tips - useful links to explore
These are Translated versions of the documentation, which may be outdated compared to the English originals