Hi Camille. 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.
Brian. > On 2-Mar-2015, at 8:48 AM, LETAVERNIER Camille <camille.letavern...@cea.fr> > wrote: > > Hi all, > > 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 [1], but it is distributed under > the LGPL License, so it is not an option). > > So we’re now seriously considering the Phloc CSS Parser [2], 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. > > [1] http://cssparser.sourceforge.net/ <http://cssparser.sourceforge.net/> > [2] https://code.google.com/p/phloc-css/ > <https://code.google.com/p/phloc-css/> > > Regards, > Camille > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > <mailto:cross-project-issues-dev@eclipse.org> > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
