User Details
- User Since
- Apr 15 2015, 8:03 AM (471 w, 2 d)
- Availability
- Available
Mar 6 2024
The angular brackets thing for includes outside has actually been our coding standard since the kimageshop days, but lots of people are pretty sloppy -- and then also, files get moved from library to library.
Nov 29 2023
Okay, here is the proposal based on the KDE CI scripts:
Nov 26 2023
Okay, the Windows CI is now fully deployed. There is only one todo item that should be fixed before we move release builds to Gitlab:
Nov 20 2023
Oct 2 2023
A note from bcooksley: I would suggest we use something like teams/krita/ [namespace] for hosting those [forked dependencies]
Sep 25 2023
A text shape can flow into multiple shapes, within SVG these are just linked, so both grouped and ungrouped is possible within SVG.
Sep 18 2023
Aug 31 2023
Btw, a new set of weird technical questions:
Right now, for text path we are required to only apply 'local transforms' on the textpath
Aug 29 2023
Can this include changing the text orientation from inside the path to outside the path (for example text outside the circle and text inside the circle path)
Aug 28 2023
Aug 14 2023
Aug 7 2023
Just a note: we need some better way to manage git repositories for the deps. The thing that happened today was that @lsegovia removed a branch in their personal repo (I guess it was renamed, though I'm not sure), and it broke our deps builds.
Jun 22 2023
first update the deps, verify Krita still builds with it, and then have an MR for Krita. I'm not sure why, but I think it would give me a bit of a safe feeling...
Jun 21 2023
Just a note:
Jun 14 2023
There are two different sets of expiry times we're referring to here i'm afraid
Thank you for your replies!
Jun 13 2023
Jun 7 2023
Jun 5 2023
Weston's ICC -> GPU implementation:
Jun 1 2023
May 31 2023
Oh, another manual needed:
May 30 2023
So, what you're saying is that having deps commits mixed in with Krita commits helps somehow to figure out which dep change was related to which change in Krita <...> I don't think that's important at all.
Well, no. It won't be materially different because right now the deps build and the krita build are completely separate already. They might be in the same repo, but the build systems do not connect.
May 29 2023
Problems of the split repos:
May 26 2023
Krita's unstable branch would always checkout the master branch of the deps repo
Maybe related, maybe not, but I thought today that maybe we should spin our deps build system into a separate repo with stable and unstable branches, and actual releases.
May 24 2023
May 10 2023
Notes on the KDE's CI system
Apr 18 2023
After yesterday's discussion on IRC I have added one more requirement to the system:
Hi, @alvinhochun and @vanyossi!
Apr 17 2023
The ASWF dependency management system for the VFX platform images relies on compositing Docker images
Mar 10 2023
I have seen this warning when writing the lager code. I even tried to switch to the lambda syntax, but the resulting code looks a bit too verbose. Specifically, you need to explicitly declare all the typenames for every function argument (which might not known in the template context).
Jul 11 2022
So, conceptually, we divide that GlobalRect into smaller contiguous, non-overlaping, regions or tiles
Apr 19 2022
What is the difference between having a group with one child and having a layer with a mask? In both cases it's two entries, one below the other. Both can be compressed to just one entry, too.
the shape for background and for the border is the same, but the border one has only stroke and the background one has only a fill
Note about workflow of the knife tool:
stroke with brushes after creation
Feb 23 2022
And it seems like there is a golang-based tool that allows auto-generation of SQL files for migrations (redo+undo steps). We could actually use that: generate undo/redo SQL files with the tool and add them into the C++ wrapper that fills in the data in the new columns if needed.
Google says that the most popular Python-based migrations library (after Django) is Alembic. It also has undocommand-like API, though it doesn't have auto-generation of the undo steps.
I'm mostly worried about making life miserable for our beta testers. That would mean only going back one version
Feb 22 2022
Having possible steps between versions of the database that update an existing database to the latest version is fine, but should be decided on a case-by-case basis. My experience with maintaining a database schema dates back to the nineties, but this is how we did it back then, for our customers...
Feb 13 2022
Jan 13 2022
The proposal looks good to me :)
As far as I know, at the current state, sysadmins do everything to avoid adding any new images to Jenkins (due to the migration process). Though with the latest updates from them, you can try to install that into GitLab CI directly. It is kind of allowed now
Jan 7 2022
Just a note from IRC:
Dec 23 2021
With breaking some of these dependencies, I am not sure if that will mean the UI aspect will need to change at all
Dec 22 2021
Dec 10 2021
The task is implemented and merged now! :)
Dec 7 2021
Now when I think about it, the feature might be overlapping with the "tool presets" feature. People might start using them as presets for the tool options, e.g. Stabilized liner vs Sketch pencil. So it should be taken into account as well [0].
Dec 2 2021
From what I understand they want to switch to last used eraser preset when they switch to the "Eraser tool" They are okay with having current brush turning into and eraser but they miss the feature where they can click the eraser tool and switch to the last used brush preset as eraser.
That won't satisfy the people who want to see an eraser tool in the toolbox...
I have a feeling that giving "mutliple instances" for all the tools might be a bit of overcomplication. Especially in its definition, because it may be expected for tools to have different options in the "Tool Options" docker.
Oct 14 2021
Okay, thanks! I'll try to implement that tomorrow :)
In particular, all non-image objects call the KoShapeBackground, which in turn draws their qpainterpath for them
Sep 25 2021
This is not correct, section "Dependencies on OpenGL ES 2.0" does list it as available; also, none of the simplifications apply because you only used InvalidateBufferData for your macOS MR.
Sep 24 2021
- OES_vertex_array_object on openGL ES 2.0
Sep 13 2021
Sep 12 2021
I guess that we should take a bit different approach to the audit. It is quite difficult to discuss "what version of OpenGL we should set as a minimum requirement". We will always have some users with rather old hardware (it happened when we tried to drop openGL 2 support, but then recovered it back).
Sep 10 2021
I'll check it tomorrow. On Linux we seem to be still on 3.0 (at least on my Linux Laptop).
Aug 30 2021
what would happen if we went SQlite for the preferences handling?
Aug 26 2021
I don't think using a namespaced definition would be OK, because we'd need to leak the implementation details (QDomDocument, QSettings instance) to let the accessors get the values.
Aug 24 2021
I tried to refactor KisConfig in 2018, but stopped because it appeared to be too much of work. I tried to solve the following issues, perhaps you can address them in your implementation as well:
Aug 5 2021
Jul 8 2021
The short review for the code existing atm:
May 31 2021
a gradient is used on a number of pages and the user wants to change the gradient for all the pages..
Thanks a lot for switching into constructive discussion mode! In general I agree that this proposal will solve the issue. Though I have two questions and one problem that I would like to discuss:
May 24 2021
Now on the technical topic:
The reason this discussion has dragged on so long is basically that I am not trusted to design and write code once Dmitry has touched any part of that
One major weakness, tho, in scenario [1]: the update of the brush tip from Star(v1) to Star(v2) means Carrot would need to follow Krita blog to be notified the Star brush tip changed,
Thank you for nice usecases! I will try to model how the system will behave with all three implementation options we have atm:
May 20 2021
We still need to come to some agreement on this topic. After the Friday's discussion I tried to merge both, your feature of "dynamically linked resources" and what painters expect (based on input from @kamathraghavendra), into a set of requirements:
May 18 2021
May 7 2021
May 4 2021
After saving the latest version of a resource into a bundle, its "original md5" will change.
At least with bundles, we can save the "original" md5sum in the xml and use that for resource finding.
I am not trying to "break" anything, I'm trying to keep a relatively simple and sensible design working, instead of overcomplicating things. The version system simply is not suitable for what you're trying to do.
A version is not a resource, a resource has versions.