Re: Wicket best practice
If you just want to navigate from PageA to PageB then a wicket:link
is fine, though I rarely use them. If you want to have more involved
processing then a Link object is preferable:
thePage.add(new Link(someId) {
public void onClick() {
doThis();
validateThat();
// either
setResponsePage(PageB.class);
// or
setResponsePage(new PageB(oneParam, anotherParam));
}
});
On Sat, Feb 6, 2010 at 10:26 PM, Vineet Manohar
vineet.mano...@gmail.com wrote:
Thanks. Is one approach better than the other?
Vineet
On Sat, Feb 6, 2010 at 5:00 PM, Andrew Lombardi
and...@mysticcoders.comwrote:
There are 2 main ways to create a link with Wicket:
1. Use autolinking. wrap your link in wicket:link tags in the HTML and
take note of package structure, so if in same package HomePage.html would go
in href, and if its in a package called admin, you'd have
admin/AdminHomePage.html, etc.
2. Use one of the Link objects, which requires a wicket:id attached to
usually an anchor tag in the HTML. So you'll have to have Java code and
HTML code that match id's
-andrew
On Feb 6, 2010, at 1:27 PM, Vineet Manohar 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
To our success!
Mystic Coders, LLC | Code Magic | www.mysticcoders.com
ANDREW LOMBARDI | and...@mysticcoders.com
2321 E 4th St. Ste C-128, Santa Ana CA 92705
ofc: 714-816-4488
fax: 714-782-6024
cell: 714-697-8046
linked-in: http://www.linkedin.com/in/andrewlombardi
twitter: http://www.twitter.com/kinabalu
Eco-Tip: Printing e-mails is usually a waste.
This message is for the named person's use only. You must not, directly or
indirectly, use,
disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket best practice
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.comwrote: 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
Re: Wicket best practice
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.comwrote: 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
Re: Wicket best practice
Hi Jeremy, Thanks for the link, I'll look into it. I agree with you completely that the best practices of Wicket should be baked into the code generator. My goal is to create a free open source framework which lets users generate Wicket apps. I am trying to create an initial code generator for Wicket, which professionals like yourself can then customize to create their own flavors of code generators. With Clickframes, you can tweak/override/extend select templates from one code generator to create another. In fact, I have sometimes customized templates for a specific app if I wanted slightly different implementation. I will do some more research into how Wicket works. What's a good resource, website or book to start? Vineet On Sun, Feb 7, 2010 at 11:19 PM, Jeremy Thomerson jer...@wickettraining.com 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
Re: Wicket best practice
Wicket in Action is the best. Make sure that you really grasp the power behind models (the IModel interface implementations) and especially detachable models (i.e. LoadableDetachableModel). Don't just shove big collections of domain objects into the page or repeating views just because you can. Hope this helps. Looking forward to seeing the outcome! -- Jeremy Thomerson http://www.wickettraining.com On Sun, Feb 7, 2010 at 11:17 PM, Vineet Manohar vineet.mano...@gmail.comwrote: Hi Jeremy, Thanks for the link, I'll look into it. I agree with you completely that the best practices of Wicket should be baked into the code generator. My goal is to create a free open source framework which lets users generate Wicket apps. I am trying to create an initial code generator for Wicket, which professionals like yourself can then customize to create their own flavors of code generators. With Clickframes, you can tweak/override/extend select templates from one code generator to create another. In fact, I have sometimes customized templates for a specific app if I wanted slightly different implementation. I will do some more research into how Wicket works. What's a good resource, website or book to start? Vineet On Sun, Feb 7, 2010 at 11:19 PM, Jeremy Thomerson jer...@wickettraining.com 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
Wicket best practice
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
Re: Wicket best practice
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
Re: Wicket best practice
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
Re: Wicket best practice
There are 2 main ways to create a link with Wicket: 1. Use autolinking. wrap your link in wicket:link tags in the HTML and take note of package structure, so if in same package HomePage.html would go in href, and if its in a package called admin, you'd have admin/AdminHomePage.html, etc. 2. Use one of the Link objects, which requires a wicket:id attached to usually an anchor tag in the HTML. So you'll have to have Java code and HTML code that match id's -andrew On Feb 6, 2010, at 1:27 PM, Vineet Manohar 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 To our success! Mystic Coders, LLC | Code Magic | www.mysticcoders.com ANDREW LOMBARDI | and...@mysticcoders.com 2321 E 4th St. Ste C-128, Santa Ana CA 92705 ofc: 714-816-4488 fax: 714-782-6024 cell: 714-697-8046 linked-in: http://www.linkedin.com/in/andrewlombardi twitter: http://www.twitter.com/kinabalu Eco-Tip: Printing e-mails is usually a waste. This message is for the named person's use only. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient.
Re: Wicket best practice
Thanks. Is one approach better than the other? Vineet On Sat, Feb 6, 2010 at 5:00 PM, Andrew Lombardi and...@mysticcoders.comwrote: There are 2 main ways to create a link with Wicket: 1. Use autolinking. wrap your link in wicket:link tags in the HTML and take note of package structure, so if in same package HomePage.html would go in href, and if its in a package called admin, you'd have admin/AdminHomePage.html, etc. 2. Use one of the Link objects, which requires a wicket:id attached to usually an anchor tag in the HTML. So you'll have to have Java code and HTML code that match id's -andrew On Feb 6, 2010, at 1:27 PM, Vineet Manohar 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 To our success! Mystic Coders, LLC | Code Magic | www.mysticcoders.com ANDREW LOMBARDI | and...@mysticcoders.com 2321 E 4th St. Ste C-128, Santa Ana CA 92705 ofc: 714-816-4488 fax: 714-782-6024 cell: 714-697-8046 linked-in: http://www.linkedin.com/in/andrewlombardi twitter: http://www.twitter.com/kinabalu Eco-Tip: Printing e-mails is usually a waste. This message is for the named person's use only. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient.
