![]() ![]() When I get to that point I’ll make a thread here about the basic workflow, because there’s some UX things and potential bugs that I’m unsure about. Then I’ll be working on getting text-in-shape ready, and after that I’m investigating an ability to programatically edit text which will be the basis for the oncanvas text tool. I still need to work on tests for this initial set of updates, and one of the other devs (amyspark) is going to help me optimize the shape. I’m currently focusing on getting the text layout to handle everything we need it to handle, which in turn got interrupted by the documentation and release notes for 5.1. blender does a similar things for when they’re working on larger feature projects and its a pretty interesting read.Īs the person doing the text work, I’ll be working on text-on-canvas at some point, simply because the current text editor won’t be able to show everything the text shape will be able to handle (the most blatant of which is vertical layout). I would personally love to read more in-depth posts on some of the work being done though! developers showcasing what they’re working on (or have been working on) and talks about why they’re doing it, decisions that had to be made, and goals for the future. for example, dealing with tax authorities back in 2017… theres also a lot of time-consuming work required to maintain a large open source project that wont show up in release notes. file format support, library maintenance, color space handling, general bug fixing and optimization, and large scale projects that take several months for a pair of developers to get to a presentable state. ![]() ![]() I think its important to highlight that theres a lot of work being done that isnt immediately obvious to users but thats very necessary for kritas longevity and performance. This was a really good blog post addressing some key points in a recent discussion. ![]()
0 Comments
Leave a Reply. |