Re: Wicket roadmap

2015-03-16 Thread Martin Grigorov
On Sun, Mar 15, 2015 at 10:46 PM, Francois Meillet 
francois.meil...@gmail.com wrote:

 Thanks you all

 servlet 4.0 / yes it's too early

 monitoring / metrics / ok

 server-sent events / didn't see it / :-)

 http://bitstorm.github.io/wicket-site/ is superb
 May we add a why Wicket link in the header


Please file an issue at https://github.com/dashorst/wicket-site with your
ideas.



 I agree with Tobias's ideas on mobile


Agreed!




 François Meillet



Martin Grigorov
Freelancer, available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov





 Le 8 mars 2015 à 16:56, Andrea Del Bene an.delb...@gmail.com a écrit :

  The most up-to-date version of the site is the one from Martijn who is
 leading the development. I think there are few things left to do to
 complete this task. I've opened a PR to solve a couple of small layout
 issues in two pages. Apart from this there are some TODO in the
 documentation page to ' integrate media objects' for book pictures and
 videos, but honestly I don't know exactly what this is about. IMHO we
 should also add a new header link for 'community' pages like friends
 projects and WicketStuff.
 
 
  new web design for https://wicket.apache.org
 
  I hope this will be ready for Wicket 7.0.0 (
  https://github.com/dashorst/wicket-site,
  http://bitstorm.github.io/wicket-site/)
  @Martijn, @Andrea ?
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 




Re: Wicket roadmap

2015-03-15 Thread Francois Meillet
Thanks you all

servlet 4.0 / yes it's too early

monitoring / metrics / ok

server-sent events / didn't see it / :-) 

http://bitstorm.github.io/wicket-site/ is superb
May we add a why Wicket link in the header

I agree with Tobias's ideas on mobile


François Meillet





Le 8 mars 2015 à 16:56, Andrea Del Bene an.delb...@gmail.com a écrit :

 The most up-to-date version of the site is the one from Martijn who is 
 leading the development. I think there are few things left to do to complete 
 this task. I've opened a PR to solve a couple of small layout issues in two 
 pages. Apart from this there are some TODO in the documentation page to ' 
 integrate media objects' for book pictures and videos, but honestly I don't 
 know exactly what this is about. IMHO we should also add a new header link 
 for 'community' pages like friends projects and WicketStuff.
 
 
 new web design for https://wicket.apache.org
 
 I hope this will be ready for Wicket 7.0.0 (
 https://github.com/dashorst/wicket-site,
 http://bitstorm.github.io/wicket-site/)
 @Martijn, @Andrea ?
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 



Re: Wicket roadmap

2015-03-08 Thread Francois Meillet
Here are simple thoughts,

modularity
servlet 4.0 / http 2.0
monitoring
server-sent events

new web design for https://wicket.apache.org 
new wicket-examples
better highlighting of WicketStuff modules on https://wicket.apache.org 

Using an online survey tool could be useful

see https://java.net/downloads/javaee-spec/JavaEE8_Community_Survey_Results.pdf

François Meillet






Le 7 mars 2015 à 22:23, Martin Grigorov mgrigo...@apache.org a écrit :

 Hi,
 
 Once 7.0.0 is released I think we should create a branch for Wicket 8 and
 see what we could benefit of Java 8.
 Having less verbose Wicket would be great! But not on any price! Lambdas
 are both harder to debug and produce bigger stack, so we should decide
 carefully.
 Other things to consider:
 - whether to use Optional for AjaxFallback** components. I don't remember
 the exact reason why Igor's Optional didn't make it, but we may reevaluate
 - use the new DateTime APIs for wicket-datetime (new Converters, etc.)
 - ???
 
 We should also ask the community what they don't like in Wicket and what
 they would like to be added to make it better.
 
 Martin Grigorov
 Wicket Training and Consulting
 https://twitter.com/mtgrigorov
 
 On Sat, Mar 7, 2015 at 11:05 AM, Francois Meillet 
 francois.meil...@gmail.com wrote:
 
 Hi All,
 
 
 Is there any Wicket roadmap for the future (after version 7) ?
 
 What is your point of view about the Wicket's future  ?
 
 
 Thanks
 François Meillet
 
 
 
 
 
 
 



Re: Wicket roadmap

2015-03-08 Thread Martin Grigorov
Hi,

Thanks for sharing your ideas!

On Sun, Mar 8, 2015 at 10:00 AM, Francois Meillet 
francois.meil...@gmail.com wrote:

 Here are simple thoughts,

 modularity


what do you mean with that ?


 servlet 4.0 / http 2.0


I'm afraid it is too early for this.
We can make sure Wicket works fine in a container supporting those but it
is too early to require that.
Servlet 4.0 is still in design process. Apache Tomcat didn't started
implementing any features from it. I am not sure about the status in Jetty.
I know that Undertow (the web container for JBoss Wildfly) supports HTTP
2.0 but I haven't heard of any Servlet 4.0 features.
It will take us some time to release 8.0.0 but I think it will be too early
to require Servlet 4.0 even then.


 monitoring


I wanted to see how Wicket could provide some metrics (
https://dropwizard.github.io/metrics/3.1.0/)
what else do you have in mind ?


 server-sent events


https://github.com/wicketstuff/core/blob/master/jdk-1.7-parent/wicket-html5-parent/wicket-html5/src/main/java/org/wicketstuff/html5/eventsource/EventSourceResource.java
provides this for 2 or 3 years now
So far there were no bug reports for it. I guess no one uses it :-)



 new web design for https://wicket.apache.org


I hope this will be ready for Wicket 7.0.0 (
https://github.com/dashorst/wicket-site,
http://bitstorm.github.io/wicket-site/)
@Martijn, @Andrea ?



 new wicket-examples


I've done some work at
https://github.com/apache/wicket/tree/3435-use-bootstrap-for-examples but
it needs some love from someone with better CSS skills than me


 better highlighting of WicketStuff modules on https://wicket.apache.org


Andrea added some docs about some of the projects at
http://wicket.apache.org/guide/guide/wicketstuff.html
Ideas for improvements can be filed at
https://github.com/dashorst/wicket-site/issues




 Using an online survey tool could be useful


good idea!



 see
 https://java.net/downloads/javaee-spec/JavaEE8_Community_Survey_Results.pdf

 François Meillet






 Le 7 mars 2015 à 22:23, Martin Grigorov mgrigo...@apache.org a écrit :

  Hi,
 
  Once 7.0.0 is released I think we should create a branch for Wicket 8 and
  see what we could benefit of Java 8.
  Having less verbose Wicket would be great! But not on any price! Lambdas
  are both harder to debug and produce bigger stack, so we should decide
  carefully.
  Other things to consider:
  - whether to use Optional for AjaxFallback** components. I don't remember
  the exact reason why Igor's Optional didn't make it, but we may
 reevaluate
  - use the new DateTime APIs for wicket-datetime (new Converters, etc.)
  - ???
 
  We should also ask the community what they don't like in Wicket and what
  they would like to be added to make it better.
 
  Martin Grigorov
  Wicket Training and Consulting
  https://twitter.com/mtgrigorov
 
  On Sat, Mar 7, 2015 at 11:05 AM, Francois Meillet 
  francois.meil...@gmail.com wrote:
 
  Hi All,
 
 
  Is there any Wicket roadmap for the future (after version 7) ?
 
  What is your point of view about the Wicket's future  ?
 
 
  Thanks
  François Meillet
 
 
 
 
 
 
 




Re: Wicket roadmap

2015-03-08 Thread Tobias Soloschenko
Hi,

just a few minds I had when I thought about new features and Wicket 8.0.0:

Because mobile devices are growing significantly in importance - we maybe could 
sum some standardized functions of mobile browsers - like image capture for 
example and build some wicket-components (would also be great for 
wicket-bootstrap) covering those functionalities. 

Image capture example: 
https://dev.opera.com/articles/media-capture-in-mobile-browsers/

kind regards

Tobias

 Am 08.03.2015 um 13:31 schrieb Martin Grigorov mgrigo...@apache.org:
 
 I've created a new page in the Wiki:
 https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+8.0
 
 Martin Grigorov
 Wicket Training and Consulting
 https://twitter.com/mtgrigorov
 
 On Sun, Mar 8, 2015 at 1:50 PM, Martin Grigorov mgrigo...@apache.org
 wrote:
 
 Hi,
 
 Thanks for sharing your ideas!
 
 On Sun, Mar 8, 2015 at 10:00 AM, Francois Meillet 
 francois.meil...@gmail.com wrote:
 
 Here are simple thoughts,
 
 modularity
 
 what do you mean with that ?
 
 
 servlet 4.0 / http 2.0
 
 I'm afraid it is too early for this.
 We can make sure Wicket works fine in a container supporting those but it
 is too early to require that.
 Servlet 4.0 is still in design process. Apache Tomcat didn't started
 implementing any features from it. I am not sure about the status in Jetty.
 I know that Undertow (the web container for JBoss Wildfly) supports HTTP
 2.0 but I haven't heard of any Servlet 4.0 features.
 It will take us some time to release 8.0.0 but I think it will be too
 early to require Servlet 4.0 even then.
 
 
 monitoring
 
 I wanted to see how Wicket could provide some metrics (
 https://dropwizard.github.io/metrics/3.1.0/)
 what else do you have in mind ?
 
 
 server-sent events
 
 
 https://github.com/wicketstuff/core/blob/master/jdk-1.7-parent/wicket-html5-parent/wicket-html5/src/main/java/org/wicketstuff/html5/eventsource/EventSourceResource.java
 provides this for 2 or 3 years now
 So far there were no bug reports for it. I guess no one uses it :-)
 
 
 
 new web design for https://wicket.apache.org
 
 
 I hope this will be ready for Wicket 7.0.0 (
 https://github.com/dashorst/wicket-site,
 http://bitstorm.github.io/wicket-site/)
 @Martijn, @Andrea ?
 
 
 
 new wicket-examples
 
 I've done some work at
 https://github.com/apache/wicket/tree/3435-use-bootstrap-for-examples but
 it needs some love from someone with better CSS skills than me
 
 
 better highlighting of WicketStuff modules on https://wicket.apache.org
 
 
 Andrea added some docs about some of the projects at
 http://wicket.apache.org/guide/guide/wicketstuff.html
 Ideas for improvements can be filed at
 https://github.com/dashorst/wicket-site/issues
 
 
 
 
 Using an online survey tool could be useful
 
 good idea!
 
 
 
 see
 https://java.net/downloads/javaee-spec/JavaEE8_Community_Survey_Results.pdf
 
 François Meillet
 
 
 
 
 
 
 Le 7 mars 2015 à 22:23, Martin Grigorov mgrigo...@apache.org a écrit :
 
 Hi,
 
 Once 7.0.0 is released I think we should create a branch for Wicket 8
 and
 see what we could benefit of Java 8.
 Having less verbose Wicket would be great! But not on any price! Lambdas
 are both harder to debug and produce bigger stack, so we should decide
 carefully.
 Other things to consider:
 - whether to use Optional for AjaxFallback** components. I don't
 remember
 the exact reason why Igor's Optional didn't make it, but we may
 reevaluate
 - use the new DateTime APIs for wicket-datetime (new Converters, etc.)
 - ???
 
 We should also ask the community what they don't like in Wicket and what
 they would like to be added to make it better.
 
 Martin Grigorov
 Wicket Training and Consulting
 https://twitter.com/mtgrigorov
 
 On Sat, Mar 7, 2015 at 11:05 AM, Francois Meillet 
 francois.meil...@gmail.com wrote:
 
 Hi All,
 
 
 Is there any Wicket roadmap for the future (after version 7) ?
 
 What is your point of view about the Wicket's future  ?
 
 
 Thanks
 François Meillet
 

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket roadmap

2015-03-08 Thread Martin Grigorov
I've created a new page in the Wiki:
https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+8.0

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Sun, Mar 8, 2015 at 1:50 PM, Martin Grigorov mgrigo...@apache.org
wrote:

 Hi,

 Thanks for sharing your ideas!

 On Sun, Mar 8, 2015 at 10:00 AM, Francois Meillet 
 francois.meil...@gmail.com wrote:

 Here are simple thoughts,

 modularity


 what do you mean with that ?


 servlet 4.0 / http 2.0


 I'm afraid it is too early for this.
 We can make sure Wicket works fine in a container supporting those but it
 is too early to require that.
 Servlet 4.0 is still in design process. Apache Tomcat didn't started
 implementing any features from it. I am not sure about the status in Jetty.
 I know that Undertow (the web container for JBoss Wildfly) supports HTTP
 2.0 but I haven't heard of any Servlet 4.0 features.
 It will take us some time to release 8.0.0 but I think it will be too
 early to require Servlet 4.0 even then.


 monitoring


 I wanted to see how Wicket could provide some metrics (
 https://dropwizard.github.io/metrics/3.1.0/)
 what else do you have in mind ?


 server-sent events



 https://github.com/wicketstuff/core/blob/master/jdk-1.7-parent/wicket-html5-parent/wicket-html5/src/main/java/org/wicketstuff/html5/eventsource/EventSourceResource.java
 provides this for 2 or 3 years now
 So far there were no bug reports for it. I guess no one uses it :-)



 new web design for https://wicket.apache.org


 I hope this will be ready for Wicket 7.0.0 (
 https://github.com/dashorst/wicket-site,
 http://bitstorm.github.io/wicket-site/)
 @Martijn, @Andrea ?



 new wicket-examples


 I've done some work at
 https://github.com/apache/wicket/tree/3435-use-bootstrap-for-examples but
 it needs some love from someone with better CSS skills than me


 better highlighting of WicketStuff modules on https://wicket.apache.org


 Andrea added some docs about some of the projects at
 http://wicket.apache.org/guide/guide/wicketstuff.html
 Ideas for improvements can be filed at
 https://github.com/dashorst/wicket-site/issues




 Using an online survey tool could be useful


 good idea!



 see
 https://java.net/downloads/javaee-spec/JavaEE8_Community_Survey_Results.pdf

 François Meillet






 Le 7 mars 2015 à 22:23, Martin Grigorov mgrigo...@apache.org a écrit :

  Hi,
 
  Once 7.0.0 is released I think we should create a branch for Wicket 8
 and
  see what we could benefit of Java 8.
  Having less verbose Wicket would be great! But not on any price! Lambdas
  are both harder to debug and produce bigger stack, so we should decide
  carefully.
  Other things to consider:
  - whether to use Optional for AjaxFallback** components. I don't
 remember
  the exact reason why Igor's Optional didn't make it, but we may
 reevaluate
  - use the new DateTime APIs for wicket-datetime (new Converters, etc.)
  - ???
 
  We should also ask the community what they don't like in Wicket and what
  they would like to be added to make it better.
 
  Martin Grigorov
  Wicket Training and Consulting
  https://twitter.com/mtgrigorov
 
  On Sat, Mar 7, 2015 at 11:05 AM, Francois Meillet 
  francois.meil...@gmail.com wrote:
 
  Hi All,
 
 
  Is there any Wicket roadmap for the future (after version 7) ?
 
  What is your point of view about the Wicket's future  ?
 
 
  Thanks
  François Meillet
 
 
 
 
 
 
 





Re: Wicket roadmap

2015-03-08 Thread Andrea Del Bene
The most up-to-date version of the site is the one from Martijn who is 
leading the development. I think there are few things left to do to 
complete this task. I've opened a PR to solve a couple of small layout 
issues in two pages. Apart from this there are some TODO in the 
documentation page to ' integrate media objects' for book pictures and 
videos, but honestly I don't know exactly what this is about. IMHO we 
should also add a new header link for 'community' pages like friends 
projects and WicketStuff.





new web design for https://wicket.apache.org


I hope this will be ready for Wicket 7.0.0 (
https://github.com/dashorst/wicket-site,
http://bitstorm.github.io/wicket-site/)
@Martijn, @Andrea ?




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket roadmap

2015-03-07 Thread Francois Meillet
Thanks Tobias, yes I read this document last year, it's one year old 


François Meillet






Le 7 mars 2015 à 10:16, Tobias Soloschenko tobiassolosche...@googlemail.com a 
écrit :

 Hi,
 
 here are some hints about Wicket after version 7 (see last pages):
 
 http://wicketinaction.com/2014/01/the-state-of-wicket-2014/
 
 kind regards
 
 Tobias
 
 Am 07.03.15 um 10:05 schrieb Francois Meillet:
 Hi All,
 
 
 Is there any Wicket roadmap for the future (after version 7) ?
 
 What is your point of view about the Wicket's future  ?
 
 
 Thanks
 François Meillet
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 



Re: Wicket roadmap

2015-03-07 Thread Tobias Soloschenko

Hi,

here are some hints about Wicket after version 7 (see last pages):

http://wicketinaction.com/2014/01/the-state-of-wicket-2014/

kind regards

Tobias

Am 07.03.15 um 10:05 schrieb Francois Meillet:

Hi All,


Is there any Wicket roadmap for the future (after version 7) ?

What is your point of view about the Wicket's future  ?


Thanks
François Meillet










-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket roadmap

2015-03-07 Thread Francois Meillet
Hi All,


Is there any Wicket roadmap for the future (after version 7) ?

What is your point of view about the Wicket's future  ?


Thanks
François Meillet








Re: Wicket roadmap

2015-03-07 Thread Martin Grigorov
Hi,

Once 7.0.0 is released I think we should create a branch for Wicket 8 and
see what we could benefit of Java 8.
Having less verbose Wicket would be great! But not on any price! Lambdas
are both harder to debug and produce bigger stack, so we should decide
carefully.
Other things to consider:
- whether to use Optional for AjaxFallback** components. I don't remember
the exact reason why Igor's Optional didn't make it, but we may reevaluate
- use the new DateTime APIs for wicket-datetime (new Converters, etc.)
- ???

We should also ask the community what they don't like in Wicket and what
they would like to be added to make it better.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Sat, Mar 7, 2015 at 11:05 AM, Francois Meillet 
francois.meil...@gmail.com wrote:

 Hi All,


 Is there any Wicket roadmap for the future (after version 7) ?

 What is your point of view about the Wicket's future  ?


 Thanks
 François Meillet









Re: General questions regarding Wicket roadmap and plans

2009-12-13 Thread Lester Chua
But you did release them and obtained a financial benefit from the 
releases, the very fact that it is released to the outside world make 
others know of your existance and improves your exposure tremendously.


The particular point under discussion originally was whether a good and 
active component marketplace/showcase site for Wicket will help drive 
the adoption and acceptance rate, as well as allow newbies like myself 
to pick up and use Wicket more easily. It's not about the difficulty or 
ease of creating/maintaining components in Wicket.


Well, it's been pointed out that it's more of a resource issue to 
maintain such a site and I guess we'll just have to leave it at that, 
until someone outside the core Wicket team takes up the gauntlet and 
build one for the rest of us. =)


Lester

Jeremy Thomerson wrote:

+1000 to Martijn's comment.  I've released a few open source components -
and none are at the level to be sold.  Not because they can't be used - I do
use them in production.  But because there are a million use cases and I
have no desire, time, or monetary reason to accommodate those use cases.
Instead, if people contact me, I will either build them a custom component
for hire or will allow them to pay me to add features to an open source
one.

--
Jeremy Thomerson
http://www.wickettraining.com



On Fri, Dec 4, 2009 at 2:54 AM, Martijn Dashorst martijn.dasho...@gmail.com
  

wrote:



  

The problem with pre built components is that they never, ever are
exactly what you want or need. Maintaining such components for other
people is what I call hell. We are in the business of creating the
best Java web framework for building your own custom components with
unprecedented ease. This takes enough time already.

Anybody is welcome to build component libraries, open source or
commercially. Our license allows for that and nobody would object to
creative folks trying to earn a buck or two with their component
(libraries).

That this hasn't happened (yet) is mostly because it is so damned easy
to create your own custom components according to your coding style
that precisely fit in your application and perform exactly those task
you intend them to. And conversely it is damned hard to create a
finished, polished, released component. It is easy to start a
component, but it is *work* to ship it.

Martijn




  



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-12-09 Thread Jeremy Thomerson
+1000 to Martijn's comment.  I've released a few open source components -
and none are at the level to be sold.  Not because they can't be used - I do
use them in production.  But because there are a million use cases and I
have no desire, time, or monetary reason to accommodate those use cases.
Instead, if people contact me, I will either build them a custom component
for hire or will allow them to pay me to add features to an open source
one.

--
Jeremy Thomerson
http://www.wickettraining.com



On Fri, Dec 4, 2009 at 2:54 AM, Martijn Dashorst martijn.dasho...@gmail.com
 wrote:

 The problem with pre built components is that they never, ever are
 exactly what you want or need. Maintaining such components for other
 people is what I call hell. We are in the business of creating the
 best Java web framework for building your own custom components with
 unprecedented ease. This takes enough time already.

 Anybody is welcome to build component libraries, open source or
 commercially. Our license allows for that and nobody would object to
 creative folks trying to earn a buck or two with their component
 (libraries).

 That this hasn't happened (yet) is mostly because it is so damned easy
 to create your own custom components according to your coding style
 that precisely fit in your application and perform exactly those task
 you intend them to. And conversely it is damned hard to create a
 finished, polished, released component. It is easy to start a
 component, but it is *work* to ship it.

 Martijn



Re: General questions regarding Wicket roadmap and plans

2009-12-04 Thread Martijn Dashorst
The problem with pre built components is that they never, ever are
exactly what you want or need. Maintaining such components for other
people is what I call hell. We are in the business of creating the
best Java web framework for building your own custom components with
unprecedented ease. This takes enough time already.

Anybody is welcome to build component libraries, open source or
commercially. Our license allows for that and nobody would object to
creative folks trying to earn a buck or two with their component
(libraries).

That this hasn't happened (yet) is mostly because it is so damned easy
to create your own custom components according to your coding style
that precisely fit in your application and perform exactly those task
you intend them to. And conversely it is damned hard to create a
finished, polished, released component. It is easy to start a
component, but it is *work* to ship it.

Martijn

On Fri, Dec 4, 2009 at 6:37 AM, Lester Chua cicowic...@gmail.com wrote:
 I think it's kinda of chicken and egg issue wrt components.
 If newbies do not see components readily available, they will probably end
 up coding what they want themselves because:

 1) it takes time to articulate properly their requirements
 2) avoid facing potential embarrassment  because the component that they
 want is trivial (which turns out not to be)
 3) I know it when I see it (this is quite common and this approach
 normally requires a large library of things to pick from)

 Maybe the reason why no one is asking is one of the above reasons, or all of
 them combined.


 Igor Vaynberg wrote:

 the interesting bit is that people are saying that there are not
 enough components that wicket ships with, but no one is saying which
 componets exactly they are missing.

 -igor

 On Thu, Dec 3, 2009 at 7:41 PM, Ashley Aitken mrhat...@mac.com wrote:


 On 02/12/2009, at 10:45 AM, Igor Vaynberg wrote:



 but as you will see, there is not much
 demand for precanned components out there, they are just too easy to
 roll yourself and there are a lot of open source ones that you can at
 least get ideas from for your specific requirements.


 But isn't that missing some of the major reasons for using components:

 1. that you shouldn't have to reinvent the wheel (even if it is easy),
 2. that a component that is tried and tested (version 3+) is better than
 my
 version 1,
 3. components can encapsulate best practice that takes time to learn,
 4.  a suite of components may integrate better.

 Writing a linked list in Java is easy but I would never consider doing
 that,
 the available classe are much more powerful, general, well-tested,
 integrated, ...

 I'm not knowledgeable wrt Wicket components or JSF components, but
 generally
 speaking what components available in JSF, for example, wouldn't be
 useful
 in Wicket and why not?

 I'm with the OP in that I'm a little surprised by the lack of published
 components (from low-level to high-level).  Again, I am probably missing
 something ...

 Maybe as I learn more about Wicket and get more experience I will
 understand.

 Cheers,
 Ashley.

 --
 Ashley Aitken
 Perth, Western Australia
 Skype/iChat: MrHatken (GMT + 8hrs!)


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-12-03 Thread Ashley Aitken


On 02/12/2009, at 10:45 AM, Igor Vaynberg wrote:


but as you will see, there is not much
demand for precanned components out there, they are just too easy to
roll yourself and there are a lot of open source ones that you can at
least get ideas from for your specific requirements.


But isn't that missing some of the major reasons for using components:

1. that you shouldn't have to reinvent the wheel (even if it is easy),
2. that a component that is tried and tested (version 3+) is better  
than my version 1,

3. components can encapsulate best practice that takes time to learn,
4.  a suite of components may integrate better.

Writing a linked list in Java is easy but I would never consider doing  
that, the available classe are much more powerful, general, well- 
tested, integrated, ...


I'm not knowledgeable wrt Wicket components or JSF components, but  
generally speaking what components available in JSF, for example,  
wouldn't be useful in Wicket and why not?


I'm with the OP in that I'm a little surprised by the lack of  
published components (from low-level to high-level).  Again, I am  
probably missing something ...


Maybe as I learn more about Wicket and get more experience I will  
understand.


Cheers,
Ashley.

--
Ashley Aitken
Perth, Western Australia
Skype/iChat: MrHatken (GMT + 8hrs!)


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-12-03 Thread Igor Vaynberg
the interesting bit is that people are saying that there are not
enough components that wicket ships with, but no one is saying which
componets exactly they are missing.

-igor

On Thu, Dec 3, 2009 at 7:41 PM, Ashley Aitken mrhat...@mac.com wrote:

 On 02/12/2009, at 10:45 AM, Igor Vaynberg wrote:

 but as you will see, there is not much
 demand for precanned components out there, they are just too easy to
 roll yourself and there are a lot of open source ones that you can at
 least get ideas from for your specific requirements.

 But isn't that missing some of the major reasons for using components:

 1. that you shouldn't have to reinvent the wheel (even if it is easy),
 2. that a component that is tried and tested (version 3+) is better than my
 version 1,
 3. components can encapsulate best practice that takes time to learn,
 4.  a suite of components may integrate better.

 Writing a linked list in Java is easy but I would never consider doing that,
 the available classe are much more powerful, general, well-tested,
 integrated, ...

 I'm not knowledgeable wrt Wicket components or JSF components, but generally
 speaking what components available in JSF, for example, wouldn't be useful
 in Wicket and why not?

 I'm with the OP in that I'm a little surprised by the lack of published
 components (from low-level to high-level).  Again, I am probably missing
 something ...

 Maybe as I learn more about Wicket and get more experience I will
 understand.

 Cheers,
 Ashley.

 --
 Ashley Aitken
 Perth, Western Australia
 Skype/iChat: MrHatken (GMT + 8hrs!)


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-12-03 Thread ljw1001


I agree that more components are needed and would add that a good  
calendar would be a great place to start.


On Dec 3, 2009, at 11:16 PM, Igor Vaynberg igor.vaynb...@gmail.com  
wrote:



the interesting bit is that people are saying that there are not
enough components that wicket ships with, but no one is saying which
componets exactly they are missing.

-igor

On Thu, Dec 3, 2009 at 7:41 PM, Ashley Aitken mrhat...@mac.com  
wrote:


On 02/12/2009, at 10:45 AM, Igor Vaynberg wrote:


but as you will see, there is not much
demand for precanned components out there, they are just too easy to
roll yourself and there are a lot of open source ones that you can  
at

least get ideas from for your specific requirements.


But isn't that missing some of the major reasons for using  
components:


1. that you shouldn't have to reinvent the wheel (even if it is  
easy),
2. that a component that is tried and tested (version 3+) is better  
than my

version 1,
3. components can encapsulate best practice that takes time to learn,
4.  a suite of components may integrate better.

Writing a linked list in Java is easy but I would never consider  
doing that,

the available classe are much more powerful, general, well-tested,
integrated, ...

I'm not knowledgeable wrt Wicket components or JSF components, but  
generally
speaking what components available in JSF, for example, wouldn't be  
useful

in Wicket and why not?

I'm with the OP in that I'm a little surprised by the lack of  
published
components (from low-level to high-level).  Again, I am probably  
missing

something ...

Maybe as I learn more about Wicket and get more experience I will
understand.

Cheers,
Ashley.

--
Ashley Aitken
Perth, Western Australia
Skype/iChat: MrHatken (GMT + 8hrs!)


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-12-03 Thread Igor Vaynberg
like this?

https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-core/calendarviews-parent/

-igor

On Thu, Dec 3, 2009 at 8:32 PM, ljw1001 ljw1...@gmail.com wrote:

 I agree that more components are needed and would add that a good calendar
 would be a great place to start.

 On Dec 3, 2009, at 11:16 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:

 the interesting bit is that people are saying that there are not
 enough components that wicket ships with, but no one is saying which
 componets exactly they are missing.

 -igor

 On Thu, Dec 3, 2009 at 7:41 PM, Ashley Aitken mrhat...@mac.com wrote:

 On 02/12/2009, at 10:45 AM, Igor Vaynberg wrote:

 but as you will see, there is not much
 demand for precanned components out there, they are just too easy to
 roll yourself and there are a lot of open source ones that you can at
 least get ideas from for your specific requirements.

 But isn't that missing some of the major reasons for using components:

 1. that you shouldn't have to reinvent the wheel (even if it is easy),
 2. that a component that is tried and tested (version 3+) is better than
 my
 version 1,
 3. components can encapsulate best practice that takes time to learn,
 4.  a suite of components may integrate better.

 Writing a linked list in Java is easy but I would never consider doing
 that,
 the available classe are much more powerful, general, well-tested,
 integrated, ...

 I'm not knowledgeable wrt Wicket components or JSF components, but
 generally
 speaking what components available in JSF, for example, wouldn't be
 useful
 in Wicket and why not?

 I'm with the OP in that I'm a little surprised by the lack of published
 components (from low-level to high-level).  Again, I am probably missing
 something ...

 Maybe as I learn more about Wicket and get more experience I will
 understand.

 Cheers,
 Ashley.

 --
 Ashley Aitken
 Perth, Western Australia
 Skype/iChat: MrHatken (GMT + 8hrs!)


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-12-01 Thread Lester Chua

Hi,

Took some time to pick up this thread again as we were preparing for the 
UAT of the application rewrite using Wicket =) for the last 2 weeks.

