Re: [Wicket-user] Wicket arguments for big slow companies (Was:links about wicket scalability...)

2006-09-26 Thread Nino Wael
Hehe, I espcially agree to the unlearning effect. Had a hard time getting used 
to the fact that wicket controls what are selected in a component...


Regards Nino

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eelco Hillenius
Sent: 26. september 2006 13:12
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Wicket arguments for big slow companies (Was:links 
about wicket scalability...)

 * Very small learning curve.
   Comment: Agreed. But I still think you need at least one more
   experienced Wicket developers for more advanced things like
   manipulating html generated by other components. Of course, books
   like 'Pro Wicket' help a lot but are not for every programmer.

I'm not even sure whether I agree :) Wicket can be hard for people
that are not comfortable with OO programming. If all you've learned so
far is coding PHP, JSP or RoR will be much easier to pick up. Also,
for people who have done a bunch of projects with web MVC frameworks
like Struts, there is what Howard Lewis Ship (Tapestry) calls the
'unlearning effect'.

Wicket probably *is* very easy to learn for programmers that are
experienced OO programmers, did a lot of Swing/ SWT/ ... desktop
applications, or weren't doing too much UI before. Also, I think
Wicket is the best of all web frameworks to learn for programmers who
are now learning the trade. It's just Java and just HTML instead of
yet another DSL, and imo there's not much that will encourage bad
programming practices.

 I also thought about: * Good support for modern web pages (AJAX), while
 being compatible with older browsers. But this one is I am afraid not
 good enough. For example FireFox 1.0 is not supported.

This is not inherently true for the framework though. We provide a
convenience implementation for Ajax, which can be used with other
implementations (Dojo, scriptaculous, your own, ...). I think a strong
feature of Wicket is that you can create you custom components,
including any Ajax support you want for them, without too much
trouble.

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Wicket arguments for big slow companies (Was:links about wicket scalability...)

2006-09-26 Thread Eelco Hillenius
I prefer saying 'Just Java', which means the same (kind of), but
sounds a bit nicer and has a broader application :)

Eelco


On 9/26/06, Ryan Sonnek [EMAIL PROTECTED] wrote:
 Don't forget my *favorite* selling point of wicket...

 * NO XML!!!

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Wicket arguments for big slow companies (Was:links about wicket scalability...)

2006-09-26 Thread Marc-Andre Houle
I never liked HTML, PHP and everything related to GUI programming. Finding a Framework like Wicket that let me do all my trick in Java and never have to tweak html and CSS make me so happy, you can't understand. And the learning curve was not that hard. I begin Wicket in my new Job and after 1 week, I was at creating new Panel and delivering new stuff.
MarcOn 9/26/06, Nino Wael [EMAIL PROTECTED] wrote:
Hehe, I espcially agree to the unlearning effect. Had a hard time getting used to the fact that wicket controls what are selected in a component...Regards Nino-Original Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Eelco HilleniusSent: 26. september 2006 13:12
To: wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] Wicket arguments for big slow companies (Was:links about wicket scalability...) * Very small learning curve.
 Comment: Agreed. But I still think you need at least one more experienced Wicket developers for more advanced things like manipulating html generated by other components. Of course, books
 like 'Pro Wicket' help a lot but are not for every programmer.I'm not even sure whether I agree :) Wicket can be hard for peoplethat are not comfortable with OO programming. If all you've learned so
far is coding PHP, JSP or RoR will be much easier to pick up. Also,for people who have done a bunch of projects with web MVC frameworkslike Struts, there is what Howard Lewis Ship (Tapestry) calls the'unlearning effect'.
Wicket probably *is* very easy to learn for programmers that areexperienced OO programmers, did a lot of Swing/ SWT/ ... desktopapplications, or weren't doing too much UI before. Also, I thinkWicket is the best of all web frameworks to learn for programmers who
are now learning the trade. It's just Java and just HTML instead ofyet another DSL, and imo there's not much that will encourage badprogramming practices. I also thought about: * Good support for modern web pages (AJAX), while
 being compatible with older browsers. But this one is I am afraid not good enough. For example FireFox 1.0 is not supported.This is not inherently true for the framework though. We provide aconvenience implementation for Ajax, which can be used with other
implementations (Dojo, scriptaculous, your own, ...). I think a strongfeature of Wicket is that you can create you custom components,including any Ajax support you want for them, without too muchtrouble.
Eelco-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cashhttp://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net
's Techsay panel and you'll get the chance to share youropinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___Wicket-user mailing listWicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Wicket arguments for big slow companies (Was:links about wicket scalability...)

2006-09-26 Thread Ryan Sonnek
Don't forget my *favorite* selling point of wicket...* NO XML!!!On 9/26/06, Marc-Andre Houle [EMAIL PROTECTED]
 wrote:I never liked HTML, PHP and everything related to GUI programming. Finding a Framework like Wicket that let me do all my trick in Java and never have to tweak html and CSS make me so happy, you can't understand. And the learning curve was not that hard. I begin Wicket in my new Job and after 1 week, I was at creating new Panel and delivering new stuff.
MarcOn 9/26/06, Nino Wael 
[EMAIL PROTECTED] wrote:
Hehe, I espcially agree to the unlearning effect. Had a hard time getting used to the fact that wicket controls what are selected in a component...Regards Nino-Original Message-From: 

[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] On Behalf Of Eelco HilleniusSent: 26. september 2006 13:12
To: wicket-user@lists.sourceforge.netSubject: Re: [Wicket-user] Wicket arguments for big slow companies (Was:links about wicket scalability...)
 * Very small learning curve.
 Comment: Agreed. But I still think you need at least one more experienced Wicket developers for more advanced things like manipulating html generated by other components. Of course, books
 like 'Pro Wicket' help a lot but are not for every programmer.I'm not even sure whether I agree :) Wicket can be hard for peoplethat are not comfortable with OO programming. If all you've learned so
