WaterlooErik's Forum Posts

  • I appreciate the feedback all :-) Definitely makes me happy to see the positive experiences you're having. We don't plan on stopping here, so don't hesitate to reach out to me at eoroseoj@rim.com if you're hitting any issues, and keep an eye on devblog.blackberry.com for future events.

  • Hello all, apologies for the delayed response; I was down and out again for most of the weekend catching up on sleep.

    Blinx123: I'm truly sorry to hear that.

    ArcadEd: I appreciate you sticking to it. There have been some issues crop up when WebGL is enabled in some applications (thank you Joannesalfa for highlighting the workaround.) It's one I've been investigating but can't fully peg. I believe it's related to non-power-of-two textures, but I've also seen results that contradict that theory. If anyone has a basic sample application where WebGL ON breaks it, bu WebGL OFF works, please don't hesitate to email me (eoros@rim.com) with the CAPX and I'll investigate it further.

    In terms of next steps, the application review process can take up to 10 days, but the App World team is working around the clock to get them out ASAP. Any deadlines that depend on the approval of these applications will be adjusted in the event that reviews take longer than expected (i.e. we won't disqualify anyone if their app isn't approved by the 25th, instead we'll push that date back.) If applications are rejected, you will also have a window to resubmit the application and still be eligible for the rewards under this Port-a-Thon.

    Rewards will be communicated via email (to your vendor account email) once *all* of your applications have completed review. If you get an email but some applications are missing from the list, or if you get no email and we've announced that emails have been sent out, then please email BlackBerryDeveloperProgrammfa@rim.com to follow-up. We'll post updates on devblog.blackberry.com as we get them.

    EDIT: In terms of payments, these will be done through the vendor accounts themselves so be sure to link a PayPal account if you have not done so already. If you are in a region where PayPal is not an option, there is the possibility of wire transfers. If this is the case, please reach out to BlackBerryDeveloperProgrammfa@rim.com.

    On a last note, I'd like to thank everybody here that participated. Construct 2 is one of my personal hobbies and I'm excited to see this community become a larger part of BlackBerry 10. For those that couldn't make it, stay tuned as there will be plenty of opportunities still. That being said, post-launch App World will look a lot different than what it does today, so if you found the process worth it, it may be worthwhile to port some titles inbetween events too. And if anyone ever does have any question, I do my best to keep an eye on this forum, but don't hesitate to reach out to me directly at eorosmfa@rim.com.

    Cheers all!

  • Blinx123: I believe it would be 5:00AM GMT, 12:00AM EST. At the time of this posting there are 7 hours left in the Port-a-Thon.

    By all means take advantage of this if you can. Join the online portion (https://cgs.adobeconnect.com/r8taf15m8rg) and reach out to anyone on the Presenters list if you hit any difficulties.

    For reference, these posts outline the major steps for a Construct 2 developer to convert to a BlackBerry 10 application:

    http://www.scirra.com/forum/forum_posts.asp?TID=61922&PID=381345&title=like-money-rim-is-practically-throwing-it-at-you#381345

    http://www.scirra.com/forum/forum_posts.asp?TID=61922&PID=381364&title=like-money-rim-is-practically-throwing-it-at-you#381364

    http://www.scirra.com/forum/forum_posts.asp?TID=61922&PID=381375&title=like-money-rim-is-practically-throwing-it-at-you#381375

    Best of luck!

  • Tobye: Awesome! That makes me happy :-)

    As for the failure, I'm not sure. The error meant that the BAR file wasn't signed. Perhaps the -g flag was missed, or maybe you took the 'simulator' version instead of the 'device' version. Maybe the tools just hiccuped?

    Sounds like you followed the steps well though so I wouldn't worry about it too much.

    The review process will likely be a few days just based on the volume of apps (in 11.5 hours we've reached over 8000 apps already.) If by chance the application isn't accepted, you would get an email indicating why and there would still be a time period to resubmit and still meet eligibility for rewards.

  • That's exactly it — Basically, a particular version can only ever be signed once. So if you're going to re-sign, you will need to increment that version manually.

    If you're feeling adventurous, check out the Ripple Emulator for Chrome:

    developer.blackberry.com/html5/download

    It provides a GUI for the command-line and will do that incrementing for you. It may take a bit of playing with but just fire any questions along.

  • alfred: Lou just mentioned you got in touch in the Port-a-Thon, he should be able to sort you out momentarily with the vendor account.

  • Tobye: When you ran the bbwp command, did you include the -g STOREPASS section?

    Could you try this one more time, and then copy/send me the full console output in an email? (eoros@rim.com) Just so I can verify if any issues occurred?

  • Tobye: Normally you would need to send the ID through, but if you connect to the Port-a-Thon and send Lou Gazzola a message with your Vendor ID (and just a quick note that Erik Oros sent you), then he can approve your account as-is.

  • For reference, you can sign up for a BlackBerry App World Vendor account here:

    appworld.blackberry.com/isvportal

    During the Port-A-Thon, we're approving vendor requests on the spot, so drop on by and ask one of the Presenters for help:

    cgs.adobeconnect.com/r8taf15m8rg

  • That reminds me, I didn't discuss the Vendor Account. Tobye, have you gone that that process already of creating a Vendor Account?

    If so, you don't need to do anything special, but your Vendor Account needs to be linked with PayPal (you do that through our system.) All submissions during this time for BB10 are eligible for the rewards.

    If you haven't set up a Vendor Account yet, let me know.

  • For those interested in the Port-a-Thon, we have live support going on right now until Saturday, 11:59PM (EST):

    cgs.adobeconnect.com/r8taf15m8rg

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • This is the third post regarding converting a Construct 2 application to BlackBerry 10.

    The first post outlined adding a config.xml document to your project and requesting code signing keys.

    http://www.scirra.com/forum/forum_posts.asp?TID=61922&PID=381345&title=like-money-rim-is-practically-throwing-it-at-you#381345

    The second post outlined downloading the BlackBerry 10 WebWorks SDK and registering code signing keys.

    http://www.scirra.com/forum/forum_posts.asp?TID=61922&PID=381364&title=like-money-rim-is-practically-throwing-it-at-you#381364

    This third post will detail packaging your HTML5 project into a BlackBerry 10 application; also known as a BAR.

    Similar to how we executed a command to register code signing keys, we'll execute another command to package our application. This time, we need to execute our command from this folder:

    C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 1.0.4.7

    We can use the same trick in Windows of navigating to that folder in Windows Explorer, then holding Shift and pressing Right-Click to get the Open command window here option.

    The command that we want to execute is:

    bbwp PATH_TO_PROJECT -g STOREPASS

    Where PATH_TO_PROJECT is a path to the root folder of your project. For example:

    C:\c2projects\myProject

    And STOREPASS is your code signing password that you set when registering your keys.

    The resulting log should look similar to this:

    [BUILD]   Populating application source

    [BUILD]   Parsing config.xml

    [BUILD]   Generating output files

    [INFO]    Info: Package created: C:\wamp\www\simulator\myProject.bar

    [INFO]    Info: Package created: C:\wamp\www\device\myProject.bar

    [INFO]    Info: Bar signed.

    [BUILD]   BAR packaging complete

    The bold output indicates the BAR file in the device folder that has been packaged and signed, and is now a BlackBerry 10 application. This is the BAR file that you would then submit to BlackBerry App World.

    For submitting to BlackBerry App World, there is a video tutorial here:

    http://www.youtube.com/watch?v=cMUJyJCo1ds&feature=youtu.be

    So all of that being said, it is a fairly simplified look and some developers may run into issues. Again, if you do, do not hesitate to ask here, or directly (eoros@rim.com), or during the Port-a-Thon event (we'll have a number of people online helping at all times.) We'll do our best to help you get your application submitted and ready to go.

  • Tobye: I generally just use Notepad++ to create a new TXT document to avoid any additional formatting that Word might inject. I then rename .txt to .xml

    Creating at the 'Root' of the folder just means that config.xml shouldn't be in any sub-folder of your project. It should be at the highest level (while still being a part of your project.) I'm not sure if that clarifies...

  • This is the second post in packaging a Construct 2 game as a BlackBerry 10 application. Previously the recommendation was to request Code Signing Keys from this form:

    blackberry.com/SignedKeys/codesigning.html

    These keys are issued by an automated system, hourly, and when the keys arrive to your email, they should arrive as two (2) separate emails; each with a unique attachment.

    * client-RDK-########.csj

    * client-PBDT-########.csj

    ######## simply refers to a unique string of numbers in the filename.

    You will also need to download the BlackBerry 10 WebWorks SDK. This SDK contains the packaging tools to take your HTML files and create a BlackBerry 10 application. These can be downloaded here:

    developer.blackberry.com/html5/download

    The current version of the BlackBerry 10 WebWorks SDK is 1.0.4.7. Download the installer and install to the default directory. For this example, we'll be using the following working directory:

    C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 1.0.4.7

    The first thing you'll want to do is to copy the two CSJ files you received as Code Signing Keys and save them to the following folder:

    C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 1.0.4.7\dependencies\tools\bin

    Once copied there, you will need to open a Command Prompt / terminal to that location. If you are not familiar with the terminal, have no fear, we're only there for a short time and I'll do my best to make it as simple as possible.

    In Windows Vista / 7, if you hold Shift and Right-Click within the Explorer Window, you should get a Context Menu pop up. One of those items should be:

    Open command window here

    By clicking that, you should get a Command Prompt window that is opened to:

    C:\Program Files\Research In Motion\BlackBerry 10 WebWorks SDK 1.0.4.7\dependencies\tools\bin

    At this point, we want to execute one command to register our code signing keys. The command looks as follows:

    blackberry-signer -register -csjpin CSJPIN -storepass STOREPASS client-RDK-########.csj client-PBDT-########.csj

    Where CSJPIN needs to match the PIN you created on the online form, STOREPASS is a NEW password you are creating. You will need to enter the STOREPASS each time you create a BlackBerry 10 application, so make it something you will remember. And finally the ######## would be replaced by the numeric string in your specific code signing files.

    Run the command by hitting enter and you should get a message that the code signing keys were successfully registered.

    You should now be at the point where:

    * You have modified your project with the config.xml

    * You have downloaded and installed the BlackBerry 10 WebWorks SDK.

    * You have requested and registered your Code Signing Keys.

    All that remains now is to actually package your Construct 2 HTML files into a BlackBerry 10 application. I'll cover that in my next post.

    If at any time you have any questions or run into issues, do not hesitate to reach out here or directly at (eoros@rim.com).

  • I'll try to cover the steps here; feel free to ask any questions.

    The starting point that I'm assuming is that you have exported your Construct 2 project such that you have a single folder that houses all of your HTML, JavaScript, CSS, and resource files.

    We need to add one file to the root of this project called config.xml.

    EDIT: Updated the wording to be more clear. 'root of this project', not 'root of this folder'.

    The most basic config.xml looks as follows.

    <?xml version="1.0" encoding="utf-8"?>
<widget xmlns="http://www.w3.org/ns/widgets"
          xmlns:rim="http://www.blackberry.com/ns/widgets"
          version="1.0.0.0"
          id="A_UNIQUE_APP_ID">

     <name>Sample App</name>
     <author>Erik Oros</author>
     <content src="index.html" />
</widget>

    The parts that change are the id which is simply a string that you put in (I tend to make this just the name of my app for simplicity.) The name and author fields get updated to your own values. Finally, the content src points at the HTML file that starts our application.

    The most common thing that you may still need to add to the config.xml are application icon and access elements.

    EDIT: For information on addition an application icon, please refer to this documentation:

    developer.blackberry.com/html5/documentation/icon_element_834676_11.html

    If your application goes to any external URLs, or pulls in resources from external URLs, you will need to white-list those domains. For example, if I was pulling information from docs.google.com/myFiles/page.html then I would need to add the following access element.

         <access uri="http://google.com" subdomains="true" />

    This would be added after the content element and before the closing widget element.

    With that, you're now the majority of the way creating a BlackBerry 10 application. The last thing I'll recommend in this post for now is to navigate to the following URL and request Code Signing Keys for BlackBerry PlayBook and BlackBerry 10 and higher. If you do not have a Company, your full name will do. And I recommend making the PIN something easy that you will remember as you will require that value when registering your keys.

    blackberry.com/SignedKeys/codesigning.html

    In my next post, I'll talk about configuring your environment so that you can package your source into a BlackBerry 10 application ready for App World.