oregonshakespearefestival / captioncast Goto Github PK

While I'm parsing this on the front end I'm finding it easier to work with character and line as separate attributes of each text object. I can always split these and format them on the front end with the first colon however. Would be most efficient to have Rails do this on ingest and have linking options available later for characters. V1 of mine is just parsing lines on the front end but if rails can make the separate properties available in the model I would incorporate the change pretty quickly.

As I revise the way the display view works, we obviously want to give the Operator the option to push a blank screen. As a result, we would want to reserve a "sequence" integer that would never be used. If you recall this is the place where the line falls in the script. At the moment, I'm using 0 as the "blank" sequence and artificially seeding it on the front end so when display view goes to the server and returns 0 in the heartbeat then it shows a blank line.

Depends on how data reads in from the script though. Do we want to reserve 0 for this purpose or should we keep it something like -1? Both appear to work on the front end however, I need to know from the back end what the pref is... if using 0 requires a rewrite of something, I can make -1 work.

Also, let me know if there's any issues with this approach at all, would require some rewriting of the display front end by can def do it.

What's the preferred method that we wish to use in rails for storing a site-wide, session-wide variable? Basically this would need to be shared across all users and all controllers and would contain the sequence integer of the current "line". I can stand up the front end logic now to handle passing posting and getting to the controller however we'll need to figure out the best thing that happens from there. We have options. I imagine a rails wizard would be able to advise on this very quickly

I need to dive a little deeper on this. Does it allow us to share a variable across all sessions?
http://stackoverflow.com/questions/2979327/rails-variable-across-all-controller-actions

We can also write to the application config.
http://stackoverflow.com/questions/20857886/where-can-i-store-site-wide-variables-in-rails-4

I find this approach to be a bit strange in that we would write to it so often (does the app only look at this when it's spinning up?) and for security reasons do we want people writing to the app config... and... for stability is the frequency of i/o on this reasonable...

Open to the thoughts of a more seasoned hand here RE: Rails back end...