News for hackers. Stuff that matters.
Re:Audacity 3.0 by ketzo on Wednesday March 17, 2021 @06:42PM (#26497696)
Wow, that's awesome news!

I'm super interested in the UI design of really complex applications (like Audacity, or Photoshop, etc.). I would adore some kind of writeup on y'all's design process whenever you towards the end!

(Obviously a big ask for someone already doing a bunch of work for free, pls feel free to ignore me; just saying that I'd be interested :D)

Re:Audacity 3.0 by danybittel on Thursday March 18, 2021 @02:53AM (#26500226)
I've been designing a complex desktop application.. there's not that much info out there. I found these helpful:

Designing the Win95: https://socket3.wordpress.com/2018/02/03/designing-windows-9...

Also the final design guides: https://www.ics.uci.edu/~kobsa/courses/ICS104/course-notes/M...

A (really old) book: https://www.amazon.com/About-Face-Essentials-Interaction-Des...

Another book: https://www.amazon.com/Designing-Interfaces-Patterns-Effecti...

Oddly enough these are all ancient. There hasn't been much innovation in that space though. (apart from High Dpi and Dark Mode)

Blender recently did a redesign of their UI, they have lot's of discussions about their rationale.

Re:Audacity 3.0 by RyanHamilton on Thursday March 18, 2021 @05:22AM (#26500868)
Thanks for sharing those links. The win95 design was a great read, a proper data driven approach to user experience.
Re:Audacity 3.0 by PostThisTooFast on Thursday March 18, 2021 @05:02AM (#26500763)
"Dark mode" is not an innovation. It's a half-assed reversal of a regression.

Computers used to show light characters on a dark background. 8-bit platforms often defaulted to white text on a dark-blue background, which until just a few years ago was still available in Word as a checkbox option.

Then the "desktop publishing" craze came along, and brought the analogy of a computer screen to a piece of paper. But this inverse (black text on a white background) scheme ignored the fact that paper doesn't EMIT light. Using these systems was akin to reading the label on the surface of a lit light bulb all day.

But for two decades, Windows let you set up a system-wide color scheme whose colors would be inherited by (nearly) all applications. It was great; you could (and I did, in the early '90s) replace the dumb inverse default color scheme with a "charcoal" scheme... essentially exactly what most "dark modes" are today.

I think Unix GUIs allowed you to set up color schemes too, leaving only the vaunted Mac GUI as the hard-coded,glaring eyeball-strainer of the era.

But now that people are finally realizing that inverse color schemes suck, what did Microsoft do? REMOVE the color-scheme editor from Windows. So now we're being dribbled out "dark mode" one OS, Web page, and application at a time. And it's still hard-coded.

That's not innovation. It's pathetic.

Re:Audacity 3.0 by noisem4ker on Thursday March 18, 2021 @08:33AM (#26501975)
I fully agree that customization regressed, and it's a pity. However...

>paper doesn't EMIT light

Your retina doesn't care if the photons it receives are emitted (as with CRTs) or reflected (as with paper). If you feel like you're staring into a lightbulb, your monitor's brightness is set too high. Set it properly, and, in a well lit environment, your monitor's white should match that of the wall behind it, or that of a piece of paper on your desk.

Re:Audacity 3.0 by mortenjorck on Wednesday March 17, 2021 @08:42PM (#26498572)
Even more interesting to me, at least, would be a writeup on how the project came to be in the first place. Long-running open-source projects have a (perhaps unfair) reputation for being somewhere between ambivalent and hostile toward proposals for sweeping UX improvements, and it could be instructive to learn how this initiative got off the ground.
Re:Audacity 3.0 by eitland on Thursday March 18, 2021 @01:58AM (#26500007)
There was an interview many years ago, back when I was a student maybe, but I cannot remember where I read it (best guess is Sourceforge "Project of the Month" which used to be a thing back then at least.

The only thing I think I can remember clearly however was the question about the biggest regret which I think was one particular core datastructure that was an array but which they later wished they had used a linked list for instead.

Re:Audacity 3.0 by brokenmachine on Friday March 19, 2021 @12:15AM (#26510109)
I feel like changing an array to a linked list couldn't be that hard, but I don't know the particular complications.
Re:Audacity 3.0 by eitland on Friday March 19, 2021 @03:11AM (#26510739)
Exactly, and neither do I, I have mostly worked on Java and and with IDEs that would tell me in a nice way if what I did didn't make sense.
Re:Audacity 3.0 by cprecioso on Wednesday March 17, 2021 @07:17PM (#26497989)
I think you should check out Tentacruel’s videos on YouTube about the UX of music composing suites!
Re:Audacity 3.0 by xmprt on Wednesday March 17, 2021 @10:39PM (#26499228)
I found that video fascinating even though I couldn't really related to any of the tools he was talking about since I've never composed music in the past.

Having actually used Audacity and Photoshop, I'd love to learn a bit more about how those design decisions were made.

Re:Audacity 3.0 by cprecioso on Friday March 19, 2021 @06:23PM (#26518731)
I've never composed either, but most of his complaints are not about the specifics of the programmes but about how they fail at communicating them. Repetition, omission, modality, hiding, or over-highlighting, are problems that can crop up in any software, and he's teaching you how those are perceived by users.
Re:Audacity 3.0 by jagger27 on Wednesday March 17, 2021 @07:37PM (#26498137)
*Tantacrul
Re:Audacity 3.0 by germinalphrase on Wednesday March 17, 2021 @07:01PM (#26497869)
Even a short design rationale would be fascinating.
Re:Audacity 3.0 by noizejoy on Wednesday March 17, 2021 @06:46PM (#26497736)
You could volunteer ...