Changes between Version 2 and Version 3 of DeveloperGuidelines/Libraries


Ignore:
Timestamp:
07/04/13 10:52:03 (8 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Libraries

    v2 v3  
    1 Obviously, where possible, we should make use of existing Python libraries:
    2  * http://pypi.python.org/pypi/
     1= Libraries =
     2
     3We make use of several external libraries for which we maintain a list of dependencies within our update check:
     4* https://github.com/flavour/eden/blob/master/modules/s3_update_check.py#L38
     5
     6Wherever possible, external libraries should be optional to just the features which make use of them.
     7
     8The only core external libraries we currently have are:
     9* Web2Py
     10* lxml
     11* dateutil
     12* Shapely (mandatory for all mapping)
     13
     14We also include a few small ones within our own code base:
     15* EXIF
     16* Facebook
     17* GeoJSON
     18* PyGSM
     19* PyParsing
     20* Savage
     21* Tropo
     22* Wurfl
     23
     24As well as several JavaScript ones:
     25* jQuery & some plugins
     26* jQueryUI
     27* ExtJS
     28
     29
     30When looking to add new functionality, where possible we should make us of our existing libraries.
     31
     32Where this isn't possible we should try to make use of existing Python libraries:
     33* http://pypi.python.org/pypi/
    334
    435If these aren't available then we can make use of:
    5  * Java libraries using Py4J: http://py4j.sourceforge.net
    6  * C/C++ libraries using SWIG: http://www.swig.org
    7  * .Net libraries using !IronPython: http://www.codeplex.com/IronPython
     36* Java libraries using Py4J: http://py4j.sourceforge.net
     37* C/C++ libraries using SWIG: http://www.swig.org
     38* .Net libraries using !IronPython: http://www.codeplex.com/IronPython
    839
    940----