<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Agreed. What does that have to do with this web app?<div><br></div><div>Jeffrey</div><div><br><div><div>On Apr 8, 2013, at 1:16 PM, "Eric W. Rasmussen" <<a href="mailto:ewr@majortek.com">ewr@majortek.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
I think it would be a great idea to have a special code/ring alarm
for handicapped folks (those that are coming up via elevator). Users
would know to make a path/check the elevator for availability.<br>
<br>
<br>
<div class="moz-cite-prefix">On 08.04.2013 11:11, Jeffrey Carl Faden
wrote:<br>
</div>
<blockquote cite="mid:B7E50582-8CF4-4D38-8544-910CFEA9A808@gmail.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Some more thoughts... sorry, I'll try to wrap the rest of them
into this post:
<div><br>
</div>
<div>If you're looking to animate the transition, you should do
that using CSS instead of JS. Check the example code here: <a moz-do-not-send="true" href="http://stackoverflow.com/questions/6092239/css3-one-way-transition">http://stackoverflow.com/questions/6092239/css3-one-way-transition</a> This
will cause the button to immediately turn a color when clicked,
then fade back to the original color after a designated amount
of time.</div>
<div><br>
</div>
<div>When it comes to wiring up the pad to submit, I might suggest
using AJAX instead of just submitting the hidden form on the
page. Maybe you're already planning that.</div>
<div><br>
</div>
<div>You should also add cursor: pointer to your CSS for the table
cells (or for the buttons, if you decide to add those in for
accessibility reasons).</div>
<div><br>
</div>
<div>If you were looking to center the table, offsets like left or
right only work if you've absolutely positioned the element. But
you can't set both an offset of left and right - only one in
each dimension. You might want to use this tactic instead, which
will generate as much margin as possible equally on the left and
right of the table, pushing it to the center: "margin: 0 auto;"</div>
<div><br>
</div>
<div>Jeffrey</div>
<div><br>
<div>
<div>On Apr 8, 2013, at 10:52 AM, Jeffrey Carl Faden <<a moz-do-not-send="true" href="mailto:jeffreyatw@gmail.com">jeffreyatw@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">I would also suggest adding a <meta
name="viewport" content="width=device-width,
user-scalable=no"> to make the numbers appear fullsize
without having to zoom in.<br>
<br>
Jeffrey<br>
<br>
On Apr 8, 2013, at 10:49 AM, Jeffrey Carl Faden <<a moz-do-not-send="true" href="mailto:jeffreyatw@gmail.com">jeffreyatw@gmail.com</a>>
wrote:<br>
<br>
<blockquote type="cite">If you don't like the standard
keyboard on smartphones and would prefer a numerical one,
use <input type="number">. That will cause a numpad
to appear on iOS and Android.<br>
<br>
You might also consider putting <button> elements
inside each table cell and styling those to only show the
numbers inside them, but that is kind of a triviality.<br>
<br>
Jeffrey<br>
<br>
On Apr 7, 2013, at 11:54 AM, Garrett Smith <<a moz-do-not-send="true" href="mailto:dhtmlkitchen@gmail.com">dhtmlkitchen@gmail.com</a>>
wrote:<br>
<br>
<blockquote type="cite">On 4/7/13, Josh Juran <<a moz-do-not-send="true" href="mailto:jjuran@gmail.com">jjuran@gmail.com</a>>
wrote:<br>
<blockquote type="cite">[RFC == Request For Comments]<br>
<br>
In the interest of supporting Noisebridgers not
running Android, I'm<br>
developing an implementation of Noisegate in DHTML
(which might be<br>
better known by its marketing name "HTML5", although
Noisegate<br>
doesn't use any features introduced by HTML version
5).<br>
<br>
So far, I have a user interface that works in (at
least some) desktop<br>
browsers.<br>
<br>
</blockquote>
Why not just use an INPUT element? Should work
everywhere.<br>
<br>
Nit: better compatibility with IE for as
id="code" first child.<br>
(IE drops text nodes)<br>
-- <br>
Garrett<br>
Twitter: @xkit<br>
<a moz-do-not-send="true" href="http://personx.tumblr.com/">personx.tumblr.com</a><br>
_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a class="moz-txt-link-freetext" href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Noisebridge-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a>
<a class="moz-txt-link-freetext" href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>Noisebridge-discuss mailing list<br><a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss<br></blockquote></div><br></div></body></html>