Objet : Re: [cross-project-issues-dev] CSS Parsers Eclipse
Hi Camille,
+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
Hi Camille,
+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
-project-issues-dev] CSS Parsers Eclipse
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
On 2 Mar 2015, at 14:48, LETAVERNIER Camille 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
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
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.
