Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So firstly, there's probably a few places where these kinds of issues have already been solved - for C#, for example, have a look at <strong>Mono/Xamarin Studio</strong>. But if you're more interested in a general approach (I'll use saving data as the use case for examples):</p> <p>Look at it from the perspective of your shared library - what kind of function calls do you want to make from the shared library into the platform-specific code. This defines the interface from the shared library to the platform-specific code. E.g.</p> <pre><code>Save(data) </code></pre> <p>Once you've got that worked out, it's then a matter of implementing the platform-specific code to fulfil those functions. Since each platform has different mechanisms for any given task, you will probably need some kind of co-ordination layer that understands the sequence of actions needed to enact the desired outcomes on that specific platform. E.g</p> <p><em><strong>Platform A (check permissions + file)</em></strong></p> <pre><code>int Save(byte[] data) { var isAllowed = CheckPermissions(); if(isAllowed) { var dataFile = GetDataFile(); return SaveToFile(dataFile, data); } return -1; } </code></pre> <p><em><strong>Platform B (database)</em></strong></p> <pre><code>int Save(byte[] data) { var database = GetDatabase(); var targetTable = GetTable(database, "temp"); return AppendToTable(database, targetTable, data); } </code></pre> <p>The co-ordination layer could in turn call lower-level libraries to enact the individual actions - this may or may not make sense depending on whether there are lower-level functions that would be shared across various functions at the co-ordination level. E.g. candidates for shared use might be (from above)</p> <p><em><strong>Platform A</em></strong></p> <pre><code>CheckPermissions() GetDataFile() SaveToFile(File file, byte[] data) </code></pre> <p><em><strong>Platform B</em></strong></p> <pre><code>GetDataBase() GetTable(Database database, string tableName) AppendToTable(Database database, Table table, byte[] data) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBest Practices for Shared Android/iOS Development
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USChamila Chulatunga
    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. COThat makes sense. What about for something more complex, like getting location? For example, the Android location API provides the ability to wake up an app when the user has moved. What about registering listeners on separate threads? I figure these sorts of things are so vastly different that a common coordination layer would be very difficult to implement for these.
      singulars
      1. PO
      1. USjoshlf
    2. COIt really comes down to whether, at some level, you can envisage a common abstraction - if not, then you won't be able to avoid bleeding platform-specific stuff all the way out to your App. If you _can_ envisage a common abstraction, then you need to look at the platform-specific implementations of that common abstraction, and work out if at the implementation level there's commonalities, and based on that decide where to put what.
      singulars
      1. PO
      1. USChamila Chulatunga
    3. COOK, that sounds good.
      singulars
      1. PO
      1. USjoshlf
 

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