Hi Michael,

Getting started section is done, working with images checking reference manual now , I haven't yet uploaded new layer docker images. I'll do it soon

Updated the .csv page. I also included a picture from the TVPaint GUI for the export settings, I hope it won't hurt them, but please check it.

Yes images are welcome :) for the other plugins, include links?

@voltherav: I've created the page, please check and feel free to correct it. I'm thinking about some picture illustrations now. What do you think, could I add screenshots from TVPaint as well?

That is fine. :)

Ok, I'm going to make something for the csv format. But I need somebody to check the grammar, my English is a bit weak.

we need someone to demo spriter and csv export. @fazek maybe you could make a step-by-step for csv export/import between Krita and tv-paint?

did import...

did the animation and onion skin dockers...

did the timeline docker...

Animation and exporting has been done...

We need to add something about G'MIC filters too

Thank you very much for the patch! It looks perfect! And it compiles and runs perfect as well! Feel free to commit it to master :)

Last year we had a dedicated page (not a post) for this information. I started a list and added some bullet points with features that were added. There is a new page that I started on Krita.org that has this information.

Dropping

The problem that was solved by the patch is now fixed by KisNodeJuggler and already in master, so I guess we can drop this patch.

Thank you for the patch! :)

This has been ported to the wiki. Still needs someone to look over.

pass-through: 通過
http://www.s-arcana.co.jp/tech/2011/10/photoshop-1.html
http://www.clip-studio.com/clip_site/support/request/detail/svc/54/tid/34762
http://daredemopc.blog51.fc2.com/blog-entry-905.html
http://memob.tumblr.com/post/30780937006/photoshop%E8%AA%BF%E6%95%B4%E3%83%AC%E3%82%A4%E3%83%A4%E3%83%BC%E3%81%AE%E5%8A%B9%E6%9E%9C%E3%82%92%E3%83%95%E3%82%A9%E3%83%AB%E3%83%80%E5%86%85%E3%81%A0%E3%81%91%E3%81%AB%E3%81%99%E3%82%8B%E6%96%B9%E6%B3%95
http://psgips.blog24.fc2.com/blog-entry-253.html

I think I mentioned this a few times on IRC but forgot to write it down here: I am holding off on this until the Lazy Brush is finished, since the methods used in that tool will be very useful for implementing a new magnetic lasso.

the commitment in Wed Feb 3 02:38:31 2016 UTC, krita.po (Revision 1451901) by Tokiedian.
Revise translations.

the commitment in Wed Dec 16 13:26:51 2015 UTC, krita.po (Rev. 1447402) by tokiedian
Add translation in Animation and LoD. Revise many translations about Brush Editor and others.

Here we go, PSstyle shortcuts and input profile. I feel that ideally this would be the same file selected with the same dropdown, but maybe a bit fiddly to program?

@abrahams yes it would be good to have a P.S. scheme , I had made a list of features which are common in krita and Ps and their corresponding shortcuts
you can view the list here -> https://docs.google.com/spreadsheets/d/1RckfJgtTOOrdGARZOqGh2nTbSZnLNq_2y5G2GbMg8c0/edit?usp=sharing

Yes, raghukamath made a comparison list with ps, might be worth taking that and turning it into a proper sceme.

With schemes support, we can provide a "PS-style defaults" scheme to aid the transition.

The 'frameworks' branch? Is it used?

Perhaps will think about this more when we get to testing the frameworks branch regularly.

Maybe it would be handy to push this to master so it gets updated whenever something else needs updating?

Done in libs and krita.

Rebase against master

We have an KisOutlineGenerator class that performs all the outline generation for brushes and selections. You can see an example of usage in KisPixelSelection::outline().

Okay, and that idea won't work either because the contents of the layerbox are directly coupled to the model that reflects the layer order in the image. We really dropped the ball here, design-wise. It must be possible to rearrange the image while blocking the recalculation of the projection. All the other actions done to layer contents or whatever are irrelevant here. We must have a way to push all kinds of actions to the image without having to wait for the projection to be recalculated, just like we do on loading images. And there we use lock(), don't we?

In D263#4710, @rempt wrote:

It looks like it would be simpler to queue the layer movements and when none is forthcoming anymore, calculate the move, skipping all in-between moves...

It looks like it would be simpler to queue the layer movements and when none is forthcoming anymore, calculate the move, skipping all in-between moves...

In D263#4706, @rempt wrote:

Well, I suspected that. What it tells me is that our architecture/api is dangerous, because both your solutions are way too complicated for what should be a really simple thing, delaying the recomposition of the image until the user stops doing things in the ui.

Hm, looking through our KisUpdateSchedular api, shouldn't

Thanks for looking it over! I'll make the change. Do you think the alterations you linked to should be done in a script?

Well, I suspected that. What it tells me is that our architecture/api is dangerous, because both your solutions are way too complicated for what should be a really simple thing, delaying the recomposition of the image until the user stops doing things in the ui.