These are chat archives for fieldpapers/fieldpapers

16th
Dec 2015
Ian Ross
@ian-ross
Dec 16 2015 13:11
Yeah, I was just writing you an email...
But instead of writing an email, I'll just say things here where it's more visible!
I like the first wireframe better, even though the other two are probably "cuter". The reason for that is mostly just about UI visibility. In the current wizard-based Field Papers UI, the things that you can modify when creating an atlas are spread across a bunch of pages, so it's hard for a user to get an overview of what factors they can change. The first wireframe you made basically solves that problem at one stroke because everything is right there and visible. The other approaches with buttons and stuff sliding in and out are just as discoverable, of course, but there's little enough "stuff" in the Field Papers UI that I think it makes sense to just present it right there to the user all in one go.
Ian Ross
@ian-ross
Dec 16 2015 13:18
Anyway, what I'd suggest you do next is to set yourself up a "ui-experiments" branch in the Cadasta/fp-web repo and make the standalone HTML+Javascript testbed we talked about. (For everyone else, the idea here was that Lindsey could make a standalone thing for experimenting with UI setup before we make changes to the RoR backend to accommodate whatever new workflow the UI has. The most difficult bits of all this are working out a really good UI process for managing the page composer grid, and it seems as though it would be easier to do that independently of the backend. It will also make it clear how easy or difficult it will be to serve up the Javascript UI as a separate component for embedding Field Papers in other applications.)