At 20:27 25.05.01 +0200, Guillermo S. Romero / Familia Romero wrote:
[EMAIL PROTECTED] (2001-05-25 at 2113.57 +0300):
[...]
Maybe there should be a separate gimp site for the windows users. The
windows users are so different than the linux users. They don't mind
They are? The gimp is just
At 10:24 06.06.01 +0200, David Monniaux wrote:
On 5 Jun 2001, Sven Neumann wrote:
He's speaking of the Win32 version here which of course looks and feels
different than the usual win32 application. This feeling will change as
Let's add that the UI in the Win32 version is *BUGGY* (my mom
At 23:08 05.06.01 +0200, Sven Neumann wrote:
Chris Brown [EMAIL PROTECTED] writes:
[..., removed becuase I totally agree to the points Sven made]
My second suggestion is more technical, finding a way (and forgive me if
there already is) to allow Gimp to have skins or something like that so
At 14:11 17.12.01 -0700, Nathan C Summers wrote:
On 17 Dec 2001, Sven Neumann wrote:
Hi,
Nathan C Summers [EMAIL PROTECTED] writes:
Some horrible kludge could also be dreamed up involving GTKPlugs. That
would move the windowing system dependance down to the GDK level, but
would
At 21:37 05.06.02 +0100, Adam D. Moss wrote:
I already tried. I was very disappointed to see that you guys seem to be
following in GNOME's footsteps, and suddenly requiring 3 times the
amount of
library dependancies.
I feel your pain.
This is as good a point to ask as any; in following the
At 02:37 27.05.03 +, Tor Lillqvist wrote:
Hans Breuer writes:
BTW: just tried to compile fontconfig with msvc. It does _not_
build out of the box.
Did anybody claim it would?
Not that I know of.
Builds fine with gcc (mingw), but it has
more POSIX emulation stuff bundled than MSVC.
Yeah
At 01:21 25.05.03 +, Tor Lillqvist wrote:
Hans Breuer writes:
IMO fontconfig is a X-only library
No it isn't. Its sources don't require any X headers, so in what way
could it be an X-only library? On the contrary, when fontconfig is
used on X11 (by Xft), this is precisely in order
At 15:20 20.06.03 +0200, Sven Neumann wrote:
Hi,
Hans Breuer [EMAIL PROTECTED] writes:
- Intercept every PDB call if a macro recorder instance is running.
(try to guess the call stack depth to avoid recording functions
called by a plug-in)
That would mean that all actions go through
At 15:05 20.06.03 +0200, Sven Neumann wrote:
Hi,
Hans Breuer [EMAIL PROTECTED] writes:
Sent to gtk-devel w/o response
Did you file a bug-report? This is unlikely ever to be fixed without a
bug-report.
Current Gimp cvs (compiled on win32) triggers
the one in g_scanner_get_char
At 23:11 20.06.03 -0700, [EMAIL PROTECTED] wrote:
1. In plugins like whirlpinch.py we have:
(PF_SLIDER, whirl, Whirl angle, 90, (-360, 360, 1)),
I would assume the second item is the display version and is what should
show up in the UI, however whirl is what is displayed in the dialog box.
At 07:01 23.06.03 -0700, Nathan Carl Summers wrote:
On Fri, 20 Jun 2003, Hans Breuer wrote:
I'm about to give it another try with current cvs code
base, but before I would like to get some information
to avoid (if possible) fast rotting bits.
In short the approach (more info in bugzilla
[already sent off-list by mistake]
At 17:15 23.06.03 +0200, Sven Neumann wrote:
Hi,
Nathan Carl Summers [EMAIL PROTECTED] writes:
In short the approach (more info in bugzilla) :
- Intercept every PDB call if a macro recorder instance is running.
The cvs version of Libpdb already provides a
At 23:22 27.07.03 +, Tor Lillqvist wrote:
[...]
One irritating thing with GIMP on Windows currently is GTK bug
#112402, I really need to fix that soon. GIMP's toolbox and some other
windows are currently positioned with their title bar exactly off
screen.
This is a regression of previous
At 20:18 10.09.03 +0100, Alan Horkan wrote:
While a Screenshot plugin can be useful (easy enough to discover) it was
never what I really what I wanted as a windows user.
Rather I would have much preffered to be able to simply use the built in
Print Scrn (or Alt+Print Scrn to grab just the current
At 09:44 28.09.03 -0700, Jeff Trefftzs wrote:
Hi all,
As we are about to move to the next stage of gimpery, I have begun
looking closely at my large collection of plug-ins, many of which I
remember compiling with GIMP_ENABLE_COMPAT_CRUFT, and wondering how to
make them usable again under the new
At 21:31 12.10.03 +, Tor Lillqvist wrote:
I am getting tired of maintaining the .def files that list entry
points exported by DLLs. Gcc doesn't really need them anyway. If you
don't give it any .def file, it exports all global symbols, just like
Unix compilers/linkers traditionally work. (All
At 06:37 17.11.03 +, Tor Lillqvist wrote:
I wrote:
If you are using MSVC, I guess the real question is, is there any
chance that we will be able to claim supporting a MSVC build out of
the box with a straight face?
Hans Breuer writes:
Probably not, at least not until the issues
At 10:18 12.12.03 +0100, Dave Neary wrote:
Hi Shrinivas,
Shrinivas Kulkarni wrote:
Is there any help on steps to build GIMP 1.3.22 using MSVC++ 6.0?
There are instructions on building the GIMP for windows in the wiki:
http://wiki.gimp.org/gimp/HowToCompileGimp/MicrosoftWindows, but that
trying to build current cvs for --prefix=/opt I have compiled
glib, gtk+, pango, atk, gtkhtml (all from cvs) for the same
prefix [to not screw up my whole system].
I've set :
PKG_CONFIG_PATH=/opt/lib/pkgconfig
LDFLAGS=-L/opt/lib
LD_LIBRARY_PATH=/opt/lib
but still have problems building
On 04.10.2006 15:37, Alexander Rabtchevich wrote:
I've compiled the current version of fblur plug-in for Windows. But when
engaged, it complies: Pango-warning. Couldn't load font Tahoma italic
8... The plug-in works with Gimp 2.3.11, GTK 2.8.18.
There is no font definitions in the source code
On 05.10.2006 07:54, Williams, Andrew wrote:
With some difficulty I built Gimp 2.3.7 with Python using MinGW on Win
XP. Make and make install completed without error.
Gimp starts, but there is no Python in the Toolbars/Xtns menu (or any
others); Script explorer shows NO python scrips.
You
On 02.11.2006 07:01, Kevin Cozens wrote:
Hans Breuer wrote:
To make the new script-fu compile and work on win32 with msvc some
small source adaptions were necessary.
I've been looking over the patches. I have updated my copy of the source
with some of the proposed changes.
plug-ins
On 16.12.2006 12:22, David Gowers wrote:
Hi,
Is there some way of convincing GIMP to send warning/error/informative
messages to a useful place on Win32? I have some PyGimp plugins, written
for Linux GIMP, that either fail to register their procedures or do not run
properly when I install them
The recently added GIMP_LOG macro does not compile on win32/msvc6.
D:\devel\from-svn\gimp\appnmake -nologo -f makefile.msc sub-one THIS=display
[...]
..\../app\gimp-log.h(31) : error C2010: '.' : unexpected in macro formal
parameter list
[...]
gimpdisplayshell-callbacks.c(671) : error C4002: too
Sun Nov 18 09:07:38, Michael Natterer:
On Sun, 2007-11-18 at 13:29 +0100, Hans Breuer wrote:
The recently added GIMP_LOG macro does not compile on win32/msvc6.
[...]
It would be nice if the GIMP_LOG facility could be modified to follow the
pattern given by GDK_NOTE [2] to not exclude all
At 03.10.2008 14:02, Sven Neumann wrote:
Hi,
On Fri, 2008-10-03 at 01:58 -0400, Alec Burgess wrote:
Clicking [Use Web Browser] changes parameter Help browser to use: to
Web browser but does NOT open anything in my default browser (Portable
Firefox 3)
The code that opens the default
At 03.10.2008 15:50, Tor Lillqvist wrote:
As far as I know there is no GIO/win32 backend which supports http.
Http is supported in libgio itself (using the winhttp API from
winhttp.dll, which is looked up at run-time, so if you lack that, it
won't work). See gio/win32/gwinhttp*.c.
The DLL
At 03.10.2008 16:44, Hans Breuer wrote:
At 03.10.2008 15:50, Tor Lillqvist wrote:
As far as I know there is no GIO/win32 backend which supports http.
Http is supported in libgio itself (using the winhttp API from
winhttp.dll, which is looked up at run-time, so if you lack that, it
won't work
At 03.10.2008 20:21, Sven Neumann wrote:
Hi,
On Fri, 2008-10-03 at 19:37 +0200, Hans Breuer wrote:
The attached patch fixes this, but also adds a lot of hard to translate
strings. Should it be commited ?
We shouldn't add new translatable messages at this point. Could you
commit
At 09.01.2009 20:49, Michael Natterer wrote:
[...]
So finally, I hereby suggest to move to GPL3 asap.
Comments from any developers appreciated.
Fine with me and thanks for asking.
Hans
Hans at Breuer dot Org ---
Tell me what you need, and I'll tell you how to
get
30 matches
Mail list logo