@Bollebib I think doing that wouldn't be too difficult but would require a new Export UI for the compositions docker to accommodate for more advanced settings (kind of like the existing Animation Exporter UI?)

Is there any chance of getting composition docker export to work with animation? this would be good for more powerful exporting options and layer control for those exported PNGS or movies

Timeline Docker: Time Change Shouldn't Mark Document as "Changed" (https://bugs.kde.org/show_bug.cgi?id=409443)

Hey @dkazakov . Thanks for the input.

so we ALMOST have cycles

-Export as PNG for different pages should also be possible, not only PDF's.
-Rightclicking a thumbnail maybe should provide the option to open the image (or a range of images) as a new krita file so you can start expanding the scene or animating. Set the size of the project and import the thumbnails into it. (wish)

@dkazakov, @scottpetrovic, @Bollebib @timotheegiet, @Deevad Added a new mockup here

My bad, I'll look into doing this on Gitlab later today!

Oh, my bad, sorry! I'll look into it later today :)

Oh damn... I know it's confusing, but the whole KDE is switching to giltab and Krita already switched (...mostly, at least what we could switch); hence, all code review is done on Gitlab on our KDE Invent instance: https://invent.kde.org/kde/krita
Instruction how to use it: https://docs.krita.org/en/untranslatable_pages/intro_hacking_krita.html#contributing-patches (you can use your current KDE account).

We use Gitlab for patch reviews now, please for Krita and make a Merge Request here.

I have two variations of the storyboard docker with UI directions. The first example is closer to the direction on how something like Storyboarder does it. The second one is a direction we could go based off how Storyboard Pro does it.

Just notes:

I can't look into this any further today maybe, but here's what I have so far. There's still that bug that I mentioned in the previous message, as well as the changes not being reflected immediately.

The layout of exported document should be configured somehow (use SVG for that?)

Humm, I'm getting a bit of strange behavior. If I alter any settings, and then reset the configurations, everything in the 'kritarc' file is deleted EXCEPT the changes done BEFORE resetting the configurations. Any clues?

I was using the already mentioned function 'askClearConfig()' on KisApplication. It does in fact delete the kritarc file from '.local/share/krita', but not the correct file. After switching to your line, it works! It requires a restart to apply theme changes though, so I have a feeling that I'm still missing one last piece of the puzzle. After that I'll create a PR!

You probably should use a line like this (remember it's not only for Linux, but also Windows and Mac. And there is higher chance that the manual page is wrong (or that the location differs from one Linux system to another) than that we should change the code):
const QString configPath = QStandardPaths::writableLocation(QStandardPaths::GenericConfigLocation);
(I took it from kis_config.cc)

@scottpetrovic We might also need to add and remove metadata fields.

The fields in metadata should be configured in per-document basis

Okay, so I made some good progress, and there's a button in the settings to reset the Krita configurations. However, there's something strange, the code says that the file 'kritarc' is located in '.local/share/krita/', where in fact it is stored in the '.config' folder. Any pointers as to how you want this addressed (puns not intended)?

@confifu, @dkazakov, @Bollebib @timotheegiet, @Deevad - I also came up with an idea for the storyboard docker for the wireframes.

This is perfect @dkazakov. Thanks for putting these functional requirements together.

Go ahead :-)

I can try to do this issue, but this is my first time looking at Krita code, and my C++ is a bit rusty, and my Qt skills are non-existent. Still, should be an interesting challenge, if you guys don't mind!

