Web and WebWorks Development

[sh2sg]

It's solved, no need to recompile with BB10 SDK. Thanks for your tip anyway.

[sh2sg]

2. Performance will be better with the BB10 SDK since it's using the Native SDK to compile instead of the AIR one

Compilation performance or runtime performance? 

[nathanpc]

Runtime performance. The compilation performance is almost the same as the AIR SDK, but since the wrapper is using native code instead of AIR it runs better and can connect with the system better too.

[sh2sg]

I don't think bar file compiled with BB10 's SDK  works on Playbook. I have to compile for BB10 and PB separately and submit them as bundle right? 

I have spent couple of days on changing my apps to support both PB and BB10 in a signle binary, now I still have to separate them... that's sad.

[nathanpc]

That's what everyone does. Compile the PlayBook version with the PlayBook SDK and then compile the BB10 version with the BB10 SDK, then submit them to the App World in the same release bundle.

[sh2sg]

Thanks, I just did that. Noticed BB10 SDK compiled bar loads faster than PB SDK compiled bar, but rotation detection is slower than PB's SDK. maybe worth maintaining 2 binaries.

[nathanpc]

It's completely worth keeping two binaries. Anyway, this is the script I wrote to automate the process: https://github.com/nathanpc/build-webworks

[sh2sg]

I have a question for Package ID.

My apps old versions in AppWorld are all PB only.

If I update my app and compile with PB and BB10 SDK and submit file bundle

I need to

1. compile and sign PB version first,

2. extract Package ID from signned PB bar file

3. Add package ID to BB10 config.xml 

    <widget xmlns="http://www.w3.org/ns/widgets" xmlns:rim="http://www.blackberry.com/ns/widgets" version="2.0.1" id="package-id">

4. compile and sign BB10 bar

Is this correct? 

[nathanpc]

Yup, you need to do that just in the first time, since the Package-ID from the PlayBook package never changes.

[sh2sg]

Thank you nathanpc, much appreciated.