Problems building on Ubuntu 16.04
by mathog
Upgraded the Ubuntu 14.04 system which had endless build problems to
Ubuntu 16.04.
It doesn't seem to like 16.04 much better. Different problems, but
still problems.
Cleaned out the build directory and did:
cmake ..
which failed at
...
WITH_OPENMP: ON
WITH_PROFILING: OFF
WITH_YAML: OFF
------------------------------------------------------------------------
CMake Error: The following variables are used in this project, but they
are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
POPPLER_INCLUDE_DIR
used as include directory in directory /usr/local/src/inkscape_trunk
used as include directory in directory /usr/local/src/inkscape_trunk
used as include directory in directory /usr/local/src/inkscape_trunk
used as include directory in directory /usr/local/src/inkscape_trunk
<SNIP many lines>
-- Configuring incomplete, errors occurred!
See also
"/usr/local/src/inkscape_trunk/build/CMakeFiles/CMakeOutput.log".
This is at revision 15617. These poppler pieces are present
ii gir1.2-poppler-0.18 0.41.0-0ubuntu1
ii libpoppler-dev:i386 0.41.0-0ubuntu1
ii libpoppler-glib-dev 0.41.0-0ubuntu1
rc libpoppler-glib4 0.12.4-0ubuntu5.2
ii libpoppler-glib8:i386 0.41.0-0ubuntu1
rc libpoppler19:i386 0.18.4-1ubuntu3.1
rc libpoppler44:i386 0.24.5-2ubuntu4.4
rc libpoppler5 0.12.4-0ubuntu5.2
ii libpoppler58:i386 0.41.0-0ubuntu1
ii poppler-utils 0.41.0-0ubuntu1
What needs to be tweaked to make this work?
Thanks,
David Mathog
mathog@...1176...
Manager, Sequence Analysis Facility, Biology Division, Caltech
4 years, 11 months
Marketing Inkscape - Survey Preview
by Ryan Gorley
Hello all,
I have been in communication with Martin and Maren about assisting with
some marketing on the project. I am a designer and marketer by profession.
You can read the conversation
<http://forum.inkscapecommunity.com/index.php?topic=497.0> that got this
all started if you're interested, but in short, I feel passionately about
helping Inkscape succeed.
I am emailing to get your feedback on a survey I would like to begin
collecting responses for. As I see it, growing users and growing
contributors are two sides of the same coin for any successful FOSS
project. This particular survey is focusing on the user side of that coin.
My intent is to help develop criteria for, and consensus around, who our
primary markets for Inkscape should be. A free and open application is of
course for anyone to use for any reason. However, because our resources in
marketing this application are finite, we really need to clarify and
prioritize to have any hope for success.
So here is the survey: https://goo.gl/forms/ReZkSjOMokkaoSln2
*Don't spend your time responding (yet)*. I would like to make sure I'm
covering the right user segments here, so do email me with your thoughts.
I'm glad to meet you all and thanks for the help!
Ryan Gorley @ Dijt <https://dijt.co/>
5 years, 9 months
Offer to help put inkscape on windows store
by Marc Jeanmougin
Hi all,
I recently discussed on IRC with dwcares from Miscrosoft who wants to
help us simplify precesses on windows.
Here is his email:
===
David Washington from Microsoft here. Earlier this afternoon I had
conversation with Marc about potentially publishing the Inkscape app to
the Windows Store, the app store for Windows 10 PCs.
The Windows Store now supports publishing Win32 Desktop apps with little
or no code change using the Windows Desktop Bridge. Taking advantage of
the Windows Desktop Bridge and Distributing through the Windows Store
also provides simplified options for automated updates, easy install
and uninstall, and provides a new distribution path for folks who may
have not found Inkscape before.
Our team has identified Inkscape as a top desktop app that we’d love to
see in the Windows Store. Given this we have some resources to help with
the process of getting this ported using the Windows Desktop Bridge and
published to the Windows Store. The process itself is lightweight, and
our team is equipped help walk you through getting it ported and
published. We’ve done some early investigation on the Inkscape binaries
and we haven’t identified any issues getting it published.
If this is something that seems interesting to you, we can get together
on the phone and talk through the details for the next steps of getting
this published. If you’d rather make progress in email/IRC, we’re happy
to accommodate what works for your team. We’re prepared to work with
you on getting this published as early as next week.
I look forward to working together. I’ve included some folks from my
team who will be helping you.
Thanks much,
David Washington
Microsoft | Developer Experience | 206-605-2062
===
Eduard, Nicolas or Partha, iirc you're the ones doing stuff on windows,
could you take it from here if it seems interesting ?
Thanks,
--
Mc
5 years, 10 months
Re: [Inkscape-devel] Any chance we can make some docs material? (targeting the moon)
by Maren Hachmann
Would it make sense to use gitlab's new subgroups feature for this?
The inkscape-docs team could be a sub-team of Inkscape, that way. There
are only 4 members as of now, so changing wouldn't be so difficult as it
might be later on.
Maren
> Am 28.04.2017 um 16:14 schrieb Martin Owens:
>> On Fri, 2017-04-28 at 12:39 +0100, C R wrote:
>>> I'd love to quit my job and just do docs. :) Unfortunately, that's
>>> what it would probably take to get docs going to the extent we'd
>>> like.
>>> It's been discussed before, but never gone anywhere because of lack
>>> of time/hands involved.
>>>
>>> Yes, we should use Scribus to do it. In fact, it should probably be a
>>> github project to attract contributors. This way we can patch what
>>> needs to be patched when stuff changes in subsequent releases.
>>
>> Sounds like you have a solid step one Chris.
>>
>> Here's the inkscape-docs group on gitlab, EVERYONE should join, there
>> should be a button to join:
>>
>> https://gitlab.com/inkscape-docs
>>
>> And here's the new book/manual/docs project where files can be put:
>>
>> https://gitlab.com/inkscape/manuals
>>
>> I recommend using the wiki attached to the project to plan the
>> adventure slowly. Add a bit at a time and don't rush to have something
>> "complete" but have something small produced.
>>
>> 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 years, 10 months
Hackfest possibility - Paris Please Respond ASAP if interested!
by Tavmjong Bah
Hi,
Marc has been looking for free spaces in Paris to hold a hackfest. He's
found what looks like an ideal spot:
Carrefour Numérique² located at the Cité des Sciences et de l'Industrie
(an excellent modern science museum) in northeast Paris.
http://www.cite-sciences.fr/fr/accueil/
http://www.cite-sciences.fr/en/explore/learn/carrefour-numeriqu
e2/
There are Inkscape users there and they've even written their own in-
house Inkscape plug-ins to drive their CNC machines. They've hosted
other open-source groups including a monthly Blender users group and
twice-a-year Ubuntu parties.
They can offer us a "Numeric classroom" with five tables with power and
wired Internet connection from May 29th to June 2nd.
The question is, is there sufficient developer interest to pursue this?
Please respond if you can attend. If there is enough interest I will
present this option at the board meeting Friday.
Tav
5 years, 10 months
website moderation policy
by brynn
Hi Friends,
I've been helping to test some new moderation features which Martin has
been working on (and Maren helping too), for the website. We have realized that
(A) we might have different opinions about what the moderation policies should
be, and (B) the current CoC might not cover them. But we all agree that the
larger community should be involved, if the CoC needs to be edited.
For convenience, the CoC says this:
"Guidelines for User Submitted Content:
Art and other content submitted to the Inkscape website should adhere to the
following rules:
-- Art must be your own original creation or derived from artwork available
under an open licence. We cannot accept submissions that infringe copyrights.
-- No nudity or graphic violence. (Note: we may allow this type of content
once it is possible to tag it as such, but pornographic and/or illegal material
would still be disallowed.)
-- No content that is explicitly discriminatory in nature.
-- No political agitation or totalitarian symbolism."
Up until the moderation features are completed, installed and in use,
the policy for images in the gallery has been this. As long as the image
doesn't violate those 4 guidelines, it's acceptable, even though it may have
nothing to do with Inkscape. After that, the gallery has been relying on a very
small upload quota for members, to prevent mass spam attacks.
In my opinion, resources uploaded to the website should bear some
relation to Inkscape. Or more specifically, those which have no relation to
Inkscape should not be allowed. Here's what I propose:
>> Images should be made in whole or in part with Inkscape, or depict how
>> Inkscape was utilized in user projects (such as a photo of a t-shirt which
>> design was made with Inkscape).
>> Any other images need to have some relation to Inkscape, the Inkscape Project
>> (website, forums, hackfest), vector graphics, or marginally, FOSS. (maybe
>> not FOSS?)
This would exclude images like these:
https://inkscape.org/en/~stacymcgraw@...1081.../%E2%98%85img-0616
https://inkscape.org/en/~KarenFechter/%E2%98%8520160319-150913+1
https://inkscape.org/en/~lgimenezborges/%E2%98%85vklsd
https://inkscape.org/en/~Astro.C/%E2%98%85three-musketeers
https://inkscape.org/en/~richardkwok0128/%E2%98%85testing+0
The reason I feel this way, is because there must be hundreds, if not thousands
of galleries on the internet, where people can upload any kind of random photo.
Why should the Inkscape website waste its resources hosting images which weren't
made with Inkscape and have nothing to do with it? If the Inkscape website is
going to the trouble of creating and maintaining a gallery, it ought to promote
Inkscape, vector graphics, and maybe FOSS, almost, if not completely
exclusively. My opinion of course ;-)
So I propose the following, or something like it, should be the first
item in the list of Guidelines for User Submitted Content. No doubt it could be
worded better.
-- Images must be created using Inkscape, in whole or in part; or depict how
Inkscape was utilized for the user's project (such as a photo of a t-shirt which
design was created using Inkscape). Or otherwise the image or resource must bear
some relation to Inkscape, the Inkscape Project, vector graphics (or FOSS??)
Does anyone have any thoughts or opinions on this?
Thank you very much,
brynn
PS - Should this be cross posted to the user list too?
5 years, 10 months
Fwd: Re: Any chance we can make some docs material? (targeting the moon)
by Miguel Lopez
I have made videos of workarounds, and anyone making a workaround docs can use my video without my permission. I will upload them soon. Those docs can be deleted once Inkscape gets certain features, and I will delete those videos the minute Inkscape supports certain features.
For now I have this - https://www.youtube.com/watch?v=k5TkIETfQa4
The point of the video is to show users how they can make a easily accessible editable mask in Inkscape without ever having to release mask. It also shows how to get some fade-out effect usually made with raster programs. There's the issue of the mask showing over the target object, and if I hide the editable mask layer, so does the mask goes to black.
The one I will upload after are
2 Gradient Stroke workarounds videos - With Profile LIne, and without profile line
1 tangency line workaround video utilizing spiro, b-spline, and regular bezier path
Way later I will do a shoe render, and how to use clip and masks in order to generate a extremely realistic-looking shoe that is 100 percent vector, but some of those results can easily be achieved with raster programs. I will also try to generate a warped pattern, and show how to achieve that.
I know I'm not the best person to make a tutorial.
On 4/29/2017 6:36 PM, Victor Westmann wrote:
Hi Miguel,
I think this is a GREAT advantage for the entire Inkscape project. It makes all the sense of the world to help users do all the needed workarounds and, if they want, help send funds to the project ($$) and/or a bug request on Gitlab(is it at Gitlab really?).
Amazing. The more transparent we are (and we really are) the better.
--Victor Westmann
2017-04-29 10:39 GMT-07:00 Miguel Lopez <reptillia39@...3425...<mailto:reptillia39@...3425...>>:
I want to put out something regarding documentations. What about
workarounds to Inkscape limitations as part of the documentation? Some
users really need some answers to the limitation of Inkscape. There's
another idea I have in mind. For making tutorials shorter, we can use
existing tutorials of our own and linking to them as part of advanced
section of Inkscape tutorials. Advanced users should already know the
program in and out to know how to apply them for advanced rendering.
Some of those might need workarounds though.
My only issue with those workaround is the amount of time they require,
and the tax on limited resources. Otherwise, if those weren't a issue,
they would be fantastic though they're still not a replacement to what
other programs has to offer. I can offer making workaround docs if
anyone wants me to show how to work around Inkscape limits.
For example :
1) Gradient Stroke -
1a) Method 1 (If profile line aren't needed) - Duplicate and then adjust
stroke width, and then convert to path. Every strokes must be converted
to path. You copy and paste the path that is going to get removed by
applying the path difference. You repeat the process, and then you get
every individual stroke which can be colored as however you please.
1b) Method 2 (If profile line is needed) You apply the same thing to the
above, but you are not going to use stroke width. Instead, you are going
to use power stroke to emulate profile line with gradient stroke.
2) Realistic Rendering of convulated objects like a shoe.
2a) This involves series of clipping, blurring, gradient mesh and
brushing. Right now, Inkscape users can only use gradient mesh for basic
overall lighting, and some bit of coloring using filtering since
gradient mesh is underdeveloped in Inkscape. You apply blur to brushes
in order to emulate shading. Doing this a lot can give very sastifying
result within Inkscape, but also drains so much of rendering speed
within Inkscape even with a powerful computer. But results are literally
comparable to raster programs, and in some way even better because well,
it's scalable.
3) The lack of warp tool for textures workaround
3a) As of now, we do have lattice tool, and the tweak liquifying tool.
Those two can be used as a workaround to the lack of warp tool. Lattice
deformation tool should had the option of allowing users to tweak the
tangency line though instead of the tangency line being tangent to the
horizontal and vertical direction. This is not something that can have a
decent workaround since it requires duplicating so many objects and then
tweaking it would be a major pain. For complicated textures, it can't be
done within Inkscape unless you have a infinite amount of time and
resource, and as we all know that's not possible.
4) For people who have trouble with tangency snapping (I'm one of
those), and no that snapping option does not help one bit.
4a) The obvious workaround involves using the show handles. You can make
tangent line utilizing the result of the show handles LPE. Also, this
enables users to be able to create perpendicular, and tangent spiro path.
5) The lack of ease regarding manipulating mask/clip
5a) The workaround to this is well, using the clone as the
masking/clipping source while retaining the original for
clipping/masking at another location. This workaround works because you
can always manipulate the source object, and hide it. It is almost
exactly like as if you were manipulating transparency mask within Krita
or Photoshop or GIMP. After testing it, it's beautiful really when you
change between layer/group.
6) PDF export limitation
6a) The obvious workaround here is well, export to png and then convert
to pdf. Of course, some rasterization would be needed if one has to
convert to pdf, literally at times.
I think those are the 6 issues that could be addressed via docs tutorial
for those who are desperate to find a solution to those. They can always
resort to Krita for those (except 6 because pdf export is not planned),
but that's not a option if they have to create a vector render. If
there's anything I miss regarding workarounds, lemme know. I can
probably add more workarounds if I miss anything as I know the program
in and out from a user perspective.
On 4/29/2017 11:54 AM, C R wrote:
>> I don't mean to slow anyone's roll here. But wouldn't it make more sense to put
>> any kind of energy towards documentation into the much discussed, direly needed,
>> user-focused, step by step manual? Rather than starting from scratch on a whole
>> different kind of project?
> Yea, this actually makes a lot of sense as a first step.
>
>> There are many books out there already, which amount to a series of tutorials.
>> It's not a bad thing. I just think this kind of project is better suited for a
>> single author, or maybe a small team. And I think the project needs the manual
>> much, more more than the community needs another book of tutorials.
> I agree. I think the book could be a lot of things in one. But I agree
> with finishing what we already have before starting something new.
>
>
>> As far as I understand, all that's needed is an English translation of...well
>> can't find a link to the French version. Here's a link to whatever has been
>> translated already:
>> https://fr.flossmanuals.net/start-with-inkscape/introduction/
> I can't help with translation, unfortunately. But I'd like to see this
> finished. So +1 for the suggestion.
>
>> Once we have the translation, we'll be off and running to update and finish it!
>> By the way, is there anything those of us who can't translate, can do, to help
>> the translators?
> I volunteer to help this effort in what ways are needed.
>
>> And won't such a new book of tutorials have to be published? A big obstacle to
>> writing any book is getting it published. You almost have to have an invitation
>> from a publisher to be certain a book will get published. Or publish it
>> yourself, which is not easy eitiher.
> Books done in Scribus can be "published" in a variety of ways, opened
> in browsers, laptops, eReaders, or just printed out. We could sell
> printed copies along with other Inkscape stuff. Maybe copies signed by
> members of the project would be kinda cool. No idea what the market is
> for it, but the idea that we could do all of these at once is
> attractive, and why I recommend Scribus.
>
> -C
>
>> Just my opinion :-)
>>
>> brynn
>>
>> -----Original Message-----
>> From: Maren Hachmann
>> Sent: Friday, April 28, 2017 4:01 PM
>> To: Inkscape-Docs ; Inkscape Devel List
>> Subject: Re: [Inkscape-devel] Any chance we can make some docs material?
>> (targeting the moon)
>>
>> Would it make sense to use gitlab's new subgroups feature for this?
>>
>> The inkscape-docs team could be a sub-team of Inkscape, that way. There
>> are only 4 members as of now, so changing wouldn't be so difficult as it
>> might be later on.
>>
>> Maren
>>
>>> Am 28.04.2017 um 16:14 schrieb Martin Owens:
>>>> On Fri, 2017-04-28 at 12:39 +0100, C R wrote:
>>>>> I'd love to quit my job and just do docs. :) Unfortunately, that's
>>>>> what it would probably take to get docs going to the extent we'd
>>>>> like.
>>>>> It's been discussed before, but never gone anywhere because of lack
>>>>> of time/hands involved.
>>>>>
>>>>> Yes, we should use Scribus to do it. In fact, it should probably be a
>>>>> github project to attract contributors. This way we can patch what
>>>>> needs to be patched when stuff changes in subsequent releases.
>>>> Sounds like you have a solid step one Chris.
>>>>
>>>> Here's the inkscape-docs group on gitlab, EVERYONE should join, there
>>>> should be a button to join:
>>>>
>>>> https://gitlab.com/inkscape-docs
>>>>
>>>> And here's the new book/manual/docs project where files can be put:
>>>>
>>>> https://gitlab.com/inkscape/manuals
>>>>
>>>> I recommend using the wiki attached to the project to plan the
>>>> adventure slowly. Add a bit at a time and don't rush to have something
>>>> "complete" but have something small produced.
>>>>
>>>> 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<mailto:Inkscape-devel@lists.sourceforge.net>
>>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>>>
>>
>> ------------------------------------------------------------------------------
>> 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<mailto:Inkscape-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>
>>
>> ------------------------------------------------------------------------------
>> 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<mailto:Inkscape-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> ------------------------------------------------------------------------------
> 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<mailto:Inkscape-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
------------------------------------------------------------------------------
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<mailto:Inkscape-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
5 years, 10 months
Email spam from inkscape.org
by Martin Owens
Hi all,
I've disabled the email server on osuosl's machine which is hosting
inkscape.org, it sent out some spam (50~140) with a rather inviting
political headline subject, and a mortgage advert body. whereupon 22
people emailed me (the webmaster) with abuse.
I'm going to continue to monitor it, but without some sort of expert
that can tell if the machine is compromised, I may just have to keep
email offline for now.
Sorry for the inconvenience. Effected will be: registration
confirmation emails, password resets and any website notifications.
Best Regards, Martin Owens
5 years, 11 months