The UAT was quite successful, with minor modifications required (expected).
The real good news is that Wicket performed admirably in terms of 
productivity and the bugs tracing and fixes in the lead up to the UAT.
We rewrote the modules in under a month (the original took about 4). The 
productivity boost actually came from the tweaks we needed for UI 
interaction as well as code tracing when unexpected behaviour occured.


The experience using Wicket has been real refreshing, I truly enjoyed 
the departure from the model2  as well as the json-rest/rich-client 
frameworks we were used to.


Ok enough ambling. I have some responses below.

Igor Vaynberg wrote:

On Wed, Nov 18, 2009 at 9:27 PM, Lester Chua cicowic...@gmail.com wrote:
  

Thanks for the reply.



1) Product Roadmap (Release plans, upcoming features etc)
This is important to us because it will at least indicate the intentions
of
Wicket Team. As any technology that is adopted enterprise-wide needs to
be
long-lived and well supported in addition to it's features and
technology,
some visibility about the product lifecycle is required.



http://cwiki.apache.org/WICKET/wicket-15-wish-list.html
http://cwiki.apache.org/WICKET/wicket-14-wish-list.html

  

I did see the wishlist but was wishing for something more like a roadmap
with projected release timelines, I can see why that it will probably not be
accurate for an open sourced project but an indication of a rough ETA and
included features will be good.

