A case statement is undoubtedly the best/simplest logic for this implementation.
IMHO, if you are going to address the browser 'type', then you might consider
extending the taglib to include at least an appropriate sub-set of other client-side
properties.
Christian
-----Original Message-----
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, September 20, 2001 7:48 AM
To: [EMAIL PROTECTED]
Subject: Re: Browser detection taglib
been off the list for a bit. worm issues.
Anyway, a browser taglib sounds like a pretty nice idea. How exactly would
you envisage it working? Something that let's you do a kind of case-switch
statement on browsers?
<useragent:if browser="netscape" version="5">
Some mozilla html
</useragent:if>
??
<useragent:browser/> would output the name of the browser
<useragent:version/> would output the version
<useragent:platform/> would output the OS
or something else?
If no one else is working on it, then it's definitely on my TODO
list. Nice idea.
Bay
On Thu, 20 Sep 2001, Bob Lee wrote:
> I believe BrowserHawk has this covered, but it costs $$$. I free one would
> be nice.
>
> Bob
>
> > Hi all,
> >
> > Is there a browser/user-agent detection taglib in development out there
> > somewhere? If not would other people have use for it too?
> >
> > kind regards,
> > k@rl
>
>
>
>
application/ms-tnef
