[Ssc-dev] frontend stuff

[Svetlana Chirkova]

Hi guys, and Jonathan more specifically,
I'm pulling out all the j3m retrieval and parsing logic out of the JS
framework on the front end, and moving it to python. With the goal of
unloading the client side and having the option of persisting the separate
j3m artifacts.

so far it's all going in here v2j3m.py
<https://github.com/harlo/InformaFrontend/blob/master/v2j3m.py> for
testing, but will be broken up into more modular structure.

Question: the original plan was to make a lightweight REST api making each
j3m artifact (mapping to an icon or a value or a graph) available via a
GET, so it can be called asyncronously by the presenttinng page.

but while making a test page  http://localhost:8888/v2j3mview/<doc -id> (
e,g. http://localhost:8888/v2j3mview/22f9261d2bee2058379095d8d9ea73b1), i
realised the other option i to have tornado run all the functions in
parallel and render the parts to the page when each becomes ready (since it
has all this cool async and multithread stuff built in to it).

So Jonanthan - which would you rather? i can wrap each part in what ever
html template is necessary. Or do the requests yourself?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/ssc-dev/attachments/20140927/ae7fbf67/attachment.html>