Another example of an app builder is the Sakai App Builder, which is an Eclipse plugin for quickly creating an example tool/app integrated into the Sakai Framework. http://confluence.sakaiproject.org/display/BOOT/Sakai+App+Builder
It allows you to select from a number of view technologies (JSF,JSP etc) and I added the Wicket components to allow it to generate a Sakai Wicket app. It could probably do with an overhaul from the things I've learned in the past year or so ;) It can create just the basic skeleton or a working app using the Sakai API, so we use it a lot for new developers to Sakai as a launchpad app. The working app is still quite basic though since we want the developers to follow established best practices in extending it and creating their own Sakai tool. cheers, Steve On 08/02/2010, at 3:19 PM, Jeremy Thomerson wrote: > Look at jWeekend's "LegUp" as an example of a working app: > http://www.jweekend.com/dev/LegUp > > However, with no offense intended, here's my $0.02.... Creating a Wicket > app for people from a spec file is a great idea. But doing it without > understanding how Wicket works is a bad idea. You'll likely end up > introducing more bad practices to people who are new to Wicket. > > It's a great idea - and I think it could be a great thing for Wicket, but > I'd highly suggest that you team up with some Wicket professionals so that > you write it the right way. There are a few key things to understand about > Wicket that most newcomers don't "just get" until they've used it for a > while. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Sat, Feb 6, 2010 at 3:27 PM, Vineet Manohar > <vineet.mano...@gmail.com>wrote: > >> Thanks. I will look at the maven archetype. >> >> More than just pages, I am looking at links, forms, inputs etc. For >> example, >> to create a link I am either use <a href=""> in the HTML, or I can use >> Wicket link component model, what's the difference and which one should I >> use? >> >> Btw, my goal is to automatically generate a working Wicket app with full >> database integration using JPA and security integration as well. The Seam >> code generation project that I did was a success, you can write a spec like >> this one: >> >> http://code.google.com/p/clickframes-seam-issuetracker-demo/source/browse/trunk/src/main/clickframes/appspec.xml >> >> and instantly get a working app like this: >> live demo link: >> http://demo.clickframes.org/tracker >> >> Of course you can add/remove pages from the app by changing the appspec >> xml. >> >> I am trying to replicate the same thing for Wicket, hoping to get some help >> from user community! >> >> On Sat, Feb 6, 2010 at 4:09 PM, Riyad Kalla <rka...@gmail.com> wrote: >> >>> Vineet, very cool stuff you are wooing on. As for best practices with >>> regard >>> to layout, there is actually a Maven Wicket archetype that would probably >>> answer those questions well. From what I remember its pretty straight >>> forward maven web layout. And yes, HTML and Java source are in same main >>> packages together. >>> >>> On Feb 6, 2010 1:33 PM, "Vineet Manohar" <vineet.mano...@gmail.com> >> wrote: >>> >>> Hi, >>> >>> I am trying to write a code generator (using Clickframes code generation >>> framework) which would generate a fully working Wicket project directly >>> from >>> the Spec. Is there a document which describes the best practice for >>> folder/package structure in a wicket project. >>> >>> To write the code generator, the only thing I need to know is the Wicket >>> project structure that I should be created. For example: >>> 1) should html files be colocated in src/main/java/com/mypackage/ along >>> with >>> Java files (as in the helloworld example) or in src/main/webapp. >>> 2) should there be one html file per page (I am assuming yes) >>> ... and other such questions related to folder structure >>> >>> I am the lead developer of open source code generation framework >>> Clickframes >>> (http://www.clickframes.org) and have written a similar code generator >> for >>> JSF/Seam which instantly gives you a working app directly from the spec >>> which the developer can then customize. I think a similar approach for >>> Wicket would be very helpful to Wicket users who are trying to start a >>> brand >>> new project. >>> >>> Here's what I have so far. >>> http://code.google.com/p/clickframes-wicket-plugin/ >>> >>> I am a Wicket novice, so any help or direction is appreciated. >>> >>> Thanks, >>> >>> Vineet Manohar >>> http://www.vineetmanohar.com >>> >>
smime.p7s
Description: S/MIME cryptographic signature
