gimp-web r1876 - in trunk: . about about/splash about/splash/images admin bugs/howtos downloads images release-notes release-notes/images screenshots source style unix
- From: martinn svn gnome org
- To: svn-commits-list gnome org
- Subject: gimp-web r1876 - in trunk: . about about/splash about/splash/images admin bugs/howtos downloads images release-notes release-notes/images screenshots source style unix
- Date: Tue, 30 Sep 2008 22:32:06 +0000 (UTC)
Author: martinn
Date: Tue Sep 30 22:32:05 2008
New Revision: 1876
URL: http://svn.gnome.org/viewvc/gimp-web?rev=1876&view=rev
Log:
Merged the GIMP 2.6 branch (branches/v2.6, r1808:1875) to trunk.
Added:
trunk/about/splash/images/gimp-splash-2.6.png
- copied unchanged from r1875, /branches/v2.6/about/splash/images/gimp-splash-2.6.png
trunk/images/frontsplash26.png
- copied unchanged from r1875, /branches/v2.6/images/frontsplash26.png
trunk/release-notes/gimp-2.6.htrw
trunk/release-notes/images/2.6-brush-dynamics.jpg
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-brush-dynamics.jpg
trunk/release-notes/images/2.6-empty-image-window.png
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-empty-image-window.png
trunk/release-notes/images/2.6-experimental-gegl-tool.png
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-experimental-gegl-tool.png
trunk/release-notes/images/2.6-lgm-2008-groupshot.jpg
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-lgm-2008-groupshot.jpg
trunk/release-notes/images/2.6-new-free-select-tool.png
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-new-free-select-tool.png
trunk/release-notes/images/2.6-scroll-beyond-border.png
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-scroll-beyond-border.png
trunk/release-notes/images/2.6-text-tool-and-rectangle-handles.png
- copied unchanged from r1875, /branches/v2.6/release-notes/images/2.6-text-tool-and-rectangle-handles.png
trunk/release-notes/images/gimp-curves-tool-2-4-vs-2-6.png
- copied unchanged from r1875, /branches/v2.6/release-notes/images/gimp-curves-tool-2-4-vs-2-6.png
trunk/screenshots/2.6-brush-dynamics-example-thumb.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/2.6-brush-dynamics-example-thumb.jpg
trunk/screenshots/2.6-brush-dynamics-example.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/2.6-brush-dynamics-example.jpg
trunk/screenshots/alternative-2-6-ui-layout-example-one-thumb.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/alternative-2-6-ui-layout-example-one-thumb.jpg
trunk/screenshots/alternative-2-6-ui-layout-example-one.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/alternative-2-6-ui-layout-example-one.jpg
trunk/screenshots/alternative-2-6-ui-layout-example-two-thumb.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/alternative-2-6-ui-layout-example-two-thumb.jpg
trunk/screenshots/alternative-2-6-ui-layout-example-two.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/alternative-2-6-ui-layout-example-two.jpg
trunk/screenshots/gnome-1280x800-fresh-start-thumb.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/gnome-1280x800-fresh-start-thumb.jpg
trunk/screenshots/gnome-1280x800-fresh-start.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/gnome-1280x800-fresh-start.jpg
trunk/screenshots/on-canvas-preview-of-gaussian-blur-in-2-6-thumb.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/on-canvas-preview-of-gaussian-blur-in-2-6-thumb.jpg
trunk/screenshots/on-canvas-preview-of-gaussian-blur-in-2-6.jpg
- copied unchanged from r1875, /branches/v2.6/screenshots/on-canvas-preview-of-gaussian-blur-in-2-6.jpg
Removed:
trunk/images/frontsplash24.png
Modified:
trunk/ChangeLog
trunk/about/history.htrw
trunk/about/splash/index.htrw
trunk/about/splash/stable.html
trunk/admin/gimp-web-urls
trunk/bugs/howtos/bugzilla.htrw
trunk/downloads/source.xhtml
trunk/index.htrw
trunk/release-notes/ (props changed)
trunk/screenshots/index.htrw
trunk/source/index.htrw
trunk/style/wgo.css
trunk/unix/fonts.htrw
trunk/unix/index.htrw
Modified: trunk/about/history.htrw
==============================================================================
--- trunk/about/history.htrw (original)
+++ trunk/about/history.htrw Tue Sep 30 22:32:05 2008
@@ -62,6 +62,11 @@
<li>2007-10-24 <strong><a href="/release-notes/gimp-2.4.html">GIMP 2.4.0</a></strong></li>
<li>2007-10-31 GIMP 2.4.1</li>
<li>2007-11-20 GIMP 2.4.2</li>
+ <li>2007-12-16 GIMP 2.4.3</li>
+ <li>2008-01-30 GIMP 2.4.4</li>
+ <li>2008-02-29 GIMP 2.4.5</li>
+ <li>2008-05-29 GIMP 2.4.6</li>
+ <li>2008-08-21 GIMP 2.4.7</li>
</ul>
<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
Modified: trunk/about/splash/index.htrw
==============================================================================
--- trunk/about/splash/index.htrw (original)
+++ trunk/about/splash/index.htrw Tue Sep 30 22:32:05 2008
@@ -37,8 +37,8 @@
<li>Make the splash <b>300x200</b> or more. (Smaller splashs will make
text being cut off)</li>
<li>Go to your personal GIMP directory. For UNIX users, this is
- usually in <b>/home/username/.gimp-2.4/</b>. For Windows, this is
- usually in <b>C:\Documents and Settings\username\.gimp-2.4\</b>
+ usually in <b>/home/username/.gimp-2.6/</b>. For Windows, this is
+ usually in <b>C:\Documents and Settings\username\.gimp-2.6\</b>
(you may have to enable the option "Show Hidden Files" in your file
browser).</li>
<li>Create a "splashes" directory if it does not exist.</li>
Modified: trunk/about/splash/stable.html
==============================================================================
--- trunk/about/splash/stable.html (original)
+++ trunk/about/splash/stable.html Tue Sep 30 22:32:05 2008
@@ -42,6 +42,8 @@
<a href="images/gimp-splash-2.4.png" rel="imagebox-splash" title="GIMP 2.4<br /> Author: Paul Davey"><img alt="#" id="gimp-splash-2.4" src="images/gimp-splash-2.4.png" width="128" height="128" /></a>
+<a href="images/gimp-splash-2.6.png" rel="imagebox-splash" title="GIMP 2.6<br /> Author: Alexia Death"><img alt="#" id="gimp-splash-2.6" src="images/gimp-splash-2.6.png" width="128" height="128" /></a>
+
</div>
<br style="clear: both">
Modified: trunk/admin/gimp-web-urls
==============================================================================
--- trunk/admin/gimp-web-urls (original)
+++ trunk/admin/gimp-web-urls Tue Sep 30 22:32:05 2008
@@ -1,3 +1,7 @@
+["href", "http:gegl", { "href": "http://gegl.org/"}]
+["href", "http:babl", { "href": "http://gegl.org/babl"}]
+["href", "http:gtk", { "href": "http://gtk.org/"}]
+
["href", "http:Package-autoconf", { "href": "http://www.gnu.org/software/autoconf/"}]
["href", "http:Package-automake", { "href": "http://www.gnu.org/software/automake/automake.html"}]
["href", "http:Package-bash", { "href": "http://www.gnu.org/software/bash/bash.html"}]
Modified: trunk/bugs/howtos/bugzilla.htrw
==============================================================================
--- trunk/bugs/howtos/bugzilla.htrw (original)
+++ trunk/bugs/howtos/bugzilla.htrw Tue Sep 30 22:32:05 2008
@@ -6,167 +6,198 @@
<h2>or How To Report GIMP Bugs</h2>
<p>
- If you find a bug or think you find a bug, it is very important to report it.
- If the developers don't know it is broken (or might be broken), they can't
- fix it. So there you are at your computer trying to do something with GIMP
- and it freaks out at you. It can be a frightening experience at times.
+ If you find a bug or think you find a bug, it is very important to
+ report it. If the developers don't know it is broken (or might be
+ broken), they can't fix it. So there you are at your computer trying
+ to do something with GIMP and it freaks out at you. It can be a
+ frightening experience at times.
</p>
<h3>First, Next, Third</h3>
<p>
- First: Get out a piece of paper or open a text file and scribble down
- everything you can remember about what you were doing when it happened. Also
- write down the exact wording of any error messages you received.
-</p>
-<p>
- Next: Go away and yell and scream and do whatever you need to do to relax
- again. Your next step will be to brave Bugzilla, the GNOME bug tracker. It is
- used to track bug reports and requests for enhancements for GIMP and <span
- class="help" title="the GIMP ToolKit">GTK+</span> (see also <a
- href="/bugs/why_bugzilla.html">why we are using Bugzilla</a>).
-</p>
-<p>
- Third: Check to see if your bug has been reported yet. Go to the
- <a href="home:gimp-bugzilla_stable_current">Current Bug List</a> to see if
- something that looks like your bug has been reported yet. Don't worry if it
- has, you can still help. See the section: <a href="#enhance">Enhancing Bug Reports</a>.
- If you can't find something that sounds like your bug there, you will need to
+ First: Get out a piece of paper or open a text file and scribble
+ down everything you can remember about what you were doing when it
+ happened. Also write down the exact wording of any error messages
+ you received.
+</p>
+<p>
+ Next: Go away and yell and scream and do whatever you need to do to
+ relax again. Your next step will be to brave Bugzilla, the GNOME bug
+ tracker. It is used to track bug reports and requests for
+ enhancements for GIMP and <span class="help" title="the GIMP
+ ToolKit">GTK+</span> (see also <a href="/bugs/why_bugzilla.html">why
+ we are using Bugzilla</a>).
+</p>
+<p>
+ Third: Check to see if your bug has been reported yet. Go to the
+ <a href="home:gimp-bugzilla_stable_current">Current Bug List</a> to
+ see if something that looks like your bug has been reported
+ yet. Don't worry if it has, you can still help. See the
+ section: <a href="#enhance">Enhancing Bug Reports</a>. If you can't
+ find something that sounds like your bug there, you will need to
report it.
</p>
<h2>Getting Ready to Report and Reporting a Bug</h2>
<p>
- The goal of the following is to give the developers as much information about
- what goes wrong as possible. This helps them find out what needs to be fixed.
+ The goal of the following is to give the developers as much
+ information about what goes wrong as possible. This helps them find
+ out what needs to be fixed.
</p>
<h3>The Steps</h3>
<ol>
<li>
<p>
- Use <kbd>gimp --version</kbd> or the about dialog to check your GIMP
- version. Next check with <a href="home:gimp">www.gimp.org</a> to see
- what the most recent GIMP release is. If your GIMP is old, update then
- try to to reproduce the bug. Your bug may have been fixed in the most
- recent release. If you are running GIMP from CVS, update your CVS and
- recompile.
+ Use <kbd>gimp --version</kbd> or the about dialog to check your
+ GIMP version. Next check
+ with <a href="home:gimp">www.gimp.org</a> to see what the most
+ recent GIMP release is. If your GIMP is old, update then try to
+ to reproduce the bug. Your bug may have been fixed in the most
+ recent release. If you are running GIMP from CVS, update your
+ CVS and recompile.
</p>
+
</li>
<li>
<p>
- Attempt to reproduce the problem. Go do what you were doing when it
- happened and see if you can do it again.
+ Attempt to reproduce the problem. Go do what you were doing
+ when it happened and see if you can do it again.
</p>
<p>
- If using GIMP for GNU/Linux, start the program from a terminal with the
- command <kbd>gimp</kbd>. Sometimes the program will output error messages
- that can help. This is especially important if GIMP crashes completely
- without warning. After reproducing the bug, copy the error messages from
- your terminal into somewhere where you can save them for the bug report.
- It is better to give too much information than not enough.
- </p>
- <p>
- To narrow down the exact cause of the problem, attempt to reproduce it
- in other ways. Prepare yourself to explain how to reproduce it in your
- bug report. If you are running GIMP in another language, try switching
- your GIMP to English so you can report menu items exactly with the
- English menu item name. It helps. (Developers generally understand
- English) If you cannot reproduce the bug, assume it was some weird
- freak event and don't report it. If it recurs, consult with your
- appropriate <a href="wgo:mail_lists">user mailing list</a>. Perhaps
- someone else can find the key to reproducing it.
+ If using GIMP for GNU/Linux, start the program from a terminal
+ with the command <kbd>gimp</kbd>. Sometimes the program will
+ output error messages that can help. This is especially
+ important if GIMP crashes completely without warning. After
+ reproducing the bug, copy the error messages from your terminal
+ into somewhere where you can save them for the bug report. It
+ is better to give too much information than not enough.
+ </p>
+ <p>
+ To narrow down the exact cause of the problem, attempt to
+ reproduce it in other ways. Prepare yourself to explain how to
+ reproduce it in your bug report. If you are running GIMP in
+ another language, try switching your GIMP to English so you can
+ report menu items exactly with the English menu item name. It
+ helps. (Developers generally understand English) If you cannot
+ reproduce the bug, assume it was some weird freak event and
+ don't report it. If it recurs, consult with your
+ appropriate <a href="wgo:mail_lists">user mailing
+ list</a>. Perhaps someone else can find the key to reproducing
+ it.
</p>
</li>
<li>
<p>
- Prepare to face the horror. Go to <a href="home:gimp-bugzilla">bugzilla.gnome.org</a>.
- If you don't have a login yet, follow the directions to create one. The
- reason to do this and report a bug with your e-mail address is so the
- developers can contact you if they have any questions. That way if we
- miss some useful tidbit of debugging information, they can tell you what
- to do to get it. Log in.
+ Prepare to face the horror. Go
+ to <a href="home:gimp-bugzilla">bugzilla.gnome.org</a>. If you
+ don't have a login yet, follow the directions to create
+ one. The reason to do this and report a bug with your e-mail
+ address is so the developers can contact you if they have any
+ questions. That way if we miss some useful tidbit of debugging
+ information, they can tell you what to do to get it. Log in.
</p>
</li>
<li>
<p>
- Select "Enter a New Bug Report". From the list of products
- provided, select GIMP. This opens the actual entry form.
+ Select "Enter a New Bug Report". From the list of
+ products provided, select GIMP. This opens the actual entry
+ form.
</p>
</li>
<li>
<p>
- Here you have to tell the developers everything about your system, your
- version of GIMP, and your bug. Just do your best to tell them about it.
- A crappy bug report is better than no report at all, but if you write
- down everything you can clearly, you will create a decent bug report.
+ Here you have to tell the developers everything about your
+ system, your version of GIMP, and your bug. Just do your best
+ to tell them about it. A crappy bug report is better than no
+ report at all, but if you write down everything you can
+ clearly, you will create a decent bug report.
</p>
<ol>
<li>
<p>
- Select the "version" that corresponds with the version of GIMP in which you
- found the bug. It is the information you got with <kbd>gimp --version</kbd>.
+ Select the "version" that corresponds with the
+ version of GIMP in which you found the bug. It is the
+ information you got with <kbd>gimp --version</kbd>.
</p>
</li>
<li>
<p>
- Select the appropriate "component". If you don't know what component
- it is, submit the bug under General. Descriptions of the components
+ Select the appropriate "component". If you don't
+ know what component it is, submit the bug under
+ General. Descriptions of the components
are <a href="home:gimp-bugzilla_components">available</a>.
</p>
</li>
<li>
<p>
- Classify the "severity" of your bug. If the bug causes
- GIMP to crash totally or do other really ucky things so you can't
- use the program at all, classify it as critical. If it completely
- disables some part of GIMP, classify it as major (for example, keeps
- you from using a tool). Most bugs are "normal". If you don't know
- what severity to use, call it "normal". Trivial bugs are
- annoying but don't really keep you from using the program. Cosmetic
- bugs are things like spelling errors or UI (User Interface,
- "the look and feel") issues. If you are requesting a new
- feature, choose "enhancement". Don't worry if you choose
- the wrong severity. The people getting your bug report will adjust
- it. Don't mark it higher than it really is just to get their
- attention.
+ Classify the "severity" of your bug. If the bug
+ causes GIMP to crash totally or do other really ucky things
+ so you can't use the program at all, classify it as
+ critical. If it completely disables some part of GIMP,
+ classify it as major (for example, keeps you from using a
+ tool). Most bugs are "normal". If you don't know
+ what severity to use, call it "normal". Trivial
+ bugs are annoying but don't really keep you from using the
+ program. Cosmetic bugs are things like spelling errors or
+ UI (User Interface, "the look and feel")
+ issues. If you are requesting a new feature, choose
+ "enhancement". Don't worry if you choose the
+ wrong severity. The people getting your bug report will
+ adjust it. Don't mark it higher than it really is just to
+ get their attention.
</p>
</li>
<li>
<p>
- Select your "operating system". <a href="wgo:windows">WinGIMP</a> and
- <a href="wgo:unix">GNU/Linux GIMP</a> bugs are not always identical. It would be
- annoying to get a GNU/Linux GIMP developer trying to reproduce a WinGIMP-specific
- bug. Under "OS Details" (OS, operating system), provide specifics
- about the version of your operating system. For GNU/Linux, provide the distro and
- version. It is also useful to list the desktop or window manager you are using.
- Sometimes a problem is caused by an interaction between the two. It won't always
- be relevant, but it is good to get into the habit of listing it anyway.
+ Select your "operating
+ system". <a href="wgo:windows">WinGIMP</a> and
+ <a href="wgo:unix">GNU/Linux GIMP</a> bugs are not always
+ identical. It would be annoying to get a GNU/Linux GIMP
+ developer trying to reproduce a WinGIMP-specific bug. Under
+ "OS Details" (OS, operating system), provide
+ specifics about the version of your operating system. For
+ GNU/Linux, provide the distro and version. It is also
+ useful to list the desktop or window manager you are using.
+ Sometimes a problem is caused by an interaction between the
+ two. It won't always be relevant, but it is good to get
+ into the habit of listing it anyway.
</p>
</li>
<li>
<p>
- Leave "Assigned to:" blank. Bugzilla will do that automatically. Only worry
- about CC: if you want to send a copy of your bug report to someone else.
+ Leave "Assigned to:" blank. Bugzilla will do that
+ automatically. Only worry about CC: if you want to send a
+ copy of your bug report to someone else.
</p>
</li>
<li>
<p>
- For "Summary", write a brief description of your bug. This summary
- will help other users see if their bug might be like your bug. Write something
- that would help you if you were looking for a bug like yours.
+ For "Summary", write a brief description of your
+ bug. This summary will help other users see if their bug
+ might be like your bug. Write something that would help you
+ if you were looking for a bug like yours.
</p>
</li>
<li>
<p>
- "Description" is the hard part. It is the actual bug report. First
- provide the detailed description of your bug: a brief overview of when it
- happened and exactly what went wrong (including error messages). Next,
- describe step-by-step how to reproduce the bug. Use the exact name of menu
- items. Describe tools, windows, and clicks as precisely as possible. If they
- can't reproduce the bug, it will be very hard for them to fix it. Last, tell
- them anything else you can think of that might be relevant. This could include
- recently installed programs or hardware that might interfere with GIMP.
+ "Description" is the hard part. It is the actual
+ bug report. First provide the detailed description of your
+ bug: a brief overview of when it happened and exactly what
+ went wrong (including error messages). Next, describe
+ step-by-step how to reproduce the bug. Use the exact name of
+ menu items. Describe tools, windows, and clicks as precisely
+ as possible. If they can't reproduce the bug, it will be
+ very hard for them to fix it. Last, tell them anything else
+ you can think of that might be relevant. This could include
+ recently installed programs or hardware that might interfere
+ with GIMP.
</p>
+ <p>
+ Finally, please add the output you get from
+ running <kbd>gimp --version --verbose</kbd> to your bug
+ report.
+ </p>
</li>
</ol>
</li>
@@ -174,42 +205,46 @@
<h2><a name="enhance"></a>Enhancing Bug Reports</h2>
<p>
- If someone has already reported a bug like yours, read the bug report
- carefully. Read through all the additional comments. Make sure every bit of
- information you know about the bug is in there. If your version is different
- or you had a slightly different experience with the bug, add a comment
- providing your information. Check the status of the bug carefully. If it is
- marked "NEEDINFO", see if you can provide the information needed. Do not add
- a "me too" comment unless your comment provides additional information that
- might be helpful for the developer.
-</p>
-<p>
- If you have provided a bug report and later get more information (like a more
- specific error message or fancy stuff like a trace), add a comment to your
- original bug with that information. It is especially important to add a
- comment if you somehow resolve your bug. For example, you update something
- else on your system and the bug no longer appears. In that case, add a comment
- describing what you updated from what version to what version that resolved
- the bug.
+ If someone has already reported a bug like yours, read the bug
+ report carefully. Read through all the additional comments. Make
+ sure every bit of information you know about the bug is in there. If
+ your version is different or you had a slightly different experience
+ with the bug, add a comment providing your information. Check the
+ status of the bug carefully. If it is marked "NEEDINFO",
+ see if you can provide the information needed. Do not add a "me
+ too" comment unless your comment provides additional
+ information that might be helpful for the developer.
+</p>
+<p>
+ If you have provided a bug report and later get more information
+ (like a more specific error message or fancy stuff like a trace),
+ add a comment to your original bug with that information. It is
+ especially important to add a comment if you somehow resolve your
+ bug. For example, you update something else on your system and the
+ bug no longer appears. In that case, add a comment describing what
+ you updated from what version to what version that resolved the bug.
</p>
<h2>The Wait Patiently Part</h2>
<p>
- <cite>Whee!!</cite> You survived! If you managed to get through all this and submit your
- bug report, be happy. Be proud. You will later get e-mails about your bug.
- It might include a request for more information. If you get something that
- says your bug is not a bug, do not be discouraged from reporting in the future.
- Next time it might be. Submitting careful bug reports and providing additional
- information where possible helps make GIMP better. The day will come where you
- submit a bug and later get an e-mail that says your bug is "FIXED"
- or "RESOLVED". Then you will know that some developer out there found
- your bug, reproduced it, and fixed it.
+ <cite>Whee!!</cite> You survived! If you managed to get through all
+ this and submit your bug report, be happy. Be proud. You will later
+ get e-mails about your bug. It might include a request for more
+ information. If you get something that says your bug is not a bug,
+ do not be discouraged from reporting in the future. Next time it
+ might be. Submitting careful bug reports and providing additional
+ information where possible helps make GIMP better. The day will come
+ where you submit a bug and later get an e-mail that says your bug is
+ "FIXED" or "RESOLVED". Then you will know that
+ some developer out there found your bug, reproduced it, and fixed
+ it.
</p>
<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
<div>
<span id="footerleft">
- How To Bugzilla © 2002 <a href="mail:People-Walter_Rebecca_J">Rebecca J. Walter</a>
+ How To Bugzilla
+ © 2002 <a href="mail:People-Walter_Rebecca_J">Rebecca J. Walter</a>
</span>
<span id="footerright">
<a href="mail:People-webmaster">webmaster gimp org</a>
Modified: trunk/downloads/source.xhtml
==============================================================================
--- trunk/downloads/source.xhtml (original)
+++ trunk/downloads/source.xhtml Tue Sep 30 22:32:05 2008
@@ -1,14 +1,14 @@
- <h2>Source for version 2.4 (Stable)</h2>
+ <h2>Source for version 2.6 (Stable)</h2>
<p>GIMP releases available from gimp.org and its
<a href="#mirrors">mirrors</a> contain the source code and have to be
compiled in order to be installed on your system.
</p>
- <p>GIMP 2.4.7 is now available
- at <a href="ftp://ftp.gimp.org/pub/gimp/v2.4/";>ftp://ftp.gimp.org/pub/gimp/v2.4/</a>.
- You may want to read the <a href="/release-notes/gimp-2.4.html">Release
- Notes for GIMP 2.4</a>.
+ <p>GIMP 2.6.0 is now available
+ at <a href="ftp://ftp.gimp.org/pub/gimp/v2.6/";>ftp://ftp.gimp.org/pub/gimp/v2.6/</a>.
+ You may want to read the <a href="/release-notes/gimp-2.6.html">Release
+ Notes for GIMP 2.6</a>.
</p>
<p>To allow you to check the integrity of the tarballs, here are the
@@ -19,41 +19,13 @@
<th>MD5 sum</th>
</tr>
<tr>
- <td>gimp-2.4.0.tar.bz2</td>
- <td><kbd>35fecf14cd5237065aef624b93030d5e</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.1.tar.bz2</td>
- <td><kbd>51edbadd77235837535a6882ad63d8fb</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.2.tar.bz2</td>
- <td><kbd>ebd8902d29753d41c8d51a3efd84d1bf</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.3.tar.bz2</td>
- <td><kbd>958988ac02642e2dfda7ad7d045e2a84</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.4.tar.bz2</td>
- <td><kbd>41d0568581de99f3fd2ecb5babae1f6e</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.5.tar.bz2</td>
- <td><kbd>162e264dc5f0c7e4de8794e78818381f</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.6.tar.bz2</td>
- <td><kbd>a0bd1560f81f15c23ed4c0c6cb9c4b59</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.4.7.tar.bz2</td>
- <td><kbd>8d0e059597d70fbdeb77e6447bae29c4</kbd></td>
+ <td>gimp-2.6.0.tar.bz2</td>
+ <td><kbd>712414b7684e8a21f87599f76faa81af</kbd></td>
</tr>
</table>
</p>
- <p>GAP (the GIMP Animation Package) for GIMP 2.4 is available at
+ <p>GAP (the GIMP Animation Package) for GIMP 2.4 and above is available at
<a href="ftp://ftp.gimp.org/pub/gimp/plug-ins/v2.4/gap";>ftp://ftp.gimp.org/pub/gimp/plug-ins/v2.4/gap</a>.
</p>
@@ -66,8 +38,11 @@
<h2>Development snapshots</h2>
- <p>GIMP 2.5.4 is a snapshot of current development towards GIMP 2.6. The
- source code is available from <a href="ftp://ftp.gimp.org/pub/gimp/v2.5/";>ftp://ftp.gimp.org/pub/gimp/v2.5/</a>. Please make sure you read the <a href="/release-notes/gimp-2.5.html">Release Notes for GIMP 2.5</a>.
+ <p>There are no development releases yet.</p>
+
+<!--
+ <p>GIMP 2.7.0 is a snapshot of current development towards GIMP 2.8. The
+ source code is available from <a href="ftp://ftp.gimp.org/pub/gimp/v2.7/";>ftp://ftp.gimp.org/pub/gimp/v2.7/</a>. Please make sure you read the <a href="/release-notes/gimp-2.7.html">Release Notes for GIMP 2.7</a>.
</p>
<p>To allow you to check the integrity of the tarballs, here are the
@@ -78,24 +53,8 @@
<th>MD5 sum</th>
</tr>
<tr>
- <td>gimp-2.5.0.tar.bz2</td>
- <td><kbd>8ba5d24c700b495e8a9f32743369c925</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.5.1.tar.bz2</td>
- <td><kbd>da2a6ffd8ed5e137d34784ef3fba9a04</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.5.2.tar.bz2</td>
- <td><kbd>98add4a1ca6af2e20f80ae3f5a84a922</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.5.3.tar.bz2</td>
- <td><kbd>35a282a646520ce2a2e01c70a23e79c3</kbd></td>
- </tr>
- <tr>
- <td>gimp-2.5.4.tar.bz2</td>
- <td><kbd>e9fd4b1083b0c01de19ec4c5a52a7c32</kbd></td>
+ <td>gimp-2.7.0.tar.bz2</td>
+ <td><kbd>[ insert checksum here]</kbd></td>
</tr>
</table>
</p>
@@ -104,9 +63,10 @@
at <a href="http://developer.gimp.org/NEWS";>developer.gimp.org</a>.
</p>
+ -->
<h1><a name="mirrors"></a>FTP and Web Mirrors</h1>
<!--#include virtual="/downloads/mirrors.xhtml" -->
<p>If you want to add a new mirror, please <a href="/webmasters.html">contact us</a>.</p>
-
+
Modified: trunk/index.htrw
==============================================================================
--- trunk/index.htrw (original)
+++ trunk/index.htrw Tue Sep 30 22:32:05 2008
@@ -7,15 +7,15 @@
<!--#include virtual="/includes/wgo-page-init.xhtml" -->
<div class="splash">
-<img id="splashbg" alt="GIMP 2.4 Released!" title="GIMP 2.4 Released!"
+<img id="splashbg" alt="GIMP 2.6 Released!" title="GIMP 2.6 Released!"
src="/images/frontsplash.jpg" />
<img id="fadesplash" alt="-" src="/images/fade.png" />
-<img id="splash24overlay" alt="-" src="/images/frontsplash24.png" usemap="#splashmap" />
+<img id="splash24overlay" alt="-" src="/images/frontsplash26.png" usemap="#splashmap" />
</div>
<map name="splashmap" id="splashmap">
<area shape="rect" coords="152,99,288,133" href="/downloads/" alt="download" />
-<area shape="rect" coords="10,99,144,133" href="/release-notes/gimp-2.4.html" alt="release notes" />
+<area shape="rect" coords="10,99,144,133" href="/release-notes/gimp-2.6.html" alt="release notes" />
</map>
Added: trunk/release-notes/gimp-2.6.htrw
==============================================================================
--- (empty file)
+++ trunk/release-notes/gimp-2.6.htrw Tue Sep 30 22:32:05 2008
@@ -0,0 +1,347 @@
+<!--#include virtual="/includes/wgo-xhtml-init.xhtml" -->
+<title>GIMP 2.6 Release Notes</title>
+<!--#include virtual="/includes/wgo-look-feel.xhtml" -->
+<!--#include virtual="/includes/wgo-page-init.xhtml" -->
+
+<div class="splash">
+<img class="splashbg" alt="#"
+src="images/2.4-releasesplash.jpg" width="640" height="200" />
+</div>
+
+
+
+<h1>GIMP 2.6 Release Notes</h1>
+
+
+
+<h2>Introduction</h2>
+
+<p>
+ GIMP 2.6 is an important release from a development point of view.
+ It features changes to the user interface addressing some often
+ received complaints, and a tentative integration of GEGL, the graph
+ based image processing library that will eventually bring high
+ bit-depth and non-destructive editing to GIMP.
+</p>
+
+
+<h2>User Interface</h2>
+
+<h3>Toolbox Menubar Removed</h3>
+<img class="right" src="images/2.6-empty-image-window.png" alt="Empty Image Window screenshot" />
+<p>
+ The toolbox menubar has been removed and merged with the image
+ window menubar. To be able to do this a window called the <i>empty
+ image window</i> has been introduced. It hosts the menubar and keeps
+ the application instance alive when no images are opened. It also
+ acts as a drag and drop target. When opening the first image the
+ empty image window is transformed into a normal image window, and
+ when closing the last image, that window becomes the empty image
+ window.
+</p>
+
+<h3>Toolbox and Docks are Utility windows</h3>
+<p>
+ With the empty image window acting as a natural main window, the
+ default window hints for the Toolbox and Docks have been
+ changed to <i>Utility window</i>. This enables window managers to do
+ a much better job of managing the GIMP windows, including omitting
+ the Toolbox and Docks from the taskbar and ensuring that the Toolbox
+ and Docks always are above image windows.
+</p>
+
+<h3>Ability to Pan Beyond Image Border</h3>
+<img class="right" src="images/2.6-scroll-beyond-border.png" alt="Scroll Beyond Border illustration" />
+<p>
+ It is now possible to pan beyond the image border, making image
+ window navigation much less constrained. It is no longer a problem
+ to use the edge of a brush on the edge of an image while being
+ zoomed in, and one can adapt the canvas to any utility windows
+ covering parts of the image window.
+</p>
+
+<h3>Minor Changes</h3>
+<ul>
+ <li>
+ Renamed Dialogs menu to Windows.
+ </li>
+ <li>
+ Keep a list of recently closed Docks and allow reopening them.
+ </li>
+ <li>
+ Make opening images in already running GIMP instances work better
+ on Windows.
+ </li>
+ <li>
+ You can now enter the image zoom ratio directly in the status bar.
+ </li>
+ <li>
+ Added support for using online help instead of a locally
+ installed GIMP Help package.
+ </li>
+ <li>
+ Make it possible to lock tabs in docks to prevent accidental
+ moving.
+ </li>
+</ul>
+
+
+<h2>Tools, Filters & Plug-ins</h2>
+
+<h3>Improved Free Select Tool</h3>
+<img class="right" src="images/2.6-new-free-select-tool.png" alt="New Free Select Tool in action" />
+<p>
+ The freehand select tool has been enhanced to support polygonal
+ selections. It also allows mixing free hand segments with polygonal
+ segments, editing of existing segments, applying angle-constraints
+ to segments, and of course the normal selection tool operations like
+ add and subtract. Altoghether this ends up making the Free Select
+ Tool a very versatile, powerful and easy-to-use selection tool.
+</p>
+
+<h3>Brush Dynamics</h3>
+<img class="right" src="images/2.6-brush-dynamics.jpg" alt="Brush Dynamics illustration" />
+<p>
+ Brush dynamics let you map different brush parameters, commonly at
+ least size and opacity, to one or more of three input dynamics:
+ pressure, velocity and random. Velocity and random are usable with a
+ mouse. The Ink tool, that supported velocity before, has been
+ overhauled and now handles velocity-dependent painting much better.
+</p>
+<p>
+ Brush dynamics have enabled a new feature in stroking paths. There
+ is now a check box under the "paint tool" option, for emulating
+ brush dynamics if you stroke using a paint tool. What this means is
+ that when your stroke is being painted by GIMP, it tells the brush
+ that its pressure and velocity are varying along the length of the
+ stroke. Pressure starts with zero, ramps up to full pressure and
+ then ramps down again to no pressure. Velocity starts from zero and
+ ramps up to full speed by the end of the stroke.
+</p>
+
+<h3>Minor Changes</h3>
+<ul>
+ <img class="right"
+ src="images/2.6-text-tool-and-rectangle-handles.png"
+ alt="Text Tool bounding box and outside rectangle handles screenshot" />
+ <li>
+ Added a bounding box for the Text Tool that supports automatic
+ wrapping of text within that bounding box.
+ </li>
+ <li>
+ Move handles for rectangle based tools like Crop and Rectangle
+ Select to the outside of the rectangle when the rectangle is
+ narrow.
+ </li>
+ <li>
+ Added motion constraints to the Move Tool.
+ </li>
+ <li>
+ Improved event smoothing for paint tools.
+ </li>
+ <li>
+ Mark the center of rectangles while they are moved, and snap the
+ center to grid and rulers.
+ </li>
+ <li>
+ Enable brush scaling for the Smudge tool.
+ </li>
+ <li>
+ Added ability to save presets in all color tools for color
+ adjustments you use frequently.
+ </li>
+ <li>
+ Allow to transfer settings from <i>Brightness-Contrast</i> to
+ <i>Levels</i>, and from <i>Levels</i> to <i>Curves</i>.
+ </li>
+ <li>
+ Allow changing opacity on transform tool previews.
+ </li>
+ <li>
+ The Screenshot plug-in has been given the ability to capture the
+ mouse cursor (using Xfixes).
+ </li>
+ <li>
+ Display aspect ratio of the Crop and Rectangle Select Tool
+ rectangles in the status bar.
+ </li>
+ <li>
+ Desaturate has been given an on-canvas preview.
+ </li>
+ <li>
+ The Flame plug-in has been extended with 22 new variations.
+ </li>
+ <li>
+ Data file folders like brush folders are searched recursively for
+ files.
+ </li>
+ <li>
+ Replaced the PSD import plug-in with a rewritten version that does
+ what the old version did plus some other things, for example
+ reading of ICC color profiles.
+ </li>
+</ul>
+
+
+<h2>Under the Hood</h2>
+
+<h3>GEGL</h3>
+<p>
+ Important progress towards high bit-depth and non-destructive
+ editing in GIMP has been made. Most color operations in GIMP are now
+ ported to the powerful graph based image processing
+ framework <a href="http:gegl">GEGL</a>, meaning that the
+ interal processing is being done in 32bit floating point linear
+ light RGBA. By default the legacy 8bit code paths are still used,
+ but a curious user can turn on the use of GEGL for the color
+ operations with <i>Colors / Use GEGL</i>.
+</p>
+<img class="right" src="images/2.6-experimental-gegl-tool.png" alt="Experimental GEGL tool screenshot" />
+<p>
+ In addition to porting color operations to GEGL, an
+ experimental <i>GEGL Operation</i> tool has been added, found in
+ the <i>Tools</i> menu. It enables applying GEGL operations to an
+ image and it gives on-canvas previews of the results. The screenshot
+ to the right shows this for a Gaussian Blur.
+</p>
+
+<h3>Minor Changes</h3>
+<ul>
+ <li>
+ Ported many widgets to use the 2D graphics
+ library <a href="http://www.cairographics.org/";>cairo</a> for
+ drawing. See
+ this <a href="images/gimp-curves-tool-2-4-vs-2-6.png">comparison</a>
+ for an example of how much better this looks.
+ </li>
+</ul>
+
+
+<h2>Miscellaneous</h2>
+
+<h3>Plug-in Development</h3>
+<p>
+ There are new things for a plug-in developer to enjoy as well. For
+ example, procedures can now give a detailed error description in
+ case of an error, and the error can be propagated to the user. Here
+ is
+ a <a href="http://developer.gimp.org/api/2.0/libgimp/libgimp-index-new-in-2-6.html";>list
+ of new symbols in GIMP 2.6</a>.
+</p>
+
+<h3>Backwards Compatibility</h3>
+<p>
+ Script-Fu has undergone some clean up and includes several bug
+ fixes. One important bug fix,
+ for <a href="http://bugzilla.gnome.org/show_bug.cgi?id=512105";>bug #508020</a>,
+ prevents a possible crash of Script-Fu. A side effect of the fix
+ will break any script which does not provide an initial value for a
+ variable in the binding portion of a <i>let</i>, <i>let*</i>,
+ or <i>letrec</i> block.
+</p>
+<p>
+ An initial value for a variable is required as stated in
+ the <a href="http://www.schemers.org/Documents/Standards/R5RS/r5rs.pdf";>R5RS
+ Scheme standard document</a>. The initial value can be provided as a
+ simple constant, or as the result of a function call. The following
+ examples will illustrate the problem and show a simple change that
+ will fix a broken script.
+</p>
+<p>
+ This example shows a <i>let*</i> block with incorrect syntax that
+ will no longer work in Script-Fu.
+</p>
+<pre class="code">
+(let* (
+ (four (+ 2 2))
+ (this-is-wrong)
+ )
+</pre>
+<p>
+ This example shows a <i>let*</i> block with the correct syntax.
+</P>
+<pre class="code">
+(let* (
+ (four (+ 2 2))
+ (this-is-correct 0)
+ )
+</pre>
+
+<h3>Known Problems</h3>
+<ul>
+ <li>The <i>Utility window</i> hint is currently only known to work
+ well in the GNOME desktop environment.
+ </li>
+ <li>
+ Using the Text Tool is currently not an optimal experience. Making
+ it work better is a goal for GIMP 2.8.
+ </li>
+ <li>
+ If you build GIMP yourself and don't
+ have <a href="http://en.wikipedia.org/wiki/GVFS";>GVfs</a> support
+ on your platform you need to explicitly
+ pass <kbd>--without-gvfs</kbd> to configure, otherwise opening
+ remote files will not work properly.
+ </li>
+</ul>
+
+<h3>What's Planned</h3>
+<p>
+ For the interested, here is roughly what is planned for GIMP 2.8,
+ the next stable release:
+</p>
+<ul>
+ <li>
+ Merging Google Summer of Code 2008 projects to trunk, namely
+ on-canvas text editing, tagging of GIMP resources and Python
+ scripting enhancements.
+ </li>
+ <li>
+ Continue integration of GEGL.
+ </li>
+ <li>
+ And of course many other improvements...
+ </li>
+</ul>
+
+<h2>GIMP 2.6 Screenshots</h2>
+<div class="plain-screenshots">
+ <a href="../screenshots/gnome-1280x800-fresh-start.jpg" />
+ <img src="../screenshots/gnome-1280x800-fresh-start-thumb.jpg" alt="First GIMP 2.6 startup" />
+ </a>
+ <p>First startup of GIMP 2.6 on a 1280x800 GNOME desktop.</p>
+
+ <a href="../screenshots/on-canvas-preview-of-gaussian-blur-in-2-6.jpg" />
+ <img src="../screenshots/on-canvas-preview-of-gaussian-blur-in-2-6-thumb.jpg" alt="On-canvas Gaussian Blur" />
+ </a>
+ <p>Full screenshot of on-canvas preview of Gaussian Blur using the experimental GEGL Operation tool.</p>
+
+ <a href="../screenshots/alternative-2-6-ui-layout-example-one.jpg" />
+ <img src="../screenshots/alternative-2-6-ui-layout-example-one-thumb.jpg" alt="Alternative UI example" />
+ </a>
+ <p>UI layout example: Tool Options moved out of the toolbox.</p>
+
+ <a href="../screenshots/alternative-2-6-ui-layout-example-two.jpg" />
+ <img src="../screenshots/alternative-2-6-ui-layout-example-two-thumb.jpg" alt="Another alternative UI example" />
+ </a>
+ <p>UI layout example: Using the image window as a background window.</p>
+
+ <a href="../screenshots/2.6-brush-dynamics-example.jpg" />
+ <img src="../screenshots/2.6-brush-dynamics-example-thumb.jpg" alt="Brush Dynamics at use" />
+ </a>
+ <p>Demonstrating the kind of effects the new Brush Dynamics can create.</p>
+</div>
+
+
+<h2>We Hope You Enjoy GIMP 2.6!</h2>
+
+<img class="figure" src="images/2.6-lgm-2008-groupshot.jpg" alt="LGM 2008 shot of the GIMP team" />
+<p>
+ <i>A picture of (mostly) GIMP developers, taken by Garrett LeSage at
+ Libre Graphics Meeting 2008, licenced
+ under <a href="http://creativecommons.org/licenses/by/2.0/deed.en";>CC-By</a></i>
+</p>
+
+
+<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
+<!--#include virtual="/includes/wgo-xhtml-fini.xhtml" -->
Modified: trunk/screenshots/index.htrw
==============================================================================
--- trunk/screenshots/index.htrw (original)
+++ trunk/screenshots/index.htrw Tue Sep 30 22:32:05 2008
@@ -11,27 +11,36 @@
<div class="screenshots">
- <a href="linux_fullscreen.jpg" rel="imagebox-screenshots" title="GIMP running fullscreen, side by side with <a href='http://f-spot.org'>F-Spot</a>."><img src="linux_fullscreen_thumb.jpg" alt="Grid, Fullscreen Screenshot" /></a>
-
- <a href="linux_mixer.jpg" rel="imagebox-screenshots" title="Full control over B/W process using the channel mixer.."><img src="linux_mixer_thumb.jpg" alt="Channel Mixer" /></a>
-
-<a href="linux_dualscreen_griatch_art.jpg" rel="imagebox-screenshots" title="Digital artwork from scratch in GIMP."><img src="linux_dualscreen_griatch_art_thumb.jpg" alt="Digital artwork" /></a>
-
+ <!-- TODO: Make it easy to add new screenshots and add the rest of
+ the screenshots that are in this directory. -->
+ <a href="linux_fullscreen.jpg" rel="imagebox-screenshots" title="GIMP running fullscreen, side by side with <a href='http://f-spot.org'>F-Spot</a>.">
+ <img src="linux_fullscreen_thumb.jpg" alt="Grid, Fullscreen Screenshot" />
+ </a>
+
+ <a href="linux_mixer.jpg" rel="imagebox-screenshots" title="Full control over B/W process using the channel mixer..">
+ <img src="linux_mixer_thumb.jpg" alt="Channel Mixer" />
+ </a>
+
+ <a href="linux_dualscreen_griatch_art.jpg" rel="imagebox-screenshots" title="Digital artwork from scratch in GIMP.">
+ <img src="linux_dualscreen_griatch_art_thumb.jpg" alt="Digital artwork" />
+ </a>
</div>
<h2>Microsoft Windows Screenshots</h2>
<div class="screenshots">
- <a href="windows_crop.jpg" rel="imagebox-screenshots" title="GIMP running on Microsoft Windows features a widget theme mimicking the native environment."><img src="windows_crop_thumb.jpg" alt="GIMP on Microsoft Windows" /></a>
-
+ <a href="windows_crop.jpg" rel="imagebox-screenshots" title="GIMP running on Microsoft Windows features a widget theme mimicking the native environment.">
+ <img src="windows_crop_thumb.jpg" alt="GIMP on Microsoft Windows" />
+ </a>
</div>
<h2>Mac OS X Screenshots</h2>
<div class="screenshots">
- <a href="osx_aperture.jpg" rel="imagebox-screenshots" title="GIMP side by side with Apple Aperture on Mac OS X."><img src="osx_aperture_thumb.jpg" alt="GIMP on the Mac" /></a>
-
+ <a href="osx_aperture.jpg" rel="imagebox-screenshots" title="GIMP side by side with Apple Aperture on Mac OS X.">
+ <img src="osx_aperture_thumb.jpg" alt="GIMP on the Mac" />
+ </a>
</div>
Modified: trunk/source/index.htrw
==============================================================================
--- trunk/source/index.htrw (original)
+++ trunk/source/index.htrw Tue Sep 30 22:32:05 2008
@@ -5,13 +5,13 @@
<h1>GIMP from Source</h1>
<p>
- The official distribution of GIMP is the source code,
- distributed in tar files from the GIMP FTP site and its <a
- href="wgo:downloads-mirrors">mirrors</a>. The same source code can be
- compiled to create binaries for different platforms such as <a
- href="wgo:unix">GNU/Linux</a>, <a href="wgo:windows">Microsoft Windows</a>, <a
- href="wgo:macintosh">Mac OS X</a>, <a href="wgo:unix">Solaris</a> and
- many others.
+ The official distribution of GIMP is the source code, distributed in
+ tar files from the GIMP FTP site and
+ its <a href="wgo:downloads-mirrors">mirrors</a>. The same source
+ code can be compiled to create binaries for different platforms such
+ as <a href="wgo:unix">GNU/Linux</a>, <a href="wgo:windows">Microsoft
+ Windows</a>, <a href="wgo:macintosh">Mac OS
+ X</a>, <a href="wgo:unix">Solaris</a> and many others.
</p>
<ul>
<li><a href="#source">GIMP Source Code</a></li>
@@ -72,7 +72,7 @@
README in the tarballs for details.
</p>
-<h2>Stable version 2.2.x</h2>
+<h2>Stable version 2.6.x</h2>
<table>
<tr>
<th>Package</th>
@@ -83,7 +83,7 @@
</tr>
<tr>
<td>pkg-config</td>
-<td>0.15.0</td>
+<td>0.16.0 or newer</td>
<td>-</td>
<td><a href="http://www.freedesktop.org/software/pkgconfig/";>Download</a></td>
<td>A system for managing library compile/link flags</td>
@@ -91,65 +91,41 @@
<tr>
<td>GTK+</td>
-<td>2.4.4</td>
-<td><a href="ftp://ftp.gimp.org/pub/gtk/";>Download</a></td>
+<td>2.12.1 or newer</td>
+<td><a href="ftp://ftp.gtk.org/pub/gtk/";>Download</a></td>
<td>-</td>
<td>The GIMP toolkit</td>
</tr>
<tr>
<td>GLib</td>
-<td>2.4.5</td>
-<td><a href="ftp://ftp.gtk.org/";>Download</a></td>
+<td>2.16.1 or newer</td>
+<td><a href="ftp://ftp.gtk.org/pub/glib";>Download</a></td>
<td>-</td>
<td>Glib Convenience Library</td>
</tr>
<tr>
<td>Pango</td>
-<td>1.4.0</td>
-<td><a href="ftp://ftp.gtk.org/";>Download</a></td>
+<td>1.18.0 or newer</td>
+<td><a href="ftp://ftp.gtk.org/pub/pango";>Download</a></td>
<td>-</td>
<td>Text layout engine</td>
</tr>
<tr>
-<td>ATK</td>
-<td>1.6.1</td>
-<td><a href="ftp://ftp.gtk.org/pub/gtk/v2.4/";>Download</a></td>
-<td>-</td>
-<td>Accessibility Toolkit</td>
-</tr>
-
-<tr>
-<td>FreeType2</td>
-<td>2.1.7</td>
-<td>-</td>
-<td><a href="http://www.freetype.org/";>Download</a></td>
-<td colspan="2">Font rendering</td>
-</tr>
-
-<tr>
<td>Fontconfig</td>
-<td>2.2.2</td>
+<td>2.2.0 or newer</td>
<td>-</td>
<td><a href="http://freedesktop.org/fontconfig/release/";>Download</a></td>
<td>Font Configuration</td>
</tr>
-<tr>
-<td>libart2</td>
-<td>2.x</td>
-<td><a href="ftp://ftp.gnome.org/pub/gnome/sources/libart_lgpl/";>Download</a></td>
-<td>-</td>
-<td>Vector rendering
-</td></tr></table>
-
<h1><a name="gimp_from_cvs">GIMP from Subversion</a></h1>
<p>
- We only recently migrated from CVS to Subversion. Due to this change, the
- following HOWTOs are somewhat outdated. We are looking for volunteers to
- update them.
+ At some point in the source code was migrated from CVS to
+ Subversion. Due to this change, the following HOWTOs are somewhat
+ outdated. We are looking for volunteers to update them.
</p>
<ul>
<li><a href="wgo:source-howtos-stable_cvs_get">Get The Stable GIMP from CVS</a></li>
@@ -176,7 +152,6 @@
<table>
<tr>
<th>Package</th>
- <th>Version</th>
<th>FTP</th>
<th>HTTP</th>
<th>Description</th>
@@ -184,17 +159,7 @@
</tr>
<tr>
-<td>gimp-print</td>
-<td>>= 4.2.6</td>
-<td>-</td>
-<td><a href="http://gimp-print.sourceforge.net";>Download</a></td>
-<td>Gimp-print</td>
-<td>Optional (explicit disable)</td>
-</tr>
-
-<tr>
<td>aalib</td>
-<td>>= 1.4</td>
<td>-</td>
<td><a href="http://aa-project.sourceforge.net/aalib/";>Download</a></td>
<td>ASCII art library</td>
@@ -202,7 +167,6 @@
<tr>
<td>libexif</td>
-<td>>= 0.5.12</td>
<td>-</td>
<td><a href="http://sourceforge.net/projects/libexif";>Download</a></td>
<td>EXIF tag support for JPEGs</td>
@@ -211,7 +175,6 @@
<tr>
<td>libjpeg</td>
-<td>>= v6b</td>
<td><a href="ftp://ftp.uu.net/graphics/jpeg/";>Download</a></td>
<td>-</td>
<td>JPEG support</td>
@@ -220,7 +183,6 @@
<tr>
<td>libpng</td>
-<td>>= 1.2.5</td>
<td><a href="ftp://ftp.gimp.org/pub/gimp/libs/";>Download</a></td>
<td><a href="http://www.libpng.org/";>Download</a></td>
<td>PNG support</td>
@@ -229,7 +191,6 @@
<tr>
<td>libtiff</td>
-<td>>= 3.5.7</td>
<td><a href="ftp://ftp.gimp.org/pub/gimp/libs/";>Download</a></td>
<td><a href="http://www.remotesensing.org/libtiff/";>Download</a></td>
<td>TIFF support</td>
@@ -238,7 +199,6 @@
<tr>
<td>libmng</td>
-<td>>= 1.0.5</td>
<td>-</td>
<td><a href="http://www.libmng.com/";>Download</a></td>
<td>MNG support</td>
@@ -247,7 +207,6 @@
<tr>
<td>libxpm</td>
-<td>>= 4.3.0</td>
<td><a href="ftp://ftp.x.org/contrib/libraries/";>Download</a></td>
<td><a href="http://koala.ilog.fr/ftp/pub/xpm/";>Download</a></td>
<td>XPM support</td>
@@ -256,7 +215,6 @@
<tr>
<td>librsvg</td>
-<td>>= 2.2</td>
<td><a href="ftp://ftp.gnome.org/mirror/gnome.org/sources/librsvg/";>Download</a></td>
<td><a href="http://librsvg.sourceforge.net/";>Download</a></td>
<td>Scalable Vector Graphics</td>
@@ -265,7 +223,6 @@
<tr>
<td>libwmf</td>
-<td>>= 0.2.8</td>
<td>-</td>
<td><a href="http://wvware.sourceforge.net/libwmf.html";>Download</a></td>
<td>Library to convert wmf files</td>
@@ -273,8 +230,15 @@
</tr>
<tr>
+<td>webkit</td>
+<td>-</td>
+<td><a href="http://live.gnome.org/WebKitGtk";>Download</a></td>
+<td>HTML renderer and web content engine</td>
+<td>Optional (Help Browser won't be built)</td>
+</tr>
+
+<tr>
<td>zlib</td>
-<td>>= 1.1.4</td>
<td><a href="ftp://ftp.gimp.org/pub/gimp/libs/";>Download</a></td>
<td><a href="http://www.gzip.org/zlib/";>Download</a></td>
<td>Compression routines</td>
@@ -283,21 +247,13 @@
<tr>
<td>Python</td>
-<td>>= 2.2.0</td>
<td><a href="ftp://ftp.python.org/pub/python/";>Download</a></td>
<td><a href="http://www.python.org/";>Download</a></td>
<td>Python support</td>
<td>Optional</td>
</tr>
-<tr>
-<td>Perl</td>
-<td>>= 5.8</td>
-<td><a href="ftp://ftp.funet.fi/pub/CPAN/src/";>Download</a></td>
-<td><a href="http://ftp.funet.fi/pub/CPAN/src/";>Download</a></td>
-<td>Perl support</td>
-<td>Optional
-</td></tr></table>
+</table>
<!--#include virtual="/includes/wgo-page-fini.xhtml" -->
<!--#include virtual="/includes/wgo-xhtml-fini.xhtml" -->
Modified: trunk/style/wgo.css
==============================================================================
--- trunk/style/wgo.css (original)
+++ trunk/style/wgo.css Tue Sep 30 22:32:05 2008
@@ -368,6 +368,33 @@
margin-right: 40px;
}
+div.plain-screenshots {
+ margin-left: 3em;
+ margin-right: 1em;
+ margin-bottom: 2em;
+}
+
+div.plain-screenshots p {
+ margin: 0;
+ margin-bottom: 1.5em;
+ padding: 0;
+ max-width: 380px;
+}
+
+div.plain-screenshots a {
+ border: 0px;
+}
+
+div.plain-screenshots img {
+ margin: 2px;
+}
+
+div.plain-screenshots img:hover {
+ margin: 0;
+ border: 2px solid #f57900;
+ padding: 0px;
+}
+
.screenshots, div.splashes {
margin-left: 3em;
margin-right: 1em;
Modified: trunk/unix/fonts.htrw
==============================================================================
--- trunk/unix/fonts.htrw (original)
+++ trunk/unix/fonts.htrw Tue Sep 30 22:32:05 2008
@@ -48,7 +48,7 @@
possible, GIMP 2.x also looks for fonts in the GIMP specific font
search path that can be configured in your <tt>gimprc</tt> or from the
<i>Preferences Dialog</i>. So, in order to install fonts to be used
-with GIMP, you can just copy them to <tt>~/.gimp-2.4/fonts</tt>, press
+with GIMP, you can just copy them to <tt>~/.gimp-2.6/fonts</tt>, press
the <i>Refresh</i> button in the <i>Fonts</i> dialog and start using
them.</p>
Modified: trunk/unix/index.htrw
==============================================================================
--- trunk/unix/index.htrw (original)
+++ trunk/unix/index.htrw Tue Sep 30 22:32:05 2008
@@ -12,7 +12,7 @@
www.gimp.org, you can get binaries for various flavors of UNIX.</p>
<p>At the moment we know about the following binary packages for GIMP
-2.2 or 2.4 on UNIX. These binaries are provided by GIMP users. We did
+2.4 or 2.6 on UNIX. These binaries are provided by GIMP users. We did
not test them; use at your own risk.
<ul>
@@ -55,7 +55,7 @@
</ul>
</p>
-<p>If you cannot find a pre-compiled package of GIMP 2.4 for your
+<p>If you cannot find a pre-compiled package of GIMP 2.6 for your
system, you can <a href="wgo:source">build and install GIMP from the
source code</a>. This is not that hard, so don't be afraid and give
it a try.</p>
@@ -73,23 +73,26 @@
the following is a list of what you will need to run GIMP on your
system:</p>
-<p>For the stable version (2.4):</p>
+<p>For the stable version (2.6):</p>
<ul>
<li>
- <b>GTK+ 2.10.13</b> or better (Gimp Toolkit).
+ <b>GLib 2.16.1</b> or better.
</li>
<li>
- <b>GLib 2.12.3</b> or better.
+ <b><a href="http:gtk">GTK+</a> 2.12.1</b> or better.
</li>
<li>
- <b>PangoFT2</b> 1.12.2 or better. PangoFT2 is a Pango backend that uses <b>FreeType2</b>.
+ <b><a href="http:babl">babl</a> 0.0.22</b> or better.
</li>
<li>
- <b>Fontconfig 2.2.0</b> or better.
+ <b><a href="http:gegl">GEGL</a> 0.0.18</b> or better.
+ </li>
+ <li>
+ <b>PangoFT2</b> 1.18.0 or better. PangoFT2 is a Pango backend that uses <b>FreeType2</b>.
</li>
<li>
- <b>libart2</b>
+ <b>Fontconfig 2.2.0</b> or better.
</li>
</ul>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