Note: we only have the crash log available on Windows. (And I've never been able to get the ctrl-alt-shift way of clearing the settings to work...)

I think that a new option in the Settings tab with a confirmation prompt would suffice. I also agree that a way to access crash logs would be really useful. Something like a pop-up showing the latest 10 crashes, maybe?

I tried to sum up what I suggested on IRC today:

Conversation with tiar on IRC on 16 March 2020

Conversation with @Bollebib on IRC on 16 March 2020

Options suggested for saving and loading data by @rempt on IRC on 22 March 2020

Option 1: Every board is a .kra file and can have everything a .kra file can have, including animation. A metafile describes the storyboard. The docker would load the xml file and thumbnails, but only the active board is loaded in krita
Option 2: the .kra file contains the board as separate images. You’d save the .kra file with multiple images inside. The docker would load the kra file and find the boards. All boards are loaded into memory.
Option 3: the .kra file contains layer groups, and every top-level group is a board. The docker would list the top level layer groups, and when a board is selected use the isolate layer feature on that group to show the board.
Option 4: Reusing the technique the compositions docker uses. That would make it possible for different boards in a storyboard to share elements, like a background layer. Basically, every board then consists of one or more layers from a single Krita image.

a single .Kra seems more manageable

For the waveform visualizer UX, we could do what audacity does, so dropping this link for reference.

@Bollebib @timotheegiet Is saving a .kra file for each storyboard image and loading them from those saved files okay, or we should save those images inside a single .kra file as storyboard images.

@scottpetrovic We can add a QList of storyboard structs to KisDocument. Changing kra_saver and kra_loader might be needed for getting that data to and from kra file and KisDocument. I think we wouldn't need the animation API. Would the animation API have any advantage over saving it explicitly as a member of KisDocument ?

number 8 seems a bit weird though. Having a visibility button would mean the comment section will dissappear when you click it no?

@confifu as a first glance the mockup looks okay.

@scottpetrovic I never/rarely use text , so it should also work as a purely visual tool.

If I was doing this, I would probably make the storyboard docker a separate docker than the timeline and animation docker. Under the hood it would still use the existing animation API, but you wouldn't need those other dockers to do storyboarding. The reasoning for me is that storyboarding is a separate part in the workflow, and I think the decisions that people want to make are different. The few times I have storyboarded, this was the workflow I have used.

@Bollebib Should we make the storyboard docker independent of timeline docker. That way you can add any image on the canvas or even .kra files. For "playing the storyboard" we can have a duration associated with each image in storyboard and play it from storyboard itself.

So, the clone animation stuff is actually already very far in progress (it's in the cycles patch), but tyyppi never finished it. There's some leftover bugs with it.

I may have missed it but this is something related to animation and that Tyyppi knows about, maybe it should be included here.

1. A small little request may be that using mouse scroll no longer goes from frame to frame but that it scrolls the timeline up or down

this is interesting but is a huge task tho. This would need lotsof mockups first...

i think if it was only visual that would also have limitations and annoyances

Thank you for your comment. My shortcuts are different, so if I press the alt-[ and alt-] combo it works! Yes. i should have read the manual.

@hurgar You can cycle up and down layers using the "Page Up" and "Page Down" keys. =]

Would it be possible to pickwalk throug the layers in the timeline docker? If you press up or down in de timeline docker you change the selected frame, but it would be handy if you could walk through the layers just as in the layers docker. And what would other users think of "isolate selected layer" so that you can view the contents of the layer while pickwalking through the layers.
The function would only make the layer visible that is selected, and if you select another layer (by mouse selecting or pickwalking in the layers docker or timeline docker), than that layer is going to be the only layer that is visible.

@Bollebib also suggested adding more Layers Docker functionality to the Timeline Docker.

In T12801#223052, @ognarb wrote:

• Enve use travis for the CI, we could replace it with Jenkins but we can't build AppImages yet with it.

Krita uses Jenkins to build appimages for both nightlies (both stable and from master) and for all releases and beta versions: https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ - I don't know technical details though.

• Enve is very young project and doesn't have yet an translations infrastucture set, so it would be easy for them to adopt the KDE localizations infra.
• Enve use github but it is easy to migrate to gitlab
• Enve could need some help with their website and promotion, something that the KDE web and promo team can help with

I think this would be interesting for everybody working on the "All about the Applications" goal also.