On Oct 28, 2010, at 7:28 AM, PalaniKannan K wrote:
and params will be changed.
Kindly correct the above frameset operations. Its not creating
frames. Kindly suggest me your vision on this issue.
Palani Kannan. K,
Step back and ask yourself what problem you are intending to solve by
using frames. If it’s a user interface thing (scrolling area within a
larger page) then you can solve that easily with CSS. If it’s
accessing one view within another, then look into partials – this can
be a very elegant way to solve this problem within a single flat page.
Frames are such a mess to work with in any case, both for you and your
users, because they don’t provide a single URL for a single view. Your
Rails app would have to create an outer frameset page, then a separate
frame src page for each pane of that frameset. What holds these
together? What signals the default content for each sub-frame? If
you’ve got any sort of dynamic content happening within these frames,
what method are you using to glue them all together? If the user
updates one frame, how does that signal back to the others (if any
updates are necessary)? If the user updates one frame or navigates
within that frame, can she ever get back to a default page showing
this combination of information?
Please say a little more about your application, what it does, and why
frames are the solution in your case.