Slashdot Mirror
Here's What 2019 Holds For Paint.NET (betanews.com)
The developer of the popular image editing tool Paint.NET, Rick Brewster, has shared his vision of what the coming year holds for his software. The 2019 roadmap for Paint.NET is an exciting one, promising migration to .NET Core, support for brushes and pressure sensitivity, and an expanded plugin system.
BetaNews: Changes are on the cards for app icons and improved high-DPI support -- something that may be seen as mere aesthetic by some, but important changes by others. Switching to .NET Core could have big implications for the software, as Brewter explains: "It's clear that, in the long-term, Paint.NET needs to migrate over to .NET Core. That's where all of the improvements and bug fixes are being made, and it's obvious that the .NET Framework is now in maintenance mode. On the engineering side this is mostly a packaging and deployment puzzle of balancing download size amongst several other variables. My initial estimations shows that the download size for Paint.NET could balloon from ~7.5MB (today) to north of 40MB if .NET Core is packaged 'locally'. That's a big sticker shock... but it may just be necessary."
And, for those who're interested: the move to .NET Core will finally enable a truly portable version of Paint.NET since. Proposals for better DDS support and brushes and pressure sensitivity will be welcomed by digital artists, and there can be few users who are not excited at the prospect of an expanded plugin system.
And, for those who're interested: the move to .NET Core will finally enable a truly portable version of Paint.NET since. Proposals for better DDS support and brushes and pressure sensitivity will be welcomed by digital artists, and there can be few users who are not excited at the prospect of an expanded plugin system.
Why would I prefer to download and install this over GIMP?
Just askin
I can't tell you what you prefer. But I can point you at a comparison site so you can make your own decision (the Paint.Net vs Gimp is about 2/3 of the way down)
http://fixthephoto.com/paint-n...
I am Slashdot. Are you Slashdot as well?
Blenders problem was that it was a inhouse 3D editing tool intended for polygonal editing.
So what was Blender 2.49 good at? Using hotkeys to edit models. Using textures to modify models. Modifying models.
It had enough tools to do primitive animation and physics, but not well presented UI to make the USER use those features.
And if you used 2.49 you know that the internal render is crap, but the user interface is atrocious.
Hence 2.50 was a eventually, where a massive project would try to make everything in the suite as impressive as the raw 3D editing was. And going from 2.49, to the beta, to cycles, to whatever the last version i used: I would say their success should be held to unrestrained clapping and cheering.
The key remaining problem is that Blender is now a "Advanced 3D package", where the less primary features such as animations still has a terrible UI. But advanced users can't tell that because they have learned it, and gotten used to the quirks. This extends to rendering, physics, and all other tools as well.
I hope since they used it they finally added a direct selector to texture painting, instead of randomly having one of 3 possibly windows having a non visible selector.
Paint.NET is standalone software. You're thinking of the Paint program that comes with Windows.
Irony: Agile development has too much intertia to be abandoned now.
It's being developed more slowly than .NET Core is as it's far more widely installed and changes that are being made in Core are not necessarily going to be applied to the framework as they might break things. It's not being abandoned but Core is the future.