My favorites | Sign in
Project Home Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 17: Improve wicket page work
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Jun 2011

Sign in to add a comment
Reported by, Feb 20, 2011

First, thanks for qwickie. Young but already usefull ;).

I have an idea of improvement which can greatly help the work on wicket pages :
When opening a page element (.java, .html, .properties), rather than opening the default associated editor, open one Editor which contains sp├ęcialized one in tab, one for "source", one for "html" and one "properties".

For user it mean, open one element and all the page component are together in the editor ;)
Feb 26, 2011
Project Member #1 count.negative
Like in I won't do this. To use multiple tabs, just have a look at wicket bench

Status: WontFix
Feb 26, 2011
Wicket bench is a dead project now.
Your link is broken too.

from :
"Wicket Bench is an Eclipse plugin for Wicket. Due to the lack of maintainers for the plugin the codebase has been forked and it has been moved to a new sourceforge project. Ideas & help are more then welcome."

But, the sf project is empty, no realease, no changes :

So at this time, qwickie is the only Wicket eclipse IDE integration project alive.
Feb 28, 2011
Project Member #3 count.negative
KnowI know. This was one of the reasons for me to write qwickie ;-)
Jun 3, 2011
Can you at least add some kind of Wicket-Template so that you can create a new wicket-class and it also generates the corresponding html file for it? It also would change both when you refactor the name.
Jun 3, 2011
Project Member #5 count.negative
Hm, that would mean a new eclipse wizard for wicket pages. Sounds possible. 
Status: Accepted
Labels: -Type-Defect Type-Enhancement
Jun 4, 2011
Project Member #6 count.negative
see 0.8.3
Status: Fixed
Sign in to add a comment

Powered by Google Project Hosting