>>GridLayout is deceptively evil,
>
> That's what i mean by disparaging remarks. It's an option in the IDE, learn
> to use it properly.
Just because something exists as an option, doesn't mean it isn't a
feature that will cause more harm than good.
> If it didn't have a bona fide use, it would not be included - it wouldn't
> even be the default in two released versions.
> That by itself should be meaningful in and of itself.
Agreed, but there are things that cause more harm than good, regardless
of if they are options. For example, Option Explicit does not need to
be included in a VBScript/old school VB program, but should be, always,
and shouldn't have to be added to be included, agreed?
> * Why does the control I put beneath my DataGrid become covered up by
> my DataGrid when it has too many items?
> * My users are complaining because they have to horizontally scroll,
> how do I fix this?
> * I have a user with an older browser version, and the page looks like
> junk. What's wrong with ASP.NET, why won't it work for older browsers?
>
> All these concerns have extremely easy fixes that I trust you are imparting
> as a responsible and objective teacher.
Naturally. I show them the workaround, and then encourage them to
explore FlowLayout in more depth. With my students, I find that it's
ignorance that makes them hesitant to switch. They come from a non-Web
background, so they are not familiar with using <DIV>s, <table>s, or
other HTML elements to position content. This is all fine and good, but
the point is my experience of people who are proponents of Grid over
Flow are those who don't have a firm grasp on laying out a page without
absolute positioning. I believe in an earlier comment in this thread
you mentioned you had some good reasons for using Grid over Flow, I'd be
interested in hearing them.
> My take is that the web has evolved from simple web submission forms to
> complex applications that run in a browser - functionally equivalent to a
> windows application in a browser.
We're getting there, yes, but HTML is not going to be the markup to take
us there, XAML will. So I agree that GridLayout will be very important
in the future, but right now I find it to be substandard.
> For that type of programming, gridlayout is a must. For all other options,
> use gridlayout (that's not a typo either).
I take it you are developing your Web apps on an intranet, where the
browser is guaranteed? Do you still promote GridLayout when you know
you'll have visitors who, for example, might be coming from 2nd world
nations or universtities, where they might not be using the latest and
greatest browsers?
--
Scott Mitchell
http://www.4GuysFromRolla.com
* When you think ASP.NET, think 4GuysFromRolla.com!