Databases
StackOverflow2013
Postsdbo
POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
    primarykey
    data
    text
    <p>First, some background:</p> <p>I've decided to start a new project designed from the ground up to run on multiple platforms (Windows, iOS, OSX, Linux, Android). Since my background is mostly C++ I intend to write the core functionality using C++11. That being said, on each platform I'll need to write a platform-specific UI that can inter-operate with the C++ core.</p> <p>The first platform I'm targeting is Windows (the second is iOS). I will have data stored in a SQLite database as well as user-supplied data that will be entered using a WPF DataGrid (inserting rows, manipulating existing data, etc.). This is my first time working with WPF (though I've used Windows Forms) and my first time working with C++ in a managed environment. I plan to make this an MVC-style architecture so in my mind SQLite is the Model, WPF is the View, and the C++ code is the Controller.</p> <p>My question is this:</p> <p>Are there any examples out there illustrating how to grab data from a C++ interface and display it using C# and WPF without destroying/mangling the C++ code itself (since it must work on multiple platforms)? I've read a tiny bit about P/Invoke (tedious, but works) and mixed assemblies (works, but will mangle my C++?) but Google hasn't been helpful when it comes to concrete examples (especially those involving populating WPF controls with data obtained via a C++ DLL).</p> <p>Thanks!</p> <p>EDIT: While searching for approaches to this problem I came across CXXI. I'm not very familiar with it but it seems like it may be a simple solution to my problem. Any thoughts? My grasp of all these concepts is limited.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRotsiser Mho
    1. USRotsiser Mho
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't have any WPF experience, but I can tell you that what you're doing is going to be somewhat difficult. When you get to the OS X app (and I'm sure iOS is the same), you will have to write quite a bit of Objective-C code. I think it largely depends on the nature of the app you're making, but you're basically going to have to re-write much of it for each platform.
      singulars
      1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
      1. USHassan
    2. COThanks for your input Hassan. I know I've got a lot of work ahead of me but my goal is to code the UI natively for each platform. I feel that delivers the best user experience as well as the best learning experience :)
      singulars
      1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
      1. USRotsiser Mho
    3. COYou're right, it does deliver the best user experience. And if the hardest part of the UI is the table, then I'd say you're in good shape. I hope someone actually answers now...
      singulars
      1. POLooking for a cross-platform, end-to-end example of C++ to WPF/Cocoa interoperability
      1. USHassan
 

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