Closed GoogleCodeExporter closed 9 years ago
Sorry, can't reproduce here in a plain Indigo Java EE installation. Please
check if your markup editor is set correctly (Preferences - General - Editors -
File Assoc - *.html)
What is happening when Ctrl clicking the wicket:id? Is there any error log
(Window - Show View - Error log)?
Original comment by count.negative
on 18 Nov 2011 at 9:31
> Preferences - General - Editors - File Assoc - *.html
I have changed association for *.html from default JBoss Tools HTML editor to
HTML Editor, but it does not have effect.
> What is happening when Ctrl clicking the wicket:id?
The binary class file (Jade disassembled view of the class displayed) is opened
instead of HTML editor.
Original comment by pra...@orangecap.net
on 20 Nov 2011 at 11:40
[deleted comment]
Could you please hold the ctrl key and do a mouseover the wicket:id. Is there a
little box showing:
Open Declaration
Open html file an jump to wicket:id ""
Original comment by count.negative
on 21 Nov 2011 at 9:45
> Could you please hold the ctrl key and do a mouseover the wicket:id.
With ctrl key and mouseover it underlines the id.
If mouseover without ctrl it shows box with HTML fragment in a tool-tip style
window.
Instead of navigating to HTML editor it enters Jade viewer of the class byte
code.
> Is there a little box showing: Open Declaration Open html file an jump to
wicket:id "
NO
Thanks for the support!
Pranas
Original comment by accou...@seopilot.com.au
on 22 Nov 2011 at 2:26
Ok, now I see. If clicking on a wicket:id in html, qwickie tries to find the
corresponding java source code. If you've written the source code for yourself,
then eclipse returns the source. But if you have a html component that comes
from the wicket.jar file itself (e.g. focus-tracker or focus-restore) then
eclipse returns a ResolvedBinaryType. That means it will open it with the
*.class file viewer (in your case the Jade viewer).
So, if you're working with maven, try to right click on the wicket.jar file and
click download source. Then you'll see the wicket source code.
I assume, the corresponding wicket component for your wicket:id is in a
compiled jar file - right?
Original comment by count.negative
on 24 Nov 2011 at 8:09
I see there is some slight misunderstanding. The there are no problems
navigating from HTMS to Java, but it is not working as explained from Java to
HTML.
I guess Groovy or JBoss plug-ins on my environment have some negative effect on
qwickie.
Anyway, it is already great for me to have ability to navigate from HTML
template to the corresponding Java file location.
Thanks again!
Original comment by marylove...@gmail.com
on 24 Nov 2011 at 9:41
Do you have an example code snippet? I'd like to investigate a little bit more.
So, please let me know if a ctrl mouseover shows a little context menu like in
the attached image.
The default click action here is to open the declaration of the java file.
Maybe I can change this, but I need to know some more details about this
bevahior.
Original comment by count.negative
on 24 Nov 2011 at 11:41
Attachments:
Original comment by count.negative
on 11 Dec 2011 at 8:48
Original issue reported on code.google.com by
accou...@seopilot.com.au
on 18 Nov 2011 at 1:05