far is coding PHP, JSP or RoR will be much easier to pick up. Also,for people who have done a bunch of projects with web MVC frameworkslike Struts, there is what Howard Lewis Ship (Tapestry) calls the'unlearning effect'.
Wicket probably *is* very easy to learn for programmers that areexperienced OO programmers, did a lot of Swing/ SWT/ ... desktopapplications, or weren't doing too much UI before. Also, I thinkWicket is the best of all web frameworks to learn for programmers who
are now learning the trade. It's just Java and just HTML instead ofyet another DSL, and imo there's not much that will encourage badprogramming practices. I also thought about: * Good support for modern web pages (AJAX), while
 being compatible with older browsers. But this one is I am afraid not good enough. For example FireFox 1.0 is not supported.This is not inherently true for the framework though. We provide aconvenience implementation for Ajax, which can be used with other
implementations (Dojo, scriptaculous, your own, ...). I think a strongfeature of Wicket is that you can create you custom components,including any Ajax support you want for them, without too muchtrouble.

Eelco-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___Wicket-user mailing listWicket-user@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wicket-user-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net

's Techsay panel and you'll get the chance to share youropinions on IT  business topics through brief surveys -- and earn cash

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___Wicket-user mailing list
Wicket-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Wicket arguments for big slow companies(Was:links about wicket scalability...)

2006-09-26 Thread Che Schneider

+1 because this actually _is_ a very important point. 

// Che


 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf 
 Of Ryan Sonnek
 Sent: Tuesday, September 26, 2006 3:29 PM
 To: wicket-user@lists.sourceforge.net
 Subject: Re: [Wicket-user] Wicket arguments for big slow 
 companies(Was:links about wicket scalability...)
 
 Don't forget my *favorite* selling point of wicket...
 
 * NO XML!!!
 
 
 On 9/26/06, Marc-Andre Houle [EMAIL PROTECTED]  wrote:
 
   I never liked HTML, PHP and everything related to GUI 
 programming.  Finding a Framework like Wicket that let me do 
 all my trick in Java and never have to tweak html and CSS 
 make me so happy, you can't understand.  And the learning 
 curve was not that hard.  I begin Wicket in my new Job and 
 after 1 week, I was at creating new Panel and delivering new stuff. 
   
   Marc
   
   
   
   On 9/26/06, Nino Wael  [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED]  wrote:
 
   Hehe, I espcially agree to the unlearning 
 effect. Had a hard time getting used to the fact that wicket 
 controls what are selected in a component...
   
   
   Regards Nino
   
   -Original Message-
   From: [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED]  
 [mailto:[EMAIL PROTECTED] ] On Behalf 
 Of Eelco Hillenius
   Sent: 26. september 2006 13:12 
   To: wicket-user@lists.sourceforge.net
   Subject: Re: [Wicket-user] Wicket arguments for 
 big slow companies (Was:links about wicket scalability...) 
   
* Very small learning curve. 
  Comment: Agreed. But I still think you 
 need at least one more
  experienced Wicket developers for more 
 advanced things like
  manipulating html generated by other 
 components. Of course, books 
  like 'Pro Wicket' help a lot but are 
 not for every programmer.
   
   I'm not even sure whether I agree :) Wicket can 
 be hard for people
   that are not comfortable with OO programming. 
 If all you've learned so 
   far is coding PHP, JSP or RoR will be much 
 easier to pick up. Also,
   for people who have done a bunch of projects 
 with web MVC frameworks
   like Struts, there is what Howard Lewis Ship 
 (Tapestry) calls the
   'unlearning effect'. 
   
   Wicket probably *is* very easy to learn for 
 programmers that are
   experienced OO programmers, did a lot of Swing/ 
 SWT/ ... desktop
   applications, or weren't doing too much UI 
 before. Also, I think
   Wicket is the best of all web frameworks to 
 learn for programmers who 
   are now learning the trade. It's just Java and 
 just HTML instead of
   yet another DSL, and imo there's not much that 
 will encourage bad
   programming practices.
   
I also thought about: * Good support for 
 modern web pages (AJAX), while 
being compatible with older browsers. But 
 this one is I am afraid not
good enough. For example FireFox 1.0 is not supported.
   
   This is not inherently true for the framework 
 though. We provide a
   convenience implementation for Ajax, which can 
 be used with other 
   implementations (Dojo, scriptaculous, your own, 
 ...). I think a strong
   feature of Wicket is that you can create you 
 custom components,
   including any Ajax support you want for them, 
 without too much
   trouble.
   
   Eelco
   
   
 --
 ---
   Take Surveys. Earn Cash. Influence the Future of IT
   Join SourceForge.net's Techsay panel and you'll 
 get the chance to share your 
   opinions on IT  business topics through brief 
 surveys -- and earn cash
   
 http://www.techsay.com/default.php?page=join.phpp=sourceforge
 CID=DEVDEV 
 http://www.techsay.com/default.php?page=join.phpp=sourceforg
 eCID=DEVDEV 
   ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net 
   
 https://lists.sourceforge.net/lists/listinfo/wicket-user 
 https://lists.sourceforge.net/lists/listinfo/wicket-user 
   
   
   
 --
 ---
   Take Surveys. Earn Cash. Influence the Future of IT
   Join SourceForge.net 's Techsay panel and 
 you'll get the chance to share your
   opinions on IT  business