-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation? #3
Comments
Agree with you completely. This project was done as more of a proof of concept, until I actually got it to work well. I'll be building it up in the next few weeks and it will most definitely have detailed documentation. Thanks for your suggestions @cfjedimaster. In response to the Camera plugin, it only provides base64 for now. In the future however, the extension should interpret the Any other suggestions would be great. |
Would you be able to roughly describe how the other ones are mocked? For example, motion, what kind of data will it return? |
All of the plugins can be found in the The device motion mock produces preset integers like so:
|
Ah - I have to read then. Bah. ;) Ok, thanks. :) On Thu, Dec 11, 2014 at 4:10 PM, Paolo Bernasconi [email protected]
Raymond Camden, Web Developer for Adobe Email : [email protected] |
Can you please document how this exactly works? I tried it on a camera demo. It never prompted me to select a picture, so I'm assuming the mock does... something automatic (what it does should be documented of course). The file URI returned by the plugin didn't work when entered in the DOM. So perhaps the mock only supports the base64 version - if so - again - it should be documented.
The text was updated successfully, but these errors were encountered: