design advice

[=?Utf-8?B?cm9kY2hhcg==?=]

hey all,
i need to create a web page that has plenty of tabs on it (more than 10).
what would be the best way to go about this? would it be better to have an
..aspx page for each tab or a single .aspx page?

thanks,
rodchar

[David Wier]

That all depends - on each of these many tabs you have, do you have what
would relate to a page or more of information?
Also - is there anything that instrinsically locks each of the tabs together
(information-wise)?

IMHO, if you have quite a bit of info for each tab, (a page or more
information), I would create separate pages, with a menu for each of them

Still - it all depends on the content and size of the data....I, myself
would really need more information on your situation to make a really valid
decision.

--
David Wier
MVP/ASPInsider
http://aspnet101.com
http://aspexpress.com
"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:03**********************************@microsof t.com...

hey all,
i need to create a web page that has plenty of tabs on it (more than 10).
what would be the best way to go about this? would it be better to have an
.aspx page for each tab or a single .aspx page?

thanks,
rodchar

[Alexey Smirnov]

On Feb 28, 6:36 pm, rodchar <[e-mail]:

hey all,
i need to create a web page that has plenty of tabs on it (more than 10).
what would be the best way to go about this? would it be better to have an
.aspx page for each tab or a single .aspx page?

There are no best practices, I think. This is related to developer (if
no any tech.specs.) and you have to decide it.

Do you know about MultiView Control? Maybe it can answer this
question :-)

[=?Utf-8?B?cm9kY2hhcg==?=]

Could you please give me a small analogy about what you mean by
information-wise?

"David Wier" wrote:

That all depends - on each of these many tabs you have, do you have what
would relate to a page or more of information?
Also - is there anything that instrinsically locks each of the tabs together
(information-wise)?

IMHO, if you have quite a bit of info for each tab, (a page or more
information), I would create separate pages, with a menu for each of them

Still - it all depends on the content and size of the data....I, myself
would really need more information on your situation to make a really valid
decision.

--
David Wier
MVP/ASPInsider
http://aspnet101.com
http://aspexpress.com
"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:03**********************************@microsof t.com...

hey all,
i need to create a web page that has plenty of tabs on it (more than 10).
what would be the best way to go about this? would it be better to have an
.aspx page for each tab or a single .aspx page?

thanks,
rodchar

[Kevin Spencer]

It all depends on how much the pages have in common with one another. The
tabs are essentially unimportant. It is the links which the tabs represent
that are important. Each tab links to a page. If the pages have a great deal
in common with one another in terms of layout and functionality, you might
want to consider consolidating them into a single page that handles requests
differently according to QueryString and Form values sent. Otherwise, you
may be loading too much unused code into a single page, which would impact
performance.

--
HTH,

Kevin Spencer
Microsoft MVP

Help test our new betas,
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:03**********************************@microsof t.com...

hey all,
i need to create a web page that has plenty of tabs on it (more than 10).
what would be the best way to go about this? would it be better to have an
.aspx page for each tab or a single .aspx page?

thanks,
rodchar

[=?Utf-8?B?cm9kY2hhcg==?=]

Thanks everyone for the generous replies I appreciate it a lot.
Rod.

"Kevin Spencer" wrote:

It all depends on how much the pages have in common with one another. The
tabs are essentially unimportant. It is the links which the tabs represent
that are important. Each tab links to a page. If the pages have a great deal
in common with one another in terms of layout and functionality, you might
want to consider consolidating them into a single page that handles requests
differently according to QueryString and Form values sent. Otherwise, you
may be loading too much unused code into a single page, which would impact
performance.

--
HTH,

Kevin Spencer
Microsoft MVP

Help test our new betas,
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:03**********************************@microsof t.com...

hey all,
i need to create a web page that has plenty of tabs on it (more than 10).
what would be the best way to go about this? would it be better to have an
.aspx page for each tab or a single .aspx page?

thanks,
rodchar