'Re: The resource bundle and resource md5 sums.'

[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:       <animtim () gmail ! com>
Date:       2015-01-23 13:11:45
Message-ID: 54C24891.1090004 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Le 23/01/2015 12:56, Stefano Bonicatti a écrit :
> 2015-01-23 12:44 GMT+01:00 Timothée Giet <animtim@gmail.com 
> <mailto: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.
>
>
Ok, I was talking only from the usability point of view, the deep 
technical implementation details are quite further my coding knowledge.

For gradient, why can't we just always copy the files from the 
/gradients folders in the bundles? I mean there is no dirty-preset 
option for gradient, so (except for the two generate gradients) a 
gradient in the list is always loaded from what's in the gradient file.

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Le 23/01/2015 12:56, Stefano Bonicatti
      a écrit :<br>
    </div>
    <blockquote
cite="mid:CAGMAV48QaMQRcPxP77L5VZA2d3CuHjQVzw53=UDxk+uYqK=r8Q@mail.gmail.com"
      type="cite">
      <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 moz-do-not-send="true"
                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'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>
      <br>
    </blockquote>
    Ok, I was talking only from the usability point of view, the deep
    technical implementation details are quite further my coding
    knowledge.<br>
    <br>
    For gradient, why can't we just always copy the files from the
    /gradients folders in the bundles? I mean there is no dirty-preset
    option for gradient, so (except for the two generate gradients) a
    gradient in the list is always loaded from what's in the gradient
    file.<br>
    <br>
  </body>
</html>

_______________________________________________
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] 