this to the installer of whatever windows software. It's just
silly to say that the GIMP user installation would be overly complex
or annoying.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
at least reduce
confusion among our users.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
users. The dialog is great and much better than a html help page for
example, but it's presented at a time people will have no clue what it
means.
Perhaps we should show it on every startup then ?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED
because it was needed. It serves its
role, it works, there are hundreds of places where developers effort
is better spent than in removing it.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
it.
Maybe it could come along with XCF, even though not being complete,
on the 1.3.x series?
Definitely not. The 1.3.x series is coming to an end and we will
certainly not start to change our native file format a few weeks
before the first release candidates for 2.0 are supposed to be ready.
Sven
overhaul of the web-site could help to improve this
situation.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
in The GIMP seems to be using
asm()
I don't know this stuff good enough to know the difference, but I'd
say we need to change the configure check so that is uses the same
asm constructs that the code in app/composite is using.
Sven
___
Gimp-developer
Hi David,
could you please test the attached diff to configure.in. It should
find the problem with your compiler and it even simplifies things a
bit.
Sven
Index: configure.in
===
RCS file: /cvs/gnome/gimp/configure.in,v
retrieving
Hi,
Christopher Curtis [EMAIL PROTECTED] writes:
We actually had something else in mind but since you don't seem to be
interested I won't waste my time explaining our ideas.
It is very sad to see that Sven thinks that Robin Rowe is the only
person to whom his ideas should be told. Pity
for a number of
reasons. I don't see why I should let it disappear for no good reason.
The attitude I keep encountering is a strong resistance to progress.
Sorry, but removing features looks more like a regression to me.
Sven
___
Gimp-developer
.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
in the spirit of not delivering promised features? Did we
ever promise anything? I can not remember that we did that.
Sorry, if this sounds as if I would not believe you, but this idea
seems beyond my imagination...
Sven
___
Gimp-developer mailing list
/. But
please don't bug me with any problems you might have to compile or run
them...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
not sure of its current
state).
I think we shouldn't do this change since I can not follow your
arguments. Everyone seems to be using a different keybinding for Redo
and we use Ctrl-R for quite some time now. Why should we change the
default? Perhaps we need a hig-menurc...
Sven
Hi,
[EMAIL PROTECTED] (Tino Schwarze) writes:
Why not simply (?) use both keystrokes?
Because IIRC, GTK+ simply does not support this. Apart from that, I
think it would introduce clutter and confusion.
Sven
___
Gimp-developer mailing list
[EMAIL
to add more mnemonics to the menus (mnemonics are those
underlined characters that improve keyboard navigation). As soon as
you start using them, you will find yourself accidentally reassigning
keyboard shortcuts quite frequently.
Sven
___
Gimp-developer
anoncvs.gnome.org
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. Until that has happened, I'd prefer if you not reclaimed the title
Web Maintainer in any discussion related to gimp.org.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. The menubar has no
additional value.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
-bar, rulers, status-bar
and the like. These changes do not affect the state of the view in
normal mode and this state is saved and will be used again when you
switch to fullscreen mode again later. I hope this clarifies things.
Sven
___
Gimp-developer
and the archive hierarchy in sync.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
mode and that we
even decided to allow you to tweak what gets hidden and what not is
just an additional nicety and I'm actually tempted to remove it.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo
to compress the archive.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
access to it as simple as possible. Of course this goal could
also be achieved by providing a library that handles whatever weirdo
binary format we come up with...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
it but it violates the spec. If I am
wrong here, please show me where the spec defines the special role of
the NULL character.
Is there a special reason you dislike the idea of using an archive
instead of a single XML file? I thought we would have been past this
point already...
Sven
Hi,
David Neary [EMAIL PROTECTED] writes:
No - it's enabled by default because I thought it should be. I'm
quite sure that Sven has turned it off :)
I have it turned on so I get reminded how akward it is all the time I
use The GIMP. Actually I tried to get used to it but I still can't
stand
scriptable, etc...
You can do all this with an uncompressed archive as I suggested.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
CVS or 1.3.16 attached to the
bug-report.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
thanks to Mitch the behaviour of full-screen mode is now fully
configurable. The change to implement this was probably a lot smaller
than most of the comments on this subject that appeared on this
list...
Sven
___
Gimp-developer mailing list
and IMO this should happen
soon.
Well, what will happen after the final 2.0.0 release? I think we
should try to target a quick 2.2 release with only minor feature
improvements but this is really something that I would want to discuss
at the camp...
Sven
will be dropped then.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
saving a channel
(presumably the cut selection) or (2) necessarily pops up the
Save-As-PNG dialogue (even though all those parameters were
presumably set in the call to (file-save-png).
Could you make your script available so that we have a chance to look
at it?
Sven
of having this new file format in 2.0?
No, it's definitely too late to introduce a new file format now.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
, and
saves CMYK TIFFs...
Could you send me (or the list) a copy of this plug-in? I am
particularily interested in the CMYK loading and saving routines.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo
the arguments a few times and finally
decided that we want to go for 2.0. What is so insistent about this?
It's a decision and it had to be done at some point. Now please, for
the good of GIMP, accept it and let us proceed to prepare this
release.
Sven
___
Gimp
is the fact that we don't seem to be able
to end a discussion and proceed with development.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
most
of the points you brought up. Dave, is that really you who wrote this??
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
-browser in 1.3? I know that
there are issues with the URL combo widget but apart from that it
should work fine. Is there a problem we don't know about? Perhaps
someone should file a bug-report then.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED
thing, we
would better not do this change. After all it involves touching _lots_
of files.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
to postpone this until after the release. However we
should probably add a dummy pointer to the conversion functions now so
that we can use it for passing a color profile later.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
) but I am sure it can
be done.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
for this.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
of contributions a particular voter has made to this project.
If you stood up and publicly said something like: yes, the majority
here is against it, but I, the Sven who does by far most of the
coding work (might include Mitch, too, since you are his voice
here) just overrule everybody else and force out
the framework and encourage
people to contribute help for gimp-2.0. We could setup some text that
is displayed for all missing pages and that explicitely encourages
people to write help on this topic.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
on the users.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
of course
depend on yelp and use it but it will pull in a whole bunch of other
dependencies.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
a
look at the Wiki pages or just mail me (or preferably the list).
https://wiki.camp.ccc.de/Camp/view/Main/GimpTent
https://wiki.camp.ccc.de/Camp/view/Main/GIMPDevelopersConference
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
for the docs is not one of them.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
have a tarball ready but since I believe that the 2.0
version number change needs to be outlined in the release notes, I am
delaying the release until tomorrow. If someone wants to help with the
release notes, I would very much appreciate a draft until tomorrow.
Sven
them distinct. If I am wrong about this being a different
topic, this may be because you never explained what you are actually
doing with this plug-ins XML file that you are working on.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
to
discuss it over, but for me there's no point in supporting a quick
hack instead of a proper long term solution which the HTML one
simply cannot be, at least not in this form, and I haven't heard of
a better one yet.
I tried to outline one. Should I try to explain it again?
Sven
to fry, but I'd ask the current project maintainers to
reconsider releasing the current HEAD branch as 1.4 instead of 2.0.
The ball is rolling now and any further discussion about it is only
hurting GIMP's reputation.
Sven
___
Gimp-developer mailing list
Hi,
Kelly Martin [EMAIL PROTECTED] writes:
Sven Neumann wrote:
The ball is rolling now and any further discussion about it is only
hurting GIMP's reputation.
You're going to do what you're going to do. I'm just offering my
counsel. Claiming that offering my counsel is hurting GIMP's
have integrated it to their homepage.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
that help for this subject is missing.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
must.
The API has html_document_find_anchor() which seems to fit our needs
just perfectly.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
==
- Made the text tool optionally create a path [Sven, Mitch]
- Added the ability to reverse gradients to the blend tool [Mitch]
- Added dithering to the blend tool [Alastair M. Robinson]
- Changed all(?) GIMP-1.4 references to GIMP-2.0 [Sven]
- Allow to transform paths using
Hi,
I've added a list of GIMP related CVS modules to
http://developer.gimp.org/cvs.html
Could needs some stylesheet tweaking though...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
to follow the
GIMP-1.3 API changes. It requires at least GIMP-1.3.17. If you want to
write a larger plug-in for GIMP 2.0, this package should give you a
good start.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
is not out-of-date.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
available that are needed to build
GIMP-1.3. If we decided to change our dependencies to a newer version,
we always checked if this is really necessary.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo
operations is properly working.
I wouldn't mind if you or someone else filed bug-reports for these two
issues...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
in a single place, we could change it to use and preview a circle.
Would that make sense?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
layer, but rest assured, you won't
notice the difference at the user interface level. It's just a fact
that we could include the possibility to restore the text later and I
wonder if we should do that.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED
in any
formulas.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
to be somewhat usable you'd have to take the
in/out coverage of the pixels under the radius into account or
you'll get disturbing results for small sizes.
Of course I assumed a correct implementation.
Sven
___
Gimp-developer mailing list
[EMAIL
this is important
enough to be changed. It should be a very simple hack.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
helpful.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
all files? You must be kidding.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
on Shift-wheel since some early 1.1 version.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
Alan Horkan [EMAIL PROTECTED] writes:
so how do you scroll sideways (using the wheel)?
is this the same keybinding as Photoshop?
Dunno what PS uses but GIMP uses Ctrl.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
Hi,
I've been asked by Øyvind Kolås [EMAIL PROTECTED] to
forward this proposal to the list on his behalf...
Sven
---BeginMessage---
Sven could you forward this to the list, my mailing possiblities from the
camp is kind of braindead.
What follows is a proposal for a format to save a GEGL
should be defined by
GEGL and GIMP will only add some user interface specific things in its
own namespace.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
to be embedded makes the definition of our format a lot
simpler however and allows for various established compression
techniques to be used.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
difference.
Actually with GEGL, a solid white or black image will be represented
using a special layer node that has no image data at all.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
dialogs can be maximized and widgets reflow as you
described. What are you talking about?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
in the archive, not embedded in
the XML. I've also mentioned that I don't think that we should have
folders in the archive since the structural information should be in one
place, not in the XML and in some sort of directory tree.
Sven
___
Gimp-developer
talking about.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
the win32 build but it looks as if you need
to cvs update in the virtual build module in the toplevel directory in
order to get win32/compile-resource.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo
exception of a few message dialogs). (Similarly
you there should probably be a minimise icon for any of the non modal
dialogs).
We certainly don't fiddle with the window decorations. It's entirely the
fault of your WM.
Sven
___
Gimp-developer mailing
define this? It should.
I'll probalby file a bug report to keep track and help me remember. I'll
assign it to myself, please dont close it invalid until I can properly
verify that the problem is not with the GIMP.
Please file it against metacity.
Sven
a discussion started. We should also try to
involve more people early. I suggest we ask for volunteers on the
gimp-user list and other user forums.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
install these they should be cross-linked
with the libgimp API reference as well as the GLib/GTK+ reference
manuals.
Below I have included the GIMP core object hierarchy in text format for
you to look at while gtk-doc is busy to generate the real thing...
Sven
to gimp-help and I wasn't sure what to respond. A web-page
to refer people to would certainly help a lot.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
on a
translation, I thought we should bring this up. There seemed to be much
consensus on the help system lately but the lack of a write-up makes it
hard to do the changes to the helpbrowser that will be needed to use the
new help pages.
Sven
___
Gimp-developer
the buttons and
the WM has all the hints it needs to detect that our dialogs are
resizeable. Did Havoc ever explain why metacity is behaving like this?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
an editor that copes with UTF-8, you can simply use
umlauts in your texts.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. It's impossible to start an implementation based on this.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
tips file you will notice that it becomes
rather hard to handle with the amount of translations in there. That's
why I said that your current approach doesn't scale well. However if you
evaluated the available tools and decided against them, that's your
choice then.
Sven
understand it. It will probably be best
if I keep myself out of this then and stop to try to work with you.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
a
cross-linked HTML version of this. What I posted here is just some
intermediate file created by gtk-doc using introspection.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
, but what are UTF-8 entities? I had a look at the
stuff in CVS:
secondaryEinfuuml;hrung/secondary
and I would have expected:
secondaryEinfhrung/secondary
(Let's hope the mail client transfers this correctly and marks the mail
as UTF-8 encoded).
Sven
Hi,
On Tue, 2003-08-19 at 09:48, Raphaël Quinet wrote:
On Tue, 19 Aug 2003 01:35:33 +0200, Sven Neumann [EMAIL PROTECTED] wrote:
What I care about is how the generated HTML files in different languages
will be structured since the helpbrowser will have to choose the
appropriate files based
will not any longer waste any of my
free time dealing with you.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
file. All XML-1.0 compatible tools must handle UTF-8
correctly and there is thus no need to use entities.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Bugzilla only. Anything that is not coming from
Bugzilla would be bounced back to the sender.
I think everyone keeps suggesting this for quite some time already but
we need Yosh to implement this suggestion...
Sven
___
Gimp-developer mailing list
[EMAIL
will have to drop these workarounds and depend on gtk+-2.2.2 or
newer.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
likely
see gtk+-2.4 being released. But I'd rather avoid a dependency on that
version of possible.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
at that.
I'd really like to see libgimpthumb going into the next release but I
surely won't manage to finish this today. I was also suggesting to do a
release before the end of the week though.
If you send me your output from 'make distcheck' I could probably help
you to figure out that problem.
Sven
-08-22 but Yosh removed
the offending language from configure.in on the same day so I doubt that
this was causing the problem for you. I have sent mail to the translator
who broke the build explaining the situation and pointing him at
README.i18n.
Sven
501 - 600 of 3034 matches
Mail list logo
