If the custom skin does not have a version, remove the skin-version element.ĭeploy the application to iOS Simulator to verify that the new skin is being picked.Īfter upgrading to a new Oracle SOCS version, the custom skin changes are still applied over the base application. Update the skin-version element if the custom skin was defined with a different version. Update the skin-family element with the name of the custom skin family that should be applied to the entire application. For more details on configuring skins in maf-skins.xml, see Chapter 9, Skinning MAF Applications, in n Framework Developing Mobile Applications with Oracle Mobile Applicatio. If the skin should be versioned, in the Structure Pane, right click the skin element just created, and select Insert Inside skin > version.įill out the popup with the skin version information. Note that the style-sheet-name should reference the CSS skin file created in Step 3. In the Structure Pane, right click the adfmf-skins node and select Insert Inside adfmf-skins > skin.įill in the fields in the popup. When JDeveloper has restarted in the Customization Developer role, open the maf-skins.xml file. Switch JDeveloper to the Customization Developer role by selecting the Tools menu and then Switch Roles > Customization Developer. For more information on how to create CSS skin files and how MAF skinning works, see Chapter 9, Skinning MAF Applications, in n Framework Developing Mobile Applications with Oracle Mobile Applicatio. Open the Oracle SOCS workspace created from the delivered MAA file.Ĭreate a new CSS skin file in the SIMApplicationController project. Open JDeveloper in the Studio Developer role. The following steps assume that a workspace has already been created from the Oracle SOCS MAA file: If the Oracle SOCS application is upgraded to a newer version at a later date, the skinning customizations are still applied on top of the upgraded version by MDS. Since MAF supports MDS customizations of the maf-skins.xml and maf-config.xml files, it is possible to apply a custom skin to the application. The overall look and feel of the Oracle SOCS application is controlled by a skin. A feature link is included by specifying the featureId and optionally a label. The footers section allows for setting up feature links that should be displayed regardless of current feature group. Tapping on a feature item in the group or a submenu allows you to navigate to the provided feature identifier. If the options property is specified, another level of feature nodes can be placed in it to form a submenu (the springboard does not support nesting submenus), and name is required in this case. If no name is provided, the name of the feature referenced is used. Finally, the next level of nodes are the features within the group. The nodes under it are the feature groups to display on the switcher page. The name of this node is displayed on the switcher page of the springboard. The menus section begins with the root node of the hierarchy. If an alias is not declared, the full bundle path must be used instead of the alias. Translated strings can then be used for name/label with, similar to the usage in AMX pages (after using loadBundle). The bundles section allows the declaration of aliases to XLIFF bundles. The springboard is configured by a navigation.json file in the application controller project. There is no need to update the navigation configuration unless changes in organization, labeling, and so on are desired. For more information on the setup, as well as version compatibility, see Oracle Mobile Application Framework documentation. For more information, see their respective documentations.ĭeploying Oracle SOCS for use on an Android device requires that you have a computer that has the Android SDK installed. Additionally, you must have installed JDeveloper, Xcode and Oracle MAF extension. For more information on the setup, including provisioning profiles and certificates, see Apple's documentation at /. maa downloaded from for the appropriate version of Store Operations Cloud Service.ĭeploying Oracle SOCS for use on an iOS device requires that you have a computer running Mac OS X set up for iOS development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |