[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: [CREATE] [Gimp-developer] Brushpack file format
From: Dave Crossland <dave () lab6 ! com>
Date: 2013-04-16 20:58:50
Message-ID: CAEozd0ymm5wvVwFdpSvBhVS6A-rCfFXLbM7MoP4+xQ3Jj4uG5Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Cc zero not pd please :-)
On Apr 16, 2013 12:49 PM, "Boudewijn Rempt" <boud@valdyas.org> wrote:
>
> On Tue, 16 Apr 2013, Alexia Death wrote:
>
> Hi,
>>
>> Brushpacks should not be mixed: so no mypaint brushes and gimp
>> brushes in one brushpack.
>>
>>
>> Why this restriction
>>
>
> To make life easier for users. We discussed this a lot, but creating a
> brush pack that contains, for instance, both Krita and MyPaint brushes
> wasn't seen as desirable.
>
> and why different internal formats
>>
>
> I'm not getting this question -- the formats are there because that's how
> applications define their brushes. Mypaint's .myb format is different from
> Krita's .kpp and Gimp's .gdyn.
>
> and why such a complicated create folder format?
>>
>
> Hm... What do you consider the complications? Basically, it's just the
> equivalent of the way the create spec stores patterns, brushes, gradients
> etc. in separate directories, extended to allow new brush types that are
> not in create, like kpp, myb etc.
>
> It would
>> be very simple to have a pack& create forder structure that allows for
>> both mixed packets and for each app only
>> handle what it can/need...
>>
>> something along the lines of:
>> /manifest.xml
>> /coolpack-cutes/tags.xml
>> /coolpack-cutes/shared/* - resources in common formats - svg, png, gif,
>> whatever, as long as the format isnt app
>> specific, pehaps subfoolders by resource intended use...
>>
>
> I'm not really seeing right away the improvement that adding a "shared"
> directory level gives above having the common resources in their already
> defined create directory names.
>
> /coolpack-cutes/mypaint/* -stuff in mypaint format, acceptable to mypaint
>> and dictated by mypaint
>> /coolpack-cutes/gimp/* - stuff in gimp format, following gimp resource
>> structure, subfolders for brushes,
>> dynamics, etc
>> /coolpack-cutes/krita/*- stuff in krita format that only krita can
>> understand
>>
>> and same structure in create/ resource folder.
>>
>> So, if gimp starts supporting mypaint, all it needs to do, is dig into
>> shared mypaint resources in create. Same
>> goes for krita and for say mypaint getting a brush engine that lets it
>> read gimp resources...
>>
>
>
> If I get you correctly, you'd prefer to copy a gradient or pattern that is
> used by a brush into the create-defined location for gradients or patterns?
> We decided against that because those gradients or patterns (or even the
> brush tips themselves) are only packaged because they belong to a
> particular brush and shouldn't be automatically made available as a shared
> gradient or pattern.
>
> Boudewijn
> _______________________________________________
> CREATE mailing list
> CREATE@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/create
>
>
[Attachment #5 (text/html)]
<p>Cc zero not pd please :-) </p>
<div class="gmail_quote">On Apr 16, 2013 12:49 PM, "Boudewijn Rempt" <<a \
href="mailto:boud@valdyas.org">boud@valdyas.org</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
On Tue, 16 Apr 2013, Alexia Death wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Hi,<br>
<br>
Brushpacks should not be mixed: so no mypaint brushes and gimp brushes in \
one brushpack.<br> <br>
<br>
Why this restriction<br>
</blockquote>
<br>
To make life easier for users. We discussed this a lot, but creating a brush pack \
that contains, for instance, both Krita and MyPaint brushes wasn't seen as \
desirable.<br> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> and why different internal formats<br>
</blockquote>
<br>
I'm not getting this question -- the formats are there because that's how \
applications define their brushes. Mypaint's .myb format is different from \
Krita's .kpp and Gimp's .gdyn.<br> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> and why such a complicated create folder format?<br>
</blockquote>
<br>
Hm... What do you consider the complications? Basically, it's just the equivalent \
of the way the create spec stores patterns, brushes, gradients etc. in separate \
directories, extended to allow new brush types that are not in create, like kpp, myb \
etc.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> It would<br>
be very simple to have a pack& create forder structure that allows for both mixed \
packets and for each app only<br> handle what it can/need...<br>
<br>
something along the lines of:<br>
/manifest.xml<br>
/coolpack-cutes/tags.xml<br>
/coolpack-cutes/shared/* - resources in common formats - svg, png, gif, whatever, as \
long as the format isnt app<br> specific, pehaps subfoolders by resource intended \
use...<br> </blockquote>
<br>
I'm not really seeing right away the improvement that adding a "shared" \
directory level gives above having the common resources in their already defined \
create directory names.<br> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> /coolpack-cutes/mypaint/* -stuff in mypaint format, \
acceptable to mypaint and dictated by mypaint<br> /coolpack-cutes/gimp/* - stuff in \
gimp format, following gimp resource structure, subfolders for brushes,<br> dynamics, \
etc<br> /coolpack-cutes/krita/*- stuff in krita format that only krita can \
understand<br> <br>
and same structure in create/ resource folder.<br>
<br>
So, if gimp starts supporting mypaint, all it needs to do, is dig into shared \
mypaint resources in create. Same<br> goes for krita and for say mypaint getting a \
brush engine that lets it read gimp resources...<br> </blockquote>
<br>
<br>
If I get you correctly, you'd prefer to copy a gradient or pattern that is used \
by a brush into the create-defined location for gradients or patterns? We decided \
against that because those gradients or patterns (or even the brush tips themselves) \
are only packaged because they belong to a particular brush and shouldn't be \
automatically made available as a shared gradient or pattern.<br>
<br>
Boudewijn<br>_______________________________________________<br>
CREATE mailing list<br>
<a href="mailto:CREATE@lists.freedesktop.org">CREATE@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/create" \
target="_blank">http://lists.freedesktop.org/mailman/listinfo/create</a><br> \
<br></blockquote></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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic