I'll wade into the point about IDE plugins since I was the original maintainer of Wicketforge (https://code.google.com/p/wicketforge/), which is still being actively developed by Minas Manthos.
As it stands today, Wicketforge is a great productivity enhancer when developing Wicket apps. It provides autocompletion of Wicket IDs, templated panel and page creation, as well as a few inspections and intentions to make life easier (More info here: https://code.google.com/p/wicketforge/wiki/PluginFeatures). More features could be added, but the value is questionable given IDEA's already excellent HTML and Java support. Right now Wicketforge has no open tickets. If the plugin doesn't do something you want it to do, checkout the source and contribute back. I'm sure Minas would love to get some patches, and if he's busy I'll come out of plugin retirement and take a look. -Nick On Tue, Feb 5, 2013 at 10:45 AM, procrastinative.developer < procrastinative.develo...@gmail.com> wrote: > I really enjoy wicket, it's really easy to create complex site with it. For > me the biggest problem was a 'wicket way'. To create site effectivly, we > need to learn a lot about how wicket works etc. Without good documentation > process of learning can be frustrating. > > I see this problems in wicket: > 1)lack of good documentation (for beginners is ok, but for more complex > problems sometimes I need to spend a lot of time to discover how I need to > do that) > 2)lack of good IDE support - I use netbeans and intellij and tools for it > are not very good. > 3)lack of good list of tools -in my wicket career i found a lot usefull > tools, but in 50% it was a matter of luck. > 4)a lot of abandoned plugins - because of a lot of api breaks between > wicket 1.4 and wicket 6.0 some plugin not working with current version of > wicket. > > Wicket developers did a lot of good work. Wicket popularity depends on > wicket community. Maybe developers of plugins and wicket tools(not only > wicket components, but also IDE plugins developers and tools like wicket > RAD > etc) should give feedback what they need for easier tools creation. Wicket > dev should freeze api. I think that now wicket is very mature framework and > with version 6.0 its time to start building infrastructure around it that > help developers to create webapplications. > > Maybe it's time to build site like "wicket repository" where user can > publish and search information about created by other users plugins? > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-job-market-tp4656048p4656092.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
