to help you.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
(G_convertion 'str != NULL' failed
See http://bugzilla.gnome.org/show_bug.cgi?id=132366
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. But I don't think there's any reason to take it down.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
layer which is
a combination of the visible ones?
Selection-Copy Visible is next to Selection-Copy. That's IMO the
perfect place and it does certainly not belong into the Layer menu.
You might not have noticed, but there is no Layers menu at all.
Sven
Hi,
Dave Neary [EMAIL PROTECTED] writes:
I don't have a Copy visible entry in the Selection menu. Is this in
2.0.x or in the HEAD?
Me stupid. Of course it's Edit-Copy Visible, next to Edit-Copy.
And IIRC it's there since GIMP-1.0. It's definitely in GIMP-1.2 and
GIMP-2.0.
Sven
lacking the data that would support those
conclusions.
It's you who is interpreting that into the words I've written.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
this statement or not.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
-list archive not working?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
lately, I don't see why we shouldn't manage to do
the same.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
exactly is going wrong but there's some debugging needed
here.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
mentioned this because I hope that someone else but me can have a look
at this problem.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
analysis tool.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. Of course this doesn't work
with all file formats.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
the information we need here is not in the
CVS log message nor in the ChangeLog. All that's needed is information
about who changed how many lines in which files at what time.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu
Hi,
for those of you that are into statistiscs, have a look at this:
http://libresoft.dat.escet.urjc.es/cvsanal/gnome-cvs/index.php?menu=Modulesmodule=gimp
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
Hi,
Alan Horkan [EMAIL PROTECTED] writes:
I was thinking that Jpeg support might have to be preemptively removed
like Gif support was removed. (Although the Gif patents have expired in
America and will expire in Europe in June)
When was GIF support removed and why didn't I notice?
Sven
Hi,
Pedro Gimeno Fortea [EMAIL PROTECTED] writes:
Also, perhaps there is consensus on that the lists should be
moderated. If so,
- How many people don't agree about it being moderated?
Me.
But I agree that we should try to keep discussions on-topic.
Sven
that you can install gimp-2.0 and
gimp-2.1 into the same prefix. The two installations are _not_
disjunct, you need to keep them in separate prefixes!
When we approch gimp-2.2, we will probably change most version
numbers back to the GIMP API version which is 2.0.
Sven
potential patent problems.
We will also not remove the JPEG plug-in from the GIMP tarball. If
packagers decide to not include it in their binary packages for
whatever reason, that's the problem of the packagers (and their
customers) then.
Sven
___
Gimp
license from GPL that GIMP would need to get
permission from all authors, or reserve the right to change the
license later. Sven has said in the past that he often checks in
patches in his own name in CVS, that GIMP does not keep exact
records of who its authors are.
Sorry, but that's not true
it into a library eventually. Same
is true for the GimpUnitComboBox that I recently added to the core but
already noted that it's supposed to end up in libgimpwidgets as soon
as it's full-featured and the API has settled.
Sven
___
Gimp-developer mailing list
-in as a client. Or
alternatively, the PDB as a broker and both the plug-ins and the rest
of the core as clients.
Well, we have had this discussion before and not everyone necessarily
sees it your way. That's why we added that extra file that explains
our view of the license.
Sven
to give any reason why that should happen.
The papers you are pointing us at might be worth reading and they
could certainly inspire us for new ideas. But I don't see why you keep
bashing on the current vectors framework since obviosuly you didn't
even look at it yet.
Sven
the core to our
libraries. Moving code to libgimp* only makes sense if it provides
functionality that is useful for plug-ins. That isn't very often the
case. Most of the time it's better to expose the functionality to the
plug-ins through the PDB.
Sven
colour. Which is complicated.It
would be nicer (imho) if the text tool used the active FG if it hadn't
been set yet, rather than defaulting to black.
Sorry, but that's definitely not how it works nor how it's supposed to
work.
Sven
___
Gimp-developer
the
textcolorwidget but there is only the color dialog which is
inconvenient. I prefer 'o'.
You don't have to use the color dialog that you open from the text
tool options. Simply drag a color on the color button to change the
text color.
Sven
___
Gimp
. In
that case it needs to use the color of the text layer and that's why
the color button is needed.
All that needs to be done here is to get the bug fixed and resurrect
the intended behaviour.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
. With the introduction of text layers the
color button became necessary.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
? Or is that how it is supposed
to be?
I thought I explained that already. Unless a text layer is selected,
the color button in the text tool options is supposed to stay in sync
with the foreground color. That's how it works in the HEAD branch. I
am not sure when and why it broke in gimp-2.0.
Sven
managed?
Sven does it, mostly.
Well, yes. But please don't send me patches by email. Given the amount
of spam I receive I might not even get your mail. And even if it
reached me, I would ask the sender to open a bug report and attach the
patch to it. That's the only way to assure that patches aren't
managed?
The developer FAQ has answers to your questions:
http://developer.gimp.org/faq.html
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
started to make the toolbox configurable. Needs code to save and
load these settings as well as a more untuitive GUI. I guess you can
expect this to work when I'll send the next status report...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED
at all. You should still be
able to drag the corners just as in GIMP 1.2. We only added a
convenient way to crop the image to the size of the current selection
(Image-Crop Image) but that's not really related.
Sven
___
Gimp-developer mailing list
[EMAIL
recent version
and theming it so that it looks more GIMPish. We only didn't get
around to do this yet...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
later refactor code?
Looks like you didn't understand the role of libgimp. libgimp is
strictly a plug-in library; the core doesn't use libgimp. It's
basically the C language binding of the PDB.
Perhaps this information can help you to refactor your question.
Sven
you put some work into this
but I think you should show the same respect to other people's work
that you expect for your's. Sometimes things just don't work out and
hours of work have to be thrown away. Happens every day. There's no
reason to get pissy about that.
Sven
. But I'd rather not do too many changes to the dialogs in this
development cycle. Keeping some of the established user interface
elements will the switch to 2.2 easier for our users.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
; if not, the parasite is just a bare header.
Would it be preferable to not create a parasite in this case?
That sounds like the right thing to do.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo
property to one of the base classes of the GimpRc
object:
http://developer.gimp.org/api/2.0/app/app-config-objects.html
This code lives in app/config. It would certainly not hurt to let us
know what you are working on...
Sven
___
Gimp-developer mailing list
are
interested...
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
it wants to use as long as it's possible to integrate it with
the GLib main loop.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
, actually the plan was to make the preferences dialog a one-level
hierarchy. We'd like to finish this task for GIMP-2.2. Any help with
this would be appreciated.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu
.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
which
clearly refers to a device that gives coordinate input.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. A sane approach for GIMP running on
X11 is to run GIMP and a simple window manager in an Xnest session.
Perhaps we should bundle a script that does this with the standard
GIMP distribution.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
. I wonder if there's a way to convert between the menu XML
files and the Wiki content. That would make it possible to easily try
the suggested menu layout.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
Deweirdifier does. If it works well, maybe I can make the patch
available as an attachment to bug #7379. Here's the result:
http://perso.wanadoo.es/p.gimeno/temp/bgw-screenshot-1024.png
I don't understand this screenshot; it seems to just add another
window. What's the advantage?
Sven
not desire this
feature at all since all Mac applications behave like GIMP currently
does. What the Mac people are asking for is to have the image and
toolbox menus merged into a menubar at the top of the screen.
Sven
___
Gimp-developer mailing list
[EMAIL
=edit-fill-fg/
menuitem action=edit-fill-bg/
menuitem action=edit-fill-pattern/
menuitem action=edit-stroke/
menuitem action=vectors-stroke/
separator/
/menu
This stuff is found in the new toplevel source directory menus.
Sven
a look at the source.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
David Neary [EMAIL PROTECTED] writes:
Cool! Looking at Copy visible, you register a menu entry in
Image/Edit/Copy/Copy _Visible. Do placeholders act the same
as menus?
Well, we are all new to this but it looks as if that's the case.
Sven
any other GIMP
dialog.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
/plug-in.html
I don't think we should point people to this document any longer. It's
outdated and should better be removed. http://developer.gimp.org/ is
where we are collecting more uptodate information and that's where
people should be pointed to.
Sven
.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
in the GIMP source tree. Also
make sure you have the GIMP API reference manual available. It comes
with the GIMP tarball (in the devel-docs directory) and is available
online at http://developers.gimp.org/.
Sven
___
Gimp-developer mailing list
[EMAIL
GNOME
application.
Sven
PS: See http://sven.gimp.org/gimp-new-image-dialog.png for an almost
HIG compliant file-new dialog. This is a screenshot from the HEAD
branch.
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu
-in executables
are linked to at run-time. That might give you a hint on what's going
wrong.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
to work on
this.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
pkg-config --libs gimp-2.0
If you want to use libgimpthumb, you can use this:
pkg-config --cflags gimpui-2.0 gimpthumb-2.0
pkg-config --libs gimpui-2.0 gimpthumb-2.0
You should get the idea. If not, have a look at the pkg-config
man-page.
Sven
nicely on Win32 and we don't want to
change that, you can rest assured that we will not do any changes that
would cause a regression on Win32.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp
are refering to the button order in the action area, I have to
say that I am very happy about this decision. Mac OS uses this button
order and I always found it to be more logical than the Windows way of
arranging the buttons.
Sven
___
Gimp-developer
rendering, but it looks to me like
Resolution X has an extra space between X and ':.
That's due to kerning. As I said in another mail, this could be solved
by removing the colon.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
leave
them online until more screenshots are available from www.gimp.org.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
things while GIMP for experts would always come up
with the full dialog expanded. While the user explores the GIMP world,
she can expand more of the dialogs. Whenever a frame is left expanded,
GIMP should remember that and the dialog come up like this the next
time.
Sven
me. There's no intention to update the screenshots
on dgo. Instead I suggest that more screenshots are added to
http://gimp.org/screenshots/. So the screenshots should probably send
to the gimp-web team or attached to bug reports against gimp-web.
Sven
change this. A whole lot of thought went into this, it's used
consistently and there's no compelling reason to change it.
If screen readers need this info, we can certainly add a hint for them
using the ATK API.
Sven
___
Gimp-developer mailing list
but it should show the stable version only.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
you,
then you should be willing to touch it. If you aren't willing to do
any changes to gimp-web CVS module, then you should IMO refrain from
asking for changes. Doing so only shows disrespect for the people
working on the site.
Sven
___
Gimp-developer
into GIMP developers but for that to work, the site needs to
be interesting for non-developers also.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
Jimmac and Tigert drew some very nice mockups for the File-New dialog:
http://jimmac.musichall.cz/stuff/new_image_simple.png
http://jimmac.musichall.cz/stuff/new_image_expanded.png
I have implemented this in my local tree now. Here's a screenshot of
the expanded version:
frequent task, so
it should be easily accessible.
Agreed. I think it should be a first-level entry in the View menu,
as I said above.
I think it should (additionally) be a popup menu in the image status
bar.
Sven
___
Gimp-developer mailing list
[EMAIL
much room for improvement. IMHO we should stick to it.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
doesn't belong into GNOME Bugzilla.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
proprietary scripts that they don't publish anywhere,
I am going to show no tolerance towards them.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
. After all there don't seem to be many people able to
build GIMP from source on win32.
Perhaps the setup scripts should be kept in CVS then. Not sure if they
belong to the GIMP source, probably not. But there could be a separate
module.
Sven
___
Gimp
probably the best we can do.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
instead. Are there any
objections?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
- the icon that is also used in the menus
- a descriptive title of the action associated with this dialog
- a preview and the name of the viewable (image/drawable) that this
dialog operates on
IMHO removing this header would be a regression.
Sven
to? If I remember
correctly the only confusion about Edit-Copy was that I mistakenly
used Selection-Copy in one of my mails.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
it.
Mitch reenabled tearoff menus. This is probably the last regression
that was introduced with the port to GtkUIManager.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
that does copy and paste doesn't know
anything about the GimpDisplay and it's scale ratio and offsets.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
Carol Spears [EMAIL PROTECTED] writes:
is there a more reliable way to communicate this to you?
Yes, a reproducable test case. A detailed instruction on how to
reproduce the problem.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
there is anything we need to change here. You are using
a nonstandard configure option that is strictly discouraged. We know
that it doesn't work and we told you. We even plan to fix it
eventually.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
this discussion belongs to the OpenICC list and should better
be continued there.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
Stephan Menzel [EMAIL PROTECTED] writes:
as promised, I kept looking for the problem in porting refocus to
the Gimp 2. It seems like the gimptool was indeed the main issue,
but I got it running without switching to pkg-config as Sven
suggested. Thought it might be easier since I really
solution. You need to learn the syntax just once and can use it for
all those libraries that install .pc files.
Don't get me wrong, there's nothing bad about using gimptool. Just
wanted to point out the advantages of using pkg-config.
Sven
___
Gimp
. Might be a good
time to do that now.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
to think of it, it might be benificial to put some generic
convolution code in libgimp or an allied library. Just a thought.
libgimpmath would perhaps be a good place. If you can extract some
common code and give it a nice API than that would certainly be a very
good idea.
Sven
version.
Would it be a good idea to remove Laplace and Sobel then? Perhaps
after adding the extra Sobel options to edge.c?
Of course it would also be a good idea to help the user to choose a
reasonable edge detection algorithm. I guess we will need a preview
for this.
Sven
to implement with the GIMP image window and
the filter plug-in being in too different processes. Especially if you
want this to perform in almost real-time.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
isn't a standard make target so if I was you I
would stick to the standards and ignore the request to add it. Just
add a note to the README or INSTALL file explaining how to install the
plug-in.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED
.
Again, sorry, but I don't understand this. What's the displayed area?
What do you mean when you say render?
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
comment.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
the buffer outside the preview widget. That would allow
the plug-in to render a larger version and implement scrolling by
changing the offset into the buffer.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman
indicator.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
to actually happen. Anyway, I consider this rather
bad style. IMO, if the preview takes considerable time, then it
shouldn't be shown halfway done but instead the progress API should be
used to draw a progress indicator in place of the preview. What do
others think?
Sven
we
should offer our help. And of course we should be willing to out
packages up on ftp.gimp.org and announce releases on www.gimp.org.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
their patches committed and I'd really
like get the outstanding preview patches in as soon as possible.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
surely need more work, so if someone would like to become
the GIMP devel-docs maintainer, that would be very much appreciated.
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
that might be needed in the
future so I am not completely sharing your optimistic view on this.
But in general it seems like the right thing to do. Nevertheless I'd
like to have a look at the proposed libgimpprint-gtk2 API before it's
finalized. Could you please post a header file here?
Sven
901 - 1000 of 3034 matches
Mail list logo
