altternative to frames

[Ravikanth[MVP]]

Hi

If you want Content Frame in scroll bar use div tag.

HTH
Ravikanth

>-----Original Message-----
>ok, Everyone hates frames in .Net. I get this. I
>understand that user controls should be used to handle

the

>same functionality but I have a few questions. Below is

a

>crude outline of a page.
>
>-------------
>Header Frame
>-------------
>Content Frame
>-------------
>Footer Frame
>-------------
>
>I need the header to always be at the top and the footer
>always at the bottom, in other words always visible.
>
>The header and footer are dynamic in that they have
>different buttons show up depending on the content frame
>(I think we worked out how to make this happen).
>
>The issue is that the content frame needs to scroll in
>some case and not in others.
>
>Is the common practice to then create a user control for
>the content frame?
>
>If this is the case I have about 100 pages to create so

in

>essence I create 100 user controls as well. Is this

right?

>
>Can I just have one aspx page and dynamically change the
>content control?
>
>Last question, I promise. We use form based security

from

>a table I assume I could deny access to the contol based
>on checking the tbale (simulating not loadin the page).
>
>Sorry for all the questions but this is quite new.

Thanks

>in advnace for any advice and input.
>.
>

[noname]

sorry this doesn't help you max...but why does everyone hate frames in
asp.net as you say? i need frames to have a scrollable list of items with
formatting that's not possible in a list box. this is impossible otherwise
right? why are frames bad?

thanks.

"Max" <mshaneyfelt@comsult.com> wrote in message
news:00d801c34d3f$14d9ead0$a101280a@phx.gbl...

> ok, Everyone hates frames in .Net. I get this. I
> understand that user controls should be used to handle the
> same functionality but I have a few questions. Below is a
> crude outline of a page.
>
> -------------
> Header Frame
> -------------
> Content Frame
> -------------
> Footer Frame
> -------------
>
> I need the header to always be at the top and the footer
> always at the bottom, in other words always visible.
>
> The header and footer are dynamic in that they have
> different buttons show up depending on the content frame
> (I think we worked out how to make this happen).
>
> The issue is that the content frame needs to scroll in
> some case and not in others.
>
> Is the common practice to then create a user control for
> the content frame?
>
> If this is the case I have about 100 pages to create so in
> essence I create 100 user controls as well. Is this right?
>
> Can I just have one aspx page and dynamically change the
> content control?
>
> Last question, I promise. We use form based security from
> a table I assume I could deny access to the contol based
> on checking the tbale (simulating not loadin the page).
>
> Sorry for all the questions but this is quite new. Thanks
> in advnace for any advice and input.

[bruce barker]

they are just out of vogue, and .net has little support for them, even
though .net smart navigation uses frames in its implementation.

-- bruce (sqlwork.com)

"noname" <askme@fake.com> wrote in message
news:e#$6OKUTDHA.3132@tk2msftngp13.phx.gbl...

> sorry this doesn't help you max...but why does everyone hate frames in
> asp.net as you say? i need frames to have a scrollable list of items with
> formatting that's not possible in a list box. this is impossible

otherwise

> right? why are frames bad?
>
> thanks.
>
> "Max" <mshaneyfelt@comsult.com> wrote in message
> news:00d801c34d3f$14d9ead0$a101280a@phx.gbl...

> > ok, Everyone hates frames in .Net. I get this. I
> > understand that user controls should be used to handle the
> > same functionality but I have a few questions. Below is a
> > crude outline of a page.
> >
> > -------------
> > Header Frame
> > -------------
> > Content Frame
> > -------------
> > Footer Frame
> > -------------
> >
> > I need the header to always be at the top and the footer
> > always at the bottom, in other words always visible.
> >
> > The header and footer are dynamic in that they have
> > different buttons show up depending on the content frame
> > (I think we worked out how to make this happen).
> >
> > The issue is that the content frame needs to scroll in
> > some case and not in others.
> >
> > Is the common practice to then create a user control for
> > the content frame?
> >
> > If this is the case I have about 100 pages to create so in
> > essence I create 100 user controls as well. Is this right?
> >
> > Can I just have one aspx page and dynamically change the
> > content control?
> >
> > Last question, I promise. We use form based security from
> > a table I assume I could deny access to the contol based
> > on checking the tbale (simulating not loadin the page).
> >
> > Sorry for all the questions but this is quite new. Thanks
> > in advnace for any advice and input.

>
>

[Kevin Spencer]

Everyone doesn't hate frames. They are simply problematic. In other words,
you can certainly use frames in an ASP.Net app, but it will require a good
bit more work to get it to work right.

In your situation, I believe that you could create 3 controls. One would be
the Header. One would be the Footer. The third would be a host control to
hold the other 2, a table with 3 rows. If you need scrollability in the
middle, it could be done in any of several ways, depending upon what browser
you're targeting. For example, if you are targeting IE only, you could use a
scrollable div. On the other hand, you could also use an iFrame, but again,
it wouldn't work in all browsers. If you have to have scrollability, AND
work in all browsers, you'll probably have to use frames.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
[url]http://www.takempis.com[/url]
Big things are made up of
lots of little things.

"Max" <mshaneyfelt@comsult.com> wrote in message
news:00d801c34d3f$14d9ead0$a101280a@phx.gbl...

> ok, Everyone hates frames in .Net. I get this. I
> understand that user controls should be used to handle the
> same functionality but I have a few questions. Below is a
> crude outline of a page.
>
> -------------
> Header Frame
> -------------
> Content Frame
> -------------
> Footer Frame
> -------------
>
> I need the header to always be at the top and the footer
> always at the bottom, in other words always visible.
>
> The header and footer are dynamic in that they have
> different buttons show up depending on the content frame
> (I think we worked out how to make this happen).
>
> The issue is that the content frame needs to scroll in
> some case and not in others.
>
> Is the common practice to then create a user control for
> the content frame?
>
> If this is the case I have about 100 pages to create so in
> essence I create 100 user controls as well. Is this right?
>
> Can I just have one aspx page and dynamically change the
> content control?
>
> Last question, I promise. We use form based security from
> a table I assume I could deny access to the contol based
> on checking the tbale (simulating not loadin the page).
>
> Sorry for all the questions but this is quite new. Thanks
> in advnace for any advice and input.