<div>'s aren't equivalent to frames in most cases... the most important
difference is that of namespacing... when you use frames, there's no
worry of Javascript or DOM element name collisions, which can occur with
simple <div>'s.
Marc, what aren't you happy about with the frame-based design? I've
done a lot of that over the years and, once you learn to avoid the
pitfalls, it's worked out great. I admit that in recent years I've
leaned towards iFrames when frames were necessary at all, and certainly
some of the problems associated with regular frames are avoided with
iFrames... but what problems are you seeing that you're trying to
overcome? That answer will guide your decision-making quite a bit.
Frank
--
Frank W. Zammetti
Author of "Practical Ajax Projects With Java Technology"
(2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
(2007, Apress, ISBN 1-59059-816-4)
and "Practical DWR 2 Projects"
(2008, Apress, ISBN 1-59059-941-1)
Java Web Parts - http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
Laurie Harper wrote:
Antonio Petrelli wrote:
2008/2/11, Marc Eckart <[EMAIL PROTECTED]>:
But we are not so happy with this frame aproaches in general. But we
don't
know how to integrate the different (indepentend) applications
transparent
to the users without frames.
A portlet container?
Regular divs loaded via AJAX? (e.g. using <s:div theme="ajax"...)
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
