Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Advice Needed

0 views
Skip to first unread message

Paul W Smith

unread,
Mar 21, 2010, 1:59:32 PM3/21/10
to
http://www.jcdarts.co.uk/History.aspx

As anyone who looks at the code for the above page will see the code is
about 3700 line long.

Does anyone have any suggestions on how I can split the code into several
pages.

I have had the idea of holding each year (or season) on a separate HTML
pages each held in a iFrame control on each page of the outer TabContainer.

Paul Smith

(Apologies if this is the wrong group to post this to)


Mike Lovell

unread,
Mar 21, 2010, 3:41:45 PM3/21/10
to

AJAX and databinding would cut that down.

--
Mike
GoTinker, C# Blog
http://www.gotinker.com

Gregory A. Beamer

unread,
Mar 22, 2010, 1:40:58 PM3/22/10
to
"Paul W Smith" <p...@NOSPAM.twelve.me.uk> wrote in message
news:OcE7NBSy...@TK2MSFTNGP06.phx.gbl...


Databinding and paging come to mind. Right now, it looks like you are only
showing a small portion of the data on screen. I did not look at source, so
I assume (based on the timing of the post) you are spitting everything out
but the div is constrained. Adopting a data bind with paging support will
allow you to show pages of information. Mike's suggestion of "repainting"
the next page using AJAX works nicely, as it gives the appearance of being
more fluid, but it is not mandatory to solve the problem.

--
Peace and Grace,
Greg

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

************************************************
| Think outside the box! |
************************************************

Alexey Smirnov

unread,
Mar 23, 2010, 11:37:08 AM3/23/10
to

If you don't want to have a refresh, use Ajax
If refresh is not a problem, do it in the regular ASP.NET way with
postbacks for every part of the page

Andy O'Neill

unread,
Mar 23, 2010, 1:21:29 PM3/23/10
to

"Paul W Smith" <p...@NOSPAM.twelve.me.uk> wrote in message
news:OcE7NBSy...@TK2MSFTNGP06.phx.gbl...
I think that's the simplest.
I would maybe try and do it with one iFrame.
Make a separate aspx page for each tab.
When the page initially loads, chuck the default child page in the iframe.
Make clicking on each tab postback.
Put the appropriate page into the iFrame on postback page load.
Everything is split out separate and the IO from web to database is reduced.

0 new messages