- Inkscape Devel - Inkscape Mailman

sodapodi?
by C R 23 Jun '17

23 Jun '17

https://www.dropbox.com/s/9tmzwlc2aysxq1j/inkscape_soda_sticker.png?dl=0 Got tea, coffee, and soda. I don't think I'll have time to make a beer one before the hackfest, but it's on the list. Am I missing any other hacking beverages? -C

3 3

Wiki account
by Ben Iofel 21 Jun '17

21 Jun '17

Hello, How can I get a wiki account? -- Ben

3 2

Re: [Inkscape-devel] User Interface files
by C R 21 Jun '17

21 Jun '17

Seems like a great idea to me. Thanks Martin! I believe this will make it much easier to test to tweaks. -C On 16 Jun 2017 03:24, "Martin Owens" <doctormo@...400...> wrote: Dear developers, I've just completed a section of work which you can find here: https://gitlab.com/inkscape/inkscape/merge_requests/15 I'd appreciate a good review of the code, especially for things like memory leaks which I'm particularly weak on. A second point is the removal of ifdefs, which I can't rally do with resource files, but I'm hopping it won't matter (famous last words). I wanted to bring up to the whole community my plans going forward. You can see how I've moved the toolbar user interface XML from being compiled in, to being a file in share/ui. The reason for this, is I want to encourage experimentation on inkscape's user interface, which we can't do at the moment without recompiling the program. With this change, it looks for the ui files, not just in /usr/share/inkscape/ui, but also ~/.config/inkscape/ui so users can generate a set of custom files with their own toolbar buttons ordered the way that they want. It's not a lot of customisation, but it's something to get going with. The future vision is to start pulling some of the complex cruddy widget creation code out and putting that into a meater ui file. I might start with some dialogs like the document properties dialog. These are more interesting, because they have things like signals and anyone editing them needs to be very careful. But if we have good code that has some good error messages and such, a designer could open the ui file in glade and mess about with the widget locations, paddings and a bunch of other visual pieces. What are all your thoughts? Best Regards, Martin Owens ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

5 6

User Interface files
by Martin Owens 21 Jun '17

21 Jun '17

Dear developers, I've just completed a section of work which you can find here: https://gitlab.com/inkscape/inkscape/merge_requests/15 I'd appreciate a good review of the code, especially for things like memory leaks which I'm particularly weak on. A second point is the removal of ifdefs, which I can't rally do with resource files, but I'm hopping it won't matter (famous last words). I wanted to bring up to the whole community my plans going forward. You can see how I've moved the toolbar user interface XML from being compiled in, to being a file in share/ui. The reason for this, is I want to encourage experimentation on inkscape's user interface, which we can't do at the moment without recompiling the program. With this change, it looks for the ui files, not just in /usr/share/inkscape/ui, but also ~/.config/inkscape/ui so users can generate a set of custom files with their own toolbar buttons ordered the way that they want. It's not a lot of customisation, but it's something to get going with. The future vision is to start pulling some of the complex cruddy widget creation code out and putting that into a meater ui file. I might start with some dialogs like the document properties dialog. These are more interesting, because they have things like signals and anyone editing them needs to be very careful. But if we have good code that has some good error messages and such, a designer could open the ui file in glade and mess about with the widget locations, paddings and a bunch of other visual pieces. What are all your thoughts? Best Regards, Martin Owens

2 2

[Reminder] Join Us to Discuss Marketing Inkscape - In 2 Hours
by Ryan Gorley 20 Jun '17

20 Jun '17

Just a reminder to all about this meeting in just over *2 hours *(20:00 GMT): - Online: https://inkscape.org/en/*developer/chat/ - IRC: irc://chat.freenode.net/#inkscape-devel I look forward to meeting you all there! On Jun 17, 2017 8:37 PM, "Victor Westmann" <victor.westmann@...400...> wrote: > No worries! > > We're all team! :) > > Victor Westmann > On Jun 17, 2017 6:07 PM, "Arlo Barnes" <arlo.barnes@...400...> wrote: > >> On Sat, Jun 17, 2017 at 6:28 PM, Victor Westmann < >> victor.westmann@...400...> wrote: >> >>> I was just trying to help publicize this Inkscape meeting even further. >>> >>> That is good! And I did not mean to diminish that, I was just curious. >> Thanks, >> —Arlo >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Inkscape-user mailing list >> Inkscape-user(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-user >> >> > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-user mailing list > Inkscape-user(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-user > >

1 0

Helpful Facebook page reporting
by Robert Sterbal 19 Jun '17

