Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>I think this is completely unmaintainable</p> </blockquote> <p>I do not agree with you. Large number of small files is much better for maintenance than couple large files. I agree that GWT is <strong>much</strong> more verbose than Spring MVC:</p> <ul> <li>You do not need all these interfaces because of dynamic nature of JSP</li> <li>JSP in Sppring MVC case is not strictly typed and give your abilities to do many low level things automatically (for example data binding). </li> <li>And do not do some things at all (no need to clean up view between requests, view is stateless).</li> </ul> <p>In a case of GWT due to strict nature of Java and statefull view you must do a lot of additional work. It is completely maintenable (if it is done correctly). Main advantage is that you can add unit tests for your presentation layer. Due to this fact it will be more maintenable <strong>for long running projects with complex UI, large codebase and big team</strong>. If it is not the case for you project (screens are simple and you do not plan to add unit tests for UI layer) then it may be better to:</p> <ul> <li>use some another more lightweight presentation technology (Spring MVC for example).</li> <li>or simplify your policy (for example allow presenter -> view interactions without interfaces). Normally you lose ability to unit test your presenters in this case. As mentioned by @Andrea Boscolo you can use <a href="https://github.com/google/gwtmockito" rel="nofollow">GwtMockito</a> as a workaround for this problem!</li> </ul> <p>Two another advantages of interfaces between view and presenters:</p> <ul> <li>You can easy switch view implementation (famous case about making desctop UI -> mobile UI switch that unfortunately I never saw implemented)</li> <li>For me it is some kind of barrier that help keep presentation logic in presenter. Presenter know only about necessary things. I like this concept. This helps me write all pieces in right places.</li> </ul> <p>What is really annoing with all these files is that it takes much time to setup one activity. To simplify it:</p> <ul> <li>Ensure that you use UiBinder template in eclipse</li> <li>Even more, you can write your code generator that will take activity name and package as parameters and then it will generate all necessary things. So you need just modify ActivityMapper and start writing important UI logic. It is done for my current project and makes me happy.</li> </ul> <p>Another source of boilerplate is data binding. Consider using editor framework.</p>
    singulars
    1. This table or related slice is empty.
    1. POGetting rid of GWT MVP boilerplate
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMaksym Demidas
    1. USMaksym Demidas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGetting rid of GWT MVP boilerplate
      singulars
      1. PTQuestion
    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. COThank you for your answer, I've removed the interfaces. Actually I'm developing the whole application myself, and I think for this project having interfaces for views and presenters wouldn't give an advantage.
      singulars
      1. PO
      1. USDavid Frank
    2. COYou are welcome!
      singulars
      1. PO
      1. USMaksym Demidas
    3. COI will leave this question open for a couple of more days, if no better answer comes in, I'll accept yours.
      singulars
      1. PO
      1. USDavid Frank
 

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