Wicket and ExtJS
So I am on the verge of giving up on integrating Wicket and ExtJS and going with some other webapp framework. I thought Wicket and ExtJS would be the perfect companions because Wicket is basically a hierarchy of components and so is ExtJS. If I could extend wicket components to write out the required javascript instead of their HTML (or even in addition to), it would be a perfect fit. My developers wouldn't need to be expert javascript developers as long as enough of us were to maintain the components. The developer could simply snap in an extended component in Wicket, and like magic, a beautiful full-featured UI widget appears in their browser. The problems I am having are probably mostly from my Wicket inexperience. I just cannot figure out how to make components that do what I want. I try using header contributors to write out the javascript, but many wicket values (like the links generated by the link components) don't seem available in the page. I envisioned being able to override a method in an extended component to write out what I wanted to write like myComponent.writeMe() to write out what I wanted to write out. But that seems like it's not how Wicket works. I am presently overriding onBeforeRender at the page level, iterating through child components looking for an interface I hung on my extended components, and calling methods to get javascript contributions from them, and then adding a header contributor to the page. But this feels like I am ESCAPING the tool, not using it. And the strict Wicket component to markup structure is frustrating because ExtJS 4 builds components solely through javascript. It feels like Wicket is fighting me every step of the way, and that screams to me that I am misusing the tool. Has anyone done something like this in Wicket? Can anyone provide some guidance? Am I approaching the problem from the wrong perspective? Brian Mulholland - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket and ExtJS
Brian, Why don´t you look at how things have been implemented for other libraries (e.g. jquery UI). Can you give a concrete example of component you want to integrate that is giving you problems? And the strict Wicket component to markup structure is frustrating because ExtJS 4 builds components solely through javascript. It feels like Wicket is fighting me every step of the way, and that screams to me that I am misusing the tool. So do many jQuery based components and they can still be integrated with wicket. Regards, Ernesto - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket and ExtJS
First, thanks for the prompt response.
Okay, so I am struggling with writing a menu component. I saw the
Suckerfish menu example and tried to adapt that towards my needs. I
want my fellow developers to be able to write something like:
MyMenu topMenu = new MyMenu(topMenu);
MyMenu subMenu1 = new SubMenu(subMenu1, Here is a submenu);
MyMenu subMenu2 = new SubMenu2(subMenu2, Here is another submenu);
subMenu1.addMenuItem(new BookmarkableLink(LINK_ID, SomePage.class),
Some Page);
subMenu2.addMenuItem(new BookmarkableLink(LINK_ID,
SomeOtherPage.class), Some Other Page);
submenu1.addMenuItem(new MyMenuSeparator());
subMenu1.addMenuItem(new Link(LINK_ID) {
public void onClick() {
//do something
}
}, An action);
subMenu1.addMenuItem(new MyClientSideAction(Do Local Work, some
javascript code or the name of a client side function to invoke or
something));
subMenu2.addMenuItem(new Link(LINK_ID) {
public void onClick() {
//do something else
}
}, Another action);
subMenu2.addMenuItem(new MyClientSideAction(Other Local Work, some
javascript code or the name of a client side function to invoke or
something));
Which would then generate Ext code. Either as one large block using
the Ext JSON config objects (if you've ever seen Ext code you know
what I mean), or generating a series of smaller scriptlets each
generating the indiidual item needed and adding by name to the
component that is it's parent.
The former might look like this (m just typing this now so forgive
any typoes).
Ext.onReady(function() {
//some code to make parent components not shown until we get to it's
items array which might look like:
items: [{
xtype: 'menu',
items: [{
xtype: 'menu',
text: 'Here is a submenu',
items: [{
xtype: 'menuitem',
text: 'Some Page',
handler: { //some magic code that somehow gets the wicket link
to forward to Some Page }
}, {
xtype: 'separator'
}, {
xtype: 'menuitem',
text: 'An Action',
handler: { //some magic code that somehow invokes the onClick
method on the server in the right link }
}, {
xtype: 'menuitem',
text: 'Do Local Work',
handler: { //the code or function provided }
}] //end first submenu's items
}, {
xtype: 'menu',
text: 'Here is another submenu',
items: [{
xtype: 'menuitem',
text: 'Some Other Page',
handler: { //some magic code that somehow gets the wicket link
to forward to Some Other Page }
}, {
xtype: 'menuitem',
text: 'Another Action',
handler: { //some magic code that somehow invokes the onClick
method on the server in the right link }
}, {
xtype: 'menuitem',
text: 'Other Local Work',
handler: { //the code or function provided }
}] //end secondsubmenu's items
}] //end topMenu's items
}] //end the parent object (whatever that is) items
});
the second proposal might have independent script tags at each
wicket:id tag, replacing the element with a script tag that gets the
parent (as detected by the parent hierarchy in wicket) and adds the
component to it's parent. Because Ext stores each function and
executes it in order, it should have the same effect as above, but
allow the component to be more independent. It only needs to detect
it's parent. I like this style better, but I have less idea how to
implement it through wicket. How can I override what wicket writes
for it's body?
So I would end up with many small block like the following throughout
my rendered markup.
SCRIPT
Ext.onReady(function(){
var parent = Ext.getCmp(myParent);
parent.add(Ext.create(whatever we are creating, {
//the config parms
});
});
/SCRIPT
Since I don't know how to do that, I have been writing towards the
first example. the result of my stumblings is a set of components
that all implement an interface that asks for the snippet of the first
example that represents their contribution, and then adds it as a
header contribution to the page. Links are resolved by css styling
the markup wicket generates as display:none, and then using javascript
to pick up the link and text of the menu item to add after render.
But this solution feels 'hacky' and inelegant. It feels like I am
sneaking around the framework, not USING the framework.
As to jQuery. I know zilch about jQuery. Because I also am just
learning wicket, I am leery of getting 'sucked into the rabbit hole'
on reading and learning how another library was implemented and then
finding out that it doesn't apply. But if you think it applies, I can
give it a shot. Is there a particular implementation that you think
is good to review?
Again, thanks for responding quickly, Ernesto. It's appreciated.
Brian Mulholland
On Mon, Oct 24, 2011 at 9:04 AM, Ernesto Reinaldo Barreiro
reier...@gmail.com wrote:
Brian,
Why don´t you look at how things have been
Re: Wicket and ExtJS
I would make class MyMenu as a Behavior or possibly a Label and class SubMenu
as a POJO (don't make it extend Component). Everything doesn't have to be a
subclass of component, right? You need to code MyMenu in such way that it
generates javascript from POJOs. That way your developers don't need to add
unnecessary elements to markup. MyMenu would be suitable as a behavior because
it's just javascript and doesn't need html elements. You would simply add the
behavior to the page. It could be a Label as well. I'm not sure which approach
has more benefits.
For the URLs that wicket must generate for you, see RequestCycle.urlFor()
methods. For example, there's the urlFor(Class, PageParameters) method that
creates a link to a page. To invoke some method on some component you would use
urlFor(component, ILinkListener.INTERFACE) and the component must implement the
ILinkListener interface.
- Original Message -
From: Brian Mulholland
Sent: 10/24/11 05:41 PM
To: users@wicket.apache.org
Subject: Re: Wicket and ExtJS
First, thanks for the prompt response. Okay, so I am struggling with writing a
menu component. I saw the Suckerfish menu example and tried to adapt that
towards my needs. I want my fellow developers to be able to write something
like: MyMenu topMenu = new MyMenu(topMenu); MyMenu subMenu1 = new
SubMenu(subMenu1, Here is a submenu); MyMenu subMenu2 = new
SubMenu2(subMenu2, Here is another submenu); subMenu1.addMenuItem(new
BookmarkableLink(LINK_ID, SomePage.class), Some Page);
subMenu2.addMenuItem(new BookmarkableLink(LINK_ID, SomeOtherPage.class), Some
Other Page); submenu1.addMenuItem(new MyMenuSeparator());
subMenu1.addMenuItem(new Link(LINK_ID) { public void onClick() { //do something
} }, An action); subMenu1.addMenuItem(new MyClientSideAction(Do Local Work,
some javascript code or the name of a client side function to invoke or
something)); subMenu2.addMenuItem(new Link(LINK_ID) { public void onClick() {
//do something else } }, Another action); sub
Menu2.addMenuItem(new MyClientSideAction(Other Local Work, some javascript
code or the name of a client side function to invoke or something)); Which
would then generate Ext code. Either as one large block using the Ext JSON
config objects (if you've ever seen Ext code you know what I mean), or
generating a series of smaller scriptlets each generating the indiidual item
needed and adding by name to the component that is it's parent. The former
might look like this (m just typing this now so forgive any typoes).
Ext.onReady(function() { //some code to make parent components not shown until
we get to it's items array which might look like: items: [{ xtype: 'menu',
items: [{ xtype: 'menu', text: 'Here is a submenu', items: [{ xtype:
'menuitem', text: 'Some Page', handler: { //some magic code that somehow gets
the wicket link to forward to Some Page } }, { xtype: 'separator' }, { xtype:
'menuitem', text: 'An Action', handler: { //some magic code that somehow
invokes the onC
lick method on the server in the right link } }, { xtype: 'menuitem', text:
'Do Local Work', handler: { //the code or function provided } }] //end first
submenu's items }, { xtype: 'menu', text: 'Here is another submenu', items: [{
xtype: 'menuitem', text: 'Some Other Page', handler: { //some magic code that
somehow gets the wicket link to forward to Some Other Page } }, { xtype:
'menuitem', text: 'Another Action', handler: { //some magic code that somehow
invokes the onClick method on the server in the right link } }, { xtype:
'menuitem', text: 'Other Local Work', handler: { //the code or function
provided } }] //end secondsubmenu's items }] //end topMenu's items }] //end the
parent object (whatever that is) items }); the second proposal might have
independent script tags at each wicket:id tag, replacing the element with a
script tag that gets the parent (as detected by the parent hierarchy in wicket)
and adds the component to it's parent. Because Ext stores each function a
nd executes it in order, it should have the same effect as above, but allow
the component to be more independent. It only needs to detect it's parent. I
like this style better, but I have less idea how to implement it through
wicket. How can I override what wicket writes for it's body? So I would end up
with many small block like the following throughout my rendered markup.
SCRIPT Ext.onReady(function(){ var parent = Ext.getCmp(myParent);
parent.add(Ext.create(whatever we are creating, { //the config parms }); });
/SCRIPT Since I don't know how to do that, I have been writing towards the
first example. the result of my stumblings is a set of components that all
implement an interface that asks for the snippet of the first example that
represents their contribution, and then adds it as a header contribution to the
page. Links are resolved by css styling the markup wicket generates as
display:none, and then using javascript to pick up the link
Re: Wicket and ExtJS
there have been plenty of discussions on wicket and extjs http://markmail.org/search/wicket+extjs my two cents is that this kind of integration is not a good idea. wicket is about manipulating existing markup in an object oriented way, while extjs is about generating the markup from code. there is a pretty big impedance mismatch between the two frameworks. further, the kind of logic that you would put into a link's onclick or a form's onsubmit is usually better written in javascript when using extjs. extjs is about creating fat clients that only use the server for data. wicket, on the other hand, is about creating thin clients where server also deals with the ui, not just data. so, here you have another impedance mismatch. imho you are better off using extjs with something like resteasy. -igor On Mon, Oct 24, 2011 at 5:54 AM, Brian Mulholland blmulholl...@gmail.com wrote: So I am on the verge of giving up on integrating Wicket and ExtJS and going with some other webapp framework. I thought Wicket and ExtJS would be the perfect companions because Wicket is basically a hierarchy of components and so is ExtJS. If I could extend wicket components to write out the required javascript instead of their HTML (or even in addition to), it would be a perfect fit. My developers wouldn't need to be expert javascript developers as long as enough of us were to maintain the components. The developer could simply snap in an extended component in Wicket, and like magic, a beautiful full-featured UI widget appears in their browser. The problems I am having are probably mostly from my Wicket inexperience. I just cannot figure out how to make components that do what I want. I try using header contributors to write out the javascript, but many wicket values (like the links generated by the link components) don't seem available in the page. I envisioned being able to override a method in an extended component to write out what I wanted to write like myComponent.writeMe() to write out what I wanted to write out. But that seems like it's not how Wicket works. I am presently overriding onBeforeRender at the page level, iterating through child components looking for an interface I hung on my extended components, and calling methods to get javascript contributions from them, and then adding a header contributor to the page. But this feels like I am ESCAPING the tool, not using it. And the strict Wicket component to markup structure is frustrating because ExtJS 4 builds components solely through javascript. It feels like Wicket is fighting me every step of the way, and that screams to me that I am misusing the tool. Has anyone done something like this in Wicket? Can anyone provide some guidance? Am I approaching the problem from the wrong perspective? Brian Mulholland - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-tools-extjs
I have a simple demo of the guestbook application. I'll post it online in the next couple of days. On Feb 7, 2008 10:54 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: Yes it's normal practice to make a simple project that demonstrates the functionality... Like http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/trunk/wicket-contrib-accordion-examples/ etc.. It usually does not take that long to construct and, is very good for users to learn from. regards Nino Flemming Boller wrote: I think you should add HomePage, or something like that, so users can see how to use this library. It is not easy to guess that for example many of the components shall not be in the markup when using this library, at least for the normal wicket user. Anyhow I found out that the ExtJS is a singleton (should it be?) and is clearing the children list after rendering. I think that is the reason why the response is rendered empty, when I press Save button on a ExtJSForm. - just a thought /FLemming On Feb 7, 2008 11:19 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: Yes, that's because I used the wicket archetype to create the project originally. I'll remove TestHomePage.java. Thanks for the catch! -Jeremy On Feb 7, 2008 1:06 PM, Flemming Boller [EMAIL PROTECTED] wrote: Hi Yes, but in your test class (TestHomePage.java) you reference HomePage.class That was why I mentioned it. /FLemming On Feb 7, 2008 8:35 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: There is no HomePage.java because this is not a wicket application. It is a library that you can use in your applications. If you want to use it you can compile it by downloading the source and then compiling with: mvn compile, or you can just add the following lines to your applications POM and maven will automatically download the appropriate files for you: !-- ExtJS (javascript library) DEPENDENCIES -- dependency groupIdorg.wickettools.extjs/groupId artifactIdextjs/artifactId version0.1.0/version /dependency also add the following to your repositories section (the files should be in the global maven repository soon): repository idwicket-tools-exjts/id namewicket-tools-extjs repository/name urlhttp://wicket-extjs.sourceforge.net/maven2//url /repository On Feb 7, 2008 8:51 AM, Flemming Boller [EMAIL PROTECTED] wrote: Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf -- Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket-tools-extjs
There is no HomePage.java because this is not a wicket application. It is a library that you can use in your applications. If you want to use it you can compile it by downloading the source and then compiling with: mvn compile, or you can just add the following lines to your applications POM and maven will automatically download the appropriate files for you: !-- ExtJS (javascript library) DEPENDENCIES -- dependency groupIdorg.wickettools.extjs/groupId artifactIdextjs/artifactId version0.1.0/version /dependency also add the following to your repositories section (the files should be in the global maven repository soon): repository idwicket-tools-exjts/id namewicket-tools-extjs repository/name urlhttp://wicket-extjs.sourceforge.net/maven2//url /repository On Feb 7, 2008 8:51 AM, Flemming Boller [EMAIL PROTECTED] wrote: Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf
Re: wicket-tools-extjs
Yeah, If you look at the comments I credited the author. -Jeremy On Feb 6, 2008 9:19 PM, Ryan Sonnek [EMAIL PROTECTED] wrote: Glancing through the javadocs, that JavascriptBuilder class looks awefully familiar. i'm assuming you've seen the wicketstuff-scriptaculous project? =) On Wed, 2008-02-06 at 20:02 -0700, Jeremy Fergason wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wicket-tools-extjs
Yes, that's because I used the wicket archetype to create the project originally. I'll remove TestHomePage.java. Thanks for the catch! -Jeremy On Feb 7, 2008 1:06 PM, Flemming Boller [EMAIL PROTECTED] wrote: Hi Yes, but in your test class (TestHomePage.java) you reference HomePage.class That was why I mentioned it. /FLemming On Feb 7, 2008 8:35 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: There is no HomePage.java because this is not a wicket application. It is a library that you can use in your applications. If you want to use it you can compile it by downloading the source and then compiling with: mvn compile, or you can just add the following lines to your applications POM and maven will automatically download the appropriate files for you: !-- ExtJS (javascript library) DEPENDENCIES -- dependency groupIdorg.wickettools.extjs/groupId artifactIdextjs/artifactId version0.1.0/version /dependency also add the following to your repositories section (the files should be in the global maven repository soon): repository idwicket-tools-exjts/id namewicket-tools-extjs repository/name urlhttp://wicket-extjs.sourceforge.net/maven2//url /repository On Feb 7, 2008 8:51 AM, Flemming Boller [EMAIL PROTECTED] wrote: Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf
Re: wicket-tools-extjs
Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf
Re: wicket-tools-extjs
Hi Yes, but in your test class (TestHomePage.java) you reference HomePage.class That was why I mentioned it. /FLemming On Feb 7, 2008 8:35 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: There is no HomePage.java because this is not a wicket application. It is a library that you can use in your applications. If you want to use it you can compile it by downloading the source and then compiling with: mvn compile, or you can just add the following lines to your applications POM and maven will automatically download the appropriate files for you: !-- ExtJS (javascript library) DEPENDENCIES -- dependency groupIdorg.wickettools.extjs/groupId artifactIdextjs/artifactId version0.1.0/version /dependency also add the following to your repositories section (the files should be in the global maven repository soon): repository idwicket-tools-exjts/id namewicket-tools-extjs repository/name urlhttp://wicket-extjs.sourceforge.net/maven2//url /repository On Feb 7, 2008 8:51 AM, Flemming Boller [EMAIL PROTECTED] wrote: Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf
Re: wicket-tools-extjs
I think you should add HomePage, or something like that, so users can see how to use this library. It is not easy to guess that for example many of the components shall not be in the markup when using this library, at least for the normal wicket user. Anyhow I found out that the ExtJS is a singleton (should it be?) and is clearing the children list after rendering. I think that is the reason why the response is rendered empty, when I press Save button on a ExtJSForm. - just a thought /FLemming On Feb 7, 2008 11:19 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: Yes, that's because I used the wicket archetype to create the project originally. I'll remove TestHomePage.java. Thanks for the catch! -Jeremy On Feb 7, 2008 1:06 PM, Flemming Boller [EMAIL PROTECTED] wrote: Hi Yes, but in your test class (TestHomePage.java) you reference HomePage.class That was why I mentioned it. /FLemming On Feb 7, 2008 8:35 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: There is no HomePage.java because this is not a wicket application. It is a library that you can use in your applications. If you want to use it you can compile it by downloading the source and then compiling with: mvn compile, or you can just add the following lines to your applications POM and maven will automatically download the appropriate files for you: !-- ExtJS (javascript library) DEPENDENCIES -- dependency groupIdorg.wickettools.extjs/groupId artifactIdextjs/artifactId version0.1.0/version /dependency also add the following to your repositories section (the files should be in the global maven repository soon): repository idwicket-tools-exjts/id namewicket-tools-extjs repository/name urlhttp://wicket-extjs.sourceforge.net/maven2//url /repository On Feb 7, 2008 8:51 AM, Flemming Boller [EMAIL PROTECTED] wrote: Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf
Re: wicket-tools-extjs
Yes it's normal practice to make a simple project that demonstrates the functionality... Like http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/trunk/wicket-contrib-accordion-examples/ etc.. It usually does not take that long to construct and, is very good for users to learn from. regards Nino Flemming Boller wrote: I think you should add HomePage, or something like that, so users can see how to use this library. It is not easy to guess that for example many of the components shall not be in the markup when using this library, at least for the normal wicket user. Anyhow I found out that the ExtJS is a singleton (should it be?) and is clearing the children list after rendering. I think that is the reason why the response is rendered empty, when I press Save button on a ExtJSForm. - just a thought /FLemming On Feb 7, 2008 11:19 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: Yes, that's because I used the wicket archetype to create the project originally. I'll remove TestHomePage.java. Thanks for the catch! -Jeremy On Feb 7, 2008 1:06 PM, Flemming Boller [EMAIL PROTECTED] wrote: Hi Yes, but in your test class (TestHomePage.java) you reference HomePage.class That was why I mentioned it. /FLemming On Feb 7, 2008 8:35 PM, Jeremy Fergason [EMAIL PROTECTED] wrote: There is no HomePage.java because this is not a wicket application. It is a library that you can use in your applications. If you want to use it you can compile it by downloading the source and then compiling with: mvn compile, or you can just add the following lines to your applications POM and maven will automatically download the appropriate files for you: !-- ExtJS (javascript library) DEPENDENCIES -- dependency groupIdorg.wickettools.extjs/groupId artifactIdextjs/artifactId version0.1.0/version /dependency also add the following to your repositories section (the files should be in the global maven repository soon): repository idwicket-tools-exjts/id namewicket-tools-extjs repository/name urlhttp://wicket-extjs.sourceforge.net/maven2//url /repository On Feb 7, 2008 8:51 AM, Flemming Boller [EMAIL PROTECTED] wrote: Hi I have tried it a little bit, but I think you have forgot to include some source files. Like HomePage.java. /FLemming On Feb 7, 2008 4:02 AM, Jeremy Fergason [EMAIL PROTECTED] wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf -- Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wicket-tools-extjs
All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hope you find this useful. -jdf
Re: wicket-tools-extjs
On Wed, 2008-02-06 at 20:02 -0700, Jeremy Fergason wrote: All, I've been trying to use the ExtJS forms from within wicket. It seemed that several people out there were trying to do this with limited success; except for the occasional person saying they had done it. I have got the integration working OK at this point and would like to make the integration module available to the community at large. If you are interested in using ExtJS forms from within wicket checkout the wicket-tools-extjs module at: www.wickettools.org I'm pretty new to wicket so please comment on the design with any suggestions of how I could improve it. Also if there is anyone who is interested in helping out I would love to have the support. Hi What's up with your site using PHP and hosting a Wicket project! :P Ok.. Just teasing.. looks ok and best of luck! ./C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
