- Inkscape Devel - Inkscape Mailman

inkscape-0.91pre2 source tarball
by Bryce Harrington 24 Aug '14

24 Aug '14

Download it at: https://sourceforge.net/projects/inkscape/files/inkscape/0.91pre2/ Tagged in trunk as: INKSCAPE_0_91_PRE2 It would be helpful if packagers could generate binary platform packages from this tarball, and upload them to sourceforge. If you spot packaging problems (like version numbers that didn't get updated correctly, or missing files needed for builds), please raise these problems with me ASAP. If you need assistance uploading packages to sourceforge please contact one of Inkscape's sourceforge admins. Bryce

4 7

Re: [Inkscape-devel] splitting FAQ in 2
by Brynn 22 Aug '14

22 Aug '14

Sorry, I forgot to say this. I looked in the manual for documentation on LaTeX, but it's not nearly as detailed as what's in the wiki. I could simply link to the manual (http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Extensions-Render.html#Extensi…), but then a lot of info will be lost. So in asking about how to handle this kind of documentation, I'm asking how to avoid losing helpful info. Or maybe in this case, the wiki info is outdated? I'm not very familiar with LaTeX. In any case, I'm asking about "some official documentation". :-) brynn -------------------------------------------------- From: "Brynn" <brynn@...3133...> Sent: Tuesday, August 19, 2014 3:02 AM To: "Bryce Harrington" <bryce@...961...> Cc: "Inkscape-Devel" <Inkscape-devel(a)lists.sourceforge.net> Subject: Re: [Inkscape-devel] splitting FAQ in 2 > "These days our documentation is actually quite thorough, and the FAQ > could probably leverage it better. For instance, it could give a brief > answer and a couple hints for the most common things people want to do, > and then "For more detailed information about customizing Inkscape, > please see the <link>Customizing Inkscape</link> chapter of the Inkscape > Manual" (or whatever)." > > As I suspected, there are indeed a lot of user-related pages in the wiki. > For this page: > http://wiki.inkscape.org/wiki/index.php/Customizing_Inkscape, Bryce > suggested: > "I think it's a bit too much for the FAQ. The contents of that wiki page > looks like it really ought to be part of some official documentation, > like the man page or something." > > Now I just ran into this page: > http://wiki.inkscape.org/wiki/index.php/LaTeX (which is linked to faq item > 2.5). I suppose this should be part of "some official documentation" as > well. But documentation, in general, is a part of Inkscape that I'm not > so familiar with. > > Really, the only documentation I know about, is the manual, the official > tutorials, and the wiki (aside from Launchpad and Sourceforge docs). So > my next question, is how to handle items which need to be added to "some > official documentation". Is there a particular person who is in charge of > documentation? I could make a list and give to this person. But then my > work can't get finished, until their work is finished. Well, then maybe I > should handle it myself? But I would need a bit of guidance. I certainly > can copy/paste, and write some html. It's just where to put it, that I'm > not sure. > > Maybe I could make a new page (at first on staging site, of course)? I > would just transfer all wiki content which is currently used to answer > user questions in the faq, to this page, and link to the info there. > > However, I suspect Bryce had something else in mind with "some official > documentation". > > How should I handle this kind of documentation? > > Thanks again, > brynn > > -------------------------------------------------- > From: "Bryce Harrington" <bryce@...961...> > Sent: Sunday, August 17, 2014 12:56 PM > To: "Brynn" <brynn@...3133...> > Cc: "Inkscape-Devel" <Inkscape-devel(a)lists.sourceforge.net> > Subject: Re: [Inkscape-devel] splitting FAQ in 2 > >> On Sun, Aug 17, 2014 at 01:48:24AM -0600, Brynn wrote: >>> Thanks Bryce. >>> >>> "> Similarly, if you follow the user list or the #inkscape user channel >>> and >>> >see questions being asked a lot (and that sound likely to continue >>> >being >>> >asked long in the future), consider adding Q&A's for those." >>> >>> I recently subscribed to the user list, but I didn't even know about >>> #inkscape user channel. That's an IRC channel...or....that's not >>> twitter, is it? (Sorry, I don't participate in the whole social >>> media thing.) However, I'm quite familiar with messages posted in >>> forums, and somewhat with messages posted in Launchpad Answers. >> >> Yes, it's an IRC channel. For more info see the end of this page: >> >> * http://inkscape.org/en/community/discussion/ >> >> Fwiw, the Jabber info on that page is all obsolete I think. >> >>> I'll make a list of the bad links (dead, empty, not found pages) >>> (which I guess is what you mean by "bitrot"), and send them to you. >>> Maybe you can find them somewhere. >> >> Yes, that's what bitrot means. >> >> FWI, I'm on travel this coming week so might not be very responsive in >> the near term, but will catch up once I'm back. >> >> We also have an #inkscape-devel channel, which you're welcome to join as >> well. su_v is very active there and she might be able to help if I'm >> not around. >> >>> Speaking of a listing of tutorials -- would those be only "official" >>> tutorials? Or should all kinds of outside tutorials (such as listed >>> on my webpage) be found on the Tutorials page? Already, there are >>> lots of tutorials from a deviantART feed that Martin set up (which >>> are "outside" tutorials). But with such a listing of outside >>> tutorials, again, you'll have the bitrot issue, and possible >>> frequent requests to be listed. >> >> The FAQ probably should only directly link to the official tutorials >> (the ones that appear in-program). Those are the ones we have direct >> control over and can prevent bitrotting. >> >> I'd love to see more work go into the Tutorials section, but don't have >> specific advice. The Tutorials page doesn't need to be limited to >> official tutorials. I like how Martin set it up to pull from deviantArt >> because then we don't have to worry about bad links on our end. >> >>> "Our >>> >software documentation is also a lot better than when this FAQ was >>> >initially written, too." >>> and regarding the Customizing Inkscape faq item >>> "> There might be a few other FAQ items like this, that should just move >>> to >>> >proper docs." >>> and >>> "Also I think it probably isn't that >>> >'frequent' of a question so once it's in the program documentation it >>> >can be dropped from the FAQ." >>> >>> Are you suggesting that if documentation for an faq item exists, >>> that it should be deleted from the faq? Or that the answer should >>> be deleted, and instead should link to the documentation? >>> >>> Because I think a lot of people, maybe even most people, think of an >>> FAQ for just exactly that "frequently asked questions". Perhaps the >>> faq has been used in the past, as a place for developers to put >>> answers, and for users to find answers, when no other documentation >>> exists. But I'm not sure taking it completely out of the faq would >>> be appropriate, if it truly is asked for frequently. For >>> customizing Inkscape, I can say that it is asked surprisingly often! >>> I've even heard people say they won't use Inkscape unless they can >>> have a customized theme! (Of course, imo, that's their problem, but >>> it is a fairly common topic.) (And btw, easily customizable themes, >>> or "skins", is a much wished-for feature!) >> >> Yes, I completely agree with all of this. It's true that in the far >> past we did put stuff in the FAQ that should have just gone into regular >> docs but we didn't have those at the time. Since then I think a lot of >> that has been scrubbed out. I just want to suggest that if you feel >> there is stuff in there that's a bit too much for the FAQ, then moving >> it into proper documentation is the right way to go. >> >> These days our documentation is actually quite thorough, and the FAQ >> could probably leverage it better. For instance, it could give a brief >> answer and a couple hints for the most common things people want to do, >> and then "For more detailed information about customizing Inkscape, >> please see the <link>Customizing Inkscape</link> chapter of the Inkscape >> Manual" (or whatever). >> >> Bryce >

2 2

I think I have a good compile at last
by john Culleton 21 Aug '14

21 Aug '14

all the various sources I have used for inkscape0.91 blow up at the same point, on a file called threads.h So in desperation I copied this file from Ubuntu to Slackware. The location is exactly the same on both systems: /usr/include.2.4/glibmm/threads.h There are other files on my Slackware partition called threads.h but this is the one Inkscape 0.91 uses. Currently my attempt at a bzr based compile has produced 0.91pre2r13528. The key to that process is to run autogen.sh, then ./configure and make. BTW Inkscape compiles run longer than any others I have done on any system since I worked on tape-only systems in the 1960's. But the results are worth it! :<) -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

4 4

Swatch dialogs improvements
by Tomasz Boczkowski 20 Aug '14

20 Aug '14

Hi! I've introduced some of the improvements to the swatch dialog, that were discussed on the mailing list. First of all the default behavior when applying solid color swatches is to apply them by color value. There's a toggle button added, that allows to switch to the mode in which solid colors are applied by reference to a paint server [1]. Currently the paint server is linear gradient, but since solidColor elements are in codebase, the dialog will use them in the future. Second improvement is related to the appearance of the swatches dialog. Padding between swatches was removed and an option to turn on borders was added [2]. The dialog also supports 16x16 tile size [3]. In this case the tiles representing gradients, patterns and hatches are bigger. Hatch support was added to Swatches dialog and Fill and Stroke dialog [4]. The UI allows to select and apply a swatch. The swatch properties dialog allows to change pitch and rotate parameters. Files containing hatches can be placed in hatches subdirectory in either user config or global config directories. I've used the file [5] containing default AutoCAD ANSI hatches. Because the end of GSOC 2014 is near, I'd like those code changes to be last ones. I'll spend the last days on writing code documentation. Hovewer if you see something that definitely has to be done before monday, please let me know. The project will evolve after GSOC ends. I'll try to make the paint preview more compact. An on-canvas editing tool for hatches will be usefull too. Regards Tomasz [1] https://www.dropbox.com/s/5wh4kojl3puht6i/swatches-link.mpeg [2] https://www.dropbox.com/s/pdp1zefvr7ha1rn/swatches-borders.png [3] https://www.dropbox.com/s/urezznmjgb6s5y1/swatches-small.png [4] https://www.dropbox.com/s/g4d9psnvgfftus3/swatches-hatch.mpeg [5] https://www.dropbox.com/s/nysmx6tl0t4hqf1/ANSI.svg

4 4

splitting FAQ in 2
by Brynn 19 Aug '14

19 Aug '14

Hi Friends, I've been helping Martin on the inkscape.org website. And that somehow has grown to include the wiki. But of course, I'm glad to help. He says user info, such as forums, tutorials and galleries should not be part of the wiki, so that the wiki is only for developers. I've already transferred (and updated!) some of that user-related stuff to a test page for the website (http://staging.inkscape.org/en/brynntest/?edit&language=en). (I think all the galleries need to be moved to another page, but that hasn't been decided yet, that I know of.) (If the Community page looks like that, then the Learn page would look like this http://staging.inkscape.org/en/brynns-learn-page/?edit&language=en). Anyway, there is a *whole bunch* of user-related stuff in the wiki, and he said it would be better to ask the community about some of these questions. Since the current FAQ, which is shown both in the wiki and on the website, has as much user-related info as developer info, it needs to be split into 2 FAQs, which I've just started working on. (Maybe the user faq would be on the Learn page?) I find that the answer to item 2.11 (Is there a way to apply a gradient to a stroke so that it bends with the stroke?), links to 2 images, which are no longer there. If I knew what the author of that faq item was talking about, I could substitute some other images. I sort of know what the text is alluding to, but without the images, it's not clear. There are at least 3 or 4 ways that I know of, to fake a curved gradient (although maybe just a couple specifically for a stroke). And I can certainly describe each one (in the answer). And I know that there is a tutorial packed with Inkscape (share/examples/rope-3D.svg), which I can provide directions for readers to find. But the community is FULL of really nice tutorials. I know that, because of my research in writing this page on my Inkscape support website http://forum.inkscapecommunity.com/index.php. And coincidentally, I just wrote a tutorial on one of these techniques. So my first question: When I come across bad links, (dead, empty, not found pages, etc), what would be the best way to handle it? Can I link to any appropriate image or tutorial? Or should the links only go to "official" resources? What if those "official" resources don't exist? The 2nd question: When I come across answers to user-related questions in the FAQ, such as item 2.21 (Can I change the Inkscape theme?) where the answer is in wiki, what should I do? In this case, the answer provides a link to here: http://wiki.inkscape.org/wiki/index.php/Customizing_Inkscape which is a fairly substantial page in the wiki. If that info should not be in the wiki, where should it be? Should I write all that info from the wiki page, in the answer in the faq? Thanks for your help. And btw, since I'm such a newbie to the mailing list, please let me know if I say or do something wrong. All best, brynn

7 19

Siggraph2014 - Vector Graphics Complexes
by Mark Schafer 18 Aug '14

18 Aug '14

Some interesting features here: - https://www.youtube.com/watch?v=-XONNPyeb5U#t=122 http://www.dalboris.com/research/vgc/

2 1

Windows XP, cannot compile rev 13520
by alvinpenner 16 Aug '14

16 Aug '14

the operative message appears to be: ============ cmd ============ windres -o build/obj/inkres.o --include-dir=src src/inkscape.rc ============================= Make error line 444: RC problem: windres: src/inkscape.rc:6: syntax error .................................................................................. full text is: C:\InkscapeBZR>btool dist-inkscape #################################################### # BuildTool v0.9.9multi #################################################### ######## PARSE : build.xml ============ cmd ============ bzr revno ============================= ######## PARSE COMPLETE ######## EXECUTE ##### Target : init ##### Do all preparatory tasks, like make directories and copy files --- init / mkdir mkdir : build --- init / mkdir mkdir : inkscape --- init / copy copy : src/helper/sp-marshal.h.mingw to src/helper/sp-marshal.h copy : skipped --- init / copy copy : src/helper/sp-marshal.cpp.mingw to src/helper/sp-marshal.cpp copy : skipped --- init / makefile ============ cmd ============ bzr revno ============================= makefile : src/inkscape-version.cpp makefile : skipped --- init / makefile makefile : config.h makefile : skipped ##### Target : cxxtest ##### generate test files --- cxxtest / cxxtestpart --- cxxtest / cxxtestpart --- cxxtest / cxxtestpart --- cxxtest / cxxtestpart --- cxxtest / cxxtestpart --- cxxtest / cxxtestpart --- cxxtest / cxxtestroot ##### Target : compile ##### compile the source to .o --- compile / cc cc : compile with 1 threads in parallel ##### Target : link ##### link objects and library to create executable --- link / rc ============ cmd ============ windres -o build/obj/inkres.o --include-dir=src src/inkscape.rc ============================= Make error line 444: RC problem: windres: src/inkscape.rc:6: syntax error -- View this message in context: http://inkscape.13.x6.nabble.com/Windows-XP-cannot-compile-rev-13520-tp4971… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 1

Re: [Inkscape-devel] precompiled version of 0.91 for Linux
by john Culleton 15 Aug '14

15 Aug '14

On Thu, 14 Aug 2014 09:09:02 -0500 Terry Brown <terry_n_brown@...36...> wrote: > > I've never had any trouble building it under > Ubuntu. I do > > sudo apt-get build-dep inkscape > > which makes Ubuntu install all the dependencies > that went into building the inkscape package > that comes with ubuntu, and then compiling the > inkscape bzr trunk as always seemed straight > forward. Just in case you weren't aware of > `build-dep`. Also this probably only works > with the "current" version of Ubuntu, seeing > it's most likely to have libraries at the > versions inkscape trunk needs. > > Cheers -Terry > > Well following the above instructions from Terry I now have a real live functioning Inkscape0.19pre1 working on a linux partition! Now all I have to do is rig my Ubuntu partition to do the things I am used to on slackware. I can take it from here. Thanks to all who offered help. Dog was not kicked. -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

1 0

Problem compiling inkscape0.91pre1 on slackware 14.1 (and others)
by john Culleton 14 Aug '14

14 Aug '14

./configure shows this: WARNING: glibmm/threads.h: present but cannot be compiled configure: WARNING: glibmm/threads.h: check for missing prerequisite headers? configure: WARNING: glibmm/threads.h: see the Autoconf documentation configure: WARNING: glibmm/threads.h: section "Present But Cannot Be Compiled" configure: WARNING: glibmm/threads.h: proceeding with the compiler's result configure: WARNING: ## ---------------------------------------------------------- ## configure: WARNING: ## Report this to http://bugs.launchpad.net/inkscape/+filebug ## -------------------------------------------------- Previous versions of Inkscape compile OK. When I attempt to report the bug as described above I end up on an Ubuntu page. Is that where inkscape bugs are to be reported? -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

2 1

precompiled version of 0.91 for Linux
by john Culleton 14 Aug '14

14 Aug '14

Is there a precompiled version of 0.91 for linux--any version? I've tried pre0 and pre1, on slackware, Ubuntu and openSUSE. The errors vary, but glibmm seems to be the culprit. Second question: what version of glibmm are the developers using? It seems to work on Windows 7 using the precompiled version. But Windows really sucks when pulling illos off the screen. And the 0.91 main screen is significantly different from 0.48.5 Why is this a big deal? Well I am writing books on two applications, book covers and web pages, both using Inkscape. I don't want them to be instantly obsolete. Help! -- John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html

4 4