headers
Bryce Harrington | 6 Nov 2006 21:27

ANN: Crucible 1.7 release

Hi all,

This is an announcement of a new Crucible 1.7 release.  Much has changed
in this release, most notably including a new, easy to use installation
system.

We have been using the crucible installation at OSDL for running Cairo
and GEGL testing, and also use it for kernel testing with NFSv4, CPU
hotplug, and more.  We'd love to see it used for more widespread
testing, and are providing the code for anyone that would like to set up
their own environment:

    http://prdownloads.sourceforge.net/crucible/crucible-1.7.tar.gz

Crucible provides a powerful, flexible backend for building automated
testing systems. It allows for conducting tests on multiple machines
(via NFS), including patching, rebuilding, and booting new kernels,
libraries, and services. Configuration and customization can be done
through simple config files and bash scripts. It is suitable for
performing tests of GUI applications, services, libraries, and kernel
patches.

Changes:  A new installation system is in place, which should make it
straightforward to getting a basic crucible install up and running
quickly.  Lots of documentation has been added.  There is a new
post-installation test 'make installcheck'.  Directory locations have
been abstracted.  Internals have been abstracted and generalized, giving
more flexibility for customization/extension.  Several new subcommands
added to 'sut' script for managing system images, adding new machines,
etc.  A new queue_plan script is added for doing easier one-off
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Nordholts | 18 Nov 2006 18:46
Picon
Gravatar

A GEGL Tile Interface

Hello!

I've been thinking about how an Undo/Redo implementation in an image 
manipulating program that uses GEGL would look. From what I can tell, 
most IMPs uses tiles for Undo/Redo implementations; after an operation, 
they store the changed tiles. On an undo, the changed tiles are reverted 
back.

However, the current gegl.h seems to offer no interface for tile access. 
Has there been any discussion about this, i.e. is a tile interface 
supposed to be available in GEGL?

Sincerely,
Martin
Permalink | Reply | 1 comment |
headers
howard chen | 19 Nov 2006 12:29
Picon

CLAMP marco is defined in which file?

Can anyone tell me where can I find the CLAMP marco?

Thanks.
Permalink | Reply | 3 comments |
headers
Michael Natterer | 19 Nov 2006 12:46
Picon

Re: CLAMP marco is defined in which file?

On Sun, 2006-11-19 at 19:29 +0800, howard chen wrote:
> Can anyone tell me where can I find the CLAMP marco?

It's in GLib.

ciao,
--mitch
Permalink | Reply | 0 comments |
headers
Sven Neumann | 19 Nov 2006 14:53
Picon

Re: CLAMP marco is defined in which file?

Hi,

On Sun, 2006-11-19 at 19:29 +0800, howard chen wrote:
> Can anyone tell me where can I find the CLAMP marco?

Perhaps it would be a good idea to install devhelp and the GLib API
reference manual (and probably other manuals as well). That way you
could look up such things easily. A lot of editors like even nicely
integrate the developer documentation. In emacs, for example, you would
press F7 while the cursor is on CLAMP and it would do the lookup for
you.

Sven
Permalink | Reply | 1 comment |
headers
howard chen | 19 Nov 2006 18:54
Picon

Re: CLAMP marco is defined in which file?

On 11/19/06, Sven Neumann <sven@...> wrote:
> Hi,
>
> On Sun, 2006-11-19 at 19:29 +0800, howard chen wrote:
> > Can anyone tell me where can I find the CLAMP marco?
>
> Perhaps it would be a good idea to install devhelp and the GLib API
> reference manual (and probably other manuals as well). That way you
> could look up such things easily. A lot of editors like even nicely
> integrate the developer documentation. In emacs, for example, you would
> press F7 while the cursor is on CLAMP and it would do the lookup for
> you.
>
>
> Sven
>
>
>

Thanks ALL!

I have another question:

Can I compile the GIMP without GTK? Or does it exist a command line
version of GIMP that is independent of GTK?

I know I can run GIMP using command, I just want to know if it is
possible to compile it without GTK...

Thanks.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Øyvind Kolås | 21 Nov 2006 02:28
Picon

Re: A GEGL Tile Interface

On 11/18/06, Martin Nordholts <enselic@...> wrote:
> I've been thinking about how an Undo/Redo implementation in an image
> manipulating program that uses GEGL would look. From what I can tell,
> most IMPs uses tiles for Undo/Redo implementations; after an operation,
> they store the changed tiles. On an undo, the changed tiles are reverted
> back.

If such an interface were to be provided it would be internal to the
GeglBuffer implementation. And it is indeed possible to implement such
a state information on a per GeglBuffer level. For many applications
it will probably be more beneficial to store the history of actions as
a sequence of operations, and rely on efficient caching to avoid re
computation of the entire stroke/filter history.

> However, the current gegl.h seems to offer no interface for tile access.
> Has there been any discussion about this, i.e. is a tile interface
> supposed to be available in GEGL?

A tile interface will most probably not be provided, as even the fact
that sparse buffers are implemented by the means of tiles is an
implementation detail of the current GeglBuffer implementation that
should not be exposed to users of the interface.

/Øyvind K.

--

-- 
«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/
(Continue reading)

Permalink | Reply | 0 comments |
headers
howard chen | 28 Nov 2006 19:04
Picon

Question abt compling GIMP

I just want to modify a plugin file (*c) in the common folder,
currently, when I modified the file, I use `make && make install` to
compile, link and install the GIMP.

But this take some times to test the feature, are there any better method?

Thanks.
Howard
Permalink | Reply | 4 comments |
headers
Øyvind Kolås | 1 Dec 2006 16:54
Picon

Review of public GEGL API

The host facing GEGL API is getting closer to a stage where it should
be scrutinized before an initial tarball release. The API that is
getting stable is the host facing API, which is the portions of the
GEGL library exposed in gegl.h[1]. Usage of this API is illustrated in
the hello world example[2] in the documentation.

1: http://cvs.gnome.org/viewcvs/gegl/gegl/gegl.h?view=markup
2: http://cvs.gnome.org/viewcvs/gegl/docs/hello-world.c?view=markup

Comments and requests for renaming/clarification of this API would be
most welcome, the API to write plug-ins as well as the XML
serialization format are still not ready to be stabilized. But the
public API should be possible to keep largely unchanged whilst adding
optimizations internally in the GEGL engine.

Right now I think there is two issues that needs resolving, the most
important one is probably exposing introspection of meta
data/properties for operations. The
current function GSList * gegl_operation_list_operations (void); which
returns a static list of operation names is not good enough. To
discover the parameters a temporary GeglNode needs to be instantiated
and it's list of properties must be examined. I want to avoid exposing
the GObject internals of GEGL in the public API.

The other issue is hit detection, this is a more minor issue, and I
think introducing API to do this can be postponed until later, but
most probably adding a function similar to the following would work:

GeglNode *gegl_node_hit_test (GeglNode *node, gint x, gint y, gdouble
alpha_threshold);
(Continue reading)

Permalink | Reply | 0 comments |

Gmane