4 ms·
Yikes! I can't imagine working like this. Every node based editing system I have used behaves exactly like you describe where adding/dropping a node on a connec
by dylan604 4y ago
Yikes! I can't imagine working like this. Every node based editing system I have used behaves exactly like you describe where adding/dropping a node on a connection between to existing nodes automatically connects the new node as expected.
The only time I've seen this add new, disconnect, make new connections are in chart/graph programs like Omnigraffle or similar programs people draw up database schemas and network topologies. Maybe the devs came from that kind of world?
- WastingMyTime89 4y agoThat’s UX improvement and we are taking about a v0.6. Maybe the devs were simply focused, on you know, making the image editing part work before working on quality of life improvements.
- dylan604 4y agoBut with enough prior research into what was there, this is the kind of thing that gets added to UX immediately, not in v1.x
- Ralfp 4y agoThis is an open-source project with 13 contributors and initial commit made two years ago you are talking about. Is it really fair to expect them to have everything from version 0.6? It's likely that they have 2137 other must-have features or blockers they have to divide their attention between.
- dylan604 4y agoDon't post your not ready for prime time project to the public if you're not open to public opinion. "here's my project i've been working on for 2 years, but don't tell me anything about what needs improving because i'm not done yet" it just farcical
- forrestthewoods 4y agoIf your biggest complaint is a relatively minor UX improvement then they're crushing it!!! TBH, that's about the most shallow, surface level feedback that could possibly be given. This project is providing a pretty radically different paradigm for image editing. Is that a good paradigm? Is it useful? Does it allow novices and/or experts to do work faster? Are there things it can't do? What would it take to do those things? Does it need new nodes types? More options on existing nodes? I don't know the answer. TBH it's a pretty hard sell. Either it works or it doesn't. A missing feature in the node editor is not in the Top 1000 most important things.
- dylan604 4y agoIf your app slows down the user by having to make repetitive tasks because your UX is lacking, then there's a whole lot of no responses to your questions. Not really sure how that's hard to comprehend. Eliminating repetitive tasks is why we invented computers. Using a computer to create a new method of repetitive tasks is not good use of those computers or the user's time. It's like the first gens of iOS that did not allow for copy&paste. Was that a shallow bit of feedback? No, because it's some of the most basic functionality a user would expect to be there. If iOS and no copy&paste was released in the 1980s, it might have been forgiven. Since it was released in 2007 after anyone using computing had seen/used copy&paste and the competing product did have that functionality, it was a huge slight against it. Was copy&paste the core functionality? Probably not, but it was a huge hindrance. After getting past the fact this is node based editing, it's pretty much an image editor after that. Again, if anything you try to implement is less than pre-existing software, what's the point. So, when you present an application that is supposed to be paradigm shifting, you better be backing it up. Again, don't want public comments, don't post the software to public forum created solely for public commenting.
- forrestthewoods 4y agoThere’s an obvious difference between “save two easy clicks” (node graph) and “save dozens to hundreds, and sometimes thousands, of awkward taps” (iOS copy/paste). If you think this feedback is genuinely helpful and valuable that’s cool. All I can say is yikes.