By the way, is the wishlist official? As in are the features present in the
wishlist official? Or is the wishlist used as an idea incubator/exchange?



its an idea incubator
  


Although it's nice to have the wishlist, it's a shame that the Wicket 
does not publish a roadmap (even a limited one with just key specific 
features to be improved on).
Is is a resource/maintenance issue you have that prevents you from doing 
so? Or is it more of a management decision to not publish the roadmap so 
that you can avoid commiting to a timeline?


The reason why I'm asking this is partly selfish. The organization that 
I'm pushing Wicket in has a technical committee that review 
frameworks/platforms for use. Anything that does not fall into their 
recommended list will need a waiver to be used and deployed.  Yea I 
know, very cumbersome but it's a fact of life here, and I suspect in 
many other organizations that have security as one of their top concerns.


After using Wicket in a real life app conversion, I think I'm able to 
address most points that has been raised including security (very 
pleased on that front) and productivity etc. But part of the checklist I 
am forced to go through is estimated product life span, road map etc.


Unfortunately, It's here that I'm stumped. Has anyone else been through 
this hoop-la-loop that your organization forced you to go through for 
the introduction of Wicket? If so it'll be great if the information on 
how that was achieved can be shared as it'll help me immensely in the 
fight to get Wicket into my enterprise environment.



