Erdal has it exactly right — this workbench engine is complementary to the SWT engine and whatever other CSS engines that are out there.
My intention is that we shouldn’t use SWT-based properties to affect changes to the model, but instead expose the model to CSS directly.
By exposing the workbench model, you can define rules that affect the model when other model changes are made. For example, you could define a rule so that certain parts within a window are hidden when the window is in a particular mode (i.e., is tagged):
TrimmedWindow.specialMode Part#my-part-id { visibility: hidden; }
or should only be shown when in that mode:
Part#my-part-id { visibility: hidden; } TrimmedWindow.specialMode Part#my-part-id { visibility: visible; }
This will work regardless of the underlying widget renderers being used.
Brian. If I get it right, there is still a need for renderer specific CSS engines: It seems that this new CSS engine handles "higher level container elements" (modelled elements), whereas it cannot style "low level widget elements" (for example, SWT Buttons).
So, they have to work *together*, no?
_______________________________________________ e4-dev mailing list e4-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/e4-dev
|