19 Jun '17

Here is a screen print regarding the last 5 posts to the inkscape facebook page: Is there a preferred way to report this? Thanks, Robert Sterbal robert@...3541... 412-977-3526 call/text

2 2

How to change visible selections in EnumParam
by Michael Soegtrop 19 Jun '17

19 Jun '17

Dear Inkscape Team, my bool op LPE has classical bool operations suitable for closed paths and line cutting operations suitable for one open and one closed path. I wanted to adjust the options shown in the EnumParam depending on the path type, but couldn't find out how. Also it would be interesting to know if there is way to know when the path in a PathParam is set, because at this point I need to adjust the options shown. Otherwise I would make the decision on the main path and always require that the operand path is closed (and give a warning if not). Or do you think it makes more sense to have two LPEs, one classical bool LPE which only works for closed paths and one path trimming LPE to trim sets of open paths with a closed path. I think separating the two might be more obvious to the user. Best regards, Michael

2 1

Re: [Inkscape-devel] How to change visible selections in EnumParam
by Jabier Arraiza 19 Jun '17

19 Jun '17

hi: On Sun, 2017-06-18 at 16:54 +0200, Michael Soegtrop wrote: > Dear Inkscape Team, > > my bool op LPE has classical bool operations suitable for closed > paths > and line cutting operations suitable for one open and one closed > path. I > wanted to adjust the options shown in the EnumParam depending on the > path type, but couldn't find out how. Also it would be interesting to > know if there is way to know when the path in a PathParam is set, > because at this point I need to adjust the options shown. Otherwise I > would make the decision on the main path and always require that the > operand path is closed (and give a warning if not). You need a header var "Geom:Pathvector older_pv" asigning it in the end of "do_before effect" and finaly compare it with current path You also need the definition of the header put the select widget to be available in all LPE, for this you redefine the "effect::widget" like in a lot of effects, perspective envelope, Laticce 2.... > Or do you think it makes more sense to have two LPEs, one classical > bool > LPE which only works for closed paths and one path trimming LPE to > trim > sets of open paths with a closed path. I think separating the two > might > be more obvious to the user. Not sure [UX] team? > Best regards, > > Michael Chers

2 1

Some help needed with making operand path invisible in bool op LPE
by Michael Soegtrop 17 Jun '17

17 Jun '17

Dear Inkscape Team, with my recent pull request, the bool op LPE should work properly. A few notes / questions: 1.) The operand (other) path is not made invisible. I typically have my operand paths in an invisible layer. Is this ok, or should the bool op LPE make the operand path invisible? If so, I wonder how this could be done. The main problem is that I have no idea how I could re-enable the operand path when the bool op LPE is disabled (with the eye button in the bool op list). As far as I can tell, the bool-op code doesn't run at all when the bool-op is disabled, only when it is enabled. Or should I change the bool op so that it works on groups of paths (as created with Ctrl+K)? This would obviously solve the problem, but then I would need a grouping LPE, because one of my operand paths is typically a result of an LPE stack, while the other isn't 2.) The cut boolops only make sense if one path is an open path and one path is a closed path. Should I disable the cut options, if this is not the case? How can I detect this? 3.) The LPE only works on paths, not on objects. Is this ok? I guess this is the case for all LPE. 4.) The LPE has options for the fill type (odd-even, non-zero, positive). For the operand path (the other path) I can find out the inherent fill type of the path. The problem is somehow that the fill type is stored in SPItem objects, but the LPEs operator on SPCurve. The closest point upstream in the call stack is SPLPEItem::performPathEffect, but the SpItem is not passed down the the specific LPE code. Any ideas? Btw.: fill type negative would be nice to have. Best regards, Michael

2 2

Marketing/Advocacy/Outreach Team - Proposed Objectives
by Ryan Gorley 17 Jun '17

17 Jun '17

As perhaps a primer to forming a new team to serve the Inkscape project, I would put forward for discussion the following *objectives* for such a team: 1. *Increasing the project's contributor base,* as measured by code commits, non-technical contributions, cash contributions, etc. 2. *Improving the market position of Inkscape*, as measured by user and target-user opinion studies, favorable press coverage, increased usage, etc. 3. *Increasing community loyalty and engagement*, as measured by participation in physical meetups, online discussions, social sharing, etc. Finding consensus about objectives seems more productive at this stage than strategy and tactics. I'd love to hear what you all think or would add/remove/edit. *(Bryce: I had this largely written prior to your response to the other thread, so feel free to steer this conversation in a different direction if you wish)*

7 19