2) Recent Adoption Statistics (No of downloads, usage projections)
We need this to gauge the interest in the project. Has it peaked? What
is the pattern like?

++ Nice idea


  

a) Although there is examples and documentation available on Wicket main
site and Wicket stuff, I find that the organization of the information is
probably not friendly enough for easy viewing. E.g. the examples site
does
not contain source and viewable example together in an easy to read page.
This can be improved on significantly.



you and your team are welcome to contribute, great ideas btw


  

Planning to once I get up to speed.


Being such an easy to use component framework, I am really puzzled about
why the
plugin development seems so bare



One reason is that it's so easy to make plugins it feels unnecessary
to publish them.


  

Actually I kinda disagree. Take Delphi which was awesome for it's component
architecture and IDE. Writing components and packaging them was very easy
but it had a HUGE thriving component library market place where you can
literally purchase thousands of packages and libraries.



desktops apps are different, you can build any kind of component you
want. wicket works with server-side html and there is a limited set of
things you can build. if you need a slider then the chances are we
wont provide it, we dont need to, just use wicket to output a hidden
field and make a slider out of it using jquery or some other frontend
library. in about two minutes you can wrap that into a jqueryslider
component, would you take the time to share something that took two
minutes to build? some people do, there are a couple of projects out
there that provide integrations between wicket and 

