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

List:       kde-kimageshop
Subject:    Re: The resource bundle and resource md5 sums.
From:       Stefano Bonicatti <smjert () gmail ! com>
Date:       2015-01-23 11:56:20
Message-ID: CAGMAV48QaMQRcPxP77L5VZA2d3CuHjQVzw53=UDxk+uYqK=r8Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2015-01-23 12:44 GMT+01:00 Timoth=C3=A9e Giet <animtim@gmail.com>:

>  In this case, saving new presets first and bundling them afterward makes
> more sense.
> Without manually saving the preset, what name and thumbnail should the
> preset use? the same as the original one? So you end up having two preset
> with same name and thumbnail? sounds bad...
>

Got you and i somewhat agree with you.
Current problem though is that some resources changes from their original
even if they are not actually changed.
To solve this, for instance for gradient, you would have to keep the non
interpreted data in memory, until the resource is actually changed, so that
if it's saved again and not modified it would output the same file as the
original one or, as i was saying, implement a dirty bit so that you know if
you have to copy the original file, because the resource is not changed, or
save it, because the resource did change.

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2015-01-23 12:44 \
GMT+01:00 Timothée Giet <span dir="ltr">&lt;<a href="mailto:animtim@gmail.com" \
target="_blank">animtim@gmail.com</a>&gt;</span>:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>In this case, saving new presets first and bundling them afterward
    makes more sense.<br></div>
    Without manually saving the preset, what name and thumbnail should
    the preset use? the same as the original one? So you end up having
    two preset with same name and thumbnail? sounds \
bad...</div></blockquote><div><br></div><div>Got you and i somewhat agree with \
you.</div><div>Current problem though is that some resources changes from their \
original even if they are not actually changed.</div><div>To solve this, for instance \
for gradient, you would have to keep the non interpreted data in memory, until the \
resource is actually changed, so that if it&#39;s saved again and not modified it \
would output the same file as the original one or, as i was saying, implement a dirty \
bit so that you know if you have to copy the original file, because the resource is \
not changed, or save it, because the resource did change.</div></div><br></div></div>



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


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