[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Patch: don't save tiles that are equal to the default tile
From:       Dmitry Kazakov <dimula73 () gmail ! com>
Date:       2010-03-16 17:28:34
Message-ID: ae32c1ef1003161028k1b2117dcw94b2d76e7f26d64a () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
> >
> > Why do you think data manager should know anything?
> I think you missed my point :)
>
> Lets say I open an image, I then select an area (non necessarily
> rectangular),
> then I go to the edit menu and choose cut or clear, it will replace my
> selection by transparent pixels in function of selectedness on my image.
> And
> neither KisDataManager::fill/KisDataManager::clear apply in this case,
> since
> they take a rectangle as argument.
>

Ok. Then we need this KisTileHashTable::purge() method. But i still don't
think we should do this during save. E.g. in my emacs workflow i save my
work every ~40sec. If i did the same with Krita, then this full scanning of
tiles would make some troubles.

Btw, AutoCAD has the purge() method too. It removes unused references and
blocks. And it is revealed to the user into File->Drawing
Utilities->Purge... Maybe it could work for Krita too...

Actually, we could do this on opening the image. It happens not so often and
do not disturb the user much. But it would mean that the image becomes
altered (internally) right after opening.


-- 
Dmitry Kazakov

[Attachment #5 (text/html)]

<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div \
class="im">&gt;<br> &gt; Why do you think data manager should know anything?<br>
</div>I think you missed my point :)<br>
<br>
Lets say I open an image, I then select an area (non necessarily rectangular),<br>
then I go to the edit menu and choose cut or clear, it will replace my<br>
selection by transparent pixels in function of selectedness on my image. And<br>
neither KisDataManager::fill/KisDataManager::clear apply in this case, since<br>
they take a rectangle as argument.<br></blockquote></div><br>Ok. Then we need this \
KisTileHashTable::purge() method. But i still don&#39;t think we should do this \
during save. E.g. in my emacs workflow i save my work every ~40sec. If i did the same \
with Krita, then this full scanning of tiles would make some troubles.<br> <br>Btw, \
AutoCAD has the purge() method too. It removes unused references and blocks. And it \
is revealed to the user into File-&gt;Drawing Utilities-&gt;Purge... Maybe it could \
work for Krita too...<br><br>Actually, we could do this on opening the image. It \
happens not so often and do not disturb the user much. But it would mean that the \
image becomes altered (internally) right after opening.<br> <br clear="all"><br>-- \
<br>Dmitry Kazakov<br>



_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop


[prev in list] [next in list] [prev in thread] [next in thread]