Hold up guys. This is a little web app for just you to use? not multiple users?
Depending on how you deploy camping you can just stick some stuff in some class variables if you just need them in one controller, or even global variables if you want them in many places. Then all you'd need to do is boot a local copy with The Camping Server and do your things. The objects will just stay in ruby's memory because unlike cgi apps or things like PHP, ruby web apps don't flush their global scope reload on every request. Wouldn't that be the ridiculously easy and straight forward way to solve this? — Jenna On 26/08/2011, at 7:33 AM, Anders Schneiderman wrote: > Thank you so much Magnus and David for your speedy advice! > > Magnus, I think you're right a SQLlight database seems like the best way to > go. > > >Cool! Is easier to manage web apps than native apps using > >NaturallySpeaking, or is it just the the native window-based UIs are > >way too complex? I've never really optimized a web app for > >accessibility (which is pretty terrible when I think about it)? > It's a bit of both. NaturallySpeaking tries to make their software as > Web-friendly as possible, so, for example, if I display the fields I want to > be able to choose as a bunch of hyperlinks in a on the page, I can click any > of them by voice as I could any link on a webpage. With wxruby, that's not > the case. And since I've done a lot of HTML/CSS work in past jobs, I can > bang it out a lot faster than learning wxruby or some other UI – and it's a > lot easier to build something that has a little style to it. :) > > Thanks very much! > Anders > _______________________________________________ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list
_______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
