On Sat, 2002-02-16 at 11:48, Christian Rose wrote:
lör 2002-02-16 klockan 06.59 skrev Marco Lamberto:
Zoom In + [Yes, changed, a bit more logical, no?]
Zoom Out-
If you have an US keyboard you'll notice that while the minus - is immediatly
As any looked into how all this will work with different window
managers? What window managers grab what keys and can the window
managers easily be configured to use alt if gimp isn't using it?
It is important to check this since we will otherwise end up with lots
of whiny users who can't
I guess you are joking but I want to state this nevertheless:
The version from CVS should always build and indeed it does so almost
all of the time. If someone has trouble to build we ask you to pester
whoever might have broken the build (check the ChangeLog!). If there's
an obvious fix
Please everyone test this how to and see if it is lacking anything. It
is intended to be a beginner tutorial for compiling gimp 1.2 from CVS.
I want everyone to read it even if you don't have time to test it.
Carol and I worked really hard on it. I wrote it as an intermediate
tutorial, but
On Mon, 2002-01-21 at 05:53, syngin wrote:
On Sun, 20 Jan 2002 16:07:04 -0500
Carol Spears [EMAIL PROTECTED] sent:
i would like to have it here, personally:
http://www.bbwellington.com/
except that they have only non-smoking rooms and don't mention having an
internet connect, and i
On Fri, 2002-01-11 at 19:01, Chandhaketh Nutthavudh wrote:
Hello there:
I'm currently developing a photoshop-liked's Terazzo for Gimp and willing
to distribute it soon. One choice is to distribute it with gimp registry
website and I'm also considering the possibility to bundle it with
GNOME has been working on a new help browser that works with XML and
scrollkeeper directly. It is worth checking. Also worth a look is the
project David Merril is working on that will make it possible to use the
XML files and Scrollkeeper stuff with any browser. It is called
Scrollserver I
Continuing Bolsh's thread...
My current project is to proofread all the strings in the program. I am
trying to standardize things like proper use of plug-in so the user is
presented with a consistent use of language in the interface. I am also
trying to improve standardization of strings as
Okay. This has gone too far.
Both sides made mistakes. How about we all admit that? Mitch and Sven
should have talked to Daniel offlist first. Perhaps requiring patches
posted to gimp-dev is going too far.
Daniel: GIMP isn't ready for optimizations. You should have talked to
Kelly before
While we're at it -- why does GIMP 1.3 suddenly have a lot of new tools
(Select by color, Adjust brightness, etc.) that you can find in the other
menus too, sometimes just as easy? (The icons look a lot like the same for
me, and IMHO they're mostly clutter :-) )
Is there any way to
On Tue, 2001-11-27 at 15:30, Sven Neumann wrote:
Hi,
Rebecca J. Walter [EMAIL PROTECTED] writes:
Mitch, Sven.. when you have time.. Can you make a to do for developers
that want to help?
http://developer.gimp.org/gimp-todo.html
it's generated from TODO.xml as found in the source
Okay, so I misjudged the state of development Gimp is in. I remember trying
to find out some time ago how hard it would be to contribute things to Gimp,
but I gave up pretty soon. In another thread Rebecca Walter suggested
creating a TODO for developers that want to help. I'd like to
On Tue, 2001-11-27 at 22:48, Laramie Leavitt wrote:
So...
Is anyone actively working on GIMP 2?
Well.. YES. Since 1.3 is the path to GIMP 2 and a lot of people are
working there butts off on 1.3.. I would say that is a BIG HUGE YES!
No one can even think about GIMP 2 until GIMP 1.3 is
Bex is only working at the core right now. Your patch is already applied
in my tree so it will certainly find its way into HEAD. I wouldn't mind
if you commit it yourself however.
Bex is slow right now because she is fighting an ucky cold or
something. Other people also paying attention
please no bugreports yet for the 1.3 series, it's just too buggy --
we'd drown in reports :)
Mitch: Can you or Sven make a formal announcement to this effect to all
relevant mailing lists and other places where this was announced? With
the announce on users too, I fear you will soon have bug
On Tue, 2001-11-13 at 23:23, [EMAIL PROTECTED] wrote:
On 13 Nov, Rebecca J. Walter wrote:
make them. Especially if bugzilla doesn't have a GIMP 1.3 thing. I
have this fear of people mistakenly submitting 1.3 bugs against 1.2
because 1.3 sin't there to choose.
FWIW there is a 1.3.0
Just to warn everyone before translators start freaking out at Sven, I
am proofreading all original strings in the head branch of GIMP CVS. I
don't know how long this will take me. I will send out another mail
when I am mostly done. While this should improve future GIMP texts, it
will break
*) I am not necessarily advocating that we do a bug week -- as the
Mozilla press review points out, a large number of people who would
normally not thought of themselves as 'developer material' apparently
can be involved with the Mozilla bug week because the UI of the
browser is coded
I think that regardless of what the original format is, translators
should be given and work with po files. Christian Rose is right in his
reasons. I have a few more to add.
1) The translator can't accidentally edit the wrong place and mess up.
2) It is what translators are used to working with
The format I've outlined above still has one problem unrelated to i18n:
Do we want to allow paragraphs in tips for nicer layouting and how do
we represent them? By adding a para.../para tag ?!
No. Any tip long enough to require an additional paragraph should not
be a tip. That information
perhaps I'm imaging something wrong here, but I think graphics would be
overkill for the tips. Stuff like this belongs to the help pages if you
ask me. It would probably help to allow links to help pages in the tips
dialog and it would also be much simpler to implement than text flow
On Sat, 2001-10-06 at 12:49, Daniel Egger wrote:
On Sat, Oct 06, 2001 at 02:06:15AM -0600, Nathan C Summers wrote:
We can also use XML for its original purpose -- a markup language. Even
just adding an emphasis tag can allow tip writers to be emmuch/em more
expressive.
That's an
it would matter if you could name an advantage it would give us. I don't
mind adding a simple XML-parser to GIMP-1.4 since it's pretty simple
using GMarkup from GLib-2.0, but I don't want to do so without a good
reason.
hmm.. XML could be quickly converted to HTML and used on the web
it might be useful if the color to alpha filter could a) interact with
the color picker or b) pull the information about the image background
from the color tool stuff and use that as the color to replace. it isnt
easy for a lot of users to select the color in the color selector
without being
IMHO, the pencil tool should be left alone for consistancies' sake
and there should be a new tool to deal with the very special case
of drawing single-pixel-wide hard-edged lines.
This hypothetical gadget could use Bresenham's algorithm or something
like that because it wouldn't *NEED* to
On Wed, 2001-08-29 at 15:44, Sven Neumann wrote:
Hi,
Branko Collin [EMAIL PROTECTED] writes:
On 29 Aug 2001, at 11:22, Sven Neumann wrote:
I plan to merge translations from the stable gimp branch (gimp-1-2)
to the HEAD branch very soon now and hereby ask all translators to
26 matches
Mail list logo
