You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by dtoffe <dt...@yahoo.com.ar> on 2007/10/12 23:30:51 UTC
Wicket Web Beans with Wicket 1.3b4 ?
Hi !
Is Wicket Web Beans from SVN (rev 136 as of now) useable with Wicket 1.3b4 ?
Should I stick to last (1.0 rc1) release with 1.2.6 ?
Cheers,
Daniel
--
View this message in context: http://www.nabble.com/Wicket-Web-Beans-with-Wicket-1.3b4---tf4616136.html#a13183356
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: Wicket AJAX vs Echo AJAX
Posted by Igor Vaynberg <ig...@gmail.com>.
wicket's ajax requirements are somewhat unique, thus we have our own ajax
implementation.
there is a dojo integration in wicket-stuff if you want to use dojo
components, but beware it is not supported by the wicket core team.
-igor
On 10/12/07, Chris Colman <ch...@stepaheadsoftware.com> wrote:
>
> > Short answer : You do not have to write a single line of
> javascriptcode
> > to use wicket ajax behaviors. This is already done for you.
>
> Great!
>
> > Regarding browser differences, I belive they are handled(by
> > wicket-ajax). AFAIK in beta 4 even safari works:)
>
> Another question: How does Dojo fit into Wicket? Is it an optional extra
> or does Wicket 'employ' it to implement AJAX?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
RE: Wicket AJAX vs Echo AJAX
Posted by Chris Colman <ch...@stepaheadsoftware.com>.
> Short answer : You do not have to write a single line of
javascriptcode
> to use wicket ajax behaviors. This is already done for you.
Great!
> Regarding browser differences, I belive they are handled(by
> wicket-ajax). AFAIK in beta 4 even safari works:)
Another question: How does Dojo fit into Wicket? Is it an optional extra
or does Wicket 'employ' it to implement AJAX?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket AJAX vs Echo AJAX
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Short answer : You do not have to write a single line of javascriptcode
to use wicket ajax behaviors. This is already done for you.
Regarding browser differences, I belive they are handled(by
wicket-ajax). AFAIK in beta 4 even safari works:)
Chris Colman wrote:
> To date we've built all of our static pages in Wicket and all dynamic
> pages/user input forms etc., in Echo because it provides a pure Java (no
> need to write any JavaScript) solution to generating AJAX powered pages.
>
> The problem is when users switch from Echo pages back to Wicket pages
> using the browser's back button (Echo only ever has one URL for all
> pages so bookmarkable pages don't exist). They kind of do a "hyperspace"
> jump that's not very user friendly. The 'back operation' does not return
> them to the previous element in the path of their navigation through the
> Echo based portion of the application but instead returns to them to the
> last non echo 'page' that they were on. Echo is very cool and very fast
> to develop in but this one issue is causing us some grief.
>
> I'm contemplating implementing the dynamic pages in Wicket instead of
> Echo but have a few questions:
>
> 1. Will I have to write any Javascript to implement AJAX powered pages
> (I'm a Java programmer of 12 years and don't want to get down an dirty
> with the browser/JavaScript ever again - tried that in about 2002 and it
> was very painful).
>
> 2. Can AJAX powered pages be generated by Wicket in such as way that
> browser differences are accommodated automatically by the Wicket
> framework - ie., transparent to the developer?
>
> These two issues are why I chose Echo (all AJAX is done transparently to
> the developer) in the first place but if Wicket covers these issues
> satisfactorily then I could move the app to 100% Wicket.
>
> ---------------------------------------------------------------------
> 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
Wicket AJAX vs Echo AJAX
Posted by Chris Colman <ch...@stepaheadsoftware.com>.
To date we've built all of our static pages in Wicket and all dynamic
pages/user input forms etc., in Echo because it provides a pure Java (no
need to write any JavaScript) solution to generating AJAX powered pages.
The problem is when users switch from Echo pages back to Wicket pages
using the browser's back button (Echo only ever has one URL for all
pages so bookmarkable pages don't exist). They kind of do a "hyperspace"
jump that's not very user friendly. The 'back operation' does not return
them to the previous element in the path of their navigation through the
Echo based portion of the application but instead returns to them to the
last non echo 'page' that they were on. Echo is very cool and very fast
to develop in but this one issue is causing us some grief.
I'm contemplating implementing the dynamic pages in Wicket instead of
Echo but have a few questions:
1. Will I have to write any Javascript to implement AJAX powered pages
(I'm a Java programmer of 12 years and don't want to get down an dirty
with the browser/JavaScript ever again - tried that in about 2002 and it
was very painful).
2. Can AJAX powered pages be generated by Wicket in such as way that
browser differences are accommodated automatically by the Wicket
framework - ie., transparent to the developer?
These two issues are why I chose Echo (all AJAX is done transparently to
the developer) in the first place but if Wicket covers these issues
satisfactorily then I could move the app to 100% Wicket.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket Web Beans with Wicket 1.3b4 ?
Posted by Dan Syrstad <ds...@ener-j.org>.
Hi Daniel,
If you check out the latest from the SVN branch branches/wicket-1.3-port, it
builds with maven/1.3.0-beta4. The trunk is still for Wicket 1.2.6. The
head of both the trunk and 1.3 branch are techinically
wicketwebbeans-1.0-rc2SNAPSHOT.
-Dan
On 10/12/07, dtoffe <dt...@yahoo.com.ar> wrote:
>
>
> Hi !
>
> Is Wicket Web Beans from SVN (rev 136 as of now) useable with Wicket 1.3b4?
> Should I stick to last (1.0 rc1) release with 1.2.6 ?
>
> Cheers,
>
> Daniel
>
> --
> View this message in context:
> http://www.nabble.com/Wicket-Web-Beans-with-Wicket-1.3b4---tf4616136.html#a13183356
> 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
>
>