WAC Widget Upload Process

1,978 views

Published on

This slide depicts how a developer would typically upload a widget to the Wholesale Applications Community (WAC) platform.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,978
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
28
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

WAC Widget Upload Process

  1. 1. WAC Widget Upload Process<br />January 25, 2011<br />Version: 2.0<br />wholesale applications community<br /> © WAC 2011<br />
  2. 2. Creating a developer account on wacapps.net<br />Create a developer account on the WAC Developer Website (http://www.wacapps.net)<br />Click on “Sign Up” and you will be takento the “Registration” page.<br />REMEMBER your unique NICKNAMEa. It will be reused while creating the widgetb. Once chosen, cannot be changed again.<br />
  3. 3. Creating a developer account on wacapps.net<br />Once you have completed the“Registration Form” and clicked “Submit”,an Email will be sent to the address provided.<br />Open your Inbox.<br />Validate your e-mail address by clicking onthe link provided in the body of the e-mail. <br />
  4. 4. Downloading the JIL Specifications<br />WAC recommends development and/or content porting begin only after the following <br />materials have been reviewed (in the Archive section):<br />WACDeveloperGuide.pdf<br />WACWidgetSystemAPISpecificationHandsetAPIv1.2.2.pdf<br />WAC Widget System HLTS Format and Packaging Specification v1.2.1.pdf<br />
  5. 5. Downloading the WAC SDK<br />Download the SDK<br />Install the SDK<br />Launch the SDK<br />The WAC SDK is available for Windows, Linux, MAC, and Transit Widget Emulator for Firefox platforms.<br />WAC 1.0 SDK for MAC<br />WAC 1.0 SDK for Linux<br />WAC 1.0 SDK for Windows<br />WAC 1.0 SDK for Transit Widget Emulator for Firefox<br />The WAC 1.0 SDK is built off of the Eclipse IDE Client and does not require an additional Eclipse IDE install.<br />At this time, WAC will not run as a Plug-in under an already deployed Eclipse IDE.<br />
  6. 6. Downloading the Sample Code/Widgets<br />For this example, we will be downloading the “Altitude” widget.<br />
  7. 7. Downloading the Sample Code/Widgets<br />Once the download has completed, locate the file on your filesystem and unzip the file. The unzipped package will reveal the WAC widget directory structure and code needed for the SDK.<br />
  8. 8. Setting Android path<br />1. Before we create a widget, set the Android path by following the navigation as shown: Window Preferences.<br />2. Browse to the folder where you have installed your SDK and click OK. Once the path is set, it checks for the Android version installed in the SDK and displays it when you click Apply andthen OK.<br />
  9. 9. Creating an AVD<br />AVD stands for "Android Virtual Device". An AVD is a virtual device profile representing one specific hardware device. <br />In order to create an AVD, clickWindow Android SDK and AVD Manager.<br />Once the window is up, click New… and enter the details accordingly.<br />The minimum size set for any widget is “10 MB”, and then clickCreate AVD.<br />
  10. 10. Loading the Sample Widget into the SDK<br />1. Launch the WAC 1.0 SDK.<br />2. Select “New > WAC 1.0 Widget Project” from the File Menu.<br />(ONLY WAC 1.0 is SUPPORTED at this time)<br />3. Select the “Create a widget from an existing widget package” radio button.<br />4. Click on “Browse” in order to select the widget to load. It is very important that you navigate from the widget root directory (unzipped folder) into the lower level “bin” directory to find the .wgt file.<br />5. Select “Altitude.wgt” and click on “Finish”<br />
  11. 11. Breaking Down the Widget Package Explorer<br />You should now see the Widget appear in the SDK Package Explorer <br />Now let’s break down the Package structure!<br />config.xml<br />This XML file contains the required configuration and meta information for the widget. The configuration file contains values like the name of the widget, who the author is, etc. (required)<br />altitude.html<br />This HTML file is the entry point to display and define the general layout of your widget. (required)<br />altitude.css<br />This CSS file contains all the style definitions used to tell the widget engine how the widget should look. Elements such as the colors of each element, or font size are defined here.<br />altitude.js<br />This JavaScript file defines what actions and functions can be executed in created widget.<br />Icon.png<br />Widget icon graphic (required)<br />Default.png<br />Background graphic<br />
  12. 12. Editing Files in the SDK<br />Double clicking on the file within the Package Explorer, the file will open in the editor pane. Multiple files can be opened at once for editing.<br />
  13. 13. Config.xml Manifest Set-up<br />The “Widget” tab contains the required configuration and meta information for the widget. In order to test your widget, you must create a Publisher ID using your wacapps.net “NickName”.<br />
  14. 14. Config.xml Manifest Set-up<br />Set “billing=true”(WAC 1.0mandates that all widgets be signed (or self-signed).<br />
  15. 15. Config.xml Manifest Set-up<br />The “Preferences” tab contains the element that was introduced by the W3C CR specification and must be supported by WAC 1.0. The value of this element can be set and retrieved through Widget.preferenceForKey() and Widget.setPreferenceForKey(), as defined in the WAC Handset API Specification.<br />Note that the optional “ReadOnly” attribute of this element must be honored by a WAC 1.0 runtime. If a preference is “ReadOnly”, then its value cannot be reassigned via the Widget.setPreferenceForKey() function.<br />
  16. 16. Config.xml Manifest Set-up<br />The “Access” tab allows the developer to describe the widget’s permissions in addition to the APIs requested using the “Feature” tab (see next slide). Access requests can be denied, and this is not a required element.<br />
  17. 17. Config.xml Manifest Set-up<br />The “Feature” tab allows the developer to describe what sensitive API or API groups this widget declares that may attempt to access.<br />Identified domain - WAC signed<br />Operator domain - Operator signed (not available at this time).<br />Explaining "restrictive" API features, users must sign their widget if those APIs are being used.<br />
  18. 18. Config.xml Manifest Set-up<br />The “Source” tab allows the developer access to the XML code being generated by the previous tabs which makes up the “config.xml” file.<br />
  19. 19. Testing the Widget on an Emulator<br />Now let’s run the “Altitude” widget on the WAC SDK Emulator!<br />From the Run menu select “Run Configurations…”.<br />
  20. 20. Testing the Widget on an Emulator<br />Select “Widget Application” and click the “New” button to create new configuration.<br />
  21. 21. Testing the Widget on an Emulator<br />A new Configuration has now been created!<br />Rename the configuration in the “Name:” text field provided.<br />Click on “Browse” in order to select which widget to run under the configuration name “Altitude” that has been created.<br />
  22. 22. Testing the Widget on an Emulator<br />Now select the Widget you wish to run on an Emulator!<br />Highlight the desired widget within the list and then press “OK”.<br />
  23. 23. Testing the Widget on an Emulator<br />Configuring the Emulator<br />Within the “Run Configurations” window find the “Emulator” tab.Here you can<br />further configure the Emulator’s environment.<br />
  24. 24. Testing the Widget on an Emulator<br />Let’s start the Emulator and see your Widget as if it were on a device!<br />Double check your selections and click Run!<br />
  25. 25. Testing the Widget on an Emulator<br />You should see “Preparing SD card” when the Emulator is trying to reach the widget you created.<br />
  26. 26. Testing the Widget on an Emulator<br />Congratulations! You have just run your first WAC Widget!<br />Now let’s upload it to the wacapps.net site!<br />
  27. 27. Submitting Your Widget to wacapps.net<br />Navigate back to the wacapps.net page. Log in, and select “Publish”.<br />
  28. 28. Submitting Your Widget to wacapps.net<br />Obtaining a Publisher ID<br />Developers wishing to publish their Widgets to various App Stores must register and purchase a Publisher ID from “TrustCenter” first before submitting a Widget to wacapps.net!<br />Confidential and proprietary material all rights reserved © JIL B.V., The Netherlands - 2010. Use, disclosure of this material is not permitted to any unauthorized persons or third parties except by written agreement.<br />
  29. 29. Obtaining a Publisher ID from TrustCenter<br />TrustCenter registration page step 1: Select Certificate Type<br />
  30. 30. Obtaining a Publisher ID from TrustCenter<br />TrustCenter registration page step 2: Define Certificate Details<br />
  31. 31. Obtaining a Publisher ID from TrustCenter<br />TrustCenter registration page step 3: Define Key length<br />
  32. 32. Obtaining a Publisher ID from TrustCenter<br />TrustCenter registration page step 4: Enter in your personal information<br />
  33. 33. Obtaining a Publisher ID from TrustCenter<br />TrustCenter registration page step 5: Define Payment data<br />
  34. 34. Obtaining a Publisher ID from TrustCenter<br />TrustCenter registration page step 6: Email Confirmation<br />The developer clicks on the URL within the e-mail to install their certificate!<br />
  35. 35. WAC Signing Widget Overview<br />A Widget is signed to identify the developer, and prove its integrity. Under WAC, when a Widget is signed, it also allows the Widget to use API extended functions, and enables it to be offered for sale.<br />Following section describes how the Widget is signed:<br />1. In order to sign a Widget, the developer first requests a Publisher ID from the<br />Certificate Authority (CA). Note that there is a fee for issuing the Publisher ID.<br />Based on the developer’s request, the CA vets the individual and/or organization<br />for certification. If the developer passes the vetting process, a Publisher ID is issued.<br />2. The developer receives the Publisher ID from the CA.<br />3. The developer signs the Widget using the Publisher ID received.<br />After the Widget is signed, Developer uploads to the WAC Developer Website.<br />4. After the developer uploads the signed Widget, WAC checks its validity.<br />5. After validity is confirmed, the Publisher ID is checked, and the Widget’s signature<br />is replaced to the WAC signature.<br />6. By replacing to the WAC signature, the Widget can be distributed to Operators.<br />Please check the CA Website for prices and validity periods.<br />
  36. 36. Signing the Widget<br />In order to sign the widget, please follow the navigation as shown :<br />Right click on the widget  Widget Tools  Signing Widget package<br />
  37. 37. Signing the widget<br />Please follow the steps sequentially as shown below, to sign the widget:<br />1<br />2<br />3<br />4<br />
  38. 38. Signed widget now has “Author-signature.xml”<br />
  39. 39. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />1. Navigate to “Publish” and select your “SIGNED” Widget.<br />2.Click “Upload”.<br />Note :You must select THE NEWLY CREATED SELF-SIGNED .WGT FILE and NOT THE UNSIGNED ONE within the SDK WIDGET /BIN DIRECTORY.<br />
  40. 40. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />Once the widget has been accepted, the user will be allowed to enter various marketing, category, and tagging information about their widget.<br />
  41. 41. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />The developer will also be able to specify targeted audiences and devices.<br />
  42. 42. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />At this point in the submission process, the developer is required to choose image files they wish to have used in the various App Stores.<br />
  43. 43. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />The final step allows the user to define their price by market/territory.<br />
  44. 44. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />The final step allows the user to define their price by market/territory. Save your details for each market.<br />
  45. 45. Submitting Your Widget to wacapps.net<br />Uploading Your Signed Widget<br />The final step allows the user to define their price by market/territory. Here we see the extended Localization details that can be defined for each carrier!<br />
  46. 46. Submitting Your Widget to wacapps.net<br />Finally, click “Save and Continue” to submit your widget to market(s).<br />
  47. 47. Submitting Your Widget to Operator Companies (OpCos)<br />
  48. 48. Submitting Your Widget to wacapps.net<br />If all steps are completed correctly, the Widget and all image assets associated with it will be accepted, after which it would be listed within the “My Area” section, and listed with a “Created” status.<br />

×