Databases
StackOverflow2013
Postsdbo
POBest Practise for GUI development for vanilla C++ application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest Practise for GUI development for vanilla C++ application
    primarykey
    data
    text
    <p>I want to know about developing of gui to vanilla C++ application. I have experience in mostly in command line application. My experience in C++ gui till now is cout and cin. I have some experience in WPF (just to mention that I do have some gui experience) I hope this will describe my level of experience with gui. Now,I want to develop an application which needs separate GUI with possibility of 3D display. Of course, one of the choice for GUI API is Qt.Also,after reading lots of stuff on internet, i think code separation would be really helpful in future. </p> <p>So, here goes my question: Is it possible if I keep my logic as generic as possible (not using winapi or qt in my logic) and make only GUI part API specific (say winapi or qt). Or I will need to add some code in my logic section, say for synchronization between logic and GUI. One can say signal and slot from qt is possible but as far as i know signals and slots are qt specific. they are not standard C++. </p> <p>In summery,my question is <strong>can i make my logic in standard C++</strong> (to stay platform/ framework independent) <strong>and only design platform specific GUI</strong>? If yes, could you please suggest a link or tutorial or book. A sample code or implementation would be 'a wish come true'. Also, some insights in code separation tactics would be quite helpful. </p> <p>Regards!!</p> <p><em><strong>EDIT::</em></strong> I will elaborate my problem. I have an application which has separate GUI and Logic section. The gui uses WinAPI and as the communication mode used is windows messages, previous user has created a HWND object in Logic which communicates to GUI. So, there is a HWND in Logic and HWND in GUI. I don't find this approach satisfying. One of the reason is that Logic part will be edited by non-programmers in later stage (not much. just modification of constants or changing implementation of function without changing para or return value). So, I just want to keep logic part in standard format (as much as possible). So once again, could anyone help me in designing business logic in C++ and GUI in any API.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBill the Lizard
    1. USuser21071987
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest Practise for GUI development for vanilla C++ application
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest Practise for GUI development for vanilla C++ application
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSearch for Model View Controller 'pattern' and presentation abstraction control 'pattern'. This would help you.
      singulars
      1. POBest Practise for GUI development for vanilla C++ application
      1. USPermanentGuest
    2. CO@PermanentGuest I am aware of these design patterns. What I am looking for is C++ implementation which is not api specific.
      singulars
      1. POBest Practise for GUI development for vanilla C++ application
      1. USuser21071987
    3. CO@user21071987 A comment on "keep logic part in standard format": If you would introduce a couple of Signals & Slots this would not interfere much with your code. Also, you use C++, you write your own classes - Qt classes are not different from that. One has to look up member functions and stuff like that anyway...
      singulars
      1. POBest Practise for GUI development for vanilla C++ application
      1. USHWende
 

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