Re: General questions regarding Wicket roadmap and plans

2009-12-01 Thread Igor Vaynberg
On Tue, Dec 1, 2009 at 5:17 PM, Lester Chua cicowic...@gmail.com wrote:
 Hi,

 Took some time to pick up this thread again as we were preparing for the UAT
 of the application rewrite using Wicket =) for the last 2 weeks.
 The UAT was quite successful, with minor modifications required (expected).
 The real good news is that Wicket performed admirably in terms of
 productivity and the bugs tracing and fixes in the lead up to the UAT.
 We rewrote the modules in under a month (the original took about 4). The
 productivity boost actually came from the tweaks we needed for UI
 interaction as well as code tracing when unexpected behaviour occured.

 The experience using Wicket has been real refreshing, I truly enjoyed the
 departure from the model2  as well as the json-rest/rich-client frameworks
 we were used to.

 Ok enough ambling. I have some responses below.

 Igor Vaynberg wrote:

 On Wed, Nov 18, 2009 at 9:27 PM, Lester Chua cicowic...@gmail.com wrote:


 Thanks for the reply.



 1) Product Roadmap (Release plans, upcoming features etc)
 This is important to us because it will at least indicate the
 intentions
 of
 Wicket Team. As any technology that is adopted enterprise-wide needs to
 be
 long-lived and well supported in addition to it's features and
 technology,
 some visibility about the product lifecycle is required.



 http://cwiki.apache.org/WICKET/wicket-15-wish-list.html
 http://cwiki.apache.org/WICKET/wicket-14-wish-list.html



 I did see the wishlist but was wishing for something more like a roadmap
 with projected release timelines, I can see why that it will probably not
 be
 accurate for an open sourced project but an indication of a rough ETA and
 included features will be good.

 By the way, is the wishlist official? As in are the features present in
 the
 wishlist official? Or is the wishlist used as an idea incubator/exchange?


 its an idea incubator


 Although it's nice to have the wishlist, it's a shame that the Wicket does
 not publish a roadmap (even a limited one with just key specific features to
 be improved on).
 Is is a resource/maintenance issue you have that prevents you from doing so?
 Or is it more of a management decision to not publish the roadmap so that
 you can avoid commiting to a timeline?

 The reason why I'm asking this is partly selfish. The organization that I'm
 pushing Wicket in has a technical committee that review frameworks/platforms
 for use. Anything that does not fall into their recommended list will need a
 waiver to be used and deployed.  Yea I know, very cumbersome but it's a fact
 of life here, and I suspect in many other organizations that have security
 as one of their top concerns.

 After using Wicket in a real life app conversion, I think I'm able to
 address most points that has been raised including security (very pleased on
 that front) and productivity etc. But part of the checklist I am forced to
 go through is estimated product life span, road map etc.

 Unfortunately, It's here that I'm stumped. Has anyone else been through this
 hoop-la-loop that your organization forced you to go through for the
 introduction of Wicket? If so it'll be great if the information on how that
 was achieved can be shared as it'll help me immensely in the fight to get
 Wicket into my enterprise environment.

