Have the UIs and mechanisms of brush editing, brush preset managing been redesigned as well? Or is it just that the internal codes of them has been replaced?

Just curious.

Right now the plan is only to replace the internals. This is so much work on it's own, that we're not even done with the core aspects at this moment(like, only boud has been working on this, because it right now is more inefficient to have more people working on it), we're hoping to get to the point more people can do work on it this month.

There will be some ui changes, like some in the resource management for better insight into what the resource system thinks it is doing, but nothing in the selectors and the like. We're hoping that once we've got the basics solid and non-buggy we can start extending it.

Thanks for all the work as always.

One more question, when I try to make a bundle in the current system : if I select (for instance) a textured brush preset, I have to additionally select the tip and texture for the brush preset to actually include the whole components of the preset. Is this an intended behavior? Or can I expect this to be fixed for the new system? (I'm not gonna be disappointed if it's not. Just asking.)

One more... If I make a preset using a tip from any external bundle, the tip is gone when the bundle is deactivated, so the preset becomes unusable.
I hope it will be fixed as well in the future.

We're hoping to have both issues fixed in the new version of the resource system, yes.

I haven't followed the development of Krita for a while now. Has the duplicate brush tagging issue been resolved meanwhile?

andreasresch wrote:I haven't followed the development of Krita for a while now. Has the duplicate brush tagging issue been resolved meanwhile?

That too is something that the resource rewrite intends to address.

As in, those bugs shouldn't happen (they are actually "fixed" (refactored out ) already, but it's not suitable for users yet), but there might be some new ones when we finish. It would be great to have people test it, not right now, but maybe in one or two months. We of course try to test everything, but we do rely on volunteer users testing development versions to report bugs before it's released to other, less technical, less advanced users.

We'll be releasing alpha version at some point in the future, I really hope that some of people who are interested in tagging and resources in general and know where to find us will test it before we release the final version so we can fix bugs before they affect a lot of users

Previously, I worked for an outsourcing company providing testing and analytics services. Now I am a freelance artist. I understand that polishing a project is a very long process. Worst of all, it takes a lot of time, since not everyone can afford a large database of testers. It was especially difficult at first to put everything together. I even had to read some hr functions articles. But the more experience I got, the less I had the desire to continue. At some point, I just give up everything and started spending time in Krita

"Worst of all, it takes a lot of time, since not everyone can afford a large database of testers." We don't have a single paid tester, actually We rely on beta testing by the users (and of course code review and testing by developers themselves). There is some amount of users who do use beta versions of Krita to get the latest features and report bugs they find.

Btw, the resource rewrite is not ready yet... but it's coming to an end, hopefully. You can check it out on Krita Next from the website, there is a new resource manager for example in Settings -> Manage Resources... which I hope will be more comfortable. Krita Next is however a bit crashy. It's recommended to backup your resource folder and your configuration before you open Krita Next.