Antwerkz, Inc.
21Jul/06Off

Qwicket 0.2

This release is the migration to the web app. You can now create your application online without downloading anything. Other than your generated application code, of course. I also switched to velocity for templating for finer grained control. Click the "Build your project" link to the left, fill in a couple of fields and press enter. The zip file will contain your runnable application skeleton. I'll put a road map up soon, but the next big feature will be a bean builder that also generates basic CRUD pages for all your beans. Watch this space for details. :)

Start your wicket app today here.

Posted by admin

Filed under: Java, qwicket Comments Off
Comments (7) Trackbacks (0)
  1. Nice work – I’ve wanted to do an online version of AppFuse for a while now, just never got around do it.

  2. Nice work – I’ve wanted a Wicket version of Appfuse for a while now, Matt just never got around do it.

  3. Very cool. Nice job.

    A couple quick items to consider for the future:

    1) When attempting to build an example created via your web interface, it fails because it’s attempting to access network resources (I’m behind a corporate firewall). You might consider supporting proxy’s. Also, not requiring network access could be a benefit for some.

    2) Supporting a basic template system would be nice, so that all the generated files could have user supplied headers/footers.

    3) Support minimal applications. I.e. I might want to create a quick and dirty webapp that doesn’t need persistence.

    Nice work though, including the web interface. Look forward to seeing where you take this.

  4. 1) The problem here is the maven-ant dependency resolution. Once you download those files, you can define “build.offline=true” and it won’t attempt to connect to the network again. That value can really be anything. As long as it’s set. I went this route to save bandwidth and download times from the website.

    2) The next revision or so will allow user accounts to store and track user and project information. Once that’s in a template for headers and footers might indeed be possible.

    3) That’s an excellent suggestion. I had planned to support other persistence layers such as JPA and ibatis. I had never considered the simple case of *no* persistence. I’ll make a note of that.

    Thanks for the feedback. All very useful suggestions.

  5. I would suggest linking to Qwicket from the Wicket site, I have been looking around for information about Wicket while evaluating frameworks for a new projectt, and it took me three days to find it.

  6. Nice work. But there’s a small mistake in the dependency reference to hibernate. The correct reference is http://www.ibiblio.org/maven2/org/hibernate/hibernate/3.2.0.cr1/, with a dot right before the last version token(cr1).

    Congrats!


Trackbacks are disabled.