- Cmake vs waf update#
- Cmake vs waf code#
I've summed up some of the discussion in two wiki pages: Accessible Graphics and Language Support. Adding language metadata (so that screen readers know what they're reading, but also for other benefits).Making it easy to add common ARIA attributes (Didn't really discuss this).Tav has pushed a fix - the text will be saved as aria-label attribute. Automatically generating alt text when converting from Text to Path.She is available Monday afternoon and/or Tuesday to talk to us about how we can make it easier in Inkscape to make accessible SVGs. (Krzysztof) Join LPEĪmelia Bellamy-Royds, an SVG WG member, will be giving a talk at LGM on making SVGs accessible.
Cmake vs waf code#
Identify clever geometry code which can be cleaned up and moved to 2Geom. Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM). Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Things like Inkscape::UI::View::View are excessive. Unnecessary profileration of namespaces (Krzysztof). Use newer Pango-Cairo text/glyph APIs ( ). Stop using Poppler internals, use the proper API via poppler-glib ( ). Change how we're utilizing 3rd party libraries (Josh). Removing 3rd party Library dependencies from version control (AV). How do we handle canvas flickering/rendering issues? Alex working on clean-up. Gtk+ 3 migration (AV) GTK3 missing some functionality. Adding a hard Cairo 1.14 dependency (AV). Moving to C++11 (AV) Alex adding tests to code base. We could discuss what to do about this.Ĭan we decide on a roadmap to work with new APIs and compilers? How do we minimize breakages for downstream users? Can we balance risk with reward? How does each migration benefit the developers, package maintainers and end users? The current approach makes it impossible to introduce errors thatĬause the XML and the SP tree to go out of sync, at the cost of The rendering tree, even though almost nothing changes. Cmake vs waf update#
Each of those update calls updates the rendering tree in turn.Īs a result, changing the document height triggers a full update of. `linux perf` can be used to identify performance critical functions. Better, easily referenced API documentation. 
I've noticed that we suffer from "cargo cult programming" where people add functions without fully understanding if they are truly needed. Having well defined diagrams will allow developers to clean up existing code and to better understand what needs to be done to add new features. Comment: Deleting an item causes Inkscape to create a new SVG document with containing the deleted item to allow pasting.Īdd a few random print statements in Inkscape and you'll see that Inkscape visits certain functions more often than one would think it should.Diagram how Inkscape behaves/should behave on:.When do we add things to the GUI? Earlier, the better with SVG 1.1 export.How do we handle fallbacks? Use Visitor's Pattern Code is tightly bound to Inkscape, must be internal.
Overview/rundown of relevant new SVG2 features. Selection - boost multiindex NOT STARTED. 4.5 Hardware Acceleration Experimentation (Bryce). 4.2 Harfbuzz: Better CSS support and User Fonts (WOFF). 3.11 Design new plugin/extension system.
0 kommentar(er)
