08-16-2013 11:14 PM
Having just reaf MSohm's blog entry on the demise of signing keys this remark stood out...
Support in the BlackBerry WebWorks SDK will be coming in its next release.
I'm just thinking that it might be a good idea to add a few of our own ideas to what we get rather than what we're simply provided with.
I'll set the ball rolling with a nice limited appeal one...
Request : Can the packager have be extended to include extensions of the type device-debug
Reason : At the moment you have only device or simulator builds possible. An extension can have debug-specific code that can be excluded from the production build of the extension by the judictious just of #ifdef (is there a pre-defined #define for debug?)
Example Use : I've added basic logging to extensions which proves highly useful when something doesn't do what you expect it do - just stick on a logging line and you can find out that was going on inside an extension (impossible otherwise). This doesn't want to be in a release build.
Note : While the JS interface for this example would still exist the returns woulld be empty as the #ifdef stuff would remove the functionality
08-17-2013 07:19 AM - edited 08-17-2013 07:20 AM
Here is my top-10:
08-17-2013 08:21 AM
(6) is almost there as part of an extension anzor_b wrote
It gives model but not subtype
There are some new APIs that give better info in 10.2