| support-rkalla wrote: |
| We agree, Wicket is a cool framework... but walking up to the president and asking for $100k to develop, support, extend a feature "Because it's cool" is the same thing as macing him and asking him for the money :)
At the end of the day decisions are based on user demand. It's also a lot easier to sell management on the idea if there is an existing plugin that can be used as the seed to the effort or get an idea of how users would want the functionality to work. You'd be surprised how many people ask for "XYZ support" and have no idea what they really mean, then when you probe them, they'll say something like "I mean autocomplete for my taglibs"... and you have to point out that the feature is already there and they were just using it wrong or something like that. So that being said, when you guys say "Wicket support" what do you mean specifically? You already have the visual page designer support for the xhtml pages. Autocomplete and validation for that, all the Java editing support and debugging AND deployment support with hotsyncing. (I've worked on a wicket project in MyEclipse before, and I honestly didn't feel like I was missing anything major). I agree that some wizards here or there that create the necessary Page Java/XHTML files would be handy, but I can't think of any show-stopping problems at the moment. Ideas? Not pie-in-the-sky ideas, but more immediate-need-ideas? |