incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: platform 'errgen'
Date Mon, 12 Mar 2012 19:00:48 GMT
Yes I like it. To reiterate what you said, if only to be able to quickly
and easily test how your application performs when only errors are
returned seems quite useful.

On 3/12/12 6:58 AM, "Patrick Mueller" <> wrote:

>About two weeks ago, I spent the morning working on a new 'platform' for
>Cordova, using the cordova-js framework.  The original goal was to build a
>platform that doesn't require ANY native code, so that you could use it in
>the browser.  Since the Cordova 'APIs' have to do >something< I decided
>have them all return errors.  I called the platform 'errgen', and here's a
>commit to a fork of mine with the code (and various drive-by fixes as
>Seems to me like there's a couple of interesting things here:
>- building a platform like this shows you what sort of internal frameworky
>things a platform has to do to get itself up and running; eg. a platform
>has to arrange to call
>`require('cordova/channel')` when `DeviceInfo`
>- having a platform that doesn't require any natives means you can load it
>in a desktop (or mobile) browser to see if you have any structural issues,
>and use desktop tooling like (real) Web Inspector to debug some bits.
>- having a platform that returns errors every time you do something would
>be a good way to test that your application actually handles errors
>Any interest in continuing this work?  There's some meta-work that needs
>be done; eg. decide how to handle "repeat-fire" APIs (eg,
>I could also see perhaps having a platform just like 'errgen', but always
>returns the same static-y 'success' bits all the time.
>Patrick Mueller

View raw message