Hi Andrew, As far as I understand, you will want to make a new feature request, in the new gitlab bug tracker, which is here: https://gitlab.com/inkscape/inbox/issues. Click on the green "New Issue" button. If you have technical or development details about how you think it should work.....I'm not sure where that should go now that we've moved away from Launchpad. Maybe in the wiki? Basically you would write a proposal with all the details you have, and link that page into your gitlab Issue. Since I've answered, I might add that I've never used GIMP's vector tools. But I have the impression, from reading comments here and there, over some years, that GIMP's vector tools are fairly rudimentary, and not nearly as sophisticated as Inkscape's. Personally I'm totally happy with Inkscape's Pen/Bezier tool. But now you've made me curious, and I might have to test GIMP's tool. I wouldn't post it in the new forum yet, because not very many people will see it. But you could post it for discussion in other forums. However, keep in mind that the forums are primarily user forums, and developers probably won't see it. Devs will see it from gitlab and the wiki (or wherever). But one good thing about posting in a user forum, is that you might learn about more Inkscape features that you weren't aware of before. Or there might be different ways to do some things. Hhmm....well, there might be some gitlab feature that would work for such a proposal. I'm not all that familiar with it, and typically get lost there, if I'm looking at anything except Issues. Maybe someone else can explain about that, if there's a way to do it on gitlab. All best, brynn -----Original Message----- From: Andrew Kurn Sent: Saturday, January 26, 2019 5:16 PM To: Inkscape User Community Subject: [Inkscape-user] new post - wish list I would like to post a wish list item. I'll tell you the topic. You tell me whether I can post it to the new forum (possible?) and whether I should (advisable?). The current user interface for drawing and editing splines (Bezier) is bad. I like the Gimp one much better, but partly because I'm used to it. We can go into detail, but this introduces the topic. Let's improve the spline interface. How to do it? Andrew _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user

Hi Andrew, As far as I understand, you will want to make a new feature request, in the new gitlab bug tracker, which is here: https://gitlab.com/inkscape/inbox/issues. Click on the green "New Issue" button. If you have technical or development details about how you think it should work.....I'm not sure where that should go now that we've moved away from Launchpad.

This is my wish:

Note that it is spelled https://electronjs.org/ . No k.

This is my wish: https://medium.com/@ole.ersoy/rewriting-inkscape-in-javascript-7e351738c37c Cheers,

> Why in the WORLD would a team actively maintaining and improving a > complex graphical project for at least 12 years, with no hint of being > painted into a corner, stop dead in their tracks and rewrite their > software in another language? Why would anyone suggest they do so? For the same reason is driving developers to switch to VSCode.  I have added many more technical and strategic reasons, including expanding the potential developer pool (There are a lot more Javascript developers than C++ and the inverse relationship is accelerating because Javascript can run on both the server and client), but the main reason I would do it personally is because it's fun and it would expand my skill sets in new and creative ways: https://medium.com/@ole.ersoy/rewriting-inkscape-in-javascript-7e351738c37c Newer vector graphics software like Gravit Designer could render Inkscape irrelevant depending on the speed and iteration at which they and VSCode editor plugin development executes.  Once users start sharing prototypes of drawings in the cloud and are able to live edit and fork instances of drawings it becomes a natural default to gravitate to.  Does that paint Inkscape into a corner? Who knows?  But it's definitely a better application if it can be embedded in blog posts and served up as a progressive web application with shared sub components that are consumed by an expanding ecosystem of users. Cheers, Ole

> expanding the potential developer pool (There are a lot more > Javascript developers than C++ and the inverse relationship is > accelerating because Javascript can run on both the server and > client), but the main reason I would do it personally is because it's > fun and it would expand my skill sets in new and creative ways: Fun is good. So is expanding your skillset.

So go ahead and rewrite Inkscape in Javascript. But don't distract the Inkscape Developers with calls to rewrite perfectly functional code

for an extremely well functioning program. Those of us who actually use Inkscape for: * Art * Diagrams * Active images * Flyers and newsletters * Mailmerged certificates * eBook covers

appreciate having developer time available for fixing any bugs (I've never found any) or carefully adding new features, rather than rewriting a hugely featureful implementation of a solution to a naturally complex problem domain for fun and experience.

Not related much to your realtime co-editing vision, but I have really appreciated the upload/download to OpenClipArt feature in terms of allowing others to help with my projects even without necessarily knowing it, and me doing the same in turn for yet others. I guess my wishlist item would be for this existing feature to become just a module in a framework for other repositories to upload to and/or download from, in particular Wikimedia Commons.

On Wed, 27 Feb 2019 18:55:16 -0600 Ole Ersoy <ole.ersoy@...155...> wrote: > This is my wish: > > https://medium.com/@ole.ersoy/rewriting-inkscape-in-javascript-7e351738c37c > > Cheers, Why in the WORLD would a team actively maintaining and improving a complex graphical project for at least 12 years, with no hint of being painted into a corner, stop dead in their tracks and rewrite their software in another language? Why would anyone suggest they do so?

I understand the value of ElectronJS: I use Kivy occasionally and apparently ElectronJS has the additional advantage of native look and feel. I'd consider using ElectronJS for new construction. But rewriting an existing application? No. SteveT _______________________________________________ Inkscape-user mailing list Inkscape-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user

Should probably have used to word "Transferring" and "Modularizing" instead of "Rewriting". I'm sure the Inkscape devs are brilliant and the code is solid. The medium posts is more targeted at what you can do once the code sits in a different platform, which I also presume will make the entire architecture nimble WRT embedding and collaborating on the web and module reuse / sharing.

transfer or moduralise to Javascript while replacing Cairo and all the intensive bits of technology?

We have done everything we can think of, to make sure people who want to report a bug go to gitlab from now on. . . .