[Noisebridge-discuss] [RFC] Noisegate Web app prototype

[Eric W. Rasmussen]

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.


On 08.04.2013 11:11, Jeffrey Carl Faden wrote:
> Some more thoughts... sorry, I'll try to wrap the rest of them into 
> this post:
>
> If you're looking to animate the transition, you should do that using 
> CSS instead of JS. Check the example code here: 
> http://stackoverflow.com/questions/6092239/css3-one-way-transition 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.
>
> 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.
>
> 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).
>
> 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;"
>
> Jeffrey
>
> On Apr 8, 2013, at 10:52 AM, Jeffrey Carl Faden <jeffreyatw at gmail.com 
> <mailto:jeffreyatw at gmail.com>> wrote:
>
>> 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.
>>
>> Jeffrey
>>
>> On Apr 8, 2013, at 10:49 AM, Jeffrey Carl Faden <jeffreyatw at gmail.com 
>> <mailto:jeffreyatw at gmail.com>> wrote:
>>
>>> 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.
>>>
>>> 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.
>>>
>>> Jeffrey
>>>
>>> On Apr 7, 2013, at 11:54 AM, Garrett Smith <dhtmlkitchen at gmail.com 
>>> <mailto:dhtmlkitchen at gmail.com>> wrote:
>>>
>>>> On 4/7/13, Josh Juran <jjuran at gmail.com <mailto:jjuran at gmail.com>> 
>>>> wrote:
>>>>> [RFC == Request For Comments]
>>>>>
>>>>> In the interest of supporting Noisebridgers not running Android, I'm
>>>>> developing an implementation of Noisegate in DHTML (which might be
>>>>> better known by its marketing name "HTML5", although Noisegate
>>>>> doesn't use any features introduced by HTML version 5).
>>>>>
>>>>> So far, I have a user interface that works in (at least some) desktop
>>>>> browsers.
>>>>>
>>>> Why not just use an INPUT element? Should work everywhere.
>>>>
>>>> Nit: better compatibility with IE for   as id="code" first child.
>>>> (IE drops text nodes)
>>>> -- 
>>>> Garrett
>>>> Twitter: @xkit
>>>> personx.tumblr.com <http://personx.tumblr.com>
>>>> _______________________________________________
>>>> Noisebridge-discuss mailing list
>>>> Noisebridge-discuss at lists.noisebridge.net
>>>> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>>>
>>
>
>
>
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noisebridge.net/pipermail/noisebridge-discuss/attachments/20130408/f9d527d8/attachment-0003.html>