I'm more interested in understanding how to go from the code we have
now, to running the steps to allow myself to generate the lens view of
I can do the following if needed:
- host the xml file
- host a json representation of the file, if I could figure out how to
generate the JSON
- host the json representatio of the file on a server that supports JSONP
I don't know how to:
- instantiate refract against this one specific file
- figure out what refract would do with that file
- figure out how to get lens to look at the file that I've generated
As I am interested in playing around with some of the tools from
then I would prefer to just
get a quick description of how to do it myself, if that's possible,
rather than having you generate a modification.
I could also just checkout on a specific commit.
On Thu, Aug 22, 2013 at 2:43 PM, Michael Aufreiter <m...@zive.at
> How important is it for you to be able to demo that _right now_? With Lens
> 0.1.0, there's the dependency to a hosted converter or static doc repository
> using JSONP. If it's really urgent I can create a hot-patched version that
> does static files again. I'll put a strong focus on allowing you to do that
> demo with the 0.2.0 version asap. Can you wait? I've got most parts of the
> refactor done already, however I'm not able to test against real docs at the
> moment since the converter isn't yet ready.
> -- Michael
> You received this message because you are subscribed to the Google Groups
> "elife lens" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elife-lens+...@googlegroups.com
> To post to this group, send email to elife...@googlegroups.com
> For more options, visit https://groups.google.com/groups/opt_out