_gui-text: This will be the label of the UI element so add a self explanatory copy.type: By default, Inkscape offers a very small set of GUI options: strings (textfields), interger(numbers field from 1 to 10), float(decimal numbers field), booleans (a checkbox selector), enum (a dropdown list), optiongroup (a multiselect), color (a colorpicker), desc (a free text ) and notebook (a tab selector ).Set an easy name because it will be used in your script to get this param value Lets see a basic example: Some default text Will the user need a textfield? A range selector? Tabs? We will use the user options in our python script afterwards. Here we will set the UI of our extension. If this file does not exist the extension will not be loaded. Here you should add the relative path to your python script (.py) file. This ID should be unique, you could just replace ‘ ’ with ‘ _name’. Remember, this will become the name in the UI button so add a nice name. The XML definition since this file is a valid XML Open your text editor, we are going to get our hands dirty! This post is a basic explanation about how I developed a couple extensions for Inkscape not being myself a python developer (actually, I had no idea about python). So I decided I should learn how to make extensions to get same same features as others have but still using open source software, push forward OSS alternatives and hopefully, help other designers to come to OSS, use it and even develop their own extensions. Ironically, people are developing open source plugins and patches for proprietary software. There are a lot of math-related thinguies here (which is great) but not the extensions that I was looking for as a designer (something like this). While using Inkscape for advanced design work I found out that is mostly used by non developers, so its extensions are made by developers, for developers. So we decided to go with Inkscape, it was very know, enough powerful and we had some previous experience with it. Since we only use open source software for our front and back end coding stuff, it made sense to use an open source tool as well for our design process. We wanted Taiga to be truly as the Taiga team is, and it required to fully understand the soul behind it. When we started developing Taiga at Kaleidos, we decided, for the first time, to design the product internally instead of hiring an external designer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |