goal of krita

does krita have a goal to be perfect? (being the best: drawing, picture editing, animation and video editor program there is).

Yes, in docs.krita.org this is stated:

Krita is a free and open source cross-platform application that offers an end-to-end solution for creating digital art files from scratch. Krita is optimized for frequent, prolonged and focused use. Explicitly supported fields of painting are illustrations, concept art, matte painting, textures, comics and animations. Developed together with users, Krita is an application that supports their actual needs and workflow. Krita supports open standards and interoperates with other applications.

And on krita.org this is stated:

Krita is a professional FREE and open source painting program. It is made by artists that want to see affordable art tools for everyone.

  • concept art
  • texture and matte painters
  • illustrations and comics

Krita doesn’t try to be a video editor at all. There are lots and lots of features unique to video editors that Krita won’t be making, or they will be working differently anyway.

2 Likes

so can I offer a list of ideas what can be added? if yes, where can I write it?

A list of ideas would be too much. We already have over four hundred feature requests in bugzilla (Bug List). In general, if you want the developers to add a new feature, you’re going to have to follow the process outlined in Developing Features — Krita Manual 4.4.0 documentation.

To add to @halla 's message, please remember that one idea like that can easily take weeks of even months of work. Out of respect to how much work it needs, one should not treat the ideas lightly but think carefully about what is the most important and most useful for the most of the userbase.

Generally if you make an idea and you want it to be added to Krita, you need to develop it with other artists to the point where the developer can come, see all the details and just start implementing right away. Think of yourself and other artists as a team of architects and developers as builders; builders are not supposed to guess where the walls should go or what is their thickness. Builders just go, look at the plans and they know exactly everything, because everything is written down (in Krita’s case: all the UI, all the user interaction with the tool or feature).

Of course, in case of Krita, developers are often more experienced so they might step in and say “this is not the priority” or “no, this is not feasible, maybe it would be enough if it did this” or “it’s better to do it this way” or “maybe let’s generalize it a bit more”, but in most cases it’s best when the artists flesh out the ideas using other tools as example how things should be done, and their workflows as a guide what features they need. If a developer needs to think about “but what parameters this feature should have”, it is usually a bit of waste of time.

And note that if you just make a list of ideas and expect other artists to step in and help you build them up to the state when the developers can start implementing them, you will most probably get disappointed, because most other users will come to your post, see like ten different one-sentence ideas and just leave because there is just too much to do, too much to discuss. It’s much better to start from one idea and put some amount of effort in it so other users can see that you’re serious in that and you want to collaborate together to figure out the best design.

Note that even the best design might still not get implemented if it’s deemed low priority by developers or too much to do right now or for some other reasons, and no volunteer came to help. However the design will be just waiting patiently until the time will come. And idea, on the other hand, will just mean that even if a volunteer ready for some work comes, they will choose something else, something “actionable”, something they can implement right away.

yes, I understand.
can I just ask something?
is there a place people can debate how to build things, so whoever want to offer something, if he want to help in giving advice of how to build it, he can give advice.

This is a good example of a thread where a simple feature request was proposed, discussed and implemented: A way to avoid storing the visible result in a saved project

This is a good example of a thread where a more complex feature was proposed and discussed, but implementing it will take time: Layer comments

does krita do a list of links to features request?
probably you have, but is there were other people can see that list, so they can give more idea how to do it?