41–50 of 98 posts
Slick design, however, I don't understand the buttons. Why is 'eval' a joystick and commit a box? Also, whenever I hit Preview I get a 500.
We're changing that joystick to a VCR like play button. The commit one being a box hints at a shell or terminal, since we couldn't find an official Git icon. Could maybe put the GitHub Octocat there - what do you think?
Earlier quoted context omitted.
Why not use the buit-in keyboard-UI in the iPad?
It looks like the UI uses an editable div. I believe that editable divs do not trigger the built in keyboard on an iPhone, and there's no way to force it to do so.
The built-in one has a dictionary and some autocompletion, which could be good or annoying... :)
Earlier quoted context omitted.
We are aware of this and are working on an on screen keyboard, kind of like this: http://googleblog.blogspot.com/2010/04/integrating-virtual-k... To answer the question below: we would need a custom layout to ensure all the curly brackets and other common JS chars are one tap away
Why not use the buit-in keyboard-UI in the iPad?
Why doesn't @contenteditable work on the iPhone?
http://stackoverflow.com/questions/723592/why-doesnt-content...
Is contentEditable not supported by iPad?
http://www.quora.com/Is-contentEditable-not-supported-by-iPa...
Slick design, however, I don't understand the buttons. Why is 'eval' a joystick and commit a box? Also, whenever I hit Preview I get a 500.
We're changing that joystick to a VCR like play button. The commit one being a box hints at a shell or terminal, since we couldn't find an official Git icon. Could maybe put the GitHub Octocat there - what do you think?
---
+++
Earlier quoted context omitted.
It looks like the UI uses an editable div. I believe that editable divs do not trigger the built in keyboard on an iPhone, and there's no way to force it to do so.
Alright, but shouldn't the solution be to allow the user to use either Google's keyboard or the built-in(by using textarea)? The built-in one has a dictionary and some autocompletion, which could be good or annoying... :)
Slick design, however, I don't understand the buttons. Why is 'eval' a joystick and commit a box? Also, whenever I hit Preview I get a 500.
Earlier quoted context omitted.
Alright, but shouldn't the solution be to allow the user to use either Google's keyboard or the built-in(by using textarea)? The built-in one has a dictionary and some autocompletion, which could be good or annoying... :)
Most likely annoying if you're writing code.