Added images showing tablet version: http://imgur.com/a/ZkbtX
On Tue, May 22, 2012 at 9:53 AM, Brian LeRoux <[email protected]> wrote: > ooh, that does look nice! a little nervous we're going to be > inheriting some strong maintenance w/ something like this but it is > pretty cool > > On Tue, May 22, 2012 at 4:41 PM, Drew Walters <[email protected]> wrote: >> Took a couple of screen captures of Libby's sample project for those >> that haven't built/run it: >> >> http://imgur.com/a/1BtRl >> >> On Tue, May 22, 2012 at 9:23 AM, Patrick Mueller <[email protected]> wrote: >>> On Tue, May 22, 2012 at 7:37 AM, Patrick Mueller <[email protected]> wrote: >>> >>>> Kinda crazy thought: howzabout some kind of mini-REPL. I often take the >>>> template and just add a button to it to get it to run some code, check the >>>> result of something, or whatever. Would be even easier to do that sort of >>>> thing it we provided the capability, out of the box. It's truly eval. >>>> >>> >>> I tried this, and it's just awful. Thought maybe in the simulator, but ... >>> no. I retract the "mini-REPL" idea. >>> >>> However, the first thing I did in the mini-REPL was to paste a sample from >>> the API docs in and run it. Which reminded me about my thought about >>> making the API doc an app, where every sample has a "run" button next to >>> it, and an output area where the output is written to. >>> >>> Compared to a green field effort like Libby's, having such an app would >>> ensure that our doc samples actually work. Kinda dog-fooding the doc ... >>> >>> This wouldn't be the "initial app" we ship; too complex. Which is probably >>> true for Libby's app as well. The initial app prolly shouldn't do much, >>> but I like Jesse's idea of writing the cordova version into the DOM at a >>> minimum. >>> >>> -- >>> Patrick Mueller >>> http://muellerware.org
