Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think I've invested some time for both frameworks. I really like both because they bring the Swing-alike coding to web development. And I don't know easier ones for me (although there is click but I don't like the velocity templating thing)</p> <p>And yes, there are differences.</p> <blockquote> <p>I wont have to worry much about the look and feel.It comes with nice themes</p> </blockquote> <p>true, but every serious company will style its app differently (unless you are prototyping)</p> <blockquote> <p>I will do all my programming in java which am very good at and wont have to spend time hacking css which am not very good at</p> </blockquote> <p>Then Vaadin would be 'better'.</p> <blockquote> <p>i will loose the ability to create UI declaratively.</p> </blockquote> <p>What are the advantages of that? (BTW: you could code declarative in groovy ;-)) </p> <p>But ok. I know what you mean: if you can effort a separate designers than wicket is 'better'.</p> <blockquote> <p>i can hardly give them a desktop look and feel. </p> </blockquote> <p>Why not? Or what do you mean here? Wicket supports ajax and there are components which supports nice 'desktop-alike' things (ajaxlink, lazycomponent, autocompletion, progressbar, see wicket stuff + extensions). ok, for any more complex component you'll have to code in javascript BUT BTW did you know that you could even <a href="https://cwiki.apache.org/WICKET/google-web-tools-starting-point.html" rel="noreferrer">use GWT within wicket</a></p> <p>Some minor experiences:</p> <p>Vaadin is surely faster while coding (no css, html stuff). But if you go production keep in mind that the ease of programming can come to the cost of performance on the client side: e.g. if you use the 'wrong' layouts such as Horizontal/VerticalLayout, ... the massive use of javascript could slow down old browser.</p> <p>But Vaadin is not slow! Use appropriate layouts such as CssLayout or FastLayout and also old browser can serve it. (Although if you would use CssLayout your coding-style is really wicket-alike.)</p> <p>One issue with Vaadin is that it is a bit harder to profile, because you don't see easily where the client needs all the CPU and the nested divs gets cryptic id-names.</p> <p>One great thing about Wicket is its <a href="http://www.atomicgamer.com/dev/2009/10/wicket-guice-2-0-warp-persist-2-0/" rel="noreferrer">warp persist integration</a></p> <p>(Guice can be integrated in Vaadin and Wicket)</p> <p>Testing the UI should be easy with Vaadin (although I didn't found unit testing stuff) and is very easy <a href="http://wicket.apache.org/apidocs/1.4/org/apache/wicket/util/tester/WicketTester.html" rel="noreferrer">with wicket</a>.</p> <p>Last but not least creating lists/tables is VERY easy in Vaadin compared to wicket.</p>
    singulars
    1. This table or related slice is empty.
    1. POWicket vs Vaadin
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKarussell
    1. USKarussell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWicket vs Vaadin
      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. COThanks for your informative response. I ended up starting the project with vaadin. This is because it is helping me come up with a relatively good looking, feature rich application with less effort . I have a better experience with wicket but i always found myself spending hours on non-core things like layout, ui colors and all that. I want the application to have a full desktop look an feel without pages and all that. while it is possible to achieve this with wicket, i find most of the things easier to do with vaadin. I will use wicket for public facing website like parts of the application.
      singulars
      1. PO
      1. USjoshua
    2. COFollow-up on the above comment: I later switched to wicket and i have never looked back since then. I had a problem with vaadin UI layout.
      singulars
      1. PO
      1. USjoshua
    3. COThanks for the update. What in detail were your problems? My initial problems were performance wise (I can only speak of ~April 2010)
      singulars
      1. PO
      1. USKarussell
 

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