Confusing windows build instructions
by mathog
Hi all,
Today while perusing the varied Windows build instructions I was struck
by some contradictory, or at least, not fully fleshed out text.
For instance, it says here:
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows
Warning: As our 32-bit development libraries (devlibs) currently do
not
offer GTK+ 3 (which is required by trunk) you have to follow the
instructions for 64-bit builds or use MSYS2 if you want to compile
the latest code (lp:inkscape)!
Is "lp:inkscape" the name on github too?
The Msys2 page says here:
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_wit...
nothing about devlibs. Presumably it doesn't need them anymore and
msys2installdeps.sh takes care of it? Never having used Msys2 it isn't
entirely clear what the "gtk3" install (for instance) is. If there is
no devlib for gtk3, what is this? More like a cygwin library?
The 64 bit build page says here:
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
in several places to use "mingw32-make". No explanation why 32 and not
64.
Somehow related to "win32 threading model and SEH exception handling"?
Finally the visual studio page says here:
http://wiki.inkscape.org/wiki/index.php/Using_Visual_Studio
"Follow all steps of guide Compiling Inkscape on Windows." At that
point one has a fully compiled and working Inkscape. Why bother with
Visual Studio? For the IDE? Is there a discussion in the wiki
somewhere about other IDEs, like CODE::BLOCKS or Eclipse?
Do any of these give instructions for packing up the built Inkscape so
that it can be given to somebody else, like in a zip file? As I recall
there are a bunch of dll's that need to be copied into the Inkscape
folder from other locations (devlibs/bin, mostly). That was for an
Inkscape built with mingw and msys and devlibs. What about Msys2 and
whatever it is using for libraries? Can you just copy over whatever it
has for devlib equivalents or are there Msys2 core libraries which must
come too (like when distributing a cygwin binary)?
Regards,
David Mathog
mathog@...1176...
Manager, Sequence Analysis Facility, Biology Division, Caltech
5 years, 7 months
Re: [Inkscape-devel] [Inkscape-docs] moderation - 'could have been made w/Inkscape'
by brynn
Hi Reidar,
Thank you for your comments. Anyone is welcome to share their comments.
It's not an interruption - it's what I was asking for :-)
I agree about integrity. I really would like the gallery to have only
Inkscape images.
But considering this post was answered by only 2 people, I guess the
community isn't very concerned. So I probably won't change much, if anything,
about the way I handle these images.
If we start to run short of space for the gallery, maybe we would want
to revisit this. But for now, it doesn't sound like the community is concerned
about this.
Thanks again for your comments!
All best,
brynn
-----Original Message-----
From: Reidar Vik
Sent: Tuesday, October 24, 2017 1:52 PM
To: brynn
Cc: C R ; Inkscape-Devel ; Inkscape-Docs
Subject: Re: [Inkscape-docs] [Inkscape-devel] moderation - 'could have been made
w/Inkscape'
@brynn, I agree about what you said about images. It is fairest and most honest
to only use images made with inkscape. Integrity is very important in this game.
(I hope I didn´t interrupt the discussion)
Vennleg helsing
Reidar Vik
Trostereiret Vik
org.nr. 912 333 485
trostereiretvik.blogspot.com
https://twitter.com/Trostereiret
2017-10-22 20:09 GMT+02:00 brynn <brynn@...3133...>:
Thanks for your comments, C R.
Re: Time as a resource: I think it's not worth anyone's time to scour
the internet trying to prove that something wasn't made in Inkscape.
Well of course, that's not what I'm proposing. For the image I did search,
there was no scouring. It was the first result of the first search I made. It
was clear enough for me just to look at the image. But I searched it out just
to prove my suspicion. (It's the only time I've done that.)
For the rest of your comments, I had the very same thoughts at first. If it
could have been....why not. But the reason I wanted to try to discuss, is
because
(a) These images are numerous, considering our limited space.
(b) Most of them could really only be done by advanced users (That's usually how
I catch them. If they really had been made with Inkscape, in my experience, the
artist wants to shout it out - not make a drive-by upload.)
(c) I'm afraid it's misrepresenting Inkscape's abilities. I'm afraid it gives
the impression that it must be easy to create amazing images.
(d) It makes it harder to find the really awesome Inkscape-made images. It kind
of dilutes the pool of awesome.
I really have always (well, since I found Inkscape 10 years ago) wanted an
Inkscape-only gallery. To me, THAT would be amazing! And to me, that's what
the website should provide.
I wonder if it would work to have another category, or another Order By option,
like All Inkscape or 100% Inkscape, or something like that? Because I certainly
have no objection to having images in the gallery, for which Inkscape was used
only for part of it. But maybe it would be nice to have the "all Inkscape"
images easier to find?
Well anyway, as I said, I already had an idea that this isn't a big concern for
the community. But I just wanted to voice a few thoughts as to why maybe it
should be.
Thanks again :-)
brynn
-----Original Message----- From: C R
Sent: Monday, October 16, 2017 4:33 AM
To: brynn
Cc: Inkscape-Docs ; Inkscape-Devel
Subject: Re: [Inkscape-devel] moderation - 'could have been made w/Inkscape'
Re: Time as a resource: I think it's not worth anyone's time to scour
the internet trying to prove that something wasn't made in Inkscape.
I can think of several ways to do the graphic in question (or at least
similar) in Inkscape, so I'd let it stay as it's actually quite
stunning and not really hurting anyone.
Even if it's not done in Inkscape, it gets people thinking about how
it could be done in Inkscape, which is not a bad thing. Maybe it will
inspire someone to post a vector resource of it in the future.
Going forward, this is my recommendation: If it looks like it could
have been done in Inkscape, and it was posted on our website, then we
can assume (for the sake of aesthetics) that it was.
Obviously if the uploader came back and replied to your comment,
saying "Oh, I've not done this in Inkscape." Then you can remove it
without having to make any guesses. :)
Thanks for bringing it to attention, Brynn. Your hard work to fight
against random non-Inkscape posts is definitely making the site much
more usable and clutter free for everyone.
-C
On Mon, Oct 16, 2017 at 5:29 AM, brynn <brynn@...3133...> wrote:
Hi Friends,
I think I probably know how the community leans on this. But since
it bothers me so much, and happens so often, I thought it was worth not
assuming the answer, and finding out for sure.
A few months ago, we decided not to allow random photos in the
gallery, which are unrelated to the project in any way. We also decided not
to bother with copyright issues. (long discussion -
https://sourceforge.net/p/inkscape/mailman/message/35798617/)
Probably equally as often as random photos being uploaded, are images
which *could have been made with Inkscape* but which I doubt were. So far,
I've been letting these go through. But as I said, I wanted to have a
discussion, rather than assume.
Here are a couple of recent examples:
-- 2 images, 1 resource and 1 thumbnail --
https://inkscape.org/en/~noahgabe@...3618.../%E2%98%85music
-- https://inkscape.org/en/~KristiBryant113/%E2%98%85jesus-saves-the-world2
(I did a little research on this one, and found it at many different sites
(many on different sites selling tshirts, as well as just web images) with
the same basic image (and this exact image here:
https://res.cloudinary.com/teepublic/image/private/s--rVeDm8Gt--/t_Previe...)
-- so I'm pretty sure it wasn't made with Inkscape)
--https://inkscape.org/en/~chiquitita/%E2%98%8515230751-703016283207581-8475381764676214363-n
To me, all of those /could have been/ made with Inkscape. But I have
reasons to doubt all of them. How do you all think they should be handled?
I think they should be handled similarly to random photos (contact the
member, explain and link to CoC, ask to explain the relation to Inkscape,
ask if they would like to remove, inform after 2 weeks we will do it, of
course with graciousness. Or do we let them have the benefit of our doubt?
I honestly don't understand why people go around posting random
images (apparently, afaict) in random galleries, once or twice, and never
come back. (I have the same curiosity about people who post 1 or 2
frivolous, sometimes meaningless messages in forums and never return.) But
it seems worth the effort not to waste our limited resource on hosting these
things.
Anyway, thanks for any thoughts or comments :-)
All best,
brynn
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-docs mailing list
Inkscape-docs(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-docs
5 years, 7 months
Should Inkscape use fonts from folder of currently opened SVG?
by Eduard Braun
Hi all,
I'm currently implementing functionality which allows Inkscape to use
fonts *not* installed on the system [1].
* Suppport for loading fonts from share/inkscape/fonts as well as the
fonts dir in Inkscape's configuration directory is already added.
* Support for custom locations configurable by the user is provided, too.
* One task is left: load fonts from the location of the currently
opened SVG document
While the last point could be especially interesting (e.g. it would
allow people to simply distribute fonts required by an SVG alongside
with it) it's also a bit tricky: fontconfig scans directories
recursively. This means if the user were to open an SVG file somewhere
at the top of the directory tree, fontconfig suddenly would scan *a lot*
of directories for fonts.
So I basically want to collect some opinions:
* Do you think this would be acceptable? In that case I'd probably
implement a boolean setting which defaults to false and explains the
risks.
* Could it make sense to rephrase the task a bit to "load fonts from
the 'fonts' directory in the folder of the currently opened SVG"? It
might be an option to offer this functionality while reducing the
risk of indexing a large amount directories, however discoverability
of the feature would be significantly reduced.
* Should I just skip the last task?
* Other ideas?
Let me know what you think!
Best Regards,
Eduard
[1] https://gitlab.com/inkscape/inkscape/merge_requests/102
5 years, 7 months
Convert to path on use/clones
by Jabier Arraiza
Hi all.
I want to start a discussion to make convert to paths function and also
the stroke to paths works on use/clone elements.
The question:
Is a good idea? To me is the expected result from a user point of
view...
Cheers, Jabier.
5 years, 7 months
Development versions for Windows available on a regular basis via AppVeyor
by alvinpenner
Just found out about this, so I'm re-posting this notice, slightly edited:
http://www.inkscapeforum.com/viewtopic.php?f=21&t=32932#p100877
Development versions of Inkscape for Windows (currently for 0.92.x branch
and for master branch (formerly called 'trunk') ) are now automatically
created on every change to the code base.
They can be found at
https://ci.appveyor.com/project/inkscape/inkscape/history
Click on the title of the build you want to test, i.e. a URL that goes like:
https://ci.appveyor.com/project/inkscape/inkscape/build/master-606
or
https://ci.appveyor.com/project/inkscape/inkscape/build/0.92.x-607
On the next page, below 'Job Name', select if you want the 32 or 64 bit
version (Environment: MSYSTEM=MINGW32 or Environment: MSYSTEM=MINGW64).
On the next page, click on 'Artifacts' (at the right, right above the
terminal-like box).
On the next page, download a 7z file.
(If necessary, you may need to install the 7z decruncher, from
http://www.7-zip.org/)
...................
For Ubuntu, there's
https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk (0.93 devel
series)
and
https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable-daily (0.92.x
series)
--
Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html
5 years, 7 months
Development versions for Windows available on a regular basis via AppVeyor
by alvinpenner
Just found out about this, so I'm re-posting this notice, slightly edited:
http://www.inkscapeforum.com/viewtopic.php?f=21&t=32932#p100877
Development versions of Inkscape for Windows (currently for 0.92.x branch
and for master branch (formerly called 'trunk') ) are now automatically
created on every change to the code base.
They can be found at
https://ci.appveyor.com/project/inkscape/inkscape/history
Click on the title of the build you want to test, i.e. a URL that goes like:
https://ci.appveyor.com/project/inkscape/inkscape/build/master-606
or
https://ci.appveyor.com/project/inkscape/inkscape/build/0.92.x-607
On the next page, below 'Job Name', select if you want the 32 or 64 bit
version (Environment: MSYSTEM=MINGW32 or Environment: MSYSTEM=MINGW64).
On the next page, click on 'Artifacts' (at the right, right above the
terminal-like box).
On the next page, download a 7z file.
(If necessary, you may need to install the 7z decruncher, from
http://www.7-zip.org/)
...................
For Ubuntu, there's
https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk (0.93 devel
series)
and
https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable-daily (0.92.x
series)
--
Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html
5 years, 7 months
GSoC mentor summit
by Marc Jeanmougin
Hi all!
Last weekend, I attended the GSoC mentor summit which had a great
variety of very interesting people and sessions, I'm just going to
summarize my thoughts about some of the most interesting sessions and
discussions. Some are mostly board-related, but most can be of interest
to the whole contributors community.
ToC:
* Diversity
* Fuzzing
* Version numbers
* Gitlab : self-hosting & independence
* Bug management
* GCI
* Funding
I started writing all this in a single email, but for clarity, I'm just
going to answer this email with an email for every individual topic,
allowing to thread it nicely on email clients and keep all threads on
mostly one topic.
--
Marc
5 years, 7 months
Re: [Inkscape-devel] Bugs
by mathog
On 20-Oct-2017 15:53, Marc Jeanmougin wrote:
> == Migration ==
>
> How I would propose to go about the migration would be to basically
> post
> on every one of the 4500 open bugs on lp a closing message with an
> invitation to try to reproduce the bug with the devel version (maybe
> with a link to a page explaining how to try it [e.g. Ubuntu with apt,
> other linux compiling, windows with downloading the latest built 7z])
> and if it can be reliably reproduced, to submit it on gitlab and close
> the issue on lp (or, if wishlist, submit it to the wishlist project).
> Distributing the task on the bug reporters may help a lot with the
> initial triaging, and (I'm an optimist) make for a smooth transition.
That is going to create a black hole into which 99% of the information
from the launchpad bug reports is going to fall, some of the ones which
are open, and all of the ones which are not. I have worked in one way
or another on ~100 bugs and will tell you right now I am NOT going to be
testing again for all of those glitches and issues! I'm not even that
big a contributor, others have worked on thousands of bugs. Just think
how long it would take to get through a list like that. Never mind the
list of people who no longer work on the project and would ignore your
request.
A smooth transition would involve some tool which automatically migrates
all of the bug information from Launchpad to some other bug tracking
platform. Note that on launchpad links from a bug to a patch/revision
are all entered manually. Whatever the bug system migrates to, it would
be nice if that function would be integrated. Ie, place a patch on the
bug reporting system, hit some "push patch" button, and presto links are
made in both directions between the bug reporting system and the
revision system, once the new revision number appears. If such a thing
actually exists.
Regards,
David Mathog
mathog@...1176...
Manager, Sequence Analysis Facility, Biology Division, Caltech
5 years, 7 months
No Align shortcuts documented in Keyboard and mouse reference of 0.92
by Raghavendra Kamath
Hello,
In Inkscape 0.92 a user can quickly align objects with the following keyboard
shortcuts
Ctrl+Alt+2 : Align bottom
Ctrl+Alt+4 : Align left
Ctrl+Alt+5 : Align horizontal and vertical center
Ctrl+Alt+6 : Align right
Ctrl+Alt+8 : Align top
Ctrl+Alt+h : Align horizontal center
you can check the discussion & commit enabling this shortcuts here -> https://
bugs.launchpad.net/inkscape/+bug/189535
However, I couldn't find these shortcuts documented in the official keys and
mouse reference. May be I am missing something? If it is not there already can
we update the shortcut sheet.
Thank you
--
Raghavendra Kamath
Illustrator
raghukamath.com
5 years, 7 months
Request for hosting sponsorship for the Inkscape Project
by Bryce Harrington
Inkscape is seeking to improve its online service hosting. To this end
we're soliciting proposals for donation/sponsorship of hosting services
for the project.
The Inkscape Project is a non-profit, volunteer-driven organization that
develops and maintains the popular Inkscape vector drawing software,
provided freely to millions of artists, designers, and other drawers of
lines. Our website is at http://www.inkscape.org
If you would be interested in sponsoring us through a donation of
hosting service, we would be happy to add you to our sponsors page, with
a mention & link on our main website's footer. Proposals can be sent to
me as contact point. These will be presented to Inkscape's board, who
will make the final determination in about a month's time.
== Background ==
We currently have various services hosted at a number of different
locations with widely varying administrative capacities. We would like
to centralize the administration of these services, such as
consolidating them onto one platform. We also want room and flexibility
to easily install additional services as we grow.
Services high on our priority list to migrate soon include mailing
lists, Mattermost, and wiki. Bug tracking, web forum and gitlab are
potential secondary priorities. Our Django-based main website may also
be worth consolidating at some point in the future.
For redundancy, we'd like to engage two distinct hosts, with one as a
primary and the other backup/space, preferrably in geographically
distinct areas (e.g. Europe and Canada).
== Requirements ==
We think that a suitable machine would look something like this:
Minimum Desired
Required Ideal
CPU: dual core quad core
RAM: 4 gb 256 gb
Storage: 500GB >1 TB (HW RAID-1)
HDD SDD
Bandwidth: 1 TB/mo 2 TB/mo
OS: Any linux Ubuntu 16.04
We like the straightforwardness of physical (metal) hardware, but could
consider virtual options if we can get similar levels of flexibility and
expandability.
* UPS power backup
* 24h support at the datacenter
- For hardware (metal) options, a technician would need to be
available for handling hardware issues, to do OS
installation/reinstallation, hook up KVM/IP if available, and to
investigate faults that can't be diagnosed remotely.
* Server would be under the administrative and technical management of
the Inkscape admin team (about 6-8 people). We would have root access
to the machine for doing system updates and to install/configure
software and services.
* We expect to be managing/maintaining our software ourselves. Items we
anticipate migrating to this include (in rough order of priority):
+ Mailman3
+ Mattermost
+ Wiki (mediawiki currently)
+ Forum (e.g. hosting for inkscapeforum.com)
+ Bug tracker (TBD)
+ Gitlab
+ Other project management tools
+ Website / Django
* Inkscape does not handle anything particularly controversial. No
copyright infringing materials, nothing political, nothing
intentionally offensive. Our windows binary has been false-positived
by virus software in the past, but we clear this up ourselves.
* Currently our website hosting is sponsored and managed by OSUOSL.
It's a root access virtual machine running postgresql, memcached,
nginx and the django site itself. Memory usage is 450MiB per web host
thread, currently 2 threads, plus 500MB for postgresql and 500MB for
memcache. CDN is hosted by Fastly, currently serving 32TB per month
for Inkscape (1:1.5 ratio US:EU, so more EU hits overall). There's
enough dynamic content that we still see a decent load (1/2 TB/mo) on
the server, notably around major releases (once every year or two); we
are continuously tweaking optimizations.
5 years, 7 months
