On 2/9/07, Bil Kleb <Bil.Kleb at nasa.gov> wrote:> Does anyone have a non-database-backed Camping app with tabs
> they could share as an example? (Or suggest an alternative
> approach entirely.)
Leaving out the database is easy -- just don''t inherit from Base
(a.k.a. ActiveRecord::Base) in your model classes. In fact, for your
model, it looks like you could basically have a single
(namelist-backed) model class, representing a ''tab'' worth of
data from
your namelist file. Presumably, you''ve written (or have ideas about
how to write) the namelist marshalling code, and some sort of handler
for the metadata files described in your Tadalist item.
As far as making it "tabbed", I would personally probably just make
each "tab" a separate page to render, defining a controller class that
took the tab as a URL parameter, and having it load the current
''tab''
worth of data. See the attached example app for some code that does
this (albeit using a minimal, ugly chunk of CSS).
Does that help at all?
-Lennon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tabbing.rb
Type: text/x-ruby-script
Size: 1943 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/camping-list/attachments/20070209/88aa7ffe/attachment.bin