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

List:       kde-kimageshop
Subject:    Re: [Gimp-developer] Brushpack file format
From:       Alexia Death <alexiadeath () gmail ! com>
Date:       2013-04-16 11:33:02
Message-ID: CA+Q=wrnva1zwidxZVHiZzFQggi-qnrUZMVyFD6siQHPz6Sd3+A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi,

Brushpacks should not be mixed: so no mypaint brushes and gimp brushes in
> one brushpack.
>

Why this restriction and why different internal formats and why such a
complcated create folder format? 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...
/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...

Best,
Alexia

-- 
--Alexia

[Attachment #5 (text/html)]

<div dir="ltr"><div>Hi,<br><br></div><div class="gmail_extra"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Brushpacks should not be mixed: so \
no mypaint brushes and gimp brushes in one \
brushpack.<br></blockquote><div><br></div><div>Why this restriction and why different \
internal formats and why such a complcated create folder format? It would be very \
simple to have a pack&amp; create forder structure that allows for both mixed packets \
and for each app only handle what it can/need...<br> <br></div><div>something along \
the lines of:<br></div><div>/manifest.xml<br></div><div>/coolpack-cutes/tags.xml<br></div><div>/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...<br> \
</div><div>/coolpack-cutes/mypaint/* -stuff in mypaint format, acceptable to mypaint \
and dictated by mypaint<br></div><div>/coolpack-cutes/gimp/* - stuff in gimp format, \
following gimp resource structure, subfolders for brushes, dynamics, etc<br> \
</div><div>/coolpack-cutes/krita/*- stuff in krita format that only krita can \
understand<br><br></div><div>and same structure in create/ resource \
folder.<br></div><div><br></div><div>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...<br> \
<br></div><div>Best,<br></div><div>Alexia<br clear="all"></div></div><br>-- \
<br>--Alexia </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]