<?xml version="1.0" ?>

<kc>
<title>Gimp Traffic</title>
<author contact="mailto:cflagg@kdigital.com">Cris Flagg</author>
<issue num="41" date="07 May 2001 00:00:00 -0800" />

<headquote>
<a href="http://www.gimp.org">The GIMP Homepage</a> | 
<a href="http://www.xach.com/gimp/news/index.html">The GIMP News Archive</a> | 
<a href="http://www.gimp.org/mailing_list.html">The GIMP Mailing Lists</a> | 
<a href="http://www.rru.com/~meo/gimp/">The GIMP FAQ</a>
</headquote>


<stats posts="9" size="25" contrib="6" multiples="2" lastweek="1">

<person posts="3" size="9" who="Sven Neumann &lt;sven@gimp.org&gt;" />
<person posts="2" size="7" who="Philip Van Hoof &lt;freax@pandora.be&gt;" />
<person posts="1" size="3" who="Hans Breuer &lt;hans@breuer.org&gt;" />
<person posts="1" size="3" who="Ken Ames &lt;kenames@pacbell.net&gt;" />
<person posts="1" size="2" who="Fabian =?ISO-8859-1?Q?Fr=E9d=E9rick?= &lt;fabian.frederick@gmx.fr&gt;" />

</stats>


<section
  title="The GIMP on Multi-User Systems"
  author="Cris Flagg"
  contact="mailto:cflagg@kdigital.com"
  subject="GIMP on multi-user systems"
  archive="http://www.mail-archive.com/gimp-developer%40lists.xcf.berkeley.edu/"
  posts="3"
  startdate="30 Apr 2001 08:39:03 -0800"
  enddate="30 Apr 2001 23:22:36 -0800"
>

<mention></mention>
<mention>Blue Lang</mention>
<mention>Daniel Egger</mention>

<p>Allan West posted about a departmental upgrade:
<quote who="Allan West">
My department is going to be putting GIMP out for general use on Sun E-220R's 
and Ultra-10's. The Ultra-10's will be one person per console, but the 
E-220R's will have SunRays attached, so we'll have a many as 31 users trying 
to run the software concurrently.</quote>  Allan wanted to know what the
proper settings for the "Tile Cache" were, since 1/2 physical ram and/or
all available ram were not appropriate answers.  His thoughts were 2-4MB
per user, or 32MB and let Solaris virtual memory handle the swapping.
Blue Lang pointed out that network latency was going to kill any RAM
cache benefit.  Daniel Egger thought the machine should have fast
enough disk IOs to handle the load, but added that having a complete
picture in RAM is never a bad idea.
</p>

</section>



<section
  title="Clipboard Selection in the Gimp"
  author="Cris Flagg"
  contact="mailto:cflagg@kdigital.com"
  subject="The clipboard selection in thegimp"
  archive="http://www.mail-archive.com/gimp-developer%40lists.xcf.berkeley.edu/msg00336.html"
  posts="5"
  startdate="02 May 2001 03:09:34 -0800"
  enddate="02 May 2001 13:18:09 -0800"
>

<mention>Hans Breuer</mention>
<mention></mention>
<mention>Sven Neumann</mention>

<p>Philip Van Hoof was wondering how to copy an
image from Gimp to the clipboard to be available
in other GKT+ applications.  Sven Neumann replied that
Gimp does not use XClipboard, and since GTK+ clipboard is
used, it can only be used for text images.  Sven also 
suggested using temporary files instead.
Philip wondered if writing a Gimp plugin might
solve the problem.  He also wondered if this was more
trouble than it was worth.  Sven thought it was possible
to write such a plugin, since gimp-edit-copy and 
gimp-edit-paste were available through the PDB
Hans Breuer pointed to a win32 version of such a plugin that
had no Linux match.  Hans thought that it would be rather
straight forward to develop a clipboard plugin if one had
developed in C before and understood the X Clipboard API.
</p>

</section>



<section
  title="The GIMP on OS/2"
  author="Cris Flagg"
  contact="mailto:cflagg@kdigital.com"
  subject="(no subject)"
  archive=""
  posts="3"
  startdate="02 May 2001 15:52:07 -0800"
  enddate="02 May 2001 21:55:14 -0800"
>

<mention>Sven Neumann </mention>
<mention></mention>

<p>Ken Ames was trying to build Gimp on OS/2 but the auto tools
kept raising errors like <quote who="Ken Ames">
aclocal: configure.in: 293: macro `AM_PATH_GLIB_' not found in 
library</quote>  Sven Neumann replied <quote who="Sven Neumann">
standard aclocal problem: aclocal only searchs in /usr/share/aclocal
while glib installs its aclocal macros into the specified prefix
(often /usr/local/share/aclocal). One solution is to copy all m4 files
from /usr/share/aclocal into $prefix/share/aclocal and replace 
/usr/share/aclocal with a link to $prefix/share/aclocal.
Please note that you should not need to use the auto tools if you
compile from a gimp tarball. The problem you describe only arises 
when you compile from CVS and need to rebuild the configure script.
</quote>
</p>

</section>



</kc>

