Anders - if you get this working, do let us know (with any relevant
links). It'd be good to show the world... I worked for some time on
disability/technology/art projects, and I know at least one large UK
network of users that would be interested - DaveE
Hi,
I need a little advice about m
There are a few places you could stash one.
If you have some class somewhere, say, MyThinger, you could declare a little
accessor like this:
class MyThinger
class << self
attr_accessor :things
end
end
Then you would be able to write MyThinger.things and use it li
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
> a SQLlight database seems like the best way to go
given your initial scenario of read-only Excel files, i disagree. why plumb
data from Excel into SQLite and from SQLite into a web UI via several layers of
Ruby code, themselves distanced from underlying datastores via ORM libraries,
when you
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 i
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 r
If I'm understanding your question correctly I think judicious use of
the @state instance variable will achieve what you're looking for.
You'll be able to store what you need and be able to access it from
request to request.
Another option would be to use sqlite in memory mode.
App::Models::Base.
On Thu, Aug 25, 2011 at 15:25, Anders Schneiderman
wrote:
> Hi,
>
> I need a little advice about maintaining state in Camping.
>
Uh oh. Maintaining complex state is *always* a hassle, regardless of
language and framework…
The general way of maintaing state is using session cookies. It works like
Hi,
I need a little advice about maintaining state in Camping.
I use NaturallySpeaking voice recognition software for most of my work -- I
don't have happy hands -- and I've been creating little Ruby projects to
make it easier to do some things by voice. I'd like to build a UI for them.
After
9 matches
Mail list logo
