Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you guys need to be careful which terms you are using in order to not confuse people who may be looking for similar help.</p> <p><strong>Environments</strong> are specific to the OS you are using. iOS, Blackberry, Android, and etc. environments.</p> <p>Skins are based on the environment, and aren't generic to all platform. When you create a skin you must choose which environment you are running in.</p> <p>So to correct some, direct updates will update <strong>all</strong> skin resources in targeted environments. </p> <p>For example: You have an app with Android and iOS versions</p> <p>When you create skins, you are creating essentially a responsive type of design to your parameters. For instance, if you have a 2.3 vs 4.2 Android OS, you can set a look and feel for both. However, these utilize a single web resource base. The APK would be the same for both versions of the app (by default) and have 2 available skins. On <strong>runtime</strong> utilizing IBM Worklight's <strong>'Runtime Skinning'</strong> (hence the name) it goes through the parameter check for the OS and loads that skins overriding web code. </p> <p>You could technically override all of the web code to be completely different for both skins, but that would be bulky and inefficient.</p> <p>When you direct update you are updating all the resources of that particular <strong>environment</strong> (to include both skins), not the common folder/environment.</p> <p>So an updated Android (both skins) would have updated web resources (if you deployed the android wlapp) and an iOS version would stay the same. </p> <p>If you look at the Android project after build (native -> assets -> www -> default or skin) you can find the shared web resources generated by the common environment. However that is only put there every time you do a new build.</p> <p><img src="https://i.stack.imgur.com/cI6Vc.png" alt="Browser Test"> In the picture, I have an older version of the Android built for both skins on the left. On the right is a preview of the newer <strong>common</strong> resources after deploying only the <strong>common.wlapp</strong>. So you can see that they are separate.</p> <p>Sorry if it was long winded, but I thought I would be thorough.</p> <p><strong>To answer the original question</strong>, have you thought of having all the parameters of the store loaded from user input or a setup? If you are trying to connect to 3 different store, create some form for settings control that will access different back ends or specific adapters. You could also create 3 different config.js that load depending on the parameters that you set so that you set. The other option is to set different versions of your apps specific to the store. </p> <p>Example. Version 1.11, 1.12,1.13 can be 3 versions of the same app for store 1, 2, &amp; 3. They can be modified and change and have 3 sets of web resources. When you need to update, jump up to version 1.21, 1.22,1.23. It seems a bit of a work around, but it may be your best bet at getting 3 versions of the same app to fall within the single application category. (keep 3 config.js types for modifying for the 3 stores).</p>
    singulars
    1. This table or related slice is empty.
    1. POWorklight Direct update
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHarryH
    1. USHarryH
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for clearing that up. The client does not want the customer to know what the store relationships are, so they want the apps branded. But the version trick seems like a good one. In the end it looks like we are probably going to either load the config into the json store on first run, or convince the client to get more licenses depending on cost.
      singulars
      1. PO
      1. UStik27
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload