[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Standard place with advice for end-users.
- To: Steve Baker <firstname.lastname@example.org>, email@example.com
- Subject: Re: [Public WebGL] Standard place with advice for end-users.
- From: Bharathan Rajaram <firstname.lastname@example.org>
- Date: Wed, 13 Oct 2010 10:18:55 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=3qQX17fmqd8A9sWeIWQ6y/9yLFQw2blhnMNOz+BVh7E=; b=ZCA9O7kr0T31d3nq9gCfgVossrqU0k64MC6ob66SozQ8WtV1QqvcmVVd6/4/n51m9u BGsjYkSbPPwim8sLIU568GJu7ZnpBhwuduLGgIDXjjsGXHVjrZVZzAqLmEJPDFYvnbiH H/v4F1CdEywdJT4dPrJXbUFGUvIMD1zgMTLyM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=vP4zZf2wVgVE9FBQgJuA/pOKMGoVBFiVzMG7mBrsnU4RWePZOBEkrOjxMHirWvlMBk Q6T4ROm6e/h9gIuBvXz/W+F30fIZf7GoVujRCX+He5lBxHyNS9a49p5+5Gl0Y90CVmSH wyRGzd5rdfBZuFJJGk0y5u73YHjc2MW3ZWjsw=
- In-reply-to: <4CB5C010.email@example.com>
- References: <4CB5C010.firstname.lastname@example.org>
- Sender: email@example.com
While there isn't a standard page, I think that this one comes pretty close:
What do you think? Is it a suitable stand in?
On Wed, Oct 13, 2010 at 8:20 AM, Steve Baker <firstname.lastname@example.org>
When the user is using a browser without WebGL support, I currently
display a page telling them that there is a problem - but I'd like to
tell them how to fix that.
It would be nice if there was a standard URL that we could redirect them
to. This page would list the available browsers for each platform and
provide download instructions/links - perhaps also outline minimum
hardware specifications. Someone would have to undertake to keep it
current. In the interests of neutrality - this should probably be the
I'm thinking of something like the provisions made for Shockwave - where
authors can use a standard icon (a lego brick with an arrow) and simply
link the user to:
Obviously in our case, it would have to say something like - "Go here to
download the latest WebGL-supporting version of Chrome, go here to get
that for Firefox, go there for Safari...etc" - it could maybe also
provide some means to check for hardware and OS compatibility.
The closest thing we have (I guess) is the Wiki page...but that's hardly
adequate for more naive end-users:
If we don't do this centrally then each application author would come up
with something different - these would get outdated - it would rapidly
become a horrible mess.
You are currently subscribed to email@example.com.
To unsubscribe, send an email to firstname.lastname@example.org with
the following command in the body of your email: