Search results

Jump to navigation Jump to search
  • ** Extensions API documentation, python, c++, gitlab... (jnweiger) *** New API, document as one learns.
    2 KB (275 words) - 17:26, 12 September 2018
  • ...werful enough to make complicated effects. Because of the small and simple API, it is possible to make an "LPE develop package" with only a few header fil
    2 KB (277 words) - 22:44, 21 July 2014
  • ...instead depending on how http is used, as data provider or as some kind of API to create/modify SVG files)
    776 bytes (92 words) - 10:07, 29 March 2018
  • * API documentation is spotty * API is not yet stable and subject to major changes
    2 KB (268 words) - 18:07, 15 July 2006
  • ...th cairo, Cairo needs to support ICC. This is an intent to propose a Cairo API that would be suitable with inkscape needs. We can get inspiration from the lcms api [http://www.littlecms.com/LCMSAPI.TXT], in particular the cmsCreateMultipro
    4 KB (674 words) - 10:17, 31 March 2012
  • ...K+ 2.20 library API. Ultimately, we will need to switch to the new GTK+ 3 API. This version of the library introduces a number of major changes that are ...e Gtk+ 2 -> Gtk+ 3 migration, we should aim to stay as up-to-date with our API usage as possible... i.e., eliminate [[#deprecated symbols]] as soon as pos
    3 KB (533 words) - 12:24, 6 March 2017
  • * Add alternate input device via joystick API
    800 bytes (119 words) - 07:52, 11 February 2009
  • This is maintained by Inkscape developers, and is not yet a stable API. * Stabilise the 2geom API
    5 KB (830 words) - 11:58, 13 April 2016
  • ...as a proposal and a discussion platform for outlining a "'''quick drawing API'''" in Python. The purpose of this page is to summarize the needs of end-us Before setting up the "API", I'd like to give an example of what I envision using pseudo-code. Excuse
    4 KB (574 words) - 16:44, 9 July 2009
  • === New Statusbar API ===
    4 KB (688 words) - 05:49, 13 July 2016
  • - Use new GFile API instead of depreciated GNOMEVFS
    1 KB (185 words) - 16:41, 2 December 2011
  • *** to Quartz-backend specific API. *** to ATSUI-backend specific API.
    4 KB (577 words) - 09:20, 24 March 2010
  • * [[#extensions-api|Extensions programming interface updated, with many new options]] - ''Note:
    1 KB (183 words) - 13:59, 2 May 2020
  • * Flesh out each category of functions in the API with ideas for what the functions should be ** Extension API Definition
    7 KB (1,038 words) - 19:51, 3 February 2023
  • * [[#extensions-api|Mise à jour de l'interface de programmation des extensions, avec beaucoup
    2 KB (250 words) - 20:08, 4 May 2020
  • === Python API === ...ew functionality described above should be gradually exposed in the Python API, so that Inkscape's extensions can call lib2geom directly instead of routin
    9 KB (1,330 words) - 17:16, 12 June 2022
  • ...slightly perverse idea might be to use the Ruby interpreter's excellent C API for this purpose. But that's just one idea. plugin API has supported all of this for years. Sadly, [[The Gimp]] did not at the beg
    5 KB (820 words) - 14:53, 26 December 2012
  • ...in working on the python extensions would be to improve the Python plugin API ** How will changes to the API affect existing effects ?
    10 KB (1,584 words) - 15:21, 11 January 2007
  • ...abling extensions to have more ability. E.g. Boolean ops. Via Dbus, Python API, ...
    2 KB (244 words) - 14:57, 15 June 2016
  • ...settings, snap settings, etc. On the application side, it should expose an API similar to Inkscape::Preferences. Some implementation details could be shar ...internal architecture as part of GSoC2009 node tool rewrite; External tool API not started
    5 KB (762 words) - 06:48, 14 August 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)