[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: recording
From: Dmitry Kazakov <dimula73 () gmail ! com>
Date: 2012-05-24 18:20:55
Message-ID: CAEkBSfXeVPYrBktn=waQJ983Sw0BPXYDSPxTJ0u=t7zGeiU5Yg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi!
Sorry, for a long answer. Just a couple of notes.
On Tue, May 15, 2012 at 10:11 PM, Sven Langkamp <sven.langkamp@gmail.com>wrote:
> It will demand at least two classes for a single action, won't it?
>>
>> Or you suggest the generation of the dialog purely on the basis of
>> properties data? If so, how are you going to create and use customized
>> widgets like the one in Resize Canvas and in Filters dialog?
>>
>
> No, it's like we do with filters currently. There we also dialog that
> writes into a properties configuration. We already have the dialogs, they
> would just need some tweaking so they could also be used in the macro
> editor.
>
Well, yes, Cyrille told a good idea that the split of the UI and actions
might make a good job given that we plan to use different GUI frameworks.
Anyway, we need to define some kind on interface for such UI's. It can be
either a function or even a class. I agree for any. What, I think, is
really important is that the place where the UI is created should be a
factory class, not the caller's code.
> Should be easy to do. I wonder where we use arrays in the UI (appart from
> curves),
>
A stroke of a Pixel Brush is action as well and it contains an array of
KisPaintInformation objects.
--
Dmitry Kazakov
[Attachment #5 (text/html)]
Hi!<br><br>Sorry, for a long answer. Just a couple of notes.<br><br><div \
class="gmail_quote">On Tue, May 15, 2012 at 10:11 PM, Sven Langkamp <span \
dir="ltr"><<a href="mailto:sven.langkamp@gmail.com" \
target="_blank">sven.langkamp@gmail.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="gmail_quote"><div class="im"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="gmail_quote"><div>It will demand at least two \
classes for a single action, won't it?<br><br>Or you suggest the generation of \
the dialog purely on the basis of properties data? If so, how are you going to create \
and use customized widgets like the one in Resize Canvas and in Filters dialog?<br>
</div></div></blockquote><br></div><div>No, it's like we do with filters \
currently. There we also dialog that writes into a properties configuration. We \
already have the dialogs, they would just need some tweaking so they could also be \
used in the macro editor.<br> </div></div></blockquote><div><br>Well, yes, Cyrille \
told a good idea that the split of the UI and actions might make a good job given \
that we plan to use different GUI frameworks. Anyway, we need to define some kind on \
interface for such UI's. It can be either a function or even a class. I agree for \
any. What, I think, is really important is that the place where the UI is created \
should be a factory class, not the caller's code.<br> </div><blockquote \
class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div> Should be easy to \
do. I wonder where we use arrays in the UI (appart from \
curves),<br></div></div></blockquote><div><br>A stroke of a Pixel Brush is action as \
well and it contains an array of KisPaintInformation objects.<br> <br \
clear="all"></div></div>-- <br>Dmitry Kazakov<br>
_______________________________________________
kimageshop 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