- Inkscape Devel - Inkscape Mailman

Inkscape gtk-3.0 Themes
by Partha Bagchi 17 Nov '14

17 Nov '14

I built Inkscape with gtk+-3.0 support. Now I am trying to test it with themes such as DeLorean-Dark-3.14. Is the current gtk+-3.0 support have theming support? No matter how I do it, Inkscape does not honor gtk-3.0 theme. I put gtk-3.0 folder with gtk.css in the etc/ folder within Inkscape installation. I also tried share/themes/gtk-3.0/ etc. Of course, I could be doing something totally wrong. Win64 8.1 etc. with gtk+-3.14.5 (or 3.15.1 doesn't matter) and glib-2.42.1 and revision 3708. Thanks in advance, Partha

1 1

Shared Access to Project Credentials
by Bryce Harrington 16 Nov '14

16 Nov '14

[ If you aren't maintaining services for Inkscape and have no interest in doing so in the future, you can stop reading here. :-) ] For the Inkscape project, a number of us have set up various online services. In some cases the services allow team management, and each of us has our own account; in others we have a single admin account which we share. For these shared admin accounts, we now have a way to securely share the credentials amongst ourselves, using GNU Privacy Guard (aka GPG), and stored in a bzr repository: % bzr branch lp:~inkscape.dev/inkscape/credentials Don't panic! There's only a handful of gpg and bzr commands you need to know to use this, and I've written them up in Cookbook format in the included README: http://bazaar.launchpad.net/~inkscape.dev/inkscape/credentials/view/head:/R… The directions are from a Ubuntu perspective -- please help expand the README with the appropriate commands for other systems. Drop me a line if you need help. Bryce

1 0

Mirror Symmetry Improved
by Jabiertxo Arraiza Cenoz 15 Nov '14

15 Nov '14

He Here are a screencast of the merge feature added to the experimental effect "mirror symetry". This is a example running in a layer but also can apply to other objects. When i have time i made a procedural template and a extension to it for work on a layer, and after, go to Kaleidoscope LPE. https://inkscape.org/en/gallery/item/1970/ Regards, Jabier.

4 5

proposals for website content, including splitting the FAQ
by Brynn 15 Nov '14

15 Nov '14

Hi Friends, As a brief backstory, Martin had contacted me some months ago, asking if I had any ideas for the new website which he'd been developing, and we had some general discussion. That was before the "new" site launched. After it launched, I had some specific suggestions, and contacted him again. He suggested I could use the django editor on the staging site, and create some sample pages, showing the changes I would make. Part of my suggestion was to incorporate some of the wiki content in the site, and that's when he explained to me about how the wiki should now be only for development topics, and most of the user content should either be on the website, or in official documentation. That's when splitting the FAQ into 2 faqs -- a user faq for the website, and a developer faq for the wiki, came up. So now I have those proposed new pages finished, and as well, the FAQ has been overhauled, and split in two. And below is the info. I'm not quite sure how the process works, for approving these kinds of things, but Martin said to post to the dev mailing list. So here are the results of all my work. Oh, I should also say that after I started all this work, I noticed this bug report, suggesting some of these changes: https://bugs.launchpad.net/inkscape-web/+bug/1274098 I still haven't figured out exactly how bug reports are handled, or who decides on the Importance, Status, etc, so I just added a comment that I was working on some of it. OK, here we go. 1 - My proposed new Community page: http://staging.inkscape.org/en/brynntest/ (Now includes all Inkscape forums, which are part of the community.) 2 - Since the listing of external galleries was so long, I put them on a new page. It's found via text link, in the 2nd sentence in the Gallery section of Community page. This is that page: http://staging.inkscape.org/en/brynn-community-pg2/ They all came from the old wiki Galleries page, which was disorganized and quite outdated, with ~ 40% bitrotted links and several spammish entries, which weren't even Inkscape related. (I'd give a link, except I deleted all those entries, after moving them to this page, on Martin's instruction.) This new list is more organized, and current. Should the page be approved, I intend to keep it up to date and organized. 3 - After moving the list of forums (from Learn page) to Community page, the Learn page would now look like this: http://staging.inkscape.org/en/brynns-learn2/ Very short page, and somewhat boring, imo. 4 - To make it more interesting, I added sort of a teaser, using a bit of content from some of the pages. That proposed new Learn page looks like this: http://staging.inkscape.org/en/brynns-learn-page/ However, what I think would be better, is to use some kind of imagery. Maybe we could find, or someone could draw for us, some clipart. Actually, for a website which promotes a graphics program, inkscape.org seems *to me* practically devoid of graphics (except of course for the front page and gallery). I think it would be nice to incorporate some Inkscape graphics on each page -- either as clipart, that is designed to help with the flow of the site (sort of like a theme, I guess); or just have an image on each page (maybe a script could call up random images from the gallery). But I'm getting off track. Just a thought :-) 5 - Here is my proposed new FAQ for Inkscape Users: http://staging.inkscape.org/en/brynns-user-faq/ It's been seriously overhauled -- several items deleted from the original, which are no longer needed; another several new ones added; re-organized; and a TON of useless html code was removed. Note that I changed the numbering system, to more of an outline style, because I think it looks better. But I did a bit of research, and found a way to keep the same numbering system, and still look better. It's just that it involves editing the CSS/style sheet, and will take me some experimenting to get it right. So I decided to use the outline style, and I can work on the other system, if there is an outcry for the old numbering system. There are still 2 issues left, before the user faq is complete. 5a - There are 5 bitrotted links, which need to be updated. The list is attached: "bitrotted-links-in-InksFAQ.txt" In a previous message, Bryce said he thought he could track them down. (Actually, only 2 for the user faq. 3 are for the dev faq.) 5b - 5 wiki articles which need to be put into some kind of documentation. The list is attached: "2b-documented-for-InksFAQ.txt" I'm still not clear how documentation is handled, so I can only provide the list. Unfortunately, I don't have the technical knowledge to write any of them myself -- except for just copying and pasting somewhere else. I assume they would need to be reviewed and updated, for accuracy, and none of those topics I happen to know, inside-out. (Related to this, I would be glad to make a listing of all user-related content that I can find, in the wiki. I've already had a look at a lot of it. But since I don't understand some of it, I would need some suggestions from more knowledgeable folks, about what to do with it (i.e. delete, put in documentation, or leave in the wiki for devs). But let me know. I'll be glad to help with any of that, if I can.) 6 - After removing the user-related parts, this is the new proposed FAQ for Inkscape Developers: http://staging.inkscape.org/en/brynn-dev-faq/ I used the django editor, but I guess it would ultimately belong in the wiki. I'll be glad to transfer to the wiki, if it's approved. Just lmk :-) Note that I was not able to update any of the developer topics section, because I'm just not knowledgeable on those. As it turns out, 3 of the 5 bitrotted links, in the attached list, are for the developer faq. It may be that they are no longer needed; I just don't know. But that's all that is outstanding, to complete it. Any and all comments or suggestions are welcomed, and especially any typos. I must have proof-read 4 or 5 times, in the end, but I still could have missed some. I appreciate the opportunity to contribute more to the Inkscape project than just answering messages in forums. And if any of my limited skills can be useful, I'll be glad to continue to help. All best, brynn

6 8

RenderTests WRT python
by Martin Owens 13 Nov '14

13 Nov '14

Johan E, I've looked at the inkscape-rendertest branch. There is a pdiff codebase and a few other bits, but I notice no use of Pillow(was PIL) to process the images. We have access to PIL.ImageChomp to select the difference rectangles and further processing (with some good guides online) for pulling out more information if we need to. http://stackoverflow.com/questions/1927660/compare-two-images-the-python-li… If we went with pdiff instead of Chomp and CMP in python, was there a reason? Thanks for your time. Best Regards, Martin Owens

3 5

Looking for Code Inefficiences
by Natalie Sanders 11 Nov '14

11 Nov '14

Hi All! I'm new to the community and I'm looking to improve any code inefficiencies, especially inefficient data structures. Do you have any suggestions on where to start? Thanks! Best, Natalie -- Natalie Sanders University of Notre Dame Class of 2016 Computer Science Major

3 2

Good Introductory Bugs
by Kathryn Weiss 11 Nov '14

11 Nov '14

Hello, I am a relatively new programmer. I am looking to gain some coding experience and I am interested in developing Inkscape. In particular, I am looking at trying to fix bugs or improve performance related to data structures. I was wondering if anyone had advice as to specific areas that need this sort of work. Thank you for your help! Sincerely, KW

3 2

Testing related
by Josh Andler 11 Nov '14

11 Nov '14

Hey all, There has been quite a bit of discussion over the past couple months related to testing. Thanks to an inquiry from someone interested in helping us improve Inkscape, it was a reminder that we have a mailing list which used to be dedicated to the topic. https://lists.sourceforge.net/lists/listinfo/inkscape-tester In looking back in the archive, there were regular posts from automated builds of Inkscape which would provide compilation warnings and errors encountered during the build. It seems like it would be great to get the results from Coverity, automated builds, and the test framework (whatever we end up with) posted there. Any thoughts on us doing this? Cheers, Josh

2 1

Feature Freeze for 0.91
by Bryce Harrington 09 Nov '14

09 Nov '14

3. Frost. √ Experimental Branch is forked √ Mainline Branch focuses on stabilization √ Only production-ready code committed to Mainline √ Post inkscape-0.91-pre0.tar.gz √ Finalize any major changes to platform packaging √ Release Notes should be >90% filled in. √ Inkscape must pass >90% of 'make distcheck' √ Start an About Screen contest √ General Bug Hunt: 1500 points √ Post additional inkscape-0.91-pre*.tar.gz releases √ Packagers test creating pkgs of the -pre* releases 4. Feature Freeze √ Stable Branch is forked from Mainline Regular development resumes on Mainline. Avoid major refactorings on Mainline. Only bug fixes committed to Stable Branch. Bug fixes are cherrypicked from Mainline. Inkscape must pass 'make distcheck' String Freeze No further string changes allowed on Stable Branch. Finalize tutorials to be shipped with release Finalize other docs included in the release Finalize about screen Finalize Release Notes except Known Issues Translators work on translations. Recruit Release Wardens for Hard Freeze Inkscape has completed the Frost phase and is moving into Freeze. Translators, please fire up your engines! You have (at least) until Nov 18th to commit translation updates to the stable branch. ------------------------------------------------------------------------ A stable branch lp:inkscape/0.91.x has been split off of trunk. Only strict bug fixes and translations may be committed to this branch; for anything else please seek release manager approval (Josh or Bryce). # Stable branch bzr clone lp:inkscape/0.91.x inkscape-0.91-stable You will need to check this out only if you intend to check in fixes to the stable branch. IMPORTANT: Do not make changes to translatable strings in the stable branch. If it is critical that a string change be made, please get approval from the release managers first! ------------------------------------------------------------------------ The lp:inkscape branch (trunk) is now open for regular development towards the 0.92.x series. # Development branch bzr clone lp:inkscape You don't need to do anything with your current branch if you just want to keep committing to the development branch. Congrats to everyone that helped us get this far, Bryce

8 22

Merge of experimental branch
by Liam White 06 Nov '14

06 Nov '14

With Bryce's permission, I have merged the experimental branch into trunk. Trunk is now open for development. Please do not make further commits to experimental. If you do not use a separate directory for build and source: > $ bzr pull lp:inkscape … > Conflict: can't delete src/dialogs because it is not empty. Not deleting. > 1 conflicts encountered. > Now on revision 13641. > $ rm -rf src/dialogs > $ bzr revert This should fix your local copy.

9 24