> > I think there are various levels of solution depending on what our goals > are. My starting goals are relatively modest, which is to make it easier > to style what we have, and to be able to style the widgets a bit more. CSS > just happens to be an existing well known format for doing the former. I > think it also raises our expectations of what our UIs should look like, > which is healthy, and pushes on the second point.
Yes, I agree. We should always start with a simple solution. > > What you're describing is even more advanced, but I think we could do the > same with a declarative model in conjunction with CSS, no? Yes, it is. > Granted XAML > has a certain elegance in combining the two. Then again, we're going to be > able to something similar with the modelled workbench, so at the part > level but not the individual widget level. I'm not sure control level > replacement is a problem we're in search of a solution, is it? > The purpose of my description is to give your an idea about the capability of a XML online style definition. Yves > Kevin_______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
