Great to see your mail...
that certainly is a great approach ...
But I was thinking on following lines ..

"Let's have an embedded IFRAME in the HTML, this shall remain invisible
though out the operation...
On click of the new tab, the html in the iframe shall be submitted to
desired action class path identifier and we manage the tab's using div or
span just the way you have explained. This approach shall use the same
IFRAME to submit for all tabs."

If it can work the way you have suggested, it would certainly make our life
simpler...we would not require the hidden IFRAME.
Cheers
Puneet
----- Original Message -----
From: "Hue Holleran" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>; "'Puneet
Agarwal'" <[EMAIL PROTECTED]>
Sent: Wednesday, March 05, 2003 11:46 AM
Subject: RE: TILES - Network Traffic...


> Hi Puneet,
>
> Sorry for the delay in responding - I've been away for a few days.
>
> What you describe is similar to what we did in a web application about 12
> months ago - but that was using <SPAN...> to display/hide the page
> contents - so in fact all tabs were loaded first and then just displayed
> when needed. This was using a bit of javascript on the client - the most
> difficult part was rebuilding the "tabs" on the client browser - to
visibly
> highlight the page being displayed. This was done by building a HTML
string
> in script and assigning the contents of the string to the innerHTML of a
> <DIV...>
>
> I guess it may be possible to check if the IFrame has been loaded (i.e.
src
> has been populated) and if not set the "src" property and set visibility
to
> "visible" (after setting the non-selected tabs' visibility to hidden).
This
> would allow re-displaying already downloaded tab's contents and
downloading
> on-the-fly new tabs. Already downloaded IFrames would be rendered but
> hidden. This may work very nicely indeed.
>
> H.
>
> -----Original Message-----
> From: Puneet Agarwal [mailto:[EMAIL PROTECTED]
> Sent: 03 March 2003 20:11
> To: Struts Users Mailing List
> Subject: Re: TILES - Network Traffic...
>
>
> Hue,
> That's exactly what I am looking at to be able to use both TILES and
> IFRAMES.
> Especially for TAB's, I want to achieve the following :
>
> "My page has two tabs, when the page loads up, it shows the fist tab and
has
> not brought the information about second tab,
> but when use clicks on the second tab, information about the second tab
> comes from the server side, now after this if user goes back to tab 1, it
> should not go to server side."
>
> I am looking as to how can I achieve this using both TILES and IFRAMES, to
> avoid the network round-trip.
>
> I understand that this may not be possible by using "TILES only".
>
> Thanks for your views
> Cheers
> Puneet
>
> ----- Original Message -----
> From: "Hue Holleran" <[EMAIL PROTECTED]>
> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>;
"'Puneet
> Agarwal'" <[EMAIL PROTECTED]>
> Sent: Monday, March 03, 2003 6:22 PM
> Subject: RE: TILES - Network Traffic...
>
>
> > Please don't flame - I'm not trying to start a tiles vs frames debate.
> >
> > If bandwidth is absolutely critical then you may want to consider
(shock!
> > horror!) frames or use inline IFrames. Tiles is great but will produce a
> bit
> > of extra output over frames as it will generally be used to render the
> > entire page, header, body, menu footer etc.  Images should be cached by
> the
> > browser, as will other add-in files if you use references to external
.js
> > files etc.
> >
> > I think it will be unlikely that you could save much bandwidth by using
> > frames but you may be able to reduce the bandwidth a little - if you
> really,
> > really have to - but this will be offset by the (significantly?)
increased
> > difficulty of managing and developing with frames, particularly.
> Personally
> > I do not favour frames.
> >
> > Tiles makes it much, much easier to manage layouts but is analagous to a
> > jsp:include (but oh so much more powerful - see link in Cedric's email
for
> > earlier thread) so will not, in itself save bandwidth.
> >
> > You can still use IFrames with tiles and this combination can be great
for
> > say a menu that needs to flick between a few options - I guess you could
> use
> > javascript to dynamically update the reference in an IFrame and this
will
> > save bandwidth.
> >
> > H.
> >
> > -----Original Message-----
> > From: Puneet Agarwal [mailto:[EMAIL PROTECTED]
> > Sent: 03 March 2003 16:45
> > To: Struts Users Mailing List
> > Subject: TILES - Network Traffic...
> >
> >
> > I am quite new to TILES and have a query abt the way it renders HTML
> pages.
> >
> > Does it embed the javaScript code into the HTML page itself or
> > it has generic JavaScript Library files, and includes them using a
> > JavaScript include directive in HTML for JavaScript file, so that it
could
> > be cached at client side and lead to smaller payload on network front.
> > If not is there any other advantage of using TILES.
> >
> > For our project network traffic is the biggest concern, the decision to
> use
> > TILES greatly depend on the above.
> > Your view shall help us greatly.
> >
> > Cheers
> > Puneet
> >
> >
> > ---------------------------------------------------------------------
> > 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]
> >
> >
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to