Earlier quoted context omitted.
Unfortunately, this 'not completely changing interface' has a side effect: it fails to evolve and become better. I am a long-time user of Inkscape (since 2007 at least), and it is sad how poor it looks now next to Sketch/Figma. Their vector tools are better, their layer tools are better. It's a million little things that make drawing a similar shape in Sketch 50x faster than in Inkscape.
It doesn’t need to be any better to satisfy this user. I also pull it out 2-4 times a year and am happy that everything has more or less stayed the same for 8+ years.
Inkscape 1.0 Beta 1
111–120 of 170 posts
Re: Inkscape 1.0 Beta 1
#112Re: Inkscape 1.0 Beta 1
#113Earlier quoted context omitted.
huh, what OS are you on ? I have hidpi screens since 2014 and inscape has always honored Xft.dpi
Are you using Xorg or Wayland? When I looked into it last there were issues in Wayland when you set the Xft.dpi clashing with things like GDK_SCALE. Like the GP I've hardly been using Inkscape recently as it's such a pain with the small icons.
Re: Inkscape 1.0 Beta 1
#114Earlier quoted context omitted.
I know and I feel bad about it, but I have to make some compromises due to limited resources. Supporting all major operating systems is already a huge undertaking even if you use Electron. Besides, everything seems to suggest that Firefox will be out of the market in the next couple of years. At least unless Mozilla adopts Chromium engine like Microsoft and Opera did.
I understand that you have to focus your resources onto Chromium; but don't count Firefox out yet. The way Google is behaving nowadays coupled with the progress that Firefox keeps making, there will be a sizable group of us Firefox users for the foreseeable future. And, we're a vocal bunch, too!
Re: Inkscape 1.0 Beta 1
#115Earlier quoted context omitted.
Full feature parity with Inkscape in a year is a bold claim, and I’m rather sceptical of it. You have built an impressive app (and I’m sure that being just one person helped with that), but there is a lot of advanced functionality in Inkscape that you don’t have at present. A few examples that spring to mind: full pressure-sensitive tablet support (and sure, this is the beauty of using the web as your platform—it’s a…
I did test the app for compatibility with Wacom Intuos. "Blob" tool already supports pressure sensitivity [1], as you said it was relatively easy to implement with the Pointer Events API. I'm not sure how pressure and tilt information could be used by other tools (other than "Spray") as SVG does not support stroke with variable width. Tracing could be easily implemented using third party libraries [2]. Custom extensi…
Inkscape 1.0 adds what’s basically a more powerful version of that, a pressure-sensitive pencil, implemented with the powerstroke live path effect—more powerful, I say, because it’s editable, because it’s not immediately flattening it to what SVG can represent, but is also keeping its own editor information in namespaced attributes. That’s how you can add things like that and mesh gradients before SVG supports the concept.
I’m still intensely sceptical of your claim of full feature parity with Inkscape in a year, but I’ll believe parity for >95% of users and use cases.
My biggest problem with your app at the moment looks to be that path editing is painful compared with Inkscape. I like to show the outline of the path, and its keyboard and mouse operation also feels just all-round superior at present, and I don’t think that that’s just my greater familiarity with Inkscape showing through.
I’d also like more text labels and fewer icons. Iconless labels have no place on something like your filters panel; text labels are objectively superior. I’d say similar for the Defs panel and other such panels.
I wish you joy!
Re: Inkscape 1.0 Beta 1
#116Earlier quoted context omitted.
It doesn’t need to be any better to satisfy this user. I also pull it out 2-4 times a year and am happy that everything has more or less stayed the same for 8+ years.
That was my point. Sure it could be better, but at a cost (design+dev'p, and alienation of users). It seems big/commercial softwares love to take that cost.
Not enhancing UX because some users might have already gotten used to the current setup is rather shortsighted (relevant XKCD: https://xkcd.com/1172/ ). What about all the people you don't get on board because the UX is terrible compared to all the other tools?
Re: Inkscape 1.0 Beta 1
#117Earlier quoted context omitted.
Me too. I only recently came across TikZ which is an even more epic way to TeX up fancy diagrams (you "program" them). Still use inkscape for most stuff though.
You and GP wrote "[to] TeX up", is this a common idiom?
Re: Inkscape 1.0 Beta 1
#118Earlier quoted context omitted.
https://caniuse.com/#compare=firefox+71,chrome+80
I meant what it doesn't support that your application needs, not the general differences in terms of functionality.
Re: Inkscape 1.0 Beta 1
#119Inkscape is my go-to example of why FLOSS is great: * Learn how to use it once * Keep using it for a life time * Not completely changing interface every major release * Keeps getting better (some commercial software seems to bloat beyond repair) * Available on many platforms * All of the above for FREE Now I dont need to do vector graphics every week, not even every month. But for those couple of times a year it's go…
Unfortunately, this 'not completely changing interface' has a side effect: it fails to evolve and become better. I am a long-time user of Inkscape (since 2007 at least), and it is sad how poor it looks now next to Sketch/Figma. Their vector tools are better, their layer tools are better. It's a million little things that make drawing a similar shape in Sketch 50x faster than in Inkscape.