Community
Participate
Working Groups
Build Identifier: rap-runtime-1.3.0-R-20100615-1734 As Tim suggested (https://bugs.eclipse.org/bugs/show_bug.cgi?id=314421#c5), I open a separate bug for the missing CSS for Tree: I checked the "Themeable RWT Widgets" section of the rap-tooling-1.3.0-R-20100615-1734.zip help and have seen that the following CSS classes, properties, states or styles that I would need are supported by Table but not by Tree: Exist Does not exist Properties, Styles, States Table-Cell Tree-Cell <at all> Table-GridLine Tree-GridLine <at all> TableColumn TreeColumn color, font TableItem TreeItem :even, :hover Table-Checkbox Tree-Checkbox width Could you please estimate if and when they would be available? Reproducible: Always
I changed the title because I think this bug is about an alignment of the CSS capabilities of Tree and Table. Replacing a Tree with a Table or vice-versa is probably a common use case and it should be possible to use the same CSS rules for both widgets with the same outcome. (In reply to comment #0) > Could you please estimate if and when they would be available? I'm sure that we can fix this bug for the 1.4 release but I can't say in which milestone.
Have you decided yet in which milestone you will fix this? I am only asking because I need to make a decision: my deadline seems to be shortly after 1.4M2 (17.09.10), so will they be available in M2?
Bogdan, I'm sorry to say, but it is very hard to schedule such a thing. The new client side Tree implementation still needs some additional improvements (see bug 320597). As Ralf said, we will fix it for the 1.4 release for sure.
For my own convenience, i'll open seperate bugs for these issues. @Bogdan B.: There is a good chance this will be fixed in M2, but no promises.
Sorry, was closed by mistake.
Fixed in CVS HEAD. The only difference is that Tree-Checkbox has "margin" property instead of "width".
(In reply to comment #6) > The only difference is that Tree-Checkbox has "margin" property instead of "width". Although I agree that a "margin" property is better than "width", I don't think that this difference between Tree and Table is acceptable for end users. IIRC, "width" has been used since we wasn't able to measure the sizes of theming images back then. Now, since image sizes are available on the client, margin offers more flexibility. How about adding a "margin" property to Table too, and deprecating "width"? We should still support "width" for compatibility, but using the new property would override the old one.
Completely agree with you. +1 for deprecating "width" in Table and introduce additional "margin" property.
Added Table-Checkbox "margin" property as suggested in comment #7.
