Search results
Jump to navigation
Jump to search
- == Implement Color Management API for Cairo == ...Cairo in the distant past to create a well-thought out and well-documented API plan[2], and there has been some preliminary experimentation work[3] and a36 KB (5,534 words) - 15:26, 3 June 2021
- ...Note however that you should use the GLib/GTK functions rather the Windows API whenever possible.17 KB (2,711 words) - 19:03, 25 October 2017
- *[[Statusbar API]]7 KB (824 words) - 19:20, 21 May 2024
- ''** Gtkmm4 requires API changed Glibmm, Cairomm, and Pangomm. In particular, enums use child namesp7 KB (723 words) - 02:12, 2 May 2024
- ...orms used camel case, including the Microsoft Windows API, Apple Macintosh API, etc. [[User:JonCruz|JonCruz]]18 KB (2,892 words) - 17:59, 15 September 2018
- ** The .h file represents the public API, or promise of functionality.10 KB (1,523 words) - 10:05, 6 January 2012
- ...encing them is not via stock ids, but rather name ids (which are different API calls for gtk widgets that use icons)10 KB (1,593 words) - 01:00, 20 January 2021
- .../j2se/1.4.2/docs/api/java/util/prefs/Preferences.html new Java preferences API added in 1.4]. They currently store to a dir/dir/xml tree on Linux, and to11 KB (1,819 words) - 18:19, 4 January 2012
- * Extension system improvements: Refactor the extension API. Clean up the kludgy class hierarchy, possibly using multiple inheritance.9 KB (1,393 words) - 12:16, 11 March 2023
- ...h.cpan.org/~twh/GD-SVG-0.28/SVG.pm GD::SVG] allow any perl script using GD API to render graphics to render SVG using cairo instead of traditional GD bitm11 KB (1,518 words) - 12:00, 15 March 2016
- * Documentation ([http://developer.gnome.org/doc/API/2.0/pango/ Man]) * Different function calls / changed API12 KB (1,947 words) - 17:50, 3 December 2011
- === API changes for extension developers === ...will continue to work for the time being but should be updated to the new API. Selection is now a type of <code>ElementList</code> which provides filteri69 KB (10,329 words) - 16:27, 25 May 2021
- ==== API Changes for Third-Party Extension Developers ==== * The '''Page API''' has been reworked to make adding or querying page information more inuti58 KB (8,836 words) - 21:46, 11 November 2023
- === API changes for extension developers === <!--T:155--> ...will continue to work for the time being but should be updated to the new API. Selection is now a type of <code>ElementList</code> which provides filteri71 KB (10,737 words) - 11:48, 2 February 2022
- * Improve the functionality and ease of use of the python effects API (see my proposal in the [[ImprovingPythonExtensionAPI]] page )13 KB (2,023 words) - 19:25, 29 February 2012
- ...ublic API. In some cases there may be doxygen in the .cpp file for public API functions - this should move to the header.24 KB (3,789 words) - 17:02, 31 August 2023
- === Änderungen der Erweiterungs-API für Entwickler === ...will continue to work for the time being but should be updated to the new API. Selection is now a type of <code>ElementList</code> which provides filteri70 KB (10,340 words) - 16:31, 25 June 2021
- ==== API Changes for Third-Party Extension Developers ==== ...features have been added to inkex, including a new Style API, a new Units API, support for multipage documents and more.101 KB (15,012 words) - 14:25, 17 May 2022
- ...g them is possible. The advantage of the façade transformation is that the API exposed by the large class is unchanged.15 KB (2,458 words) - 16:24, 23 December 2023
- ...of global functions directly manipulating an XML document, the preferences API is now exposed through the <code>Inkscape::Preferences</code> singleton. It ===Extension API changes===50 KB (8,333 words) - 11:06, 25 November 2009