Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>At the company I work for, we pretty much use the approach given by Eugen to automate the build process of apps that e.g. should simply be branded differently by exchanging certain assets, styles, strings and configurations. We tend to set up the project and build process as follows:</p> <ol> <li>Create the Android project and set it up such that it works for a specific branding. This will make sure that you can still build and run from Eclipse. Assuming that the codebase does not change between differently branded releases, that should be fine.</li> <li>Create an ant build configuration that: <ol> <li>copies any files that are going to be changed to a backup directory</li> <li>modifies the project files according to a configuration file (see below)</li> <li>compiles the project sources and signs it with a release key (if making a release build)</li> <li>copies back the files from step 1, overwriting any changes and returning the project to its original state</li> </ol></li> <li>Create configuration files for every 'branding', or language specific release in your scenario.</li> </ol> <p>Basically these steps will allow you to create branded/partner/language specific builds by simply providing the appropriate configuration with the ant build command. In our case it looks somewhat like this:</p> <pre><code>ant partner-release -Dpartner=stackoverflow </code></pre> <p>where 'stackoverflow' will point to a configuration with the same name. In our case these configuration files are small xml files that contain all the parameters that are to be replaced for that specific build. It could contain strings, but might as well point to other files (e.g. logo images) that should be copied into the assets/resources. For example:</p> <pre><code>&lt;config&gt; &lt;version_name&gt;1.00&lt;/version_name&gt; &lt;version_code&gt;1&lt;/version_code&gt; ... &lt;/config&gt; </code></pre> <p>Some more pointers:</p> <ul> <li>We use <code>xmltask</code> to modify any xml files in the project; e.g. the manifest and resources.</li> <li>Since the aforementioned task is really easy to use, our build configuration files are also set up as xml files, as illustrated above. It's quite human readable and easy and straightforward to change.</li> <li>You can also use <a href="http://ant.apache.org/manual/Tasks/replace.html" rel="nofollow"><code>replace</code></a> and <a href="http://ant.apache.org/manual/Tasks/replaceregexp.html" rel="nofollow"><code>ReplaceRegExp</code></a> tasks to change configuration-dependent variables in almost any file. The latter can be especially convenient to make build-time changes to source code.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POCustomizing parts of Android Manifest
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMH.
    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
    1. COThank you for your answer. Still I would like to add that if you introduce Jenkins in your build process, things will become even simpler. I personally did my job only using few ant tasks that basically copied all my files to new packages. Also as I use ant I think property files are more convenient than xml files.
      singulars
      1. PO
      1. USBoris Strandjev
 

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