You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Tauren Mills <ta...@tauren.com> on 2009/07/21 11:18:12 UTC
jWicket -- jQuery with Wicket integration
jWicket has now been released as a wicketstuff project. jWicket is an
integration of Wicket and jQuery that was previously called
WicketJQuery (by Stefan Lindner). I realize there are already a few
Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
implementation has some advantages over the others.
Stefan and I discussed how to best move the WicketJQuery project
forward and decided it was best if it became a standard maven project
to make it easy for others to use. We decided to host it at
wicketstuff so that it would be available via a maven repository. We
also decided to rename it since there were already wicketstuff
projects with very similar names. So it will now be known as
"jWicket".
At this point, the code committed to WicketStuff is essentially the
same codebase available on the original WicketJQuery SVN server. I
have refactored it with the org.wicketstuff.jwicket namespace and have
structured the project in a standard maven manner. I also split the
project into jwicket-parent, jwicket, and jwicket-examples. The demo
app is now separate from jwicket itself so that it doesn't need to be
imported into projects.
The original WIcketJQuery project developed by Stefan Lindner can be found at:
http://subversion.visionet.de/project/WicketJQuery/wiki
Tauren
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Sam Stainsby <sa...@sustainablesoftware.com.au>.
On Tue, 21 Jul 2009 02:18:12 -0700, Tauren Mills wrote:
> I realize there are already a few Wicket/jQuery
> integrations, but I think that Stefan's WicketJQuery implementation has
> some advantages over the others.
We've just started using WiQuery (http://code.google.com/p/wiquery/), but
are not committed to it as yet. What would you say are the advantages of
jWicket over WiQuery?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageLink deprecated in 1.4
Posted by Igor Vaynberg <ig...@gmail.com>.
the two alternatives are mentioned in the javadoc.
-igor
On Tue, Jul 21, 2009 at 11:35 AM, David R
Robison<dr...@openroadsconsulting.com> wrote:
> I noticed that the PageLink class is deprecated in 1.4. What should it be
> replaced with in my application code? David
>
> --
>
> David R Robison
> Open Roads Consulting, Inc.
> 103 Watson Road, Chesapeake, VA 23320
> phone: (757) 546-3401
> e-mail: drrobison@openroadsconsulting.com
> web: http://openroadsconsulting.com
> blog: http://therobe.blogspot.com
> book: http://www.xulonpress.com/book_detail.php?id=2579
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
PageLink deprecated in 1.4
Posted by David R Robison <dr...@openroadsconsulting.com>.
I noticed that the PageLink class is deprecated in 1.4. What should it
be replaced with in my application code? David
--
David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
phone: (757) 546-3401
e-mail: drrobison@openroadsconsulting.com
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/book_detail.php?id=2579
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Anton Veretennikov <an...@gmail.com>.
I mean,
1. What are things in other jQuery integrations that are not already
done in wicketstuff-jquery?
2. When I move to wicket 1.4-rcX, what version I need to use of
wicketstuff-jquery? (I mean conflicts of versions)
3. What are statuses of all different integrations?
-- Tony
On Wed, Jul 22, 2009 at 9:57 PM, Martijn
Dashorst<ma...@gmail.com> wrote:
> What about it?
>
> On Wed, Jul 22, 2009 at 2:41 PM, Anton
> Veretennikov<an...@gmail.com> wrote:
>> May I ask about wicketstuff-jquery's future?
>>
>> -- Tony
>>
>> On Wed, Jul 22, 2009 at 3:09 AM, Stefan Lindner<li...@visionet.de> wrote:
>>> Yes! Fixed. Now it's http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.7/WicketJQueryDemo.war
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: satar [mailto:starlton@gmail.com]
>>> Gesendet: Dienstag, 21. Juli 2009 20:27
>>> An: users@wicket.apache.org
>>> Betreff: Re: jWicket -- jQuery with Wicket integration
>>>
>>>
>>> Just an FYI, the link to the WicketJQueryDemo.war on
>>> "http://subversion.visionet.de/project/WicketJQuery/wiki" is broke. I think
>>> it should be:
>>>
>>> http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.6/WicketJQueryDemo.war
>>>
>>> instead its:
>>>
>>> http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3./WicketJQueryDemo.war
>>> --
>>> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24593132.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Martijn Dashorst <ma...@gmail.com>.
What about it?
On Wed, Jul 22, 2009 at 2:41 PM, Anton
Veretennikov<an...@gmail.com> wrote:
> May I ask about wicketstuff-jquery's future?
>
> -- Tony
>
> On Wed, Jul 22, 2009 at 3:09 AM, Stefan Lindner<li...@visionet.de> wrote:
>> Yes! Fixed. Now it's http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.7/WicketJQueryDemo.war
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: satar [mailto:starlton@gmail.com]
>> Gesendet: Dienstag, 21. Juli 2009 20:27
>> An: users@wicket.apache.org
>> Betreff: Re: jWicket -- jQuery with Wicket integration
>>
>>
>> Just an FYI, the link to the WicketJQueryDemo.war on
>> "http://subversion.visionet.de/project/WicketJQuery/wiki" is broke. I think
>> it should be:
>>
>> http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.6/WicketJQueryDemo.war
>>
>> instead its:
>>
>> http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3./WicketJQueryDemo.war
>> --
>> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24593132.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: should the IRequestLogger implement Serializable?
Posted by "Jing Ge (Besitec IT DEHAM)" <JG...@besitec.com>.
Hello Jeremy Thomerson,
For example: I want the site administrator know, for example, how many
users are active now, what are their session looks like, etc.
Thx
Jing
-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
Sent: Mittwoch, 22. Juli 2009 16:42
To: users@wicket.apache.org
Subject: Re: should the IRequestLogger implement Serializable?
Isn't the logger sort of a service that does the logging? Your page
shouldn't hold on to that. Perhaps it can get it from the application
or hold on to something else.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Jul 22, 2009 at 9:38 AM, Jing Ge (Besitec IT
DEHAM)<JG...@besitec.com> wrote:
> Hello all,
>
> I am trying to use the RequestLogger. It is really a greet idea that
the
> interface ISessionLogInfo is defined. Developer can just implement
this
> interface for logging more individual information.
>
> My requirement is:
>
> I want to use the instance of IRequestLogger for building a site
status
> page, which means the IRequestLogger need implement the Serializable
> interface.
>
> Does anyone find any drawback for letting IRequestLogger implement
> Serializable?
>
> I am using wicket 1.4 rc4
>
> Thx & best regards.
> Jing Ge
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: should the IRequestLogger implement Serializable?
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Isn't the logger sort of a service that does the logging? Your page
shouldn't hold on to that. Perhaps it can get it from the application
or hold on to something else.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Jul 22, 2009 at 9:38 AM, Jing Ge (Besitec IT
DEHAM)<JG...@besitec.com> wrote:
> Hello all,
>
> I am trying to use the RequestLogger. It is really a greet idea that the
> interface ISessionLogInfo is defined. Developer can just implement this
> interface for logging more individual information.
>
> My requirement is:
>
> I want to use the instance of IRequestLogger for building a site status
> page, which means the IRequestLogger need implement the Serializable
> interface.
>
> Does anyone find any drawback for letting IRequestLogger implement
> Serializable?
>
> I am using wicket 1.4 rc4
>
> Thx & best regards.
> Jing Ge
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: should the IRequestLogger implement Serializable?
Posted by "Jing Ge (Besitec IT DEHAM)" <JG...@besitec.com>.
Got it! Thanks!
Jing
-----Original Message-----
From: Johan Compagner [mailto:jcompagner@gmail.com]
Sent: Mittwoch, 22. Juli 2009 19:42
To: users@wicket.apache.org
Subject: Re: should the IRequestLogger implement Serializable?
you shouldnt store those kind of objects (services or application
"static"
objects)
use LoadableDetachableModel for that
On Wed, Jul 22, 2009 at 16:56, Jing Ge (Besitec IT DEHAM)
<JG...@besitec.com>wrote:
> Well, the RequestLogger is not a pure service. It is also a data
object.
> It is actually a combination of service and data object.
>
> Regard
> Jing
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Mittwoch, 22. Juli 2009 16:53
> To: users@wicket.apache.org
> Subject: Re: should the IRequestLogger implement Serializable?
>
> Would you use new Model<UserService>(getYourUserService())? It's the
> same thing - they are services, not data objects.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Jul 22, 2009 at 9:47 AM, Jing Ge (Besitec IT
> DEHAM)<JG...@besitec.com> wrote:
> > Hello johan,
> >
> > Because I want to use the information hold in the RequestLogger as
an
> > object in a model. Something like this:
> >
> > New Model<RequestLogger>(getRequestLogger());
> >
> > Thx
> > Jing
> >
> > -----Original Message-----
> > From: Johan Compagner [mailto:jcompagner@gmail.com]
> > Sent: Mittwoch, 22. Juli 2009 16:43
> > To: users@wicket.apache.org
> > Subject: Re: should the IRequestLogger implement Serializable?
> >
> > why would you serialize the request logger?
> > there is only one and that is attached to the Application it
shouldnt
> be
> > serialized.
> >
> > Just like that Settings object is also not serialize able or the
> > implementations of ISessionStore
> >
> > johan
> >
> >
> > On Wed, Jul 22, 2009 at 16:38, Jing Ge (Besitec IT DEHAM)
> > <JG...@besitec.com>wrote:
> >
> >> Hello all,
> >>
> >> I am trying to use the RequestLogger. It is really a greet idea
that
> > the
> >> interface ISessionLogInfo is defined. Developer can just implement
> > this
> >> interface for logging more individual information.
> >>
> >> My requirement is:
> >>
> >> I want to use the instance of IRequestLogger for building a site
> > status
> >> page, which means the IRequestLogger need implement the
Serializable
> >> interface.
> >>
> >> Does anyone find any drawback for letting IRequestLogger implement
> >> Serializable?
> >>
> >> I am using wicket 1.4 rc4
> >>
> >> Thx & best regards.
> >> Jing Ge
> >>
> >>
> >>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: should the IRequestLogger implement Serializable?
Posted by Johan Compagner <jc...@gmail.com>.
you shouldnt store those kind of objects (services or application "static"
objects)
use LoadableDetachableModel for that
On Wed, Jul 22, 2009 at 16:56, Jing Ge (Besitec IT DEHAM)
<JG...@besitec.com>wrote:
> Well, the RequestLogger is not a pure service. It is also a data object.
> It is actually a combination of service and data object.
>
> Regard
> Jing
>
> -----Original Message-----
> From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
> Sent: Mittwoch, 22. Juli 2009 16:53
> To: users@wicket.apache.org
> Subject: Re: should the IRequestLogger implement Serializable?
>
> Would you use new Model<UserService>(getYourUserService())? It's the
> same thing - they are services, not data objects.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Jul 22, 2009 at 9:47 AM, Jing Ge (Besitec IT
> DEHAM)<JG...@besitec.com> wrote:
> > Hello johan,
> >
> > Because I want to use the information hold in the RequestLogger as an
> > object in a model. Something like this:
> >
> > New Model<RequestLogger>(getRequestLogger());
> >
> > Thx
> > Jing
> >
> > -----Original Message-----
> > From: Johan Compagner [mailto:jcompagner@gmail.com]
> > Sent: Mittwoch, 22. Juli 2009 16:43
> > To: users@wicket.apache.org
> > Subject: Re: should the IRequestLogger implement Serializable?
> >
> > why would you serialize the request logger?
> > there is only one and that is attached to the Application it shouldnt
> be
> > serialized.
> >
> > Just like that Settings object is also not serialize able or the
> > implementations of ISessionStore
> >
> > johan
> >
> >
> > On Wed, Jul 22, 2009 at 16:38, Jing Ge (Besitec IT DEHAM)
> > <JG...@besitec.com>wrote:
> >
> >> Hello all,
> >>
> >> I am trying to use the RequestLogger. It is really a greet idea that
> > the
> >> interface ISessionLogInfo is defined. Developer can just implement
> > this
> >> interface for logging more individual information.
> >>
> >> My requirement is:
> >>
> >> I want to use the instance of IRequestLogger for building a site
> > status
> >> page, which means the IRequestLogger need implement the Serializable
> >> interface.
> >>
> >> Does anyone find any drawback for letting IRequestLogger implement
> >> Serializable?
> >>
> >> I am using wicket 1.4 rc4
> >>
> >> Thx & best regards.
> >> Jing Ge
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
RE: should the IRequestLogger implement Serializable?
Posted by "Jing Ge (Besitec IT DEHAM)" <JG...@besitec.com>.
Well, the RequestLogger is not a pure service. It is also a data object.
It is actually a combination of service and data object.
Regard
Jing
-----Original Message-----
From: Jeremy Thomerson [mailto:jeremy@wickettraining.com]
Sent: Mittwoch, 22. Juli 2009 16:53
To: users@wicket.apache.org
Subject: Re: should the IRequestLogger implement Serializable?
Would you use new Model<UserService>(getYourUserService())? It's the
same thing - they are services, not data objects.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Jul 22, 2009 at 9:47 AM, Jing Ge (Besitec IT
DEHAM)<JG...@besitec.com> wrote:
> Hello johan,
>
> Because I want to use the information hold in the RequestLogger as an
> object in a model. Something like this:
>
> New Model<RequestLogger>(getRequestLogger());
>
> Thx
> Jing
>
> -----Original Message-----
> From: Johan Compagner [mailto:jcompagner@gmail.com]
> Sent: Mittwoch, 22. Juli 2009 16:43
> To: users@wicket.apache.org
> Subject: Re: should the IRequestLogger implement Serializable?
>
> why would you serialize the request logger?
> there is only one and that is attached to the Application it shouldnt
be
> serialized.
>
> Just like that Settings object is also not serialize able or the
> implementations of ISessionStore
>
> johan
>
>
> On Wed, Jul 22, 2009 at 16:38, Jing Ge (Besitec IT DEHAM)
> <JG...@besitec.com>wrote:
>
>> Hello all,
>>
>> I am trying to use the RequestLogger. It is really a greet idea that
> the
>> interface ISessionLogInfo is defined. Developer can just implement
> this
>> interface for logging more individual information.
>>
>> My requirement is:
>>
>> I want to use the instance of IRequestLogger for building a site
> status
>> page, which means the IRequestLogger need implement the Serializable
>> interface.
>>
>> Does anyone find any drawback for letting IRequestLogger implement
>> Serializable?
>>
>> I am using wicket 1.4 rc4
>>
>> Thx & best regards.
>> Jing Ge
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: should the IRequestLogger implement Serializable?
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Would you use new Model<UserService>(getYourUserService())? It's the
same thing - they are services, not data objects.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Jul 22, 2009 at 9:47 AM, Jing Ge (Besitec IT
DEHAM)<JG...@besitec.com> wrote:
> Hello johan,
>
> Because I want to use the information hold in the RequestLogger as an
> object in a model. Something like this:
>
> New Model<RequestLogger>(getRequestLogger());
>
> Thx
> Jing
>
> -----Original Message-----
> From: Johan Compagner [mailto:jcompagner@gmail.com]
> Sent: Mittwoch, 22. Juli 2009 16:43
> To: users@wicket.apache.org
> Subject: Re: should the IRequestLogger implement Serializable?
>
> why would you serialize the request logger?
> there is only one and that is attached to the Application it shouldnt be
> serialized.
>
> Just like that Settings object is also not serialize able or the
> implementations of ISessionStore
>
> johan
>
>
> On Wed, Jul 22, 2009 at 16:38, Jing Ge (Besitec IT DEHAM)
> <JG...@besitec.com>wrote:
>
>> Hello all,
>>
>> I am trying to use the RequestLogger. It is really a greet idea that
> the
>> interface ISessionLogInfo is defined. Developer can just implement
> this
>> interface for logging more individual information.
>>
>> My requirement is:
>>
>> I want to use the instance of IRequestLogger for building a site
> status
>> page, which means the IRequestLogger need implement the Serializable
>> interface.
>>
>> Does anyone find any drawback for letting IRequestLogger implement
>> Serializable?
>>
>> I am using wicket 1.4 rc4
>>
>> Thx & best regards.
>> Jing Ge
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: should the IRequestLogger implement Serializable?
Posted by "Jing Ge (Besitec IT DEHAM)" <JG...@besitec.com>.
Hello johan,
Because I want to use the information hold in the RequestLogger as an
object in a model. Something like this:
New Model<RequestLogger>(getRequestLogger());
Thx
Jing
-----Original Message-----
From: Johan Compagner [mailto:jcompagner@gmail.com]
Sent: Mittwoch, 22. Juli 2009 16:43
To: users@wicket.apache.org
Subject: Re: should the IRequestLogger implement Serializable?
why would you serialize the request logger?
there is only one and that is attached to the Application it shouldnt be
serialized.
Just like that Settings object is also not serialize able or the
implementations of ISessionStore
johan
On Wed, Jul 22, 2009 at 16:38, Jing Ge (Besitec IT DEHAM)
<JG...@besitec.com>wrote:
> Hello all,
>
> I am trying to use the RequestLogger. It is really a greet idea that
the
> interface ISessionLogInfo is defined. Developer can just implement
this
> interface for logging more individual information.
>
> My requirement is:
>
> I want to use the instance of IRequestLogger for building a site
status
> page, which means the IRequestLogger need implement the Serializable
> interface.
>
> Does anyone find any drawback for letting IRequestLogger implement
> Serializable?
>
> I am using wicket 1.4 rc4
>
> Thx & best regards.
> Jing Ge
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: should the IRequestLogger implement Serializable?
Posted by Johan Compagner <jc...@gmail.com>.
why would you serialize the request logger?
there is only one and that is attached to the Application it shouldnt be
serialized.
Just like that Settings object is also not serialize able or the
implementations of ISessionStore
johan
On Wed, Jul 22, 2009 at 16:38, Jing Ge (Besitec IT DEHAM)
<JG...@besitec.com>wrote:
> Hello all,
>
> I am trying to use the RequestLogger. It is really a greet idea that the
> interface ISessionLogInfo is defined. Developer can just implement this
> interface for logging more individual information.
>
> My requirement is:
>
> I want to use the instance of IRequestLogger for building a site status
> page, which means the IRequestLogger need implement the Serializable
> interface.
>
> Does anyone find any drawback for letting IRequestLogger implement
> Serializable?
>
> I am using wicket 1.4 rc4
>
> Thx & best regards.
> Jing Ge
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
should the IRequestLogger implement Serializable?
Posted by "Jing Ge (Besitec IT DEHAM)" <JG...@besitec.com>.
Hello all,
I am trying to use the RequestLogger. It is really a greet idea that the
interface ISessionLogInfo is defined. Developer can just implement this
interface for logging more individual information.
My requirement is:
I want to use the instance of IRequestLogger for building a site status
page, which means the IRequestLogger need implement the Serializable
interface.
Does anyone find any drawback for letting IRequestLogger implement
Serializable?
I am using wicket 1.4 rc4
Thx & best regards.
Jing Ge
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Anton Veretennikov <an...@gmail.com>.
May I ask about wicketstuff-jquery's future?
-- Tony
On Wed, Jul 22, 2009 at 3:09 AM, Stefan Lindner<li...@visionet.de> wrote:
> Yes! Fixed. Now it's http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.7/WicketJQueryDemo.war
>
>
> -----Ursprüngliche Nachricht-----
> Von: satar [mailto:starlton@gmail.com]
> Gesendet: Dienstag, 21. Juli 2009 20:27
> An: users@wicket.apache.org
> Betreff: Re: jWicket -- jQuery with Wicket integration
>
>
> Just an FYI, the link to the WicketJQueryDemo.war on
> "http://subversion.visionet.de/project/WicketJQuery/wiki" is broke. I think
> it should be:
>
> http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.6/WicketJQueryDemo.war
>
> instead its:
>
> http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3./WicketJQueryDemo.war
> --
> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24593132.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: jWicket -- jQuery with Wicket integration
Posted by Stefan Lindner <li...@visionet.de>.
Yes! Fixed. Now it's http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.7/WicketJQueryDemo.war
-----Ursprüngliche Nachricht-----
Von: satar [mailto:starlton@gmail.com]
Gesendet: Dienstag, 21. Juli 2009 20:27
An: users@wicket.apache.org
Betreff: Re: jWicket -- jQuery with Wicket integration
Just an FYI, the link to the WicketJQueryDemo.war on
"http://subversion.visionet.de/project/WicketJQuery/wiki" is broke. I think
it should be:
http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.6/WicketJQueryDemo.war
instead its:
http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3./WicketJQueryDemo.war
--
View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24593132.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by satar <st...@gmail.com>.
Just an FYI, the link to the WicketJQueryDemo.war on
"http://subversion.visionet.de/project/WicketJQuery/wiki" is broke. I think
it should be:
http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3.6/WicketJQueryDemo.war
instead its:
http://subversion.visionet.de/project/WicketJQuery/browser/tags/0.3./WicketJQueryDemo.war
--
View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24593132.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Jason Wang <ja...@bulletin.net>.
Jeremy Thomerson wrote:
> You could write your own tag resolver - seems like it would be fairly
> easy. Obviously if the component you want is in a repeater or such,
> your tag will also have to be in the same "context" so to speak (same
> repeater, etc).
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Jul 22, 2009 at 8:00 PM, Jason Wang<ja...@bulletin.net> wrote:
>
>> I am thinking, if its possible to have a tag something looks like
>> <wicket:getIDFor="aComponentID"> which can output the Id wicket generates at
>> runtime
>> , people like me then do not need to include any javascript into wicket.
>> They can just leave
>> in the pages where they should belong to anyway.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Thats a great idea.
I love open source!
Thanks!
Jas
Re: jWicket -- jQuery with Wicket integration
Posted by Jeremy Thomerson <je...@wickettraining.com>.
You could write your own tag resolver - seems like it would be fairly
easy. Obviously if the component you want is in a repeater or such,
your tag will also have to be in the same "context" so to speak (same
repeater, etc).
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Jul 22, 2009 at 8:00 PM, Jason Wang<ja...@bulletin.net> wrote:
> I am thinking, if its possible to have a tag something looks like
> <wicket:getIDFor="aComponentID"> which can output the Id wicket generates at
> runtime
> , people like me then do not need to include any javascript into wicket.
> They can just leave
> in the pages where they should belong to anyway.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Jason Wang <ja...@bulletin.net>.
Jeremy Thomerson wrote:
> I didn't read your whole post - but if you just want to code your
> jquery stuff in jquery, you don't need any integration - why use
> WicketJQuery? Just add a header contributor that contributes jquery
> and then write your own JS.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Jul 22, 2009 at 3:44 PM, Tauren Mills<ta...@tauren.com> wrote:
>
>> Hi Richard,
>>
>> I actually tried out WiQuery before deciding it wasn't the right tool
>> for me. I can't remember the exact specifics of the issues I had with
>> it, and I only spent about a day with it. But I remember feeling like
>> I was being forced to use it whenever and wherever I wanted to add ANY
>> jQuery to my project.
>>
>> I can see how WiQuery would be good for a developer who doesn't want
>> to touch JS, and only code in Java. With WiQuery, I can add all the
>> functionality I need via the WiQuery API. I have nothing against the
>> project in this regard, it seems like a great solution for that
>> situation.
>>
>> But in my case, I want a wicket/jquery tool that is lightweight and
>> stays out of my way. I would rather code client-side only stuff just
>> in jQuery and not have anything necessary in my server code. The only
>> time I want wicket components to be aware of my jQuery code is if
>> there needs to be some client-server ajax communication. For instance,
>> drag/drop information, or sorting a list of item, etc.
>>
>> From my perspective, I could care less if wicket knows which accordion
>> panel is open in the browser, because *for my application*, that
>> doesn't matter. And I do realize there are *other applications* that
>> this would matter, for which an optional WiQuery accordion plugin
>> would be userful.
>>
>> And when I want to use another add-on jQuery plugin such as
>> superfish.js, I don't want to have to resort to WiQuery hacks or to
>> create my own WiQuery plugin to support it. I am constantly adding
>> little jQuery code here and there, and to have to make WiQuery plugins
>> for it all or to code it using the WiQuery API would be a pain that
>> I'm not willing to put up with.
>>
>> The following posting I made might give a little more insight into the
>> reason I stopped using WiQuery:
>> http://groups.google.com/group/wiquery/browse_thread/thread/190fc243777ea3ba/492092296e40fe10?lnk=gst&q=tauren#492092296e40fe10
>>
>> I had already found WicketJQuery at the time I tried out WiQuery.
>> WiQuery seemed further along and was easier to add into my
>> application, so I tried it first. But when it failed for me, I gave
>> WicketJQuery a try. At the moment, WicketJQuery (now jWicket)
>> certainly isn't perfect either, but it is closer to meeting my needs.
>> So I offered my help to Stefan to get it mavenized and moved to
>> WicketStuff. We renamed it to jWicket during this transition. This
>> new location will make it more accessible and easier to use for other
>> developers.
>>
>> Of course, I have nothing against joining forces, but I also needed
>> something to solve a problem, and I needed it now. WiQuery wasn't
>> doing it for me, and jWicket was. I also want a light weight tool, and
>> I felt like WiQuery was overkill for my needs. If there is a way to
>> join forces so that one tool can satisfy everyone without becoming
>> some big bloated thing, then I'm all for it!
>>
>> Bottom line is I just want to be able to easily add jQuery code to the
>> client side whenever and wherever I want without having to deal with
>> server side code -- except for when I need client/server communication
>> of jQuery events. Maybe I'm not normal in this regard, but the
>> WiQuery API just doesn't do it for me. I'd rather code the client side
>> in JS/jQuery and keep it out of my java code.
>>
>> Sorry for being long winded. Again, I have nothing against WiQuery,
>> and was quite impressed by it. But it just didn't seem like the right
>> tool for my needs. I'm certainly open to ideas on how to integrate the
>> projects, but from what I can tell, they really have different
>> visions.
>>
>> Tauren
>>
>>
>> On Wed, Jul 22, 2009 at 11:15 AM,
>> richardwilko<ri...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> What are the advantages of jWicket over other Wicket jQuery projects
>>> (specifically wiQuery)?
>>>
>>> It would be nice if we could all work together on a single project. wiQuery
>>> has already pooled the development resources of two other such projects.
>>>
>>> wiQuery has Wicket behaviours for the core jQuery events / actions and
>>> jQuery UI components. It also has a nice plugin mechanism for adding other
>>> jQuery widgets / behaviours and it is under active development.
>>>
>>> At jWeekend we have also just designed, developed and are testing a server
>>> side state mechanism for wiQuery components.
>>>
>>> Regards - Richard
>>> jWeekend
>>> OO, Wicket, Java Technologies - Training and Consultancy
>>> http://jWeekend.com
>>>
>>>
>>>
>>> Lionel Armanet wrote:
>>>
>>>> Hi,
>>>>
>>>> Just to talk, there's another jQuery-Wicket integration project called
>>>> "WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
>>>> (http://www.jweekend.com/dev/LWUGReg/). Did you look at this project too ?
>>>>
>>>> Lionel
>>>>
>>>>
>>>> tauren wrote:
>>>>
>>>>> jWicket has now been released as a wicketstuff project. jWicket is an
>>>>> integration of Wicket and jQuery that was previously called
>>>>> WicketJQuery (by Stefan Lindner). I realize there are already a few
>>>>> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
>>>>> implementation has some advantages over the others.
>>>>>
>>>>> Stefan and I discussed how to best move the WicketJQuery project
>>>>> forward and decided it was best if it became a standard maven project
>>>>> to make it easy for others to use. We decided to host it at
>>>>> wicketstuff so that it would be available via a maven repository. We
>>>>> also decided to rename it since there were already wicketstuff
>>>>> projects with very similar names. So it will now be known as
>>>>> "jWicket".
>>>>>
>>>>> At this point, the code committed to WicketStuff is essentially the
>>>>> same codebase available on the original WicketJQuery SVN server. I
>>>>> have refactored it with the org.wicketstuff.jwicket namespace and have
>>>>> structured the project in a standard maven manner. I also split the
>>>>> project into jwicket-parent, jwicket, and jwicket-examples. The demo
>>>>> app is now separate from jwicket itself so that it doesn't need to be
>>>>> imported into projects.
>>>>>
>>>>> The original WIcketJQuery project developed by Stefan Lindner can be
>>>>> found at:
>>>>> http://subversion.visionet.de/project/WicketJQuery/wiki
>>>>>
>>>>> Tauren
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>> -----
>>> http://richard-wilkinson.co.uk My blog: http://richard-wilkinson.co.uk
>>> --
>>> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24611730.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Totally agree. I actually have a use case which suits this approach
perfectly.
Our company hired some cheap designers from another country. The pages they
produced are full of hand written javascripts and jQuery/Prototye libs.
The best thing
for me to do is just leave them there. Only add them as resources when
there are clashes
,for example, if one javascript uses component id to do its magic and
the id is produced
at run time by wicket.
I am thinking, if its possible to have a tag something looks like
<wicket:getIDFor="aComponentID"> which can output the Id wicket
generates at runtime
, people like me then do not need to include any javascript into wicket.
They can just leave
in the pages where they should belong to anyway.
Thanks,
Jas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Jeremy Thomerson <je...@wickettraining.com>.
I didn't read your whole post - but if you just want to code your
jquery stuff in jquery, you don't need any integration - why use
WicketJQuery? Just add a header contributor that contributes jquery
and then write your own JS.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Jul 22, 2009 at 3:44 PM, Tauren Mills<ta...@tauren.com> wrote:
> Hi Richard,
>
> I actually tried out WiQuery before deciding it wasn't the right tool
> for me. I can't remember the exact specifics of the issues I had with
> it, and I only spent about a day with it. But I remember feeling like
> I was being forced to use it whenever and wherever I wanted to add ANY
> jQuery to my project.
>
> I can see how WiQuery would be good for a developer who doesn't want
> to touch JS, and only code in Java. With WiQuery, I can add all the
> functionality I need via the WiQuery API. I have nothing against the
> project in this regard, it seems like a great solution for that
> situation.
>
> But in my case, I want a wicket/jquery tool that is lightweight and
> stays out of my way. I would rather code client-side only stuff just
> in jQuery and not have anything necessary in my server code. The only
> time I want wicket components to be aware of my jQuery code is if
> there needs to be some client-server ajax communication. For instance,
> drag/drop information, or sorting a list of item, etc.
>
> From my perspective, I could care less if wicket knows which accordion
> panel is open in the browser, because *for my application*, that
> doesn't matter. And I do realize there are *other applications* that
> this would matter, for which an optional WiQuery accordion plugin
> would be userful.
>
> And when I want to use another add-on jQuery plugin such as
> superfish.js, I don't want to have to resort to WiQuery hacks or to
> create my own WiQuery plugin to support it. I am constantly adding
> little jQuery code here and there, and to have to make WiQuery plugins
> for it all or to code it using the WiQuery API would be a pain that
> I'm not willing to put up with.
>
> The following posting I made might give a little more insight into the
> reason I stopped using WiQuery:
> http://groups.google.com/group/wiquery/browse_thread/thread/190fc243777ea3ba/492092296e40fe10?lnk=gst&q=tauren#492092296e40fe10
>
> I had already found WicketJQuery at the time I tried out WiQuery.
> WiQuery seemed further along and was easier to add into my
> application, so I tried it first. But when it failed for me, I gave
> WicketJQuery a try. At the moment, WicketJQuery (now jWicket)
> certainly isn't perfect either, but it is closer to meeting my needs.
> So I offered my help to Stefan to get it mavenized and moved to
> WicketStuff. We renamed it to jWicket during this transition. This
> new location will make it more accessible and easier to use for other
> developers.
>
> Of course, I have nothing against joining forces, but I also needed
> something to solve a problem, and I needed it now. WiQuery wasn't
> doing it for me, and jWicket was. I also want a light weight tool, and
> I felt like WiQuery was overkill for my needs. If there is a way to
> join forces so that one tool can satisfy everyone without becoming
> some big bloated thing, then I'm all for it!
>
> Bottom line is I just want to be able to easily add jQuery code to the
> client side whenever and wherever I want without having to deal with
> server side code -- except for when I need client/server communication
> of jQuery events. Maybe I'm not normal in this regard, but the
> WiQuery API just doesn't do it for me. I'd rather code the client side
> in JS/jQuery and keep it out of my java code.
>
> Sorry for being long winded. Again, I have nothing against WiQuery,
> and was quite impressed by it. But it just didn't seem like the right
> tool for my needs. I'm certainly open to ideas on how to integrate the
> projects, but from what I can tell, they really have different
> visions.
>
> Tauren
>
>
> On Wed, Jul 22, 2009 at 11:15 AM,
> richardwilko<ri...@gmail.com> wrote:
>>
>> Hi,
>>
>> What are the advantages of jWicket over other Wicket jQuery projects
>> (specifically wiQuery)?
>>
>> It would be nice if we could all work together on a single project. wiQuery
>> has already pooled the development resources of two other such projects.
>>
>> wiQuery has Wicket behaviours for the core jQuery events / actions and
>> jQuery UI components. It also has a nice plugin mechanism for adding other
>> jQuery widgets / behaviours and it is under active development.
>>
>> At jWeekend we have also just designed, developed and are testing a server
>> side state mechanism for wiQuery components.
>>
>> Regards - Richard
>> jWeekend
>> OO, Wicket, Java Technologies - Training and Consultancy
>> http://jWeekend.com
>>
>>
>>
>> Lionel Armanet wrote:
>>>
>>> Hi,
>>>
>>> Just to talk, there's another jQuery-Wicket integration project called
>>> "WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
>>> (http://www.jweekend.com/dev/LWUGReg/). Did you look at this project too ?
>>>
>>> Lionel
>>>
>>>
>>> tauren wrote:
>>>>
>>>> jWicket has now been released as a wicketstuff project. jWicket is an
>>>> integration of Wicket and jQuery that was previously called
>>>> WicketJQuery (by Stefan Lindner). I realize there are already a few
>>>> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
>>>> implementation has some advantages over the others.
>>>>
>>>> Stefan and I discussed how to best move the WicketJQuery project
>>>> forward and decided it was best if it became a standard maven project
>>>> to make it easy for others to use. We decided to host it at
>>>> wicketstuff so that it would be available via a maven repository. We
>>>> also decided to rename it since there were already wicketstuff
>>>> projects with very similar names. So it will now be known as
>>>> "jWicket".
>>>>
>>>> At this point, the code committed to WicketStuff is essentially the
>>>> same codebase available on the original WicketJQuery SVN server. I
>>>> have refactored it with the org.wicketstuff.jwicket namespace and have
>>>> structured the project in a standard maven manner. I also split the
>>>> project into jwicket-parent, jwicket, and jwicket-examples. The demo
>>>> app is now separate from jwicket itself so that it doesn't need to be
>>>> imported into projects.
>>>>
>>>> The original WIcketJQuery project developed by Stefan Lindner can be
>>>> found at:
>>>> http://subversion.visionet.de/project/WicketJQuery/wiki
>>>>
>>>> Tauren
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>> -----
>> http://richard-wilkinson.co.uk My blog: http://richard-wilkinson.co.uk
>> --
>> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24611730.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Maven with Eclipse
Posted by Tauren Mills <yo...@gmail.com>.
Looks good to me. I'm looking forward to seeing your efforts!
I will hopefully be getting to adding DND to my project soon. Once I
do that, I'm planning to create a new example or update the existing
example to make it more attractive looking.
No offense, but when I first tried out the WicketJQuery example, it
kind of turned me off because it was quite messy and confusing. Once I
played with it some, it all made sense and I realized it would work
well for me. But initial impressions are important.
Tauren
On Thu, Jul 23, 2009 at 10:13 AM, Stefan Lindner<li...@visionet.de> wrote:
> Tauren,
>
> I think tooltips should be separated too. The layout will be
>
> jwicket-parent
> jwicket-core (both jwicket core and ui core)
> jwicket-plugins
> jwicket-ui-dragdrop
> jwicket-ui-resize
> jwicket-tooltip-variantA
> jwicket-tooltip-variantB
> jwicket-tooltip-variantC
> jwicket-examples
>
> Stefan
> -----Ursprüngliche Nachricht-----
> Von: Tauren Mills [mailto:yowzator@gmail.com]
> Gesendet: Donnerstag, 23. Juli 2009 18:30
> An: users@wicket.apache.org
> Betreff: Re: Maven with Eclipse
>
> Stefan,
>
> I'm using m2eclipse. But it can take a little getting used to. I also
> think it causes an occasional eclipse crash. However, I'm still glad
> to have it. Never tried the other one.
>
> Once m2eclipse installed, go to your SVN Repositories perspective,
> browse the wicketstuff-core project. Right click onto jwicket and
> select "Check out as Maven project". This will download all of the
> jwicket projects (jwicket-parent, jwicket, jwicket-examples), give
> each of them an eclipse project with maven support enabled, and
> activate subversion support. Pretty seamless to then start working
> and committing.
>
> I still find that I need to use the "mvn install" command from the
> command line sometimes to get things deployed to my local repo.
>
> How do you want to structure the sub-projects. Perhaps something like this?
>
> jwicket-parent
> jwicket
> jwicket-core
> jwicket-ui-core
> jwicket-plugins
> jwicket-ui-drag
> jwicket-ui-drop
> jwicket-ui-resize
> jwicket-tooltip
> jwicket-examples
>
> Or maybe:
>
> jwicket-parent
> jwicket-core (both jwicket core and ui core)
> jwicket-plugins
> jwicket-ui-dragdrop
> jwicket-ui-resize
> jwicket-tooltip
> jwicket-examples
>
> Should tooltips be separated into different projects too?
>
> I don't think we should go too far overboard on modularization.
>
> Tauren
>
>
> On Thu, Jul 23, 2009 at 3:54 AM, Stefan Lindner<li...@visionet.de> wrote:
>> Hi Tauren,
>>
>> wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
>> have commit acces and now I'm starting over with development.
>> Current steps:
>> 1. Add keypressed detection
>> 2. Separate the Project into small pieces
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
AW: Maven with Eclipse
Posted by Stefan Lindner <li...@visionet.de>.
Tauren,
I think tooltips should be separated too. The layout will be
jwicket-parent
jwicket-core (both jwicket core and ui core)
jwicket-plugins
jwicket-ui-dragdrop
jwicket-ui-resize
jwicket-tooltip-variantA
jwicket-tooltip-variantB
jwicket-tooltip-variantC
jwicket-examples
Stefan
-----Ursprüngliche Nachricht-----
Von: Tauren Mills [mailto:yowzator@gmail.com]
Gesendet: Donnerstag, 23. Juli 2009 18:30
An: users@wicket.apache.org
Betreff: Re: Maven with Eclipse
Stefan,
I'm using m2eclipse. But it can take a little getting used to. I also
think it causes an occasional eclipse crash. However, I'm still glad
to have it. Never tried the other one.
Once m2eclipse installed, go to your SVN Repositories perspective,
browse the wicketstuff-core project. Right click onto jwicket and
select "Check out as Maven project". This will download all of the
jwicket projects (jwicket-parent, jwicket, jwicket-examples), give
each of them an eclipse project with maven support enabled, and
activate subversion support. Pretty seamless to then start working
and committing.
I still find that I need to use the "mvn install" command from the
command line sometimes to get things deployed to my local repo.
How do you want to structure the sub-projects. Perhaps something like this?
jwicket-parent
jwicket
jwicket-core
jwicket-ui-core
jwicket-plugins
jwicket-ui-drag
jwicket-ui-drop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Or maybe:
jwicket-parent
jwicket-core (both jwicket core and ui core)
jwicket-plugins
jwicket-ui-dragdrop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Should tooltips be separated into different projects too?
I don't think we should go too far overboard on modularization.
Tauren
On Thu, Jul 23, 2009 at 3:54 AM, Stefan Lindner<li...@visionet.de> wrote:
> Hi Tauren,
>
> wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
> have commit acces and now I'm starting over with development.
> Current steps:
> 1. Add keypressed detection
> 2. Separate the Project into small pieces
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Maven with Eclipse
Posted by Tauren Mills <yo...@gmail.com>.
Stefan,
I'm using m2eclipse. But it can take a little getting used to. I also
think it causes an occasional eclipse crash. However, I'm still glad
to have it. Never tried the other one.
Once m2eclipse installed, go to your SVN Repositories perspective,
browse the wicketstuff-core project. Right click onto jwicket and
select "Check out as Maven project". This will download all of the
jwicket projects (jwicket-parent, jwicket, jwicket-examples), give
each of them an eclipse project with maven support enabled, and
activate subversion support. Pretty seamless to then start working
and committing.
I still find that I need to use the "mvn install" command from the
command line sometimes to get things deployed to my local repo.
How do you want to structure the sub-projects. Perhaps something like this?
jwicket-parent
jwicket
jwicket-core
jwicket-ui-core
jwicket-plugins
jwicket-ui-drag
jwicket-ui-drop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Or maybe:
jwicket-parent
jwicket-core (both jwicket core and ui core)
jwicket-plugins
jwicket-ui-dragdrop
jwicket-ui-resize
jwicket-tooltip
jwicket-examples
Should tooltips be separated into different projects too?
I don't think we should go too far overboard on modularization.
Tauren
On Thu, Jul 23, 2009 at 3:54 AM, Stefan Lindner<li...@visionet.de> wrote:
> Hi Tauren,
>
> wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
> have commit acces and now I'm starting over with development.
> Current steps:
> 1. Add keypressed detection
> 2. Separate the Project into small pieces
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Maven with Eclipse
Posted by Stefan Lindner <li...@visionet.de>.
Hi Tauren,
wich Eclipse plugin for maven do you prefer? m2eclipse or IAM (q4e)? I
have commit acces and now I'm starting over with development.
Current steps:
1. Add keypressed detection
2. Separate the Project into small pieces
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Jeremy Thomerson <je...@wickettraining.com>.
On Thu, Jul 23, 2009 at 1:24 AM, Reinhard
Nägele<re...@mgm-tp.com> wrote:
> To me wicketstuff presents itself as some inofficial playground with lots of
> badly documented things in it.
It is. Wicketstuff is open for anyone to join and basically do
whatever they want with it - so long as it has something to do with
Wicket. There are many abandoned projects and proofs of concept
projects there.
> However, wicketstuff-core (which is not even
> listed on the wicketstuff wiki (except for a migration guide)) seems to have
> a somewhat more official character. May the latter be taken as a
> production-ready supplement to Wicket?
Last year I took on the task of trying to improve the organization of
wicketstuff by moving all of the most qualified projects into
wicketstuff core. There's no guarantee of production-readiness. The
goal was to get it where they could all be built with numbered
releases to match Wicket. This is possible (I just built and deployed
1.4-rc7 last week). I will try to keep a numbered release matching
every Wicket release - but some of the projects under it may be more
production ready / quality than others.
> I'd appreciate it if some
> restructuring and clarification came along with the upcoming 1.4 release.
Volunteers are always welcome! It seems that most of the issues you
have are with wicketstuff (understandably) which should have no
reflection on Wicket's 1.4 release - it just so happens that some of
the same people are involved, but Wicket is the primary focus.
--
Jeremy Thomerson
http://www.wickettraining.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Reinhard Nägele <re...@mgm-tp.com>.
Given the fact that there is already wicket-jquery in wicketstoff-core,
I wonder how come it is simply possible to add another JQuery
integration to wicketstuff. What are the rules for adding stuff there?
Can committers just do whatever the like? Doesn't there have to be some
voting on the mailing list for things like that? If I was to add yet
another JQuery integration, could I just put it in there as well?
I'm currently doing a Wicket evaluation. Wicket may become one of the
standard frameworks of the company I work for. I really like what I've
seen so far, and working with Wicket can be really fun. But what looks
pretty messy to me is the way things are organized (documentation, wiki,
wicketstuff). To me wicketstuff presents itself as some inofficial
playground with lots of badly documented things in it. However,
wicketstuff-core (which is not even listed on the wicketstuff wiki
(except for a migration guide)) seems to have a somewhat more official
character. May the latter be taken as a production-ready supplement to
Wicket? I'd appreciate it if some restructuring and clarification came
along with the upcoming 1.4 release.
Thanks,
Reinhard
Tauren Mills schrieb:
> Hi Richard,
>
> I actually tried out WiQuery before deciding it wasn't the right tool
> for me. I can't remember the exact specifics of the issues I had with
> it, and I only spent about a day with it. But I remember feeling like
> I was being forced to use it whenever and wherever I wanted to add ANY
> jQuery to my project.
>
> I can see how WiQuery would be good for a developer who doesn't want
> to touch JS, and only code in Java. With WiQuery, I can add all the
> functionality I need via the WiQuery API. I have nothing against the
> project in this regard, it seems like a great solution for that
> situation.
>
> But in my case, I want a wicket/jquery tool that is lightweight and
> stays out of my way. I would rather code client-side only stuff just
> in jQuery and not have anything necessary in my server code. The only
> time I want wicket components to be aware of my jQuery code is if
> there needs to be some client-server ajax communication. For instance,
> drag/drop information, or sorting a list of item, etc.
>
> From my perspective, I could care less if wicket knows which accordion
> panel is open in the browser, because *for my application*, that
> doesn't matter. And I do realize there are *other applications* that
> this would matter, for which an optional WiQuery accordion plugin
> would be userful.
>
> And when I want to use another add-on jQuery plugin such as
> superfish.js, I don't want to have to resort to WiQuery hacks or to
> create my own WiQuery plugin to support it. I am constantly adding
> little jQuery code here and there, and to have to make WiQuery plugins
> for it all or to code it using the WiQuery API would be a pain that
> I'm not willing to put up with.
>
> The following posting I made might give a little more insight into the
> reason I stopped using WiQuery:
> http://groups.google.com/group/wiquery/browse_thread/thread/190fc243777ea3ba/492092296e40fe10?lnk=gst&q=tauren#492092296e40fe10
>
> I had already found WicketJQuery at the time I tried out WiQuery.
> WiQuery seemed further along and was easier to add into my
> application, so I tried it first. But when it failed for me, I gave
> WicketJQuery a try. At the moment, WicketJQuery (now jWicket)
> certainly isn't perfect either, but it is closer to meeting my needs.
> So I offered my help to Stefan to get it mavenized and moved to
> WicketStuff. We renamed it to jWicket during this transition. This
> new location will make it more accessible and easier to use for other
> developers.
>
> Of course, I have nothing against joining forces, but I also needed
> something to solve a problem, and I needed it now. WiQuery wasn't
> doing it for me, and jWicket was. I also want a light weight tool, and
> I felt like WiQuery was overkill for my needs. If there is a way to
> join forces so that one tool can satisfy everyone without becoming
> some big bloated thing, then I'm all for it!
>
> Bottom line is I just want to be able to easily add jQuery code to the
> client side whenever and wherever I want without having to deal with
> server side code -- except for when I need client/server communication
> of jQuery events. Maybe I'm not normal in this regard, but the
> WiQuery API just doesn't do it for me. I'd rather code the client side
> in JS/jQuery and keep it out of my java code.
>
> Sorry for being long winded. Again, I have nothing against WiQuery,
> and was quite impressed by it. But it just didn't seem like the right
> tool for my needs. I'm certainly open to ideas on how to integrate the
> projects, but from what I can tell, they really have different
> visions.
>
> Tauren
>
>
> On Wed, Jul 22, 2009 at 11:15 AM,
> richardwilko<ri...@gmail.com> wrote:
>
>> Hi,
>>
>> What are the advantages of jWicket over other Wicket jQuery projects
>> (specifically wiQuery)?
>>
>> It would be nice if we could all work together on a single project. wiQuery
>> has already pooled the development resources of two other such projects.
>>
>> wiQuery has Wicket behaviours for the core jQuery events / actions and
>> jQuery UI components. It also has a nice plugin mechanism for adding other
>> jQuery widgets / behaviours and it is under active development.
>>
>> At jWeekend we have also just designed, developed and are testing a server
>> side state mechanism for wiQuery components.
>>
>> Regards - Richard
>> jWeekend
>> OO, Wicket, Java Technologies - Training and Consultancy
>> http://jWeekend.com
>>
>>
>>
>> Lionel Armanet wrote:
>>
>>> Hi,
>>>
>>> Just to talk, there's another jQuery-Wicket integration project called
>>> "WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
>>> (http://www.jweekend.com/dev/LWUGReg/). Did you look at this project too ?
>>>
>>> Lionel
>>>
>>>
>>> tauren wrote:
>>>
>>>> jWicket has now been released as a wicketstuff project. jWicket is an
>>>> integration of Wicket and jQuery that was previously called
>>>> WicketJQuery (by Stefan Lindner). I realize there are already a few
>>>> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
>>>> implementation has some advantages over the others.
>>>>
>>>> Stefan and I discussed how to best move the WicketJQuery project
>>>> forward and decided it was best if it became a standard maven project
>>>> to make it easy for others to use. We decided to host it at
>>>> wicketstuff so that it would be available via a maven repository. We
>>>> also decided to rename it since there were already wicketstuff
>>>> projects with very similar names. So it will now be known as
>>>> "jWicket".
>>>>
>>>> At this point, the code committed to WicketStuff is essentially the
>>>> same codebase available on the original WicketJQuery SVN server. I
>>>> have refactored it with the org.wicketstuff.jwicket namespace and have
>>>> structured the project in a standard maven manner. I also split the
>>>> project into jwicket-parent, jwicket, and jwicket-examples. The demo
>>>> app is now separate from jwicket itself so that it doesn't need to be
>>>> imported into projects.
>>>>
>>>> The original WIcketJQuery project developed by Stefan Lindner can be
>>>> found at:
>>>> http://subversion.visionet.de/project/WicketJQuery/wiki
>>>>
>>>> Tauren
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>> -----
>> http://richard-wilkinson.co.uk My blog: http://richard-wilkinson.co.uk
>> --
>> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24611730.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Rodolfo Hansen <kr...@gmail.com>.
So, in less words: you find WiQuery more complex than WicketJQuery?
On my part, I believe WiQuery has alot of potential in keeping JQuery
scripting outside of the HTML files.
I would agree it could be simplified a bit though.
I found the JSStatement, and JQuery classes to great at brining jquery's
element selection mindset into wicket.
On Wed, Jul 22, 2009 at 4:44 PM, Tauren Mills <ta...@tauren.com> wrote:
> Hi Richard,
>
> I actually tried out WiQuery before deciding it wasn't the right tool
> for me. I can't remember the exact specifics of the issues I had with
> it, and I only spent about a day with it. But I remember feeling like
> I was being forced to use it whenever and wherever I wanted to add ANY
> jQuery to my project.
>
> I can see how WiQuery would be good for a developer who doesn't want
> to touch JS, and only code in Java. With WiQuery, I can add all the
> functionality I need via the WiQuery API. I have nothing against the
> project in this regard, it seems like a great solution for that
> situation.
>
> But in my case, I want a wicket/jquery tool that is lightweight and
> stays out of my way. I would rather code client-side only stuff just
> in jQuery and not have anything necessary in my server code. The only
> time I want wicket components to be aware of my jQuery code is if
> there needs to be some client-server ajax communication. For instance,
> drag/drop information, or sorting a list of item, etc.
>
> From my perspective, I could care less if wicket knows which accordion
> panel is open in the browser, because *for my application*, that
> doesn't matter. And I do realize there are *other applications* that
> this would matter, for which an optional WiQuery accordion plugin
> would be userful.
>
> And when I want to use another add-on jQuery plugin such as
> superfish.js, I don't want to have to resort to WiQuery hacks or to
> create my own WiQuery plugin to support it. I am constantly adding
> little jQuery code here and there, and to have to make WiQuery plugins
> for it all or to code it using the WiQuery API would be a pain that
> I'm not willing to put up with.
>
> The following posting I made might give a little more insight into the
> reason I stopped using WiQuery:
>
> http://groups.google.com/group/wiquery/browse_thread/thread/190fc243777ea3ba/492092296e40fe10?lnk=gst&q=tauren#492092296e40fe10
>
> I had already found WicketJQuery at the time I tried out WiQuery.
> WiQuery seemed further along and was easier to add into my
> application, so I tried it first. But when it failed for me, I gave
> WicketJQuery a try. At the moment, WicketJQuery (now jWicket)
> certainly isn't perfect either, but it is closer to meeting my needs.
> So I offered my help to Stefan to get it mavenized and moved to
> WicketStuff. We renamed it to jWicket during this transition. This
> new location will make it more accessible and easier to use for other
> developers.
>
> Of course, I have nothing against joining forces, but I also needed
> something to solve a problem, and I needed it now. WiQuery wasn't
> doing it for me, and jWicket was. I also want a light weight tool, and
> I felt like WiQuery was overkill for my needs. If there is a way to
> join forces so that one tool can satisfy everyone without becoming
> some big bloated thing, then I'm all for it!
>
> Bottom line is I just want to be able to easily add jQuery code to the
> client side whenever and wherever I want without having to deal with
> server side code -- except for when I need client/server communication
> of jQuery events. Maybe I'm not normal in this regard, but the
> WiQuery API just doesn't do it for me. I'd rather code the client side
> in JS/jQuery and keep it out of my java code.
>
> Sorry for being long winded. Again, I have nothing against WiQuery,
> and was quite impressed by it. But it just didn't seem like the right
> tool for my needs. I'm certainly open to ideas on how to integrate the
> projects, but from what I can tell, they really have different
> visions.
>
> Tauren
>
>
> On Wed, Jul 22, 2009 at 11:15 AM,
> richardwilko<ri...@gmail.com> wrote:
> >
> > Hi,
> >
> > What are the advantages of jWicket over other Wicket jQuery projects
> > (specifically wiQuery)?
> >
> > It would be nice if we could all work together on a single project.
> wiQuery
> > has already pooled the development resources of two other such projects.
> >
> > wiQuery has Wicket behaviours for the core jQuery events / actions and
> > jQuery UI components. It also has a nice plugin mechanism for adding
> other
> > jQuery widgets / behaviours and it is under active development.
> >
> > At jWeekend we have also just designed, developed and are testing a
> server
> > side state mechanism for wiQuery components.
> >
> > Regards - Richard
> > jWeekend
> > OO, Wicket, Java Technologies - Training and Consultancy
> > http://jWeekend.com
> >
> >
> >
> > Lionel Armanet wrote:
> >>
> >> Hi,
> >>
> >> Just to talk, there's another jQuery-Wicket integration project called
> >> "WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
> >> (http://www.jweekend.com/dev/LWUGReg/). Did you look at this project
> too ?
> >>
> >> Lionel
> >>
> >>
> >> tauren wrote:
> >>>
> >>> jWicket has now been released as a wicketstuff project. jWicket is an
> >>> integration of Wicket and jQuery that was previously called
> >>> WicketJQuery (by Stefan Lindner). I realize there are already a few
> >>> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
> >>> implementation has some advantages over the others.
> >>>
> >>> Stefan and I discussed how to best move the WicketJQuery project
> >>> forward and decided it was best if it became a standard maven project
> >>> to make it easy for others to use. We decided to host it at
> >>> wicketstuff so that it would be available via a maven repository. We
> >>> also decided to rename it since there were already wicketstuff
> >>> projects with very similar names. So it will now be known as
> >>> "jWicket".
> >>>
> >>> At this point, the code committed to WicketStuff is essentially the
> >>> same codebase available on the original WicketJQuery SVN server. I
> >>> have refactored it with the org.wicketstuff.jwicket namespace and have
> >>> structured the project in a standard maven manner. I also split the
> >>> project into jwicket-parent, jwicket, and jwicket-examples. The demo
> >>> app is now separate from jwicket itself so that it doesn't need to be
> >>> imported into projects.
> >>>
> >>> The original WIcketJQuery project developed by Stefan Lindner can be
> >>> found at:
> >>> http://subversion.visionet.de/project/WicketJQuery/wiki
> >>>
> >>> Tauren
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> > -----
> > http://richard-wilkinson.co.uk My blog: http://richard-wilkinson.co.uk
> > --
> > View this message in context:
> http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24611730.html
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Rodolfo Hansen
CTO, KindleIT Software Development
Email: rhansen@kindleit.net
Office: 1 (809) 732-5200
Mobile: 1 (809) 299-7332
Re: jWicket -- jQuery with Wicket integration
Posted by Tauren Mills <ta...@tauren.com>.
Hi Richard,
I actually tried out WiQuery before deciding it wasn't the right tool
for me. I can't remember the exact specifics of the issues I had with
it, and I only spent about a day with it. But I remember feeling like
I was being forced to use it whenever and wherever I wanted to add ANY
jQuery to my project.
I can see how WiQuery would be good for a developer who doesn't want
to touch JS, and only code in Java. With WiQuery, I can add all the
functionality I need via the WiQuery API. I have nothing against the
project in this regard, it seems like a great solution for that
situation.
But in my case, I want a wicket/jquery tool that is lightweight and
stays out of my way. I would rather code client-side only stuff just
in jQuery and not have anything necessary in my server code. The only
time I want wicket components to be aware of my jQuery code is if
there needs to be some client-server ajax communication. For instance,
drag/drop information, or sorting a list of item, etc.
>From my perspective, I could care less if wicket knows which accordion
panel is open in the browser, because *for my application*, that
doesn't matter. And I do realize there are *other applications* that
this would matter, for which an optional WiQuery accordion plugin
would be userful.
And when I want to use another add-on jQuery plugin such as
superfish.js, I don't want to have to resort to WiQuery hacks or to
create my own WiQuery plugin to support it. I am constantly adding
little jQuery code here and there, and to have to make WiQuery plugins
for it all or to code it using the WiQuery API would be a pain that
I'm not willing to put up with.
The following posting I made might give a little more insight into the
reason I stopped using WiQuery:
http://groups.google.com/group/wiquery/browse_thread/thread/190fc243777ea3ba/492092296e40fe10?lnk=gst&q=tauren#492092296e40fe10
I had already found WicketJQuery at the time I tried out WiQuery.
WiQuery seemed further along and was easier to add into my
application, so I tried it first. But when it failed for me, I gave
WicketJQuery a try. At the moment, WicketJQuery (now jWicket)
certainly isn't perfect either, but it is closer to meeting my needs.
So I offered my help to Stefan to get it mavenized and moved to
WicketStuff. We renamed it to jWicket during this transition. This
new location will make it more accessible and easier to use for other
developers.
Of course, I have nothing against joining forces, but I also needed
something to solve a problem, and I needed it now. WiQuery wasn't
doing it for me, and jWicket was. I also want a light weight tool, and
I felt like WiQuery was overkill for my needs. If there is a way to
join forces so that one tool can satisfy everyone without becoming
some big bloated thing, then I'm all for it!
Bottom line is I just want to be able to easily add jQuery code to the
client side whenever and wherever I want without having to deal with
server side code -- except for when I need client/server communication
of jQuery events. Maybe I'm not normal in this regard, but the
WiQuery API just doesn't do it for me. I'd rather code the client side
in JS/jQuery and keep it out of my java code.
Sorry for being long winded. Again, I have nothing against WiQuery,
and was quite impressed by it. But it just didn't seem like the right
tool for my needs. I'm certainly open to ideas on how to integrate the
projects, but from what I can tell, they really have different
visions.
Tauren
On Wed, Jul 22, 2009 at 11:15 AM,
richardwilko<ri...@gmail.com> wrote:
>
> Hi,
>
> What are the advantages of jWicket over other Wicket jQuery projects
> (specifically wiQuery)?
>
> It would be nice if we could all work together on a single project. wiQuery
> has already pooled the development resources of two other such projects.
>
> wiQuery has Wicket behaviours for the core jQuery events / actions and
> jQuery UI components. It also has a nice plugin mechanism for adding other
> jQuery widgets / behaviours and it is under active development.
>
> At jWeekend we have also just designed, developed and are testing a server
> side state mechanism for wiQuery components.
>
> Regards - Richard
> jWeekend
> OO, Wicket, Java Technologies - Training and Consultancy
> http://jWeekend.com
>
>
>
> Lionel Armanet wrote:
>>
>> Hi,
>>
>> Just to talk, there's another jQuery-Wicket integration project called
>> "WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
>> (http://www.jweekend.com/dev/LWUGReg/). Did you look at this project too ?
>>
>> Lionel
>>
>>
>> tauren wrote:
>>>
>>> jWicket has now been released as a wicketstuff project. jWicket is an
>>> integration of Wicket and jQuery that was previously called
>>> WicketJQuery (by Stefan Lindner). I realize there are already a few
>>> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
>>> implementation has some advantages over the others.
>>>
>>> Stefan and I discussed how to best move the WicketJQuery project
>>> forward and decided it was best if it became a standard maven project
>>> to make it easy for others to use. We decided to host it at
>>> wicketstuff so that it would be available via a maven repository. We
>>> also decided to rename it since there were already wicketstuff
>>> projects with very similar names. So it will now be known as
>>> "jWicket".
>>>
>>> At this point, the code committed to WicketStuff is essentially the
>>> same codebase available on the original WicketJQuery SVN server. I
>>> have refactored it with the org.wicketstuff.jwicket namespace and have
>>> structured the project in a standard maven manner. I also split the
>>> project into jwicket-parent, jwicket, and jwicket-examples. The demo
>>> app is now separate from jwicket itself so that it doesn't need to be
>>> imported into projects.
>>>
>>> The original WIcketJQuery project developed by Stefan Lindner can be
>>> found at:
>>> http://subversion.visionet.de/project/WicketJQuery/wiki
>>>
>>> Tauren
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>
>>
>
>
> -----
> http://richard-wilkinson.co.uk My blog: http://richard-wilkinson.co.uk
> --
> View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24611730.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by richardwilko <ri...@gmail.com>.
Hi,
What are the advantages of jWicket over other Wicket jQuery projects
(specifically wiQuery)?
It would be nice if we could all work together on a single project. wiQuery
has already pooled the development resources of two other such projects.
wiQuery has Wicket behaviours for the core jQuery events / actions and
jQuery UI components. It also has a nice plugin mechanism for adding other
jQuery widgets / behaviours and it is under active development.
At jWeekend we have also just designed, developed and are testing a server
side state mechanism for wiQuery components.
Regards - Richard
jWeekend
OO, Wicket, Java Technologies - Training and Consultancy
http://jWeekend.com
Lionel Armanet wrote:
>
> Hi,
>
> Just to talk, there's another jQuery-Wicket integration project called
> "WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
> (http://www.jweekend.com/dev/LWUGReg/). Did you look at this project too ?
>
> Lionel
>
>
> tauren wrote:
>>
>> jWicket has now been released as a wicketstuff project. jWicket is an
>> integration of Wicket and jQuery that was previously called
>> WicketJQuery (by Stefan Lindner). I realize there are already a few
>> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
>> implementation has some advantages over the others.
>>
>> Stefan and I discussed how to best move the WicketJQuery project
>> forward and decided it was best if it became a standard maven project
>> to make it easy for others to use. We decided to host it at
>> wicketstuff so that it would be available via a maven repository. We
>> also decided to rename it since there were already wicketstuff
>> projects with very similar names. So it will now be known as
>> "jWicket".
>>
>> At this point, the code committed to WicketStuff is essentially the
>> same codebase available on the original WicketJQuery SVN server. I
>> have refactored it with the org.wicketstuff.jwicket namespace and have
>> structured the project in a standard maven manner. I also split the
>> project into jwicket-parent, jwicket, and jwicket-examples. The demo
>> app is now separate from jwicket itself so that it doesn't need to be
>> imported into projects.
>>
>> The original WIcketJQuery project developed by Stefan Lindner can be
>> found at:
>> http://subversion.visionet.de/project/WicketJQuery/wiki
>>
>> Tauren
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
>
-----
http://richard-wilkinson.co.uk My blog: http://richard-wilkinson.co.uk
--
View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24611730.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: jWicket -- jQuery with Wicket integration
Posted by Lionel Armanet <li...@gmail.com>.
Hi,
Just to talk, there's another jQuery-Wicket integration project called
"WiQuery" (http://code.google.com/p/wiquery/) and supported by jWeekend
(http://www.jweekend.com/dev/LWUGReg/). Did you look at this project too ?
Lionel
tauren wrote:
>
> jWicket has now been released as a wicketstuff project. jWicket is an
> integration of Wicket and jQuery that was previously called
> WicketJQuery (by Stefan Lindner). I realize there are already a few
> Wicket/jQuery integrations, but I think that Stefan's WicketJQuery
> implementation has some advantages over the others.
>
> Stefan and I discussed how to best move the WicketJQuery project
> forward and decided it was best if it became a standard maven project
> to make it easy for others to use. We decided to host it at
> wicketstuff so that it would be available via a maven repository. We
> also decided to rename it since there were already wicketstuff
> projects with very similar names. So it will now be known as
> "jWicket".
>
> At this point, the code committed to WicketStuff is essentially the
> same codebase available on the original WicketJQuery SVN server. I
> have refactored it with the org.wicketstuff.jwicket namespace and have
> structured the project in a standard maven manner. I also split the
> project into jwicket-parent, jwicket, and jwicket-examples. The demo
> app is now separate from jwicket itself so that it doesn't need to be
> imported into projects.
>
> The original WIcketJQuery project developed by Stefan Lindner can be found
> at:
> http://subversion.visionet.de/project/WicketJQuery/wiki
>
> Tauren
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/jWicket----jQuery-with-Wicket-integration-tp24584280p24609833.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org