Nick, biggest problem was "RTFM". Most plugins in IJ don't need to be "activated".
I didn't realize that there were more steps than "install plugin" :) Any chance you can just auto-add the Wicket module? If it's "heavy", then at least add the comment to the plugin description like: " WicketForge assists developers creating Wicket applications. To activate for a given project, add to modules. See http://code.google.com/p/wicketforge/wiki/UsageInstructions for details on how to do so. This plugin... " I added the module, now I can jump b/w the declarations etc. The html editor still complains about wicket:id tags, of course. Which makes the 20 fake errors in html errors cover up the REAL error of non-matching wicket:id to code. But I am sure you know about that already. Would love to help you with patches, but I know NOTHING about IJ plugin development :( Drop a line in the forum when you release, please! -----Original Message----- From: Nick Heudecker [mailto:nheudec...@gmail.com] Sent: Sunday, November 15, 2009 5:57 PM To: users@wicket.apache.org Subject: Re: Intellij9 integration >From my experience, WicketForge already displays a warning if the components can't be located in the HTML or Java code. Toggling between Java and HTML also works fine for me. You can either submit a bug report or a patch. Also, feel free to submit a patch with templates you'd like to see added to WF. I'm getting ready to release 0.5.7 this week. On Sun, Nov 15, 2009 at 11:49 AM, Alex Rass <a...@itbsllc.com> wrote: > Would be good if it told you about "unmentioned" wicket:ids from the html > so > you didn't have to wait till you run. > Or if you are declaring a component that it can't find in html. > > Jumping back and forth between code and html d/n seem to work for me. > > Entirely too much typing for my taste! Idea is REALLY good at minimizing on > that. > > Bunch of templates can be written for Wicket programmers to simplify > typical > stuff. > > But yes, a lot of things in IJ work already because wicket isn't a stretch > for java. > > > -----Original Message----- > From: Peter Ertl [mailto:pe...@gmx.org] > Sent: Sunday, November 15, 2009 10:08 AM > To: users@wicket.apache.org > Subject: Re: Intellij9 integration > > Never felt like I need additional support for wicket. After all it's 95% in > type-safe java code. Keeping wicket:id's in sync is no rocket science once > you get the idea :-) > > Am 15.11.2009 um 00:38 schrieb Nick Heudecker: > > > What do you mean that the current one shows up? I haven't updated > > WicketForge to work with IDEA 9 because I'm not on IDEA 9. > > > > Feel free to submit patches. Right now WicketForge does everything I > need > > it to do, so unless I start using Wicket more often or it doesn't meet my > > needs, I'm not really inclined to spend my limited free time on it. > > > > On Sat, Nov 14, 2009 at 3:12 PM, Alex Rass <a...@itbsllc.com> wrote: > > > >> You have a point, but I've been using Idea for... 6+ years now. > >> These guys are very sales oriented. > >> They added GWT support as a point release, like it was a no big deal. > >> When they see there's a demand - they move on it. > >> And if they can add a new popular framework for the launch - they just > may, > >> to make it sell better. They are in a war with Eclipse and "we got that > and > >> it's better" has been their selling angle. > >> > >> But if someone wants to make the wicketidea plugin actually work - > that'd > >> be > >> cool too :) Current one barely shows up and is VERY sensitive. > >> > >> > >> -----Original Message----- > >> From: Andreas Petersson [mailto:andr...@petersson.at] > >> Sent: Saturday, November 14, 2009 5:00 PM > >> To: users@wicket.apache.org > >> Subject: Re: Intellij9 integration > >> > >> i think getting official support for wicket in idea is too late. the > >> roadmap was published about 6 months ago, for example at > >> http://blogs.jetbrains.com/idea/2009/05/maia-eap-is-finally-here/ > >> and there is already a beta version available at > >> http://www.jetbrains.com/idea/nextversion/index.html > >> > >> but maybe it is the right time to give wicketforge some polish. my > >> suggestions for enhancements, since it should be possible to better > >> develop plugins since it is open source now. > >> *) validation of propertymodels/CPM like idea does for expression > >> Language for jsp. ability to ctrl-click to the corresponding getter and > >> "find usages" of those getters > >> *) support for "find usages" for wicket:ids > >> *) central facet for wicket, to control its settings. > >> *) ability to turn off the "non-serializable field in serializable > >> class" warning in components for fields that are injected. > >> > >> br > >> andreas > >> > >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
