[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: RE: About Master Brush
From: Bol Bib <bollebib () hotmail ! com>
Date: 2014-07-11 15:51:07
Message-ID: DUB124-W4468946B1E3FE21C7986DFCE090 () phx ! gbl
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
yes ,I think that how boud explains it would work fine.
> From: boud@valdyas.org
> To: mohit.bits2011@gmail.com
> Subject: Re: About Master Brush
> Date: Fri, 11 Jul 2014 11:00:09 +0200
> CC: kimageshop@kde.org
>
> Hi Mohit,
>
> Sorry for not having seen your mail earlier -- the kickstarter made life rather \
> busy.
> It would be good to canvas the opinion of artists, but here are my thoughts:
>
> * the main thing that makes a brush engine unique is the actual brush painting code \
> -- whether it's a stamp like the pixel brush, brush hairs or \
> shapes.
> * all the other things are options -- some brushes already have all the options, \
> others only a subset.
> It's not going to work to have all the various painting algorithms in one brush \
> engine. The thing to do is, I think, first create the template mechanism: save the \
> brush options and load them into another brush, that can then re-use the options it \
> recognizes, and discard the ones it doesn't have.
> The next step would be to think which options are missing in which engines and \
> whether they make sense there.
> Then, instead of creating a new brush engine, I'd start implementing a smudge \
> option that would work with the existing brush engines, instead of being a separate \
> brush engine. It would be pretty cool to be able to smudge with the experiment or \
> grid brush...
> Together, I think this would implement what bollebib asked for.
>
> I've cc'ed the mailing list, since others might have more input.
>
> On Wednesday 09 July 2014 Jul 13:36:21 you wrote:
> > Hello,
> >
> > I wanted to ask about the requirements for Master Brush and how we intend
> > to go about it.
> > Since it is a relatively bigger feature, I just wanted to get a feel of
> > what can be done.
> > Here is my understanding till now.
> > So overall Master Brush is supposed to be anew brush engine that contains
> > various features(KisPaintOpOption) from other brushes. Smudge if possible
> > can be used with particle features and so on. However, to decide the
> > compatible feature -- we will have to find out a way. Maybe some can be
> > predecided -- but as new brushes come along -- I guess we will have to
> > automate that process.
> > I thought of a very naive approach that whether we can simply just add
> > KisPaintOpOptions to the Master Brush PaintOp. For example -- upon right
> > click on any of the options -- if somebody selects "Add to MasterBrush",
> > the option will be added to it.Then it is upto the option whether it is
> > supposed to work or not with the other options.For example -- I guess a
> > chalk brush option can work well with Smudge -- but not with a particle
> > brush. So that will be up to the user. But I am sure this will have more to
> > it.
> >
> > So basically, what else can we do in Master Brush? I just wanted to know
> > the requirements so that by the time Cumulative Undo/Redo is over --we can
> > get straight into this :)
> >
> >
> > Warm Regards,
> > Mohit Goyal | +918600046760
> > BITS-Pilani Goa Campus
> y
> --
> Boudewijn Rempt
> http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
>
> _______________________________________________
> Krita mailing list
> kimageshop@kde.org
> https://mail.kde.org/mailman/listinfo/kimageshop
[Attachment #5 (text/html)]
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>yes ,I think that how boud explains it would \
work fine. <br><br><div>> From: boud@valdyas.org<br>> To: \
mohit.bits2011@gmail.com<br>> Subject: Re: About Master Brush<br>> Date: Fri, \
11 Jul 2014 11:00:09 +0200<br>> CC: kimageshop@kde.org<br>> <br>> Hi \
Mohit,<br>> <br>> Sorry for not having seen your mail earlier -- the \
kickstarter made life rather busy.<br>> <br>> It would be good to canvas the \
opinion of artists, but here are my thoughts:<br>> <br>> * the main thing that \
makes a brush engine unique is the actual brush painting code -- whether it's a stamp \
like the pixel brush, brush hairs or shapes.<br>> * all the other things are \
options -- some brushes already have all the options, others only a subset.<br>> \
<br>> It's not going to work to have all the various painting algorithms in one \
brush engine. The thing to do is, I think, first create the template mechanism: save \
the brush options and load them into another brush, that can then re-use the options \
it recognizes, and discard the ones it doesn't have.<br>> <br>> The next step \
would be to think which options are missing in which engines and whether they make \
sense there.<br>> <br>> Then, instead of creating a new brush engine, I'd start \
implementing a smudge option that would work with the existing brush engines, instead \
of being a separate brush engine. It would be pretty cool to be able to smudge with \
the experiment or grid brush...<br>> <br>> Together, I think this would \
implement what bollebib asked for.<br>> <br>> I've cc'ed the mailing list, \
since others might have more input.<br>> <br>> On Wednesday 09 July 2014 Jul \
13:36:21 you wrote:<br>> > Hello,<br>> > <br>> > I wanted to ask \
about the requirements for Master Brush and how we intend<br>> > to go about \
it.<br>> > Since it is a relatively bigger feature, I just wanted to get a feel \
of<br>> > what can be done.<br>> > Here is my understanding till \
now.<br>> > So overall Master Brush is supposed to be anew brush engine that \
contains<br>> > various features(KisPaintOpOption) from other brushes. Smudge \
if possible<br>> > can be used with particle features and so on. However, to \
decide the<br>> > compatible feature -- we will have to find out a way. Maybe \
some can be<br>> > predecided -- but as new brushes come along -- I guess we \
will have to<br>> > automate that process.<br>> > I thought of a very \
naive approach that whether we can simply just add<br>> > KisPaintOpOptions to \
the Master Brush PaintOp. For example -- upon right<br>> > click on any of the \
options -- if somebody selects "Add to MasterBrush",<br>> > the option will be \
added to it.Then it is upto the option whether it is<br>> > supposed to work or \
not with the other options.For example -- I guess a<br>> > chalk brush option \
can work well with Smudge -- but not with a particle<br>> > brush. So that will \
be up to the user. But I am sure this will have more to<br>> > it.<br>> > \
<br>> > So basically, what else can we do in Master Brush? I just wanted to \
know<br>> > the requirements so that by the time Cumulative Undo/Redo is over \
--we can<br>> > get straight into this :)<br>> > <br>> > <br>> \
> Warm Regards,<br>> > Mohit Goyal | +918600046760<br>> > BITS-Pilani \
Goa Campus<br>> y<br>> -- <br>> Boudewijn Rempt<br>> \
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl<br>> \
<br>> _______________________________________________<br>> Krita mailing \
list<br>> kimageshop@kde.org<br>> \
https://mail.kde.org/mailman/listinfo/kimageshop<br></div> </div></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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic