Re: Need advice on reliable way to identifyIE asthe browser

I don't have anything against Prototype. It seems lightweight and
fundamental enough that I wouldn't be inheriting a giant library for the
sake of implementing some doodad.

On a personal level I'm suspicious of using a framework. I would find it
unacceptable to become a tool user instead of a programmer. If I made peace
with the grittier portions of JavaScript then I'd be more open. I've been in
binds and considered popular frameworks. So far I've found that it'd take me
just as long to get used to a framework's conventions as to deepen my
knowledge of JavaScript. In the short run the time spent on a framework
would probably get better mileage but I prefer the mobility of getting more
intimate with the underlying language.

On Thu, Jul 31, 2008 at 12:47 PM, Walden H. Leverich <
WaldenL@xxxxxxxxxxxxxxx> wrote:

There are some schemes for normalizing the IE and DOM event
models. The ones I've used rely on nested ternery statements
checking for the presence of properties in the event object.

Seriously, and I don't represent them, but if you're generally playing
with browser differences look at prototype, he's done it for us. Are
there cases where you'll have to go outside of prototype? Sure! But not
many.

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.