it is a combination of all these things. mainly we do not want to
commit to a feature set because we do not know what our resources will
be during the build phase. we have a general idea of what we want to
do and how, and that is outlined in discussions on the mailing lists.

 2) Recent Adoption Statistics (No of downloads, usage projections)
 We need this to gauge the interest in the project. Has it peaked? What
 is the pattern like?

 ++ Nice idea




 a) Although there is examples and documentation available on Wicket
 main
 site and Wicket stuff, I find that the organization of the information
 is
 probably not friendly enough for easy viewing. E.g. the examples site
 does
 not contain source and viewable example together in an easy to read
 page.
 This can be improved on significantly.



 you and your team are welcome to contribute, great ideas btw




 Planning to once I get up to speed.


 Being such an easy to use component framework, I am really puzzled
 about
 why the
 plugin development seems so bare



 One reason is that it's so easy to make plugins it feels unnecessary
 to publish them.




 Actually I kinda disagree. Take Delphi which was awesome for it's
 component
 architecture and IDE. Writing components and packaging them was very easy
 but it had a HUGE thriving component library market place where you can
 literally purchase thousands of packages and libraries.


 desktops apps are different, you can build any kind of component you
 want. wicket works with server-side html and there is a limited set of
 things you can build. if you need a slider then the chances are we
 wont provide it, we dont need to, just use wicket to output 

Re: General questions regarding Wicket roadmap and plans

