Terrence T said:
yea.. i dont know how to :(
First you need to download the Webwork SDK for Tablet OS here:
http://us.blackberry.com/developers/tablet/webworks.jsp
And you need to register signing key from RIM for Tablet OS (Not for BlackBerry App). Grab it here: https://www.blackberry.com/SignedKeys/
In this process, please keep in mind that the PIN you enter in the field shown below is extremely important. Do not forget this. Also, note that this PIN allows alpha-numeric characters. The catch is, the alphabets used will be forced to small-case.
You will receive a .CSJ file from RIM via email in couple of business days.
After you got Signed Keys sent from RIM via email. Download it and follow this instruction to create "sigtool.p12" key file.
In this process. You should choose the same password for both "mycskpassword" and "myp12password", simply to say, using 1 password for all will ease your life. And remember to Copy or move this file(sigtool.p12) into the bbwp/bin folder of the BlackBerry WebWorks SDK after you've done all the steps:
http://docs.blackberry.com/en/developers/deliverables/27280/Configure_signing_for_tablet_applications_1476061_11.jsp
Finally, you need to know which kinda PlayBook application you are creating:
So far we have Webworks is HTML and AIR is Flash(swf). If you create your own swf with FlashBuilder 4.x then you should go for AIR app, if you are not the original creator of the swf file, then you need to consider what version of Flash Builder of that swf file. If it's not 4.x or older, or maybe it's somehow not compatible with the Flash rendering engine of PlayBook OS then it will produce unplayable things, which are flicking all the time when run. I guess the issue is related to frame rates.
Ok whatever it is, we have 2 types of things to be signed so far. Webworks and SWF. Then here you are:
For WebWorks app:
You need to zip all webworks app necessary files into 1 zip file and sign it:
full_path_to\bbwp C:\my_app.zip -gcsk mycskpassword -gp12 myp12password -buildId 001 -o C:\my_app_output_dir
Note: -buildId needs to be different every single time you sign the package, the -buildId should be a never-used-before-number, just increment it.
For AIR app:
+Package it into bar file:
full_path_to\blackberry-airpackager -package My_App.bar My_App.xml blackberry-tablet.xml My_App.swf My_App_Icon.png
+Sign it from RIM:
full_path_to\blackberry-signer -verbose -cskpass myaskpassword -keystore path_to_sigtool.p12 -storepass myp12password My_App.bar RDK
+Sign for yourself - author:
full_path_to\blackberry-signer -keystore sigtool.p12 -storepass myp12password My_App.bar author
Now if things all go right, you can install your app onto PlayBook using instruction of the first post.
*Whew* ...
