Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you like Wicket, you should stick with what you know &amp; like. Wicket is a fine web framework and doing Scala &amp; Wicket is very nice because you can use Scala's traits to compose classes in Wicket... it really cuts down the boilerplate vs. Java.</p> <p>Lift has strengths that Wicket doesn't:</p> <ul> <li>Much better Ajax support. Lift's Ajax support is far less verbose than Wicket's. If you are going to do a lot of Ajax, learning Lift might be valuable.</li> <li>Comet support. If your application has a server-push component to it, Lift offers better comet support than any other web framework.</li> <li>Lift is more Scala-like. If you're coming from Java, then Lift's use of pattern matching and function passing is a learning curve.</li> </ul> <p>In terms of the comments in this thread, I'd like to disagree with some of the statements made:</p> <ul> <li>Lift does not require that you mix presentation and business logic. There are tons of options for you to structure your application appropriately for your coding style from a complete divorce of presentation and logic to mixing the two wildly and freely. Your choice.</li> <li>Lift does not do the same thing as Rails. Lift is not another me-too MVC framework, nor did I focus a lot of my time on the CRUD aspects of Lift. Lift is about security, developer productivity, maintainability and building highly interactive (Ajax and Comet) web apps. The Lift libraries contain a lot of modules including a number of ORM modules, JSON support, etc. This is due in part to the dearth of libraries in Scala back 2-3 years ago and due to the fact that the Lift community is awesome and supportive and the Lift release process works very well (monthly milestone releases that are stable enough to power Foursquare.)</li> <li>Lift is not focused on the HTTP request/response cycle. Lift is focused on abstracting those away. The developer spends less time worrying about parameter naming and more time focusing on business logic.</li> </ul> <p>But, once again, if you like Wicket, sticking with Wicket is a great choice... Wicket's even better in Scala.</p>
    singulars
    1. This table or related slice is empty.
    1. POFor my next project, a web-app, should use scala+wicket or scala+lift?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid Pollak
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFor my next project, a web-app, should use scala+wicket or scala+lift?
      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. 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