2009-11-19 Thread Igor Vaynberg
On Wed, Nov 18, 2009 at 6:30 PM, Lester Chua cicowic...@gmail.com wrote:
 Hi,

 I've finished converting major portions of an existing in-house application
 from EXTJS/JSON Servlets to Wicket as part of an evaluation of Wicket.
 Right now I'm VERY impressed with the framework and would like to introduce
 it to the organization I'm working for.

 There are a couple of things that I could not find and was wondering if the
 Wicket Team have them but somehow failed to make them available in the
 Wicket Site.
 I hope someone can help me out if this is available but I had somehow missed
 it.

 1) Product Roadmap (Release plans, upcoming features etc)
 This is important to us because it will at least indicate the intentions of
 Wicket Team. As any technology that is adopted enterprise-wide needs to be
 long-lived and well supported in addition to it's features and technology,
 some visibility about the product lifecycle is required.

we do not publish an official road map because its one more thing to
maintain that is not wicket. up until now there was no interest in
one because we often discuss our plans on the mailing list.

 2) Recent Adoption Statistics (No of downloads, usage projections)
 We need this to gauge the interest in the project. Has it peaked? What is
 the pattern like?

number of downloads are pretty meaningless since most users get wicket
through the maven repo and there are no statistics available for
those. especially because these repos are also proxied. eg if ibm has
a maven proxy then the wicket jar is only downloaded once although
potentially used by every ibm developer.

 Some comments about Wicket (project/product aspects), this is not a critique
 but just observations that may be wrong, do correct me if I had missed
 something or have some wrong impression about Wicket site.

 a) Although there is examples and documentation available on Wicket main
 site and Wicket stuff, I find that the organization of the information is
 probably not friendly enough for easy viewing. E.g. the examples site does
 not contain source and viewable example together in an easy to read page.
 This can be improved on significantly.

there is a source code link in the gray header of every example. i
agree, this is not the prettiest nor the coolest out there, but it
gets the job done. our users are more then welcome to submit patches
to make it better. we are still actively developing improvements to
wicket itself so sometimes projects like examples get sidelined due to
our limited resources.

 b) Having a Wicket Stuff site that does not appear updated nor actively
 maintained will HURT the project in terms of it's adoption.

i wouldnt say that wicket-stuff is officially affiliated with wicket
itself. it is a playground for developers who use wicket to share
ideas.

 Wicket is FANTASTIC as a component based solution to our current web
 development landscape. I am preaching to the sold when I say that it's easy
 to use and yet flexible to do moderately complex stuff productively. Being
 such an easy to use component framework, I am really puzzled about why the
 plugin development seems so bare

what kinds of components were you missing when building your project?

 (in comparison to other frameworks I'm used
 to like JQuery, ExtJS, Grails, Ruby on Rails etc).

extjs is also quiet bare. i was not able to find a lot of things i was
looking for when building an app using it.

jquery has a ton of plugins but most of them are garbage, and that
makes it very difficult to sift through and find a good one. you get a
plugin, it works, great. then you try to do something and it doesnt.
fine, you think, i will just go into the source and tweak it. you open
the source and your eyes start bleeding. this has been my experience
with probably 80% of jquery plugins ive used.

 In fact, Wicket makes
 plugin deployment and integration seem like a piece of cake compared to some
 of the frameworks mentioned earlier. And yet, wicket seems woefully
 underpowered in the plugins department and worse, the official site seems
 abandoned which will definitely harm Wicket's adoption rate.

http://wicket.apache.org/ is abandoned? i remember updating it just a
few weeks ago with the new 1.4.3 release

 c) The mailing list is wonderful and I have had some questions very quickly
 answered, which points to an active and supportive community for which I'm
 grateful. If there is a way to harness this and make the information more
 easily accessible, it'll be awesome.

http://markmail.org is a wonderful tool for searching apache mailing lists.

 Ok, enough bitching =), I love Wicket! Hopefully, I can become proficient
 enough to actively contribute to the documentation to make this great
 framework more accessible to newbies like myself.

yeah, we hear that a lot

-igor

 But first, I need to sell
 my team and management on the long term product aspects of Wicket.

 Any help or information about point 1  2 is greatly appreciated.

 Lester

 On 

Re: General questions regarding Wicket roadmap and plans

2009-11-19 Thread Igor Vaynberg
On Wed, Nov 18, 2009 at 9:27 PM, Lester Chua cicowic...@gmail.com wrote:
 Thanks for the reply.

 1) Product Roadmap (Release plans, upcoming features etc)
 This is important to us because it will at least indicate the intentions
 of
 Wicket Team. As any technology that is adopted enterprise-wide needs to
 be
 long-lived and well supported in addition to it's features and
 technology,
 some visibility about the product lifecycle is required.


 http://cwiki.apache.org/WICKET/wicket-15-wish-list.html
 http://cwiki.apache.org/WICKET/wicket-14-wish-list.html


 I did see the wishlist but was wishing for something more like a roadmap
 with projected release timelines, I can see why that it will probably not be
 accurate for an open sourced project but an indication of a rough ETA and
 included features will be good.

 By the way, is the wishlist official? As in are the features present in the
 wishlist official? Or is the wishlist used as an idea incubator/exchange?

its an idea incubator

 2) Recent Adoption Statistics (No of downloads, usage projections)
 We need this to gauge the interest in the project. Has it peaked? What
 is the pattern like?

 ++ Nice idea



 a) Although there is examples and documentation available on Wicket main
 site and Wicket stuff, I find that the organization of the information is
 probably not friendly enough for easy viewing. E.g. the examples site
 does
 not contain source and viewable example together in an easy to read page.
 This can be improved on significantly.


 you and your team are welcome to contribute, great ideas btw



 Planning to once I get up to speed.

 Being such an easy to use component framework, I am really puzzled about
 why the
 plugin development seems so bare


 One reason is that it's so easy to make plugins it feels unnecessary
 to publish them.



 Actually I kinda disagree. Take Delphi which was awesome for it's component
 architecture and IDE. Writing components and packaging them was very easy
 but it had a HUGE thriving component library market place where you can
 literally purchase thousands of packages and libraries.

desktops apps are different, you can build any kind of component you
want. wicket works with server-side html and there is a limited set of
things you can build. if you need a slider then the chances are we
wont provide it, we dont need to, just use wicket to output a hidden
field and make a slider out of it using jquery or some other frontend
library. in about two minutes you can wrap that into a jqueryslider
component, would you take the time to share something that took two
minutes to build? some people do, there are a couple of projects out
there that provide integrations between wicket and jquery, but most
people dont end up sharing.

 c) The mailing list is wonderful and I have had some questions very
 quickly
 answered, which points to an active and supportive community for which
 I'm
 grateful. If there is a way to harness this and make the information more
 easily accessible, it'll be awesome.


 Google reaches most of the discussion via nable/osdir.



 Yea, that is how I got most of the solutions to my little set of problems.
 =) Just wishing that it can be better.

hrm, you posted about six messages on our lists, and most times you
got an answer within a couple of hours. that is better then most
commercial support out there. and yet you are still complaining? :)

