> On Fri, Aug 23, 2013 at 1:21 PM, Greg Kempe <[email protected]> wrote: > >> .. > > >> We're exploring two options: >> >> 1. use Dancer to build the entire website >> 2. use Dancer to power a thin REST API around the library and use another >> framework (eg. in Python) to build the rich website experience. >> >> Our requirements include: >> >> * move quickly, use the right tool for the job (ie. favour re-using >> components over building everything from scratch) >> * modern website tooling, such as SASS for CSS, good HTML form support, >> model validation >> * well documented and mature software >> * relatively easy for other devs to work on the project later >>
Look at http://earth-base.org It is a Dancer1 app on server side (but it would be the same were it Dancer2) sitting between the client and various data stores (Postgres, raster files, text files, etc.). The client can be a browser (which is what you will see if you try out any of the http://earth-base.org/apps) in which case all the work is done by OpenLayers or Leaflet, jQuery, D3, etc. The client could also be other programs such as R, Python, anything that can query the server over http. As far as the clients are concerned, they have no idea what the backend is written in, and what the data stores are. Hope this gives you a few ideas. -- Puneet Kishor http://punkish.org science http://earth-base.org advocacy http://creativecommons.org _______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
