Just realized this group was here!
Brian Topping
Minas, the changes you are making with the component hierarchy window
are very interesting. I'd consider making that window dockable
(probably on the left or right side) so it can always be visible.
Being able to click in the hierarchy to either the code or the markup
would be very very handy, especially for files with a dozen or two
components.
Also, I really enjoy what you did with the orange highlighting. It's
not just an unused color in the typical selection of plugins, but it
really stands out without being hard to read. w00t!
To me, a great place to expand things now is with the inspector
(option-return) and code generation (ctrl-n) popups. I don't know
what would be good to put in there off the top of my head, but I use
those things a ton with the Spring plugin, stuff like creating
properties in a Spring bean configuration (XML) and having it create
the setter and placing the cursor right at the name of the parameter.
Follow that with another option-return, and I can create the field for
the setter and assign it automatically. That kind of thing.
Minas Manthos
It's planned to make a toolwindow with hierarchy (pretty like
structure toolwindow) . See http://groups.google.com/group/wicketforge/browse_frm/thread/f5b0f57d184d6f0f.
But first I have to catch most common implementations of wicket
additions in java file, so hierarchy could be build correctly. Only if
this research is successfully and wicketforge switches to hierarchical
we can have these things... :-)
I like the highlighting too. Thanks again for your suggestion and...
you can congrat yourself for this brilliant idea! ;-)
Thanks & regards
Minas.
Brian Topping
On Dec 15, 2010, at 1:22 PM, Minas Manthos wrote:
> I like the highlighting too. Thanks again for your suggestion and...
> you can congrat yourself for this brilliant idea! ;-)
Ideas are cheap, whatever glory is all yours. I'm just grateful for the features, thanks!
Brian Topping
On Dec 14, 2010, at 11:47 PM, Brian Topping wrote:
> To me, a great place to expand things now is with the inspector
> (option-return) and code generation (ctrl-n) popups. I don't know
> what would be good to put in there off the top of my head
Okay, I just thought of one: When I create a <a wicket:id="foo"/> in markup, I usually have to move over to the component and create the "add(new BookmarkablePageLink("foo",...))" in the component. Being able to option-return in the markup immediately after creating the tag, having it jump to someplace in the constructor and create this markup with an active popup menu asking if I wanted a BookmarkablePageLink, Link, Button, etc. would be pretty wild.
*If* something like this was possible, I realize it needs to know about the markup structure, and even then...
Like I said in previous email, ideas are cheap :-)
It would be great if IntelliJ had the IntelliSense to hire Minas to work on this thing part-time...
Minas Manthos
code.google.com/p/wicketforge/issues/detail?id=60). The problem is:
where to add the new component in Java file?... need to make some
research if this could be integrated in a good way...
regards
Minas.
PS I would more like to see that Jetbrains add official support for
wicket.. but thanks anyway ;-)