|Re: [cross-project-issues-dev] CSS Parsers & Eclipse|
De : cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
De la part de Lars Vogel
+1 for replacing the Batik parser in platform.ui. I know that Paul was looking for alternatives in the past. Please open a bug for it, so that we can continue the discussion.
Best regards, Lars
Platform UI Co-Lead
On Mon, Mar 2, 2015 at 2:48 PM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
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.
Back to the top