Community
Participate
Working Groups
Basically, mimic Java Swing's ability to render HTML in labels and tooltips by simply putting HTML <html> tag at the beginning of the text, then use any valid HTML in the remainder. For threading reasons it is not always possible to embed the Swing bridge or browser component into a label or tooltip
This has come up before and the answer has been, "Use the browser widget". Grant, can you please find the duplicate?
I am sorry, but that seems very "heavyweight" for something that is suppose to be very lightweight that could be used with tooltips. Also, does the browser get a prefered size based on the HTML string. We tried using the browser widget and I am sorry but it is a sub-optimal solution at best. Why is their pushback for something simple, lightweight and efficient?
The "heavyweight" arguement was used before. Do you have some statistics that show that memory usage is up or a benchmark that is slow? You tried using the browser and failed. Why? Was it preferred size or were there more things that were wrong?
Created attachment 104565 [details] SWT snippet of an HTML tooltip
(In reply to comment #4) > Created an attachment (id=104565) [details] > SWT snippet of an HTML tooltip This example was example of the approach to use the SWT browser widget as lightweight tooltip. The aesthetic results were less than pleasing and was very klunky looking.
Perhaps ui forms is what you are looking for?
We have used the UI Forms plugin for several of our Views and Editors. It is a very nice addition to the UI toolkit. However, in this particular case it is not what I am looking for in this situation. The UI Forms packages is not an HTML renderer. It does have some HTML-like layout capabilities, but it does not support even close to an HTML set of keywords. I think people use to developing in a Java Swing UI got very use to putting HTML labels into tooltips. Are there any open source HTML renderers that Eclipse good leverage to provide this functionality?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
