08-07-2012 08:28 PM
Is it possible to have both configurations installed at the same time for flash builder? To have the BB10 and Playbook SDK's running as separate configurations? Cause at the moment I have to install either one or the other, and when I do install one, the other is just lost.
For example, i want to port my existing playbook application to BB10. So naturally i got online, download the beta 2 BB10 Air sdk, install it. When I open flash builder, i start getting errors in my code cause im trying to access classes that were at one point in time very available in the tablet sdk, but it seems it has been replaced by the bb10 sdk.
I see no configuration setting anywhere to 'switch' between the two configurations. From my understanding, if you wanna build a BB10 app, u gotta use the BB10 sdk, and with the playbook vice versa. You are inconveniently unable to use 1 sdk and develop for both.
Am I correct in my assumptions? And could anybody please point me in the right direction as to how to manage both installations?
Solved! Go to Solution.
08-08-2012 08:45 AM
08-08-2012 02:07 PM
Well the issue is that the rim sdk's seem to install right into the regular 'Flex 4.6' sdk. So i can only choose this 1 sdk, which contains whichever rim sdk i installed last.
Am I thinking straight?
08-08-2012 06:03 PM
Under Flash Builder Preferences, under Flash Builder / Target Platforms / BlackBerr Tablet OS, unselect "Use latest installed SDK" and for tablet development, I have:
C:\Program Files\Research In Motion\blackberry-tablet-sdk-2.0.0
For BB10 development (in your other workspace), it should be:
C:\Program Files\Research In Motion\blackberry-tablet-sdk-3.0.0
Flex 4.6 should be untouched.
08-09-2012 10:44 AM
Also, you don't actually HAVE to use BB10 SDK, the PlayBook SDK(s) work as well, as long as RIM does not completely remove/deprecate their old components. You can use the Tablet OS SDKs for BB10. Which also means that you would not be able to use newer components will the old SDK, obviously
In my case, I'm still using the Tablet OS 1.1.0 SDK because our customer did not want to pay for the SDK upgrade. Porting to BB10 alpha still seems good to me, but who knows what the future will bring