I had another thought -- why not simply put everything you will ever
show in the page, but hide the things you don't need until they're
needed. If you do this hiding inside this block, up in the head of
the page:
document.observe('dom:loaded',function(){
//your hide statement here, perhaps this:
$$('.initially_hidden').invoke('hide');
});
then it will happen before the page ever shows in the browser. (in
1.6 or greater, that is)
So you go through and build your entire extended form, but the things
you want to hide for when you really need them you add the className
initially_hidden to them. And you also give them an ID so you can
show them later.
This will be a lot faster for the user, since everything is already
there. Unless your FMP server is completely under water, it's going
to be fairly straightforward to assemble a page with all the options
showing in one pass and then hide the "expert" stuff, rather than
pecking at it over and over. I believe that a lot of the pain of FMP
is waiting for it to initialize a view, kinda like CGI, right?
Walter
On Apr 9, 2008, at 1:30 PM, kodiacat wrote:
>
> Great idea! I haven't tried it yet, but I believe this is what I have
> been looking for. Thanks, I will let you know how this works.
>
> On Apr 9, 12:03 pm, Walter Lee Davis <[EMAIL PROTECTED]> wrote:
>> Instead of hiding it then, use $('tbody_id').update('') to clear it
>> again, which will leave things ready for the updater to re-fill it
>> again later.
>>
>> Walter
>>
>> On Apr 1, 2008, at 5:10 PM, kodiacat wrote:
>>
>>> Initially I thought I could leave the tbody element empty and then
>>> call the include using prototype's ajax.updater, which works, until
>>> they select no. If they select no, then the question's are still
>>> visible..if I add onclick ="element.hide"; to the no radio button,
>>> then it will hide it, but then if they select yes again it won't
>>> show.
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
