- This topic has 33 replies, 23 voices, and was last updated 12 years, 8 months ago by
.
-
Posts
-
It would be great if you could add Wicket support to MyEclipse. As Wicket is a component-based framework, it makes the use of an IDE a very logical thing to do.
There’s a very preliminar plugin for Eclipse called Wicket-bench, but it doesn’t seem to be working for Eclipse 3.1.
There’s also going to be a presentation in the upcoming JavaONE that talks about customizing Netbeans, and it’s going to use Wicket as the example.
I think Wicket is going to grow its userbase a lot in the near future, as people are finding it really easy to use.
I’m on the wicket mailing lists and follow the project for the same reason you are probably using it: JSF isn’t what you want it to be and Wicket is a really nice way to develop web apps.
At this point we would probably wait and see where Wicket-bench went before adding support for Wicket. Also since we are a commercial company, every feature we add is expensive in terms of integration, development, bug fixes and support, so there really needs to be demand for features before we add them and right now there is a very little user demand for Wicket but we know it’s an up and comming framework.
+1 for wicket for me too.
Faces, Struts and others are well supported but the fact that Wicket is missing from MyEclipse is such a pitty. If Wicket was supported my MyEclipse, I would not need any other plugins. BTW, thanks for a great product, MyEclipse guys! 😀
weliwarmer,
Thank you for the kind words. You mentioned if we included Wicket support you couldn’t need any other plugins… what Eclipse/Wicket plugins *are* available?My development would be COMPLETE if MyEclipse had Wicket support. I’m developing Wicket+Java EE 5 apps for several companies now…and full-time at my regular job.
You’ve begun support for Java EE 5, which I’m very grateful for…however Wicket would be the whipped cream on the hot fudge sundae that is MyEclipse 😉
I don’t think there’s any denying that Wicket is growing…*very* fast. Most discussions I see around the web about how bad JSF is…or how complicated it is to learn Tapestry….or how hard Struts is/was…Wicket always comes up in those threads. It’s el fuego, baby.
PLEASE!!??
+1 for me…I’d vote more if I could!
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?
@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?
I wasn’t implying that you should add support for Wicket just because I think it’s “cool”. What I was saying is; it may behoove you, sales-wise, to add support for a technology that is clearly skyrocketing…now ranking right up there w/ Struts, JSF, Tapestry, etc. – all of which you currently support in your product. It would most certainly give you a competitive advantage over other IDEs in your competing market place to be the first to support a very popular technology, commercially, no?
Here are some specific things that would be nice to have support with…please everyone help me think of more that I may have overlooked.
It would be nice to automate some things…some features:
1. “Create Wicket Application” – It would setup the initial class that launches the app (derives from WicketApplication). It would also configure the Wicket servlet in web.xml.
2. “Create Wicket Page” – Create class & respective HTML file.
3. Wicket widgets palette – Similar to what you have for JSF, Struts, etc. in the visual designer.
4. Wicket Actions – It’d be great to be able to double-click a button in the designer and have it create, and jump to, the event handler in the Java code…similar to the Matisse4MyEclipse designer.
5. Panel Support – Drag & Drop your panels into place in the designer…auto-add the line of code to add the panel to the page…in the supporting page class.
6. Validation – warn when the markup does not match the page’s class hierarchy.
7. Markup Inheritence – Visual Studio 2005 has a feature that would be very helpful for Wicket support in MyEclipse…Microsoft calls it “Master Pages”. You can see the page you’re deriving from in the designer, drag/drop page widgets, etc.
8. Widgets/Form Controls – when a widget is dragged onto the page…the matching add() call is added in the appropriate place in the page’s class file.
There is a seed project, called Wicket Bench:
http://www.laughingpanda.org/mediawiki/index.php/Wicket_Bench
I personally don’t like this plugin because it isn’t integrated w/ MyEclipse…and it’s fairly crude. It doesn’t do *much*.
Thanks!
