Iâd be somewhat interested from the Platform/UI perspective as Batikâs CSS seems unmaintained, and I think there are some CSS3 selectors that would be useful to bring in. But for us the parser is only part of the issue: the underlying rules engine is the much bigger piece.
_______________________________________________cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
In Papyrus, weâre considering a migration to the CSS version 3 (Instead of the CSS 2.1 weâre currently using). Until now, we were partially relying on the E4 CSS Engine, and the underlying Batik/CSS Parser. However, the parser doesnât support CSS3. Weâve been investigating different CSS3 parsers for Java, and found that all parsers implementing the W3C SAC API are hardly maintained (With an exception for CSSParser , but it is distributed under the LGPL License, so it is not an option).
So weâre now seriously considering the Phloc CSS Parser , which unfortunately doesnât implement SAC (So the translation is not straightforward). This means that weâll have to re-implement most of the engine as well. Are there any other projects interested in moving to a more recent version of CSS? The parser/API is the main concern here IMO, since CSS3 is split into several optional modules (You can simply ignore some of the parsed elements if you donât need to support a given module, but the parser needs to recognize every elements to successfully parse the file).
We also provide an XText editor for CSS (Currently 2.1), but itâs not good enough to be used at runtime, so we only use it as a file editor (especially for Papyrus-specific auto-completion and such). Weâll incrementally update it to support the CSS3 concepts we need, but weâre not planning to go much further.