The dom folder is compilable into a shared object without problems. Did Bob write the whole thing by himself? Parts of the code look generated somehow, e. g. http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/src/dom/ cssreader.cpp Is there any documentation or website about it?
Regards, Markus
-----Ursprüngliche Nachricht----- Von: Martin Owens [mailto:doctormo@...400...] Gesendet: Mittwoch, 26. Februar 2014 17:54 An: Jon Cruz Cc: Inkscape Devel List; Inkscape User Community Betreff: Re: [Inkscape-devel] URI
On Wed, 2014-02-26 at 08:32 -0800, Jon Cruz wrote:
A better task might be to follow-up on Bob's work with the next step and get the DOM exposed.
Sounds like we were all on the wrong page with this one. Several developers seemed to think dom was on it's way out.
Does this mean uri.cpp / uri.h should be depricated? Should uri.cpp shift from using libxml to dom? What does the css parsing mean for libcroco?
Why do we have a giant blob of code, shouldn't it be a library that many people could take advantage of?
Thank fluctuations I put it in a branch though.
Martin,
---------------------------------------------------------------------------- -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel