Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would <strong>always hand-code the GUI design</strong> where there is no standard (or <em>de-facto</em> standard) GUI markup language (as with <code>Java</code>). The reason for this is that I have found that usin a GUI builder design tool will tie you in to using a particular IDE. Over time, the best IDE for GUI design and/or writing code will change and <em>each developer should be free to choose whichever IDE they feel most comfortable with</em>.</p> <p>Where I work at the moment, we have a lot of legacy GUIs which were written using <a href="http://www.netbeans.org/" rel="noreferrer">Netbeans</a> <a href="http://www.netbeans.org/kb/articles/matisse.html" rel="noreferrer">Matisse</a> GUI builder (against my advice at the time :-). These are now almost unmaintainable because all of the developers prefer either <a href="http://www.jetbrains.com/idea/" rel="noreferrer">IntelliJ IDEA</a> or <a href="http://www.eclipse.org" rel="noreferrer">Eclipse</a> as their IDE. It is not realistsic or workable to have developers fire up Netbeans just to modify GUI layout (people don't keep the Netbeans project definitions in sync etc).</p> <p>Another point is that <em>the total time writing out GUI layout code is probably only 5% of the total development effort</em> of a given project. Even if it takes you twice as long to write the code yourself, this doesn't translate as much of an overhead in the grand scheme of things. And it's a small price to pay for long-term maintainability.</p> <p>As long as you are clear about separating out GUI layout logic from business logic, I don't believe anything suffers as a result. No-one here uses GUI builders any more!</p>
    singulars
    1. This table or related slice is empty.
    1. POHandcode GUI or use gui-designer tool
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USoxbow_lakes
    1. USoxbow_lakes
    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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't think this is a proper argument against GUI designers in general. It is an argument against how Java IDEs typically do GUI design. The GUI should be stored in some markup language, and created at runtime, so you don't end up with unmaintainable generated code. or do like Qt with uic.
      singulars
      1. PO
      1. USAdam Smith
    2. COI completely agree. If Java had an IDE-independent GUI markup (which was either a standard or a de-facto standard) then I would be happy to use it. I still think that with GridBaglayout I could achieve the same results though :-)
      singulars
      1. PO
      1. USoxbow_lakes
    3. COOh. nice comment and nice thinking :)
      singulars
      1. PO
      1. UShqt
 

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