RE: [Inkscape-devel] new AST module
Starting today, I'll be working on a new Inkscape::AST module, which will eventually replace the current SPRepr subsystem.
Hurray!!! I can't wait when it's ready! :)
But what does AST stand for?
The goal is to reduce the complexity of the XML code, while allowing for e.g. CSS and SVG path data to be manipulated in the same tree, in broken-down form (rather than as monolithic strings).
And also to automate any and all inheritance and precedence issues, so that we can use ONE function to access the effective value of any property, be it in CSS string or in attribute, no matter how many levels of parents or defs (defs can be recursive, too) may affect it.
_________________________________________________________________ Click, drag and drop. My MSN is the simple way to design your homepage. http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/
On Sun, 2004-02-29 at 16:03, bulia byak wrote:
Starting today, I'll be working on a new Inkscape::AST module, which will eventually replace the current SPRepr subsystem.
Hurray!!! I can't wait when it's ready! :)
But what does AST stand for?
Abstract Syntax Tree
And also to automate any and all inheritance and precedence issues, so that we can use ONE function to access the effective value of any property, be it in CSS string or in attribute, no matter how many levels of parents or defs (defs can be recursive, too) may affect it.
That's something that would have to happen at the SPObject level (or equivalent).
Basically what I'm doing is splitting CSS into a two-layer architecture like XML is currently (and using the same underlying system for both).
The lower layer only concerns itself with keeping the raw document structure straight; it's the layer above that which will worry about compiling/consolidating CSS properties from the various sources according to precedence.
(hopefully we can even leverage the libcroco cascade engine)
-mental
participants (2)
-
bulia byak -
MenTaLguY