Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Dan, thats a way to do that but: I'd say it is a way to "just do it" without any consideration of whether its right or wrong. Further, I'm not saying that your solution is wrong, I'm just trying to explain why <em>I believe</em> applications should not be implemented in that way.</p> <p>First of all, as I mentioned, Qt Quick, as follows from its name, is designed to create user interfaces <em>quickly</em>. Trying to embed Qt desktop widgets in the graphics scene will create an additional effort (which might be quite big - depending on the task) of exporting the APIs to the QML environment and making everything work. Architecture of a QML application is very different from the desktop. If you work with model-view-controller for example, exporting QTreeView and QItemDelegate to the QML and making it work may turn to a very complicated solution. In fact, if follow that concept, the easiest way would be to create all the UI in C++ backend and export the final solution to QML but that in fact <em>is</em> a desktop implementation that doesn't take any advantages of QML at all. If do implementations in that way, its much easier to use Qt Animation API that would provide the same "fluid" effects that QML does but just using purely QGraphicsView.</p> <p>Second, if you want to use existing desktop widgets in QGraphicsView you will have to embed them as "proxy widgets" which, according to Nokia guys who work on Qt Quick and QML has big problems with performance.</p> <p>Third, if you want to use QGraphicsWidget approach, it will lead you to the implementation of all widgets from scratch because there are no QGraphicsWidget-based widgets in Qt. Even for something as simple as Push Button widget you will need to write all the code yourself.</p> <p>Fourth, <a href="http://blog.qt.nokia.com/2011/03/07/nokia-and-digia-working-together/" rel="nofollow">as Nokia stated previously</a>, they handed off Qt desktop support to a 3rd party company explaining that they focus all their effort on Qt Quick. So I would think about the maintainability of your application. Plus with upcoming QML Scene Graph all QML API will be moved on that implementation and I'm not sure whether there will still be possible to use desktop widgets with it.</p>
    singulars
    1. This table or related slice is empty.
    1. PONormal (desktop) user-interface controls with QML?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBarbaris
    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. This table or related slice is empty.
 

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