-destructive.
(C) do brush operation, destructive.
(D) do another brush operation, destructive.
(E) do filter operation, non-destructive.
If my assumption is wrong, please let me know.
--
Souichi TAKASHIGE
___
Gimp-developer mailing list
Gimp-developer
it's better to separate destructive layers from other non-destructive
operations. Painters may use destructive layer to avoid the risk to be
slow, and others may use non-destructive one.
I think it is a GIMP's design matter rather than the implementation
problem of the GEGL.
--
Souichi TAKASHIGE
both
for speed and memory usage.
I'm anxious about the performance a little yet, but I hope GEGL to
have enough performance in the future.
--
Souichi TAKASHIGE
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https
composite. At GUADEC this year I showed a mini painting app
embedded in a presentation tool where I could freely rotate the GEGL
paint demo and paint at it at any angle.
Great! I'm looking forward to see these nice features on the GIMP.
--
Souichi TAKASHIGE
2008/7/28 Liam R E Quin [EMAIL PROTECTED]:
On Mon, 2008-07-28 at 01:19 +0900, Souichi TAKASHIGE wrote:
[...]
But it costs too much memory when we
make a lot of strokes -- and we *DO* make thousand of strokes when we
draw an image -- compared to the current implementation which has a
buffer
we
manage the undo cache. So it can't be non-destructive unless we save
that cache forever.
But maybe it's better to check the source code of gegl-paint first.
--
Souichi TAKASHIGE
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https
Hi,
1.is this going to be avaiable in some of the 2.5 releases, because if
it is,i'm gonna bug tests it
No, it is not going to be available in 2.5, unless you fix the patch
or persuade Souichi Takashige to do so.
Sorry, I'm currently working on another program, so I have not
maintained
ways.
Or we should allow users to blit a part of the nodes into newly
created image to save
memory space by discarding some of the operation history.
Please let me know the treatment of the destructive editing operations
in future gimp.
--
Souichi TAKASHIGE
In this model, modifiers can access share context and read only
operation of GIMP core
objects.
To implement the brush modifier framework, I want to allow some
privileged modules to
access internals of Gimp core objects (those are passed as the
arguments of the callback
functions.)
--
Souichi TAKASHIGE
.
If the compatibility matters much, we can introduce some version number
validation protocol to check the incompatibility easily.
But anyway, I will try to list the API which may be accessed from
privileged modules.
--
Souichi TAKASHIGE
___
Gimp-developer mailing list
parameters to
change the brush behavior.
--
Souichi TAKASHIGE
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Thank you for your advice.
2008/3/13, Martin Nordholts [EMAIL PROTECTED]:
In order to make it easier to track changes to the patch, could you
please create an enhancement request about this in Bugzilla?
(bugs.gimp.org) We can still continue discussion on the list but the
patch will be
this
framework in the
future.
If you have any comments about this framework or similar ideas, please
let me know.
Regards.
--
Souichi TAKASHIGE
[EMAIL PROTECTED]
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https
this
framework in the
future.
If you have any comments about this framework or similar ideas, please
let me know.
Regards.
Souichi TAKASHIGE
[EMAIL PROTECTED]
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU
Sorry, I sent same mail for three times.
Souichi TAKASHIGE
[EMAIL PROTECTED]
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
://www.youtube.com/watch?v=SIg8Omew9Ps
I'm keeping development of this framework and want to commit this framework
in the
future.
If you have any comments about this framework or similar ideas, please let
me know.
Regards.
--
Souichi TAKASHIGE
[EMAIL PROTECTED
16 matches
Mail list logo