-igor


 My 2cents worth ;)


 **
 Martin

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



General questions regarding Wicket roadmap and plans

2009-11-18 Thread Lester Chua

Hi,

I've finished converting major portions of an existing in-house 
application from EXTJS/JSON Servlets to Wicket as part of an evaluation 
of Wicket.
Right now I'm VERY impressed with the framework and would like to 
introduce it to the organization I'm working for.


There are a couple of things that I could not find and was wondering if 
the Wicket Team have them but somehow failed to make them available in 
the Wicket Site.
I hope someone can help me out if this is available but I had somehow 
missed it.


1) Product Roadmap (Release plans, upcoming features etc)
This is important to us because it will at least indicate the intentions 
of Wicket Team. As any technology that is adopted enterprise-wide needs 
to be long-lived and well supported in addition to it's features and 
technology, some visibility about the product lifecycle is required.


2) Recent Adoption Statistics (No of downloads, usage projections)
We need this to gauge the interest in the project. Has it peaked? What 
is the pattern like?


Some comments about Wicket (project/product aspects), this is not a 
critique but just observations that may be wrong, do correct me if I had 
missed something or have some wrong impression about Wicket site.


a) Although there is examples and documentation available on Wicket main 
site and Wicket stuff, I find that the organization of the information 
is probably not friendly enough for easy viewing. E.g. the examples site 
does not contain source and viewable example together in an easy to read 
page. This can be improved on significantly.


b) Having a Wicket Stuff site that does not appear updated nor actively 
maintained will HURT the project in terms of it's adoption.
Wicket is FANTASTIC as a component based solution to our current web 
development landscape. I am preaching to the sold when I say that it's 
easy to use and yet flexible to do moderately complex stuff 
productively. Being such an easy to use component framework, I am really 
puzzled about why the plugin development seems so bare (in comparison to 
other frameworks I'm used to like JQuery, ExtJS, Grails, Ruby on Rails 
etc). In fact, Wicket makes plugin deployment and integration seem like 
a piece of cake compared to some of the frameworks mentioned earlier. 
And yet, wicket seems woefully underpowered in the plugins department 
and worse, the official site seems abandoned which will definitely harm 
Wicket's adoption rate.


c) The mailing list is wonderful and I have had some questions very 
quickly answered, which points to an active and supportive community for 
which I'm grateful. If there is a way to harness this and make the 
information more easily accessible, it'll be awesome.


Ok, enough bitching =), I love Wicket! Hopefully, I can become 
proficient enough to actively contribute to the documentation to make 
this great framework more accessible to newbies like myself. But first, 
I need to sell my team and management on the long term product aspects 
of Wicket.


Any help or information about point 1  2 is greatly appreciated.

Lester

On a more irrelevant note when I first started web development back in 
1999, I was wondering if I could use Rational Rose to generate a UML 
model of my web project (it can't). But now with wicket, I can fully 
reverse engineer a UML model that MAKES SENSE for my Wicket App! Ok, I 
may not want to do that now, but it's actually possible, try doing that 
with any other web framework.






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-11-18 Thread Martin Makundi
 1) Product Roadmap (Release plans, upcoming features etc)
 This is important to us because it will at least indicate the intentions of
 Wicket Team. As any technology that is adopted enterprise-wide needs to be
 long-lived and well supported in addition to it's features and technology,
 some visibility about the product lifecycle is required.

http://cwiki.apache.org/WICKET/wicket-15-wish-list.html
http://cwiki.apache.org/WICKET/wicket-14-wish-list.html

2) Recent Adoption Statistics (No of downloads, usage projections)
We need this to gauge the interest in the project. Has it peaked? What
is the pattern like?

++ Nice idea

 a) Although there is examples and documentation available on Wicket main
 site and Wicket stuff, I find that the organization of the information is
 probably not friendly enough for easy viewing. E.g. the examples site does
 not contain source and viewable example together in an easy to read page.
 This can be improved on significantly.

you and your team are welcome to contribute, great ideas btw

 Being such an easy to use component framework, I am really puzzled about why 
 the
 plugin development seems so bare

One reason is that it's so easy to make plugins it feels unnecessary
to publish them.

 c) The mailing list is wonderful and I have had some questions very quickly
 answered, which points to an active and supportive community for which I'm
 grateful. If there is a way to harness this and make the information more
 easily accessible, it'll be awesome.

Google reaches most of the discussion via nable/osdir.



My 2cents worth ;)


**
Martin

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: General questions regarding Wicket roadmap and plans

2009-11-18 Thread Lester Chua

Thanks for the reply.


1) Product Roadmap (Release plans, upcoming features etc)
This is important to us because it will at least indicate the intentions of
Wicket Team. As any technology that is adopted enterprise-wide needs to be
long-lived and well supported in addition to it's features and technology,
some visibility about the product lifecycle is required.



http://cwiki.apache.org/WICKET/wicket-15-wish-list.html
http://cwiki.apache.org/WICKET/wicket-14-wish-list.html
  
I did see the wishlist but was wishing for something more like a roadmap 
with projected release timelines, I can see why that it will probably 
not be accurate for an open sourced project but an indication of a rough 
ETA and included features will be good.


By the way, is the wishlist official? As in are the features present in 
the wishlist official? Or is the wishlist used as an idea 
incubator/exchange?



2) Recent Adoption Statistics (No of downloads, usage projections)
We need this to gauge the interest in the project. Has it peaked? What
is the pattern like?

++ Nice idea

  

a) Although there is examples and documentation available on Wicket main
site and Wicket stuff, I find that the organization of the information is
probably not friendly enough for easy viewing. E.g. the examples site does
not contain source and viewable example together in an easy to read page.
This can be improved on significantly.



you and your team are welcome to contribute, great ideas btw

  

Planning to once I get up to speed.

Being such an easy to use component framework, I am really puzzled about why the
plugin development seems so bare



One reason is that it's so easy to make plugins it feels unnecessary
to publish them.

  
Actually I kinda disagree. Take Delphi which was awesome for it's 
component architecture and IDE. Writing components and packaging them 
was very easy but it had a HUGE thriving component library market place 
where you can literally purchase thousands of packages and libraries.

c) The mailing list is wonderful and I have had some questions very quickly
answered, which points to an active and supportive community for which I'm
grateful. If there is a way to harness this and make the information more
easily accessible, it'll be awesome.



Google reaches most of the discussion via nable/osdir.

  
Yea, that is how I got most of the solutions to my little set of 
problems. =) Just wishing that it can be better.


My 2cents worth ;)


**
Martin

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

  



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org