Inkscape 1.0a isn't usable at all for me at the moment on Linux when
running it under Wayland; it appears to be missing most of the mouse
events or something. I cannot draw even the simplest geometry! I haven't
figured out how to make a screencast that shows the mousepointer, but
maybe that's another Wayland issue ;-). Can't show it to you because of
this, but it's really bad.
I don't recall any reports about this and cannot find anything in the
Gitlab issues either, but surely others must be experiencing this too...
Unless everyone else is still on Xorg. I've reproduced this on both
Fedora 30, with current trunk, as well as on Ubuntu Gnome 18.04.2, using
the inkscape-trunk PPA. When I use Xorg, the problem disappears, on both
distros. This is rather problematic though, because all (?) linux
distros that have gnome also have Wayland enabled by default these days.
Any pointers? A bug report maybe? Otherwise I will file one myself, and
start some debugging.
Can someone guide me to acquire the ability to compile for Mojave using Homebrew’s paths and dependencies? I would like to help maintain the build for Homebrew. Would also like to help maintain the build for MacOS in general, in case you also need help for MacPorts.
By the way, Inkscape 0.92.2 (the last build for Homebrew) does not work with Mojave. https://github.com/Homebrew/homebrew-cask/issues/62404
I wanted to share a little side project I've been doing for fun...
Our Paypal link includes a memo field, which Inkscape's donors have used
to say some very nice things over the years, that deserve to be shared
with you all:
This is a simple applet to cycle through the non-blank donation memos,
from today backwards. It refreshes daily, although Paypal processing
adds a few days lag so it's not up to the minute.
For those of a more technical bent, the full data is at
http://alpha.inkscape.org/cheers/cheers.json. I'm posting that in the
open in hopes it can get integrated and used in other places; no changes
are planned for the data file format, so consider that stable.
The code itself for the React.js applet I've stuck on github here:
I'd like to improve the styling a bit, but otherwise am done with this
for now. Eventually this is going to be integrating into other finance
displaying scripts I'm working on... but that'll be news for some other
tldr; - Just an update on my earlier email on release status. We're
still on pause waiting on blocker bugs, no ETA for release dates yet.
Progress is getting made.
There is a lot of good activity going in by RdH, NPJ2000 and others to
get the Mac OS native packaging established. Some of that work has
landed already, and screenshots are starting to get passed around.
Of the two blocker bugs we're tracking, the test rendering offset bug
(#45 in inkscape's gitlab) is well understood now and is down to
figuring out the right form of fix, and the extensions bug (#156) has
been progressing nicely, although I don't know the exact status at the
We have 17 open bugs milestoned to 1.0:
Ideally we'd drive this list down to zero by release, although if we can
close the two Critical bugs and most of the High priority bugs we should
be in decent enough shape.
I've been thumbing through other bug reports, crash bugs in particular.
There's a lot, but thankfully most are not things ordinary users are
going to run into, as they tend to be a bit obscure. But obviously, the
more of these we can resolve before final release, the better. Please
devote some of your time to looking at bugs, even if you're not a
programmer you can do analysis and testing which can be invaluable.
Triaging work is also HIGH VALUE right now, most particularly for
tagging bugs and assigning importance levels to all bugs in the main
Chris and Maren collected a listing of problems they'd love to see
fixed, from an actual product usability point of view:
These need to be migrated to gitlab, milestoned for 1.0, and set as High
priority. Great way to score levels in the bug game, while directly
helping towards making the software stronger.
So, as to scheduling of the beta release... Since the two blocker bugs
are blocking the release process, I think it would not be wise to set
any dates just yet. However, I think beta could be released shortly
after they're resolved (or no longer considered blockers). Focusing
beta on the Mac OS package would be wise, so we can maximize user
testing, so I would also include its status in the schedule
Scheduling of release candidates for the final 1.0... June looks pretty
unlikely given the work remaining to be done. I'm guessing a late
summer release may be more likely, although difficult to predict.
I am SrrReal, a FOSS enthusiast and Inkscape user. Currently, I am a student researcher (in India) doing social sciences research of digital technologies. I recently began working on a project to explore how the identity of free software communities is shaped by its contributors. As an Inkscape user, I was keen on studying this by closely following the Inkscape community.This work is part of a course on ethnographic research - a type of research in which researchers engage closely with the people involved in the context they are studying, to gain a deep understanding.
I am writing to introduce myself (and my research) to the broader community. In the coming weeks, I hope to chat with many of you, who do different things to make Inkscape what it is!
I have put together a short survey - https://srrreal.typeform.com/to/dfhjFV as a preliminary step to guide further research. It's got about 2-3 questions and shouldn't take more than 5 minutes. It would be really helpful, if you could fill this out.
If you would like to chat about the research in more detail or have questions and suggestions (what to probe, what may be interesting, etc), I'd be happy to discuss that further. Please email me [srrreal@...3637...] or ping on Rocket Chat [@SrrReal]. Or you could indicate your interest in the survey and I'll get in touch with you!
Recently i found a bug, i don't know if this has been reported but here is.
When you use fonts, the box that contain the text cut the base of this.
When you are editing the file doesn't appear, the art looks well but when
you export this to png file, the bug appear.
If you convert the object text to traced, the bug doesn't appear either.
In my project the png looks like this
in inkscape the art looks like this
Thanks for the attention and see you soon.
José Quintanilla Ramírez
You've landed dozens of contributions to Inkscape and been recommended
by Mc and Speleo3 to have commit rights to trunk. I've granted your new
access permissions and want to echo their appreciation for your
dedication. Keep up the good work!
You don't need to change anything about your current workflow right
away, if you're comfortable with it. The other developers can answer
questions and give guidance when you're ready.
It would be great if you could assist other prospective contributors by
helping review the merge request queue, there's a lot of good work there
that needs good shepherding.
Thanks again, and welcome!