<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_02_09_027217</id>
	<title>GIMP 2.8 Will Sport a Redesigned UI</title>
	<author>kdawson</author>
	<datestamp>1265721480000</datestamp>
	<htmltext><a href="mailto:chris@swiedler.org" rel="nofollow">ceswiedler</a> writes <i>"Ars Technica's Ryan Paul <a href="http://arstechnica.com/open-source/reviews/2010/02/hands-on-new-single-window-mode-makes-gimp-less-gimpy.ars">previews the upcoming release of the GIMP</a>. It will include a single-window mode where the user can dock toolbar windows and switch between images via tabs. There are other improvements as well, including docking support in multi-window mode and improvements to the text tool."</i> To get this early preview, Paul compiled version 2.7.1 from the active development branch, along with its dependencies.</htmltext>
<tokenext>ceswiedler writes " Ars Technica 's Ryan Paul previews the upcoming release of the GIMP .
It will include a single-window mode where the user can dock toolbar windows and switch between images via tabs .
There are other improvements as well , including docking support in multi-window mode and improvements to the text tool .
" To get this early preview , Paul compiled version 2.7.1 from the active development branch , along with its dependencies .</tokentext>
<sentencetext>ceswiedler writes "Ars Technica's Ryan Paul previews the upcoming release of the GIMP.
It will include a single-window mode where the user can dock toolbar windows and switch between images via tabs.
There are other improvements as well, including docking support in multi-window mode and improvements to the text tool.
" To get this early preview, Paul compiled version 2.7.1 from the active development branch, along with its dependencies.</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072106</id>
	<title>Re:Forget the UI, change the name</title>
	<author>domatic</author>
	<datestamp>1265731380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>Let me make some suggestions then:</p><p>Professional Image Manipulation Program<br>Streamlined Image Manipulation Program<br>Windowed Image Manipulation Program<br>Lightspeed Image Manipulation Program</p><p>I would think all the pros would just leap at the change to PIMP their graphics.</p></htmltext>
<tokenext>Let me make some suggestions then : Professional Image Manipulation ProgramStreamlined Image Manipulation ProgramWindowed Image Manipulation ProgramLightspeed Image Manipulation ProgramI would think all the pros would just leap at the change to PIMP their graphics .</tokentext>
<sentencetext>Let me make some suggestions then:Professional Image Manipulation ProgramStreamlined Image Manipulation ProgramWindowed Image Manipulation ProgramLightspeed Image Manipulation ProgramI would think all the pros would just leap at the change to PIMP their graphics.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072316</id>
	<title>w00t! Now, shortcuts</title>
	<author>Anonymous</author>
	<datestamp>1265732400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Now if they provide an option to enable photoshop keyboard shortcuts, it would be uberw00t.</p></htmltext>
<tokenext>Now if they provide an option to enable photoshop keyboard shortcuts , it would be uberw00t .</tokentext>
<sentencetext>Now if they provide an option to enable photoshop keyboard shortcuts, it would be uberw00t.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073396</id>
	<title>New Interface, but Feature Lacking</title>
	<author>bigal123</author>
	<datestamp>1265736660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The new interface will have pros and cons but what is really needed are more image editing/management features.

There is still no IPTC and EXIF support viewing editing and if I remember IPTC data is actually stripped out.

8 Bit Color Support is too low and CMYK is a must i know these will come with future GEGL improvements, but still.

None of these are on the road map for 2.8.

I don't even do that much photo work and have hit the wall so I am sure there are others out there that do much more than I that have even bigger feature needs.</htmltext>
<tokenext>The new interface will have pros and cons but what is really needed are more image editing/management features .
There is still no IPTC and EXIF support viewing editing and if I remember IPTC data is actually stripped out .
8 Bit Color Support is too low and CMYK is a must i know these will come with future GEGL improvements , but still .
None of these are on the road map for 2.8 .
I do n't even do that much photo work and have hit the wall so I am sure there are others out there that do much more than I that have even bigger feature needs .</tokentext>
<sentencetext>The new interface will have pros and cons but what is really needed are more image editing/management features.
There is still no IPTC and EXIF support viewing editing and if I remember IPTC data is actually stripped out.
8 Bit Color Support is too low and CMYK is a must i know these will come with future GEGL improvements, but still.
None of these are on the road map for 2.8.
I don't even do that much photo work and have hit the wall so I am sure there are others out there that do much more than I that have even bigger feature needs.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074640</id>
	<title>Re:I love Gimp... but not on OS X</title>
	<author>Anonymous</author>
	<datestamp>1265741160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Don't forget the bugginess. It is the buggiest software I've ever used under any platform.</p><p>As you said, the GIMP UI under OS X is counter-intuitive. For example, if I'm renaming a layer and I switch over to Blender to check what name I should give to the layer, the text in the text field is highlited and it stays highlighted. When I switch back to GIMP, however, and type something, does it change the text? No, but the text is still highlighted. The UI breaks every (well, most) rules of OS X user interface design.</p></htmltext>
<tokenext>Do n't forget the bugginess .
It is the buggiest software I 've ever used under any platform.As you said , the GIMP UI under OS X is counter-intuitive .
For example , if I 'm renaming a layer and I switch over to Blender to check what name I should give to the layer , the text in the text field is highlited and it stays highlighted .
When I switch back to GIMP , however , and type something , does it change the text ?
No , but the text is still highlighted .
The UI breaks every ( well , most ) rules of OS X user interface design .</tokentext>
<sentencetext>Don't forget the bugginess.
It is the buggiest software I've ever used under any platform.As you said, the GIMP UI under OS X is counter-intuitive.
For example, if I'm renaming a layer and I switch over to Blender to check what name I should give to the layer, the text in the text field is highlited and it stays highlighted.
When I switch back to GIMP, however, and type something, does it change the text?
No, but the text is still highlighted.
The UI breaks every (well, most) rules of OS X user interface design.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162</id>
	<title>I love Gimp... but not on OS X</title>
	<author>cerberusss</author>
	<datestamp>1265726220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I love Gimp and have used it for many years for conversions, touch-ups of pictures, website graphics etc. When I switched to a MacBook, I was pleased to see the OS X version. But it doesn't really work, I'm afraid.</p><p>Besides the obvious graphical shortcomings (doesn't use Cocoa), you also have to click in each window first to activate it, then you can select your tool, activate your layer or what have you. This is so non-intuitive, and so not part of the usual routines, that I just don't use Gimp anymore on OS X.</p><p>If the new single-window mode is available and ported to OS X, I'd definitely give it a new try.</p></htmltext>
<tokenext>I love Gimp and have used it for many years for conversions , touch-ups of pictures , website graphics etc .
When I switched to a MacBook , I was pleased to see the OS X version .
But it does n't really work , I 'm afraid.Besides the obvious graphical shortcomings ( does n't use Cocoa ) , you also have to click in each window first to activate it , then you can select your tool , activate your layer or what have you .
This is so non-intuitive , and so not part of the usual routines , that I just do n't use Gimp anymore on OS X.If the new single-window mode is available and ported to OS X , I 'd definitely give it a new try .</tokentext>
<sentencetext>I love Gimp and have used it for many years for conversions, touch-ups of pictures, website graphics etc.
When I switched to a MacBook, I was pleased to see the OS X version.
But it doesn't really work, I'm afraid.Besides the obvious graphical shortcomings (doesn't use Cocoa), you also have to click in each window first to activate it, then you can select your tool, activate your layer or what have you.
This is so non-intuitive, and so not part of the usual routines, that I just don't use Gimp anymore on OS X.If the new single-window mode is available and ported to OS X, I'd definitely give it a new try.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</id>
	<title>Much more important features missing</title>
	<author>syousef</author>
	<datestamp>1265728260000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>GIMP is always compared to photoshop. There are some key features missing in GIMP that do not allow serious artists to move to it from Photoshop. Three of these are adjustment layers (which GEGL is suppose to eventually bring about, but it's been a long wait), proper 16 and 32 bit image editing and LAB and CYMK modes. (GIMP only does RGB). I'm greatful for GIMP and thankful for the developer's efforts but I'd rather they focus on these things than dicking around with windowing. The truth is once you get use to it, GIMP's windowing isn't THAT bad.</p></htmltext>
<tokenext>GIMP is always compared to photoshop .
There are some key features missing in GIMP that do not allow serious artists to move to it from Photoshop .
Three of these are adjustment layers ( which GEGL is suppose to eventually bring about , but it 's been a long wait ) , proper 16 and 32 bit image editing and LAB and CYMK modes .
( GIMP only does RGB ) .
I 'm greatful for GIMP and thankful for the developer 's efforts but I 'd rather they focus on these things than dicking around with windowing .
The truth is once you get use to it , GIMP 's windowing is n't THAT bad .</tokentext>
<sentencetext>GIMP is always compared to photoshop.
There are some key features missing in GIMP that do not allow serious artists to move to it from Photoshop.
Three of these are adjustment layers (which GEGL is suppose to eventually bring about, but it's been a long wait), proper 16 and 32 bit image editing and LAB and CYMK modes.
(GIMP only does RGB).
I'm greatful for GIMP and thankful for the developer's efforts but I'd rather they focus on these things than dicking around with windowing.
The truth is once you get use to it, GIMP's windowing isn't THAT bad.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</id>
	<title>Forget the UI, change the name</title>
	<author>Culture20</author>
	<datestamp>1265729520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Yes, this is *that* post.  Just trying to keep it fresh in your mind.  I use the GNU Image Manipulation Program all the time, and internally, I call it GIMP, and amongst friends in the know, I call it GIMP, but amongst people who are new to FOSS, I usually make an effort to use the full name.  Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days, or worse, they've never seen Pulp Fiction because they would be offended by it, but they still know "The GIMP" through cultural allusions to that character, and thus are offended by any reference to GIMP.<br> <br>
Hell, I'd even take GIMPY (the GNU Image Manipulation Program for You), since that evokes a different, albeit still negative, emotional response.<br> <br>
The best suggestion I've heard is just drop GNU or make GNU separate from the acronym: IMP, GNU IMP.</htmltext>
<tokenext>Yes , this is * that * post .
Just trying to keep it fresh in your mind .
I use the GNU Image Manipulation Program all the time , and internally , I call it GIMP , and amongst friends in the know , I call it GIMP , but amongst people who are new to FOSS , I usually make an effort to use the full name .
Every once in a while , I forget , and most people associate GIMP or " The GIMP " with Pulp Fiction these days , or worse , they 've never seen Pulp Fiction because they would be offended by it , but they still know " The GIMP " through cultural allusions to that character , and thus are offended by any reference to GIMP .
Hell , I 'd even take GIMPY ( the GNU Image Manipulation Program for You ) , since that evokes a different , albeit still negative , emotional response .
The best suggestion I 've heard is just drop GNU or make GNU separate from the acronym : IMP , GNU IMP .</tokentext>
<sentencetext>Yes, this is *that* post.
Just trying to keep it fresh in your mind.
I use the GNU Image Manipulation Program all the time, and internally, I call it GIMP, and amongst friends in the know, I call it GIMP, but amongst people who are new to FOSS, I usually make an effort to use the full name.
Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days, or worse, they've never seen Pulp Fiction because they would be offended by it, but they still know "The GIMP" through cultural allusions to that character, and thus are offended by any reference to GIMP.
Hell, I'd even take GIMPY (the GNU Image Manipulation Program for You), since that evokes a different, albeit still negative, emotional response.
The best suggestion I've heard is just drop GNU or make GNU separate from the acronym: IMP, GNU IMP.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071228</id>
	<title>re?</title>
	<author>Anonymous</author>
	<datestamp>1265726580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Correct me if I'm wrong, but the prefix "re" usually means doing something again, which in turn requires that it was actually done in the first place.</p></htmltext>
<tokenext>Correct me if I 'm wrong , but the prefix " re " usually means doing something again , which in turn requires that it was actually done in the first place .</tokentext>
<sentencetext>Correct me if I'm wrong, but the prefix "re" usually means doing something again, which in turn requires that it was actually done in the first place.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072698</id>
	<title>Re:Much more important features missing</title>
	<author>Leuf</author>
	<datestamp>1265734080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'll preface this by saying I'm using a windows version so I may be missing some things, but the only thing that really bothers me about GIMP is that it doesn't remember settings between sessions and many of the defaults are just stupid.  Resize canvas is a prime example.  Default is to maintain aspect ratio and not resize all layers.  Unsharp mask doesn't remember it's settings and is buried deep in the menus, there's a big time waster.  And unlike a lot of open source software it doesn't give you access to change those defaults.</htmltext>
<tokenext>I 'll preface this by saying I 'm using a windows version so I may be missing some things , but the only thing that really bothers me about GIMP is that it does n't remember settings between sessions and many of the defaults are just stupid .
Resize canvas is a prime example .
Default is to maintain aspect ratio and not resize all layers .
Unsharp mask does n't remember it 's settings and is buried deep in the menus , there 's a big time waster .
And unlike a lot of open source software it does n't give you access to change those defaults .</tokentext>
<sentencetext>I'll preface this by saying I'm using a windows version so I may be missing some things, but the only thing that really bothers me about GIMP is that it doesn't remember settings between sessions and many of the defaults are just stupid.
Resize canvas is a prime example.
Default is to maintain aspect ratio and not resize all layers.
Unsharp mask doesn't remember it's settings and is buried deep in the menus, there's a big time waster.
And unlike a lot of open source software it doesn't give you access to change those defaults.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071616</id>
	<title>Re:I love Gimp... but not on OS X</title>
	<author>iangoldby</author>
	<datestamp>1265728620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>you also have to click in each window first to activate it, then you can select your tool...</p></div></blockquote><p>You need to activate click-through in the X11 server. It is a pain that this isn't the default, but now that you know, you'll find GIMP <em>so</em> much nicer on OS X.</p><p>From <a href="http://darwingimp.sourceforge.net/guides/install\_leopard/" title="sourceforge.net">http://darwingimp.sourceforge.net/guides/install\_leopard/</a> [sourceforge.net]:</p><blockquote><div><p>There's one small operation we can now perform to make it easier to use (note that this is not necessary). Doing this will save you many unnecessary double-clicks during editing by not requiring you to activate GIMP windows before you can click on them. While Gimp and X11 are closed, open<nobr> <wbr></nobr>/Applications/Utilities/Terminal, and paste the following command in it and press enter:<br># If you installed the XQuartz packages :</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; defaults write org.x.X11 wm\_click\_through -bool true</p><p># If you installed the Apple X11 packages :</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; defaults write com.apple.X11 wm\_click\_through -bool true</p></div></blockquote></div>
	</htmltext>
<tokenext>you also have to click in each window first to activate it , then you can select your tool...You need to activate click-through in the X11 server .
It is a pain that this is n't the default , but now that you know , you 'll find GIMP so much nicer on OS X.From http : //darwingimp.sourceforge.net/guides/install \ _leopard/ [ sourceforge.net ] : There 's one small operation we can now perform to make it easier to use ( note that this is not necessary ) .
Doing this will save you many unnecessary double-clicks during editing by not requiring you to activate GIMP windows before you can click on them .
While Gimp and X11 are closed , open /Applications/Utilities/Terminal , and paste the following command in it and press enter : # If you installed the XQuartz packages :         defaults write org.x.X11 wm \ _click \ _through -bool true # If you installed the Apple X11 packages :         defaults write com.apple.X11 wm \ _click \ _through -bool true</tokentext>
<sentencetext>you also have to click in each window first to activate it, then you can select your tool...You need to activate click-through in the X11 server.
It is a pain that this isn't the default, but now that you know, you'll find GIMP so much nicer on OS X.From http://darwingimp.sourceforge.net/guides/install\_leopard/ [sourceforge.net]:There's one small operation we can now perform to make it easier to use (note that this is not necessary).
Doing this will save you many unnecessary double-clicks during editing by not requiring you to activate GIMP windows before you can click on them.
While Gimp and X11 are closed, open /Applications/Utilities/Terminal, and paste the following command in it and press enter:# If you installed the XQuartz packages :
        defaults write org.x.X11 wm\_click\_through -bool true# If you installed the Apple X11 packages :
        defaults write com.apple.X11 wm\_click\_through -bool true
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074320</id>
	<title>Re:Much more important features missing</title>
	<author>UnknownSoldier</author>
	<datestamp>1265739840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Also missing:</p><p>* Nested layer groups<br>* Support for ALL the blend modes</p></htmltext>
<tokenext>Also missing : * Nested layer groups * Support for ALL the blend modes</tokentext>
<sentencetext>Also missing:* Nested layer groups* Support for ALL the blend modes</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071148</id>
	<title>2 things</title>
	<author>Jorl17</author>
	<datestamp>1265726160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>First, and most important: I told you so! Really, I told you that you *had* to include a Single Document Interface while keeping the original Multi Window Interface!
<br>
<br>
Second: Seems like something pretty amazing; I've used it and prefered it over Photoshop for 3 years now, but I'm no artist. These changes make me think of sentences such as: "Oh my, oh my!! With this, I can draw letters in the sky!".</htmltext>
<tokenext>First , and most important : I told you so !
Really , I told you that you * had * to include a Single Document Interface while keeping the original Multi Window Interface !
Second : Seems like something pretty amazing ; I 've used it and prefered it over Photoshop for 3 years now , but I 'm no artist .
These changes make me think of sentences such as : " Oh my , oh my ! !
With this , I can draw letters in the sky !
" .</tokentext>
<sentencetext>First, and most important: I told you so!
Really, I told you that you *had* to include a Single Document Interface while keeping the original Multi Window Interface!
Second: Seems like something pretty amazing; I've used it and prefered it over Photoshop for 3 years now, but I'm no artist.
These changes make me think of sentences such as: "Oh my, oh my!!
With this, I can draw letters in the sky!
".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071390</id>
	<title>Single Window</title>
	<author>CFBMoo1</author>
	<datestamp>1265727600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I like it, it reminds me of Paint.NET and looks really good. The multiple windows didn't make things overly easy to manage. I like having everything in one spot and the little thumbnail ribbon at the top with open images makes it easier to go between different files. Very nicely done!</htmltext>
<tokenext>I like it , it reminds me of Paint.NET and looks really good .
The multiple windows did n't make things overly easy to manage .
I like having everything in one spot and the little thumbnail ribbon at the top with open images makes it easier to go between different files .
Very nicely done !</tokentext>
<sentencetext>I like it, it reminds me of Paint.NET and looks really good.
The multiple windows didn't make things overly easy to manage.
I like having everything in one spot and the little thumbnail ribbon at the top with open images makes it easier to go between different files.
Very nicely done!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31079360</id>
	<title>I'm glad</title>
	<author>SheeEttin</author>
	<datestamp>1265715840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm very glad they finally made this change. Working with three separate windows was hell. I'm no professional, but I'm usually working from a reference image. With one monitor on 1280x1024, I like to have the toolbox and layers/undo/brushes windows narrow, on either side, leaving the image window in the center, maximized, zoomed in as necessary.
Because of this, I'm always alt-tabbing back and forth between the reference and the editor. Eventually, I'll open another window or something, and the window order will get all messed up, or the image window will come forward without the toolbox, or the toolbox will just disappear from the KDE panel and I'll have to minimize all my windows to find it again.</htmltext>
<tokenext>I 'm very glad they finally made this change .
Working with three separate windows was hell .
I 'm no professional , but I 'm usually working from a reference image .
With one monitor on 1280x1024 , I like to have the toolbox and layers/undo/brushes windows narrow , on either side , leaving the image window in the center , maximized , zoomed in as necessary .
Because of this , I 'm always alt-tabbing back and forth between the reference and the editor .
Eventually , I 'll open another window or something , and the window order will get all messed up , or the image window will come forward without the toolbox , or the toolbox will just disappear from the KDE panel and I 'll have to minimize all my windows to find it again .</tokentext>
<sentencetext>I'm very glad they finally made this change.
Working with three separate windows was hell.
I'm no professional, but I'm usually working from a reference image.
With one monitor on 1280x1024, I like to have the toolbox and layers/undo/brushes windows narrow, on either side, leaving the image window in the center, maximized, zoomed in as necessary.
Because of this, I'm always alt-tabbing back and forth between the reference and the editor.
Eventually, I'll open another window or something, and the window order will get all messed up, or the image window will come forward without the toolbox, or the toolbox will just disappear from the KDE panel and I'll have to minimize all my windows to find it again.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071264</id>
	<title>Loved on Linux, hate hate hate on Mac</title>
	<author>mattr</author>
	<datestamp>1265726760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I loved GIMP on linux. Even made an automatic compositing system with perl-fu.<br>But I really hate, hate-hate-hate GIMP on Mac OS X. Seashore and Leeshore also suck, having thrown out all the functionality I look for, but oh GIMP in X on the Mac has been utter pain.<br>I am sooo looking forward to this.<br>FYI <a href="http://www.bicoid.com/software/leeshore/" title="bicoid.com">Leeshore</a> [bicoid.com] is the Cocoa minimized GIMP version called Seashore, but with Core Image effects added.<br>The site is all in Japanese but the program is in English.</p></htmltext>
<tokenext>I loved GIMP on linux .
Even made an automatic compositing system with perl-fu.But I really hate , hate-hate-hate GIMP on Mac OS X. Seashore and Leeshore also suck , having thrown out all the functionality I look for , but oh GIMP in X on the Mac has been utter pain.I am sooo looking forward to this.FYI Leeshore [ bicoid.com ] is the Cocoa minimized GIMP version called Seashore , but with Core Image effects added.The site is all in Japanese but the program is in English .</tokentext>
<sentencetext>I loved GIMP on linux.
Even made an automatic compositing system with perl-fu.But I really hate, hate-hate-hate GIMP on Mac OS X. Seashore and Leeshore also suck, having thrown out all the functionality I look for, but oh GIMP in X on the Mac has been utter pain.I am sooo looking forward to this.FYI Leeshore [bicoid.com] is the Cocoa minimized GIMP version called Seashore, but with Core Image effects added.The site is all in Japanese but the program is in English.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072430</id>
	<title>Re:Much more important features missing</title>
	<author>hey</author>
	<datestamp>1265732880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well maybe. But if users can't stand using (because of multiple windows everywhere) then they'll never have a chance to find out that's missing.</p></htmltext>
<tokenext>Well maybe .
But if users ca n't stand using ( because of multiple windows everywhere ) then they 'll never have a chance to find out that 's missing .</tokentext>
<sentencetext>Well maybe.
But if users can't stand using (because of multiple windows everywhere) then they'll never have a chance to find out that's missing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072256</id>
	<title>Re:Much more important features missing</title>
	<author>kikito</author>
	<datestamp>1265732160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That is a matter your opinion. I never work with LAB and CYMK colors, so for me "the lack of LAB and CYMK modes isn't that bad". However I don't like the multiwindow stuff.</p></htmltext>
<tokenext>That is a matter your opinion .
I never work with LAB and CYMK colors , so for me " the lack of LAB and CYMK modes is n't that bad " .
However I do n't like the multiwindow stuff .</tokentext>
<sentencetext>That is a matter your opinion.
I never work with LAB and CYMK colors, so for me "the lack of LAB and CYMK modes isn't that bad".
However I don't like the multiwindow stuff.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31076878</id>
	<title>Re:Forget the UI, change the name</title>
	<author>MBC1977</author>
	<datestamp>1265749140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Funny you mention that, because I'm writing a paper about bad marketing ideas for class and have specifically touched upon how a name, however cool (to its inventors and perhaps its intended audience) really can torpedo a product out of the market.  Now granted, I'm probably correct that the GNU Image Manipulation Program on first glance seems intuitive.  However, given our current culture and society it has (unfortunately) one of the most worse acronyms (and I'm being generous there) probably created (i.e. GIMP).<br> <br>

I respect that marketing is considered to be worth the effort by most technical types, and perhaps if logic was the only factor in the world (minus emotion) that would be an adequate (if boring) existence.
However, we are not emotionless drones (thankfully), and even better choosing the tool which logically fits AND emotionally satisfies normally wins.  The name "gimp" fails at the later.  A cool name is not a crutch (regardless of what the creators of the application may think), but a bad name will kill a product (good or bad) almost every time.</htmltext>
<tokenext>Funny you mention that , because I 'm writing a paper about bad marketing ideas for class and have specifically touched upon how a name , however cool ( to its inventors and perhaps its intended audience ) really can torpedo a product out of the market .
Now granted , I 'm probably correct that the GNU Image Manipulation Program on first glance seems intuitive .
However , given our current culture and society it has ( unfortunately ) one of the most worse acronyms ( and I 'm being generous there ) probably created ( i.e .
GIMP ) . I respect that marketing is considered to be worth the effort by most technical types , and perhaps if logic was the only factor in the world ( minus emotion ) that would be an adequate ( if boring ) existence .
However , we are not emotionless drones ( thankfully ) , and even better choosing the tool which logically fits AND emotionally satisfies normally wins .
The name " gimp " fails at the later .
A cool name is not a crutch ( regardless of what the creators of the application may think ) , but a bad name will kill a product ( good or bad ) almost every time .</tokentext>
<sentencetext>Funny you mention that, because I'm writing a paper about bad marketing ideas for class and have specifically touched upon how a name, however cool (to its inventors and perhaps its intended audience) really can torpedo a product out of the market.
Now granted, I'm probably correct that the GNU Image Manipulation Program on first glance seems intuitive.
However, given our current culture and society it has (unfortunately) one of the most worse acronyms (and I'm being generous there) probably created (i.e.
GIMP). 

I respect that marketing is considered to be worth the effort by most technical types, and perhaps if logic was the only factor in the world (minus emotion) that would be an adequate (if boring) existence.
However, we are not emotionless drones (thankfully), and even better choosing the tool which logically fits AND emotionally satisfies normally wins.
The name "gimp" fails at the later.
A cool name is not a crutch (regardless of what the creators of the application may think), but a bad name will kill a product (good or bad) almost every time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071008</id>
	<title>Smartest workflow move ....ever!</title>
	<author>Anonymous</author>
	<datestamp>1265725260000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>I'm glad they're doing this.</p><p>It makes it much easier to work on the images, instead of having to "mishap-click" on every single window, and having to click on the related window in order to get back into the image editor again. WAAAAY overdue, but finally here - good job guys!</p></htmltext>
<tokenext>I 'm glad they 're doing this.It makes it much easier to work on the images , instead of having to " mishap-click " on every single window , and having to click on the related window in order to get back into the image editor again .
WAAAAY overdue , but finally here - good job guys !</tokentext>
<sentencetext>I'm glad they're doing this.It makes it much easier to work on the images, instead of having to "mishap-click" on every single window, and having to click on the related window in order to get back into the image editor again.
WAAAAY overdue, but finally here - good job guys!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074576</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Junior J. Junior III</author>
	<datestamp>1265740980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days, or worse, they've never seen Pulp Fiction because they would be offended by it, but they still know "The GIMP" through cultural allusions to that character, and thus are offended by any reference to GIMP.</p></div><p>*sigh*  I guess I should forget about submitting those "leather face mask with zipper mouth" desktop icons that I've been working on.</p></div>
	</htmltext>
<tokenext>Every once in a while , I forget , and most people associate GIMP or " The GIMP " with Pulp Fiction these days , or worse , they 've never seen Pulp Fiction because they would be offended by it , but they still know " The GIMP " through cultural allusions to that character , and thus are offended by any reference to GIMP .
* sigh * I guess I should forget about submitting those " leather face mask with zipper mouth " desktop icons that I 've been working on .</tokentext>
<sentencetext>Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days, or worse, they've never seen Pulp Fiction because they would be offended by it, but they still know "The GIMP" through cultural allusions to that character, and thus are offended by any reference to GIMP.
*sigh*  I guess I should forget about submitting those "leather face mask with zipper mouth" desktop icons that I've been working on.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073800</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Anonymous</author>
	<datestamp>1265737920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>The best suggestion I've heard is just drop GNU or make GNU separate from the acronym: IMP, GNU IMP.</p></div><p>Drop the GNU?  That will surely lead to decreased user freedom.</p><p>- GNU/Stallman</p></div>
	</htmltext>
<tokenext>The best suggestion I 've heard is just drop GNU or make GNU separate from the acronym : IMP , GNU IMP.Drop the GNU ?
That will surely lead to decreased user freedom.- GNU/Stallman</tokentext>
<sentencetext>The best suggestion I've heard is just drop GNU or make GNU separate from the acronym: IMP, GNU IMP.Drop the GNU?
That will surely lead to decreased user freedom.- GNU/Stallman
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071400</id>
	<title>The illumination of OSS</title>
	<author>Anonymous</author>
	<datestamp>1265727600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt; The GIMP is an impressive application that illuminates the potential of the of the open source software community to build free and open desktop applications that nearly rival some of the best high-end commercial software tools. The recent improvements reflect the vibrance of the GIMP project and demonstrate some of the benefits of enlisting professional usability experts to contribute to open source application design.</p><p>Bwahahahahahahaahaaahahahahahaha.</p></htmltext>
<tokenext>&gt; The GIMP is an impressive application that illuminates the potential of the of the open source software community to build free and open desktop applications that nearly rival some of the best high-end commercial software tools .
The recent improvements reflect the vibrance of the GIMP project and demonstrate some of the benefits of enlisting professional usability experts to contribute to open source application design.Bwahahahahahahaahaaahahahahahaha .</tokentext>
<sentencetext>&gt; The GIMP is an impressive application that illuminates the potential of the of the open source software community to build free and open desktop applications that nearly rival some of the best high-end commercial software tools.
The recent improvements reflect the vibrance of the GIMP project and demonstrate some of the benefits of enlisting professional usability experts to contribute to open source application design.Bwahahahahahahaahaaahahahahahaha.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071824</id>
	<title>at least...</title>
	<author>yivi</author>
	<datestamp>1265729880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...we can still complain about the name.</p><p>I.-</p></htmltext>
<tokenext>...we can still complain about the name.I.-</tokentext>
<sentencetext>...we can still complain about the name.I.-</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071436</id>
	<title>Gimpshop GUI...</title>
	<author>Anonymous</author>
	<datestamp>1265727780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well, I would have preferred at least an option for a "Gimpshop" GUI (it exists but it's out of date).<br>Since there is a good overlap in functionality, an interesting side effect of that is that you could follow the many, many PS tutorials in books and magazines - there are many more of them than interesting GIMP tutorials.</p></htmltext>
<tokenext>Well , I would have preferred at least an option for a " Gimpshop " GUI ( it exists but it 's out of date ) .Since there is a good overlap in functionality , an interesting side effect of that is that you could follow the many , many PS tutorials in books and magazines - there are many more of them than interesting GIMP tutorials .</tokentext>
<sentencetext>Well, I would have preferred at least an option for a "Gimpshop" GUI (it exists but it's out of date).Since there is a good overlap in functionality, an interesting side effect of that is that you could follow the many, many PS tutorials in books and magazines - there are many more of them than interesting GIMP tutorials.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072116</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Anonymous</author>
	<datestamp>1265731440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Can you imagine a corporate effort putting a name like that on a product?</p><p>"I know!  Let's call our new package, 'FAG' or 'NIGGER'!  What a great way to market our new product!"</p><p>But hey, the development team finally got over themselves and decided to tackle the crappy GUI.  That only took ten years of childish denial.</p><p>Now if they'd be so kind as to recognize that screen real estate matters and do something about those terrible fat icons and cross hair cursors.</p><p>Though, their selection ribbon at the top is beautiful!  Photoshop should take notes!</p><p>It also seems that they are pushing ahead with 32 bits editing, though they are still working with legacy 8 bit code.</p></htmltext>
<tokenext>Can you imagine a corporate effort putting a name like that on a product ?
" I know !
Let 's call our new package , 'FAG ' or 'NIGGER ' !
What a great way to market our new product !
" But hey , the development team finally got over themselves and decided to tackle the crappy GUI .
That only took ten years of childish denial.Now if they 'd be so kind as to recognize that screen real estate matters and do something about those terrible fat icons and cross hair cursors.Though , their selection ribbon at the top is beautiful !
Photoshop should take notes ! It also seems that they are pushing ahead with 32 bits editing , though they are still working with legacy 8 bit code .</tokentext>
<sentencetext>Can you imagine a corporate effort putting a name like that on a product?
"I know!
Let's call our new package, 'FAG' or 'NIGGER'!
What a great way to market our new product!
"But hey, the development team finally got over themselves and decided to tackle the crappy GUI.
That only took ten years of childish denial.Now if they'd be so kind as to recognize that screen real estate matters and do something about those terrible fat icons and cross hair cursors.Though, their selection ribbon at the top is beautiful!
Photoshop should take notes!It also seems that they are pushing ahead with 32 bits editing, though they are still working with legacy 8 bit code.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31075690</id>
	<title>Re:I hope it will work better on osx</title>
	<author>Captain Spam</author>
	<datestamp>1265744760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Assuming you're using the X11 port of GIMP, you can tell X11.app (be it what Apple ships with or what's-its-name the most common better alternative) to behave the way that most X11 window managers behave.  It defaults to making its windows behave like OS X windows (click-to-focus but don't pass that click to the program), but you can change that somewhere in preferences.  Really irritated me when I first tried GIMP on OS X, too.  Now... well, I still use GIMP on my Linux box most often, but in a pinch...</p><p>Note that this only applies to X11 applications.  Can't help you as far as the rest of OS X goes, or if you're using a native port of GIMP.<nobr> <wbr></nobr>:-)</p></htmltext>
<tokenext>Assuming you 're using the X11 port of GIMP , you can tell X11.app ( be it what Apple ships with or what 's-its-name the most common better alternative ) to behave the way that most X11 window managers behave .
It defaults to making its windows behave like OS X windows ( click-to-focus but do n't pass that click to the program ) , but you can change that somewhere in preferences .
Really irritated me when I first tried GIMP on OS X , too .
Now... well , I still use GIMP on my Linux box most often , but in a pinch...Note that this only applies to X11 applications .
Ca n't help you as far as the rest of OS X goes , or if you 're using a native port of GIMP .
: - )</tokentext>
<sentencetext>Assuming you're using the X11 port of GIMP, you can tell X11.app (be it what Apple ships with or what's-its-name the most common better alternative) to behave the way that most X11 window managers behave.
It defaults to making its windows behave like OS X windows (click-to-focus but don't pass that click to the program), but you can change that somewhere in preferences.
Really irritated me when I first tried GIMP on OS X, too.
Now... well, I still use GIMP on my Linux box most often, but in a pinch...Note that this only applies to X11 applications.
Can't help you as far as the rest of OS X goes, or if you're using a native port of GIMP.
:-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073808</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073034</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Anonymous</author>
	<datestamp>1265735400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I've got a better idea: chop off your dick and go fuck yourself.</p></htmltext>
<tokenext>I 've got a better idea : chop off your dick and go fuck yourself .</tokentext>
<sentencetext>I've got a better idea: chop off your dick and go fuck yourself.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072278</id>
	<title>Re:Much more important features missing</title>
	<author>Anonymous</author>
	<datestamp>1265732280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Last I heard, most of those are planned to be included at some point, but they were contingent on getting gegl done and incorporated into GIMP.  Since gegl's in now, presumably it won't be that long before those features start working their way into future releases.  That said, I haven't really been following it recently, so I have no idea what the current status is.</p></htmltext>
<tokenext>Last I heard , most of those are planned to be included at some point , but they were contingent on getting gegl done and incorporated into GIMP .
Since gegl 's in now , presumably it wo n't be that long before those features start working their way into future releases .
That said , I have n't really been following it recently , so I have no idea what the current status is .</tokentext>
<sentencetext>Last I heard, most of those are planned to be included at some point, but they were contingent on getting gegl done and incorporated into GIMP.
Since gegl's in now, presumably it won't be that long before those features start working their way into future releases.
That said, I haven't really been following it recently, so I have no idea what the current status is.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071318</id>
	<title>Re:Masks</title>
	<author>suso</author>
	<datestamp>1265727120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yes and it will also support documentation that you can read so that you know what features it has.</p><p>You people that gripe about gimp's interface have really messed it up.  Thanks a lot.</p></htmltext>
<tokenext>Yes and it will also support documentation that you can read so that you know what features it has.You people that gripe about gimp 's interface have really messed it up .
Thanks a lot .</tokentext>
<sentencetext>Yes and it will also support documentation that you can read so that you know what features it has.You people that gripe about gimp's interface have really messed it up.
Thanks a lot.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31070992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071178</id>
	<title>I can't wait until. . .</title>
	<author>Anonymous</author>
	<datestamp>1265726340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I can't wait until they make a GIMP app for the Ipad.  Then I can do some smudgey finger painting on the go!</htmltext>
<tokenext>I ca n't wait until they make a GIMP app for the Ipad .
Then I can do some smudgey finger painting on the go !</tokentext>
<sentencetext>I can't wait until they make a GIMP app for the Ipad.
Then I can do some smudgey finger painting on the go!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071856</id>
	<title>Innovation</title>
	<author>Stele</author>
	<datestamp>1265730120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Got to hand it to them - it looks more and more like Photoshop with each release!</p></htmltext>
<tokenext>Got to hand it to them - it looks more and more like Photoshop with each release !</tokentext>
<sentencetext>Got to hand it to them - it looks more and more like Photoshop with each release!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31081992</id>
	<title>Gimp + Wii Sports?</title>
	<author>Psaakyrn</author>
	<datestamp>1265736060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>At least, that's what I thought this article was about when skimming through headlines..</p></htmltext>
<tokenext>At least , that 's what I thought this article was about when skimming through headlines. .</tokentext>
<sentencetext>At least, that's what I thought this article was about when skimming through headlines..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31081726</id>
	<title>Re:Much more important features missing</title>
	<author>Philip\_the\_physicist</author>
	<datestamp>1265732520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I had heard that there was a patent on something to do with CMYK handling which made the maintainers wary of including support, BICBW.</p></htmltext>
<tokenext>I had heard that there was a patent on something to do with CMYK handling which made the maintainers wary of including support , BICBW .</tokentext>
<sentencetext>I had heard that there was a patent on something to do with CMYK handling which made the maintainers wary of including support, BICBW.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071470</id>
	<title>Hell yea!</title>
	<author>TravisHein</author>
	<datestamp>1265727960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Where is the 'like' button...</htmltext>
<tokenext>Where is the 'like ' button.. .</tokentext>
<sentencetext>Where is the 'like' button...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072230</id>
	<title>Re:re?</title>
	<author>kikito</author>
	<datestamp>1265731980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So you first lease, and then release.</p></htmltext>
<tokenext>So you first lease , and then release .</tokentext>
<sentencetext>So you first lease, and then release.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071228</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074864</id>
	<title>Re:re?</title>
	<author>Anonymous</author>
	<datestamp>1265741940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Mod parent funny.</p><p>On second thought, mod parent informative.</p></htmltext>
<tokenext>Mod parent funny.On second thought , mod parent informative .</tokentext>
<sentencetext>Mod parent funny.On second thought, mod parent informative.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071228</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071654</id>
	<title>Too little, too late</title>
	<author>the-matt-mobile</author>
	<datestamp>1265728860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I quit using GIMP years ago in favor of other free alternatives, mainly because of it's terrible interface because the functionality was nearly all there.  I wonder if this move will really win anyone back?</htmltext>
<tokenext>I quit using GIMP years ago in favor of other free alternatives , mainly because of it 's terrible interface because the functionality was nearly all there .
I wonder if this move will really win anyone back ?</tokentext>
<sentencetext>I quit using GIMP years ago in favor of other free alternatives, mainly because of it's terrible interface because the functionality was nearly all there.
I wonder if this move will really win anyone back?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071004</id>
	<title>Your official guide to the Jigaboo presidency</title>
	<author>Anonymous</author>
	<datestamp>1265725260000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Congratulations on your purchase of a brand new nigger! If handled properly, your apeman will give years of valuable, if reluctant, service.</p><p>INSTALLING YOUR NIGGER.<br>You should install your nigger differently according to whether you have purchased the field or house model. Field niggers work best in a serial configuration, i.e. chained together. Chain your nigger to another nigger immediately after unpacking it, and don't even think about taking that chain off, ever. Many niggers start singing as soon as you put a chain on them. This habit can usually be thrashed out of them if nipped in the bud. House niggers work best as standalone units, but should be hobbled or hamstrung to prevent attempts at escape. At this stage, your nigger can also be given a name. Most owners use the same names over and over, since niggers become confused by too much data. Rufus, Rastus, Remus, Toby, Carslisle, Carlton, Hey-You!-Yes-you!, Yeller, Blackstar, and Sambo are all effective names for your new buck nigger. If your nigger is a ho, it should be called Latrelle, L'Tanya, or Jemima. Some owners call their nigger hoes Latrine for a joke. Pearl, Blossom, and Ivory are also righteous names for nigger hoes. These names go straight over your nigger's head, by the way.</p><p>CONFIGURING YOUR NIGGER<br>Owing to a design error, your nigger comes equipped with a tongue and vocal chords. Most niggers can master only a few basic human phrases with this apparatus - "muh dick" being the most popular. However, others make barking, yelping, yapping noises and appear to be in some pain, so you should probably call a vet and have him remove your nigger's tongue. Once de-tongued your nigger will be a lot happier - at least, you won't hear it complaining anywhere near as much. Niggers have nothing interesting to say, anyway. Many owners also castrate their niggers for health reasons (yours, mine, and that of women, not the nigger's). This is strongly recommended, and frankly, it's a mystery why this is not done on the boat</p><p>HOUSING YOUR NIGGER.<br>Your nigger can be accommodated in cages with stout iron bars. Make sure, however, that the bars are wide enough to push pieces of nigger food through. The rule of thumb is, four niggers per square yard of cage. So a fifteen foot by thirty foot nigger cage can accommodate two hundred niggers. You can site a nigger cage anywhere, even on soft ground. Don't worry about your nigger fashioning makeshift shovels out of odd pieces of wood and digging an escape tunnel under the bars of the cage. Niggers never invented the shovel before and they're not about to now. In any case, your nigger is certainly too lazy to attempt escape. As long as the free food holds out, your nigger is living better than it did in Africa, so it will stay put. Buck niggers and hoe niggers can be safely accommodated in the same cage, as bucks never attempt sex with black hoes.</p><p>FEEDING YOUR NIGGER.<br>Your Nigger likes fried chicken, corn bread, and watermelon. You should therefore give it none of these things because its lazy ass almost certainly doesn't deserve it. Instead, feed it on porridge with salt, and creek water. Your nigger will supplement its diet with whatever it finds in the fields, other niggers, etc. Experienced nigger owners sometimes push watermelon slices through the bars of the nigger cage at the end of the day as a treat, but only if all niggers have worked well and nothing has been stolen that day. Mike of the Old Ranch Plantation reports that this last one is a killer, since all niggers steal something almost every single day of their lives. He reports he doesn't have to spend much on free watermelon for his niggers as a result. You should never allow your nigger meal breaks while at work, since if it stops work for more than ten minutes it will need to be retrained. You would be surprised how long it takes to teach a nigger to pick cotton. You really would. Coffee beans? Don't ask. You have no idea.</p><p>MAKING YOUR NIGGER WORK.<br>Niggers are very, very averse to work of any kind. The nigger's most</p></htmltext>
<tokenext>Congratulations on your purchase of a brand new nigger !
If handled properly , your apeman will give years of valuable , if reluctant , service.INSTALLING YOUR NIGGER.You should install your nigger differently according to whether you have purchased the field or house model .
Field niggers work best in a serial configuration , i.e .
chained together .
Chain your nigger to another nigger immediately after unpacking it , and do n't even think about taking that chain off , ever .
Many niggers start singing as soon as you put a chain on them .
This habit can usually be thrashed out of them if nipped in the bud .
House niggers work best as standalone units , but should be hobbled or hamstrung to prevent attempts at escape .
At this stage , your nigger can also be given a name .
Most owners use the same names over and over , since niggers become confused by too much data .
Rufus , Rastus , Remus , Toby , Carslisle , Carlton , Hey-You ! -Yes-you ! , Yeller , Blackstar , and Sambo are all effective names for your new buck nigger .
If your nigger is a ho , it should be called Latrelle , L'Tanya , or Jemima .
Some owners call their nigger hoes Latrine for a joke .
Pearl , Blossom , and Ivory are also righteous names for nigger hoes .
These names go straight over your nigger 's head , by the way.CONFIGURING YOUR NIGGEROwing to a design error , your nigger comes equipped with a tongue and vocal chords .
Most niggers can master only a few basic human phrases with this apparatus - " muh dick " being the most popular .
However , others make barking , yelping , yapping noises and appear to be in some pain , so you should probably call a vet and have him remove your nigger 's tongue .
Once de-tongued your nigger will be a lot happier - at least , you wo n't hear it complaining anywhere near as much .
Niggers have nothing interesting to say , anyway .
Many owners also castrate their niggers for health reasons ( yours , mine , and that of women , not the nigger 's ) .
This is strongly recommended , and frankly , it 's a mystery why this is not done on the boatHOUSING YOUR NIGGER.Your nigger can be accommodated in cages with stout iron bars .
Make sure , however , that the bars are wide enough to push pieces of nigger food through .
The rule of thumb is , four niggers per square yard of cage .
So a fifteen foot by thirty foot nigger cage can accommodate two hundred niggers .
You can site a nigger cage anywhere , even on soft ground .
Do n't worry about your nigger fashioning makeshift shovels out of odd pieces of wood and digging an escape tunnel under the bars of the cage .
Niggers never invented the shovel before and they 're not about to now .
In any case , your nigger is certainly too lazy to attempt escape .
As long as the free food holds out , your nigger is living better than it did in Africa , so it will stay put .
Buck niggers and hoe niggers can be safely accommodated in the same cage , as bucks never attempt sex with black hoes.FEEDING YOUR NIGGER.Your Nigger likes fried chicken , corn bread , and watermelon .
You should therefore give it none of these things because its lazy ass almost certainly does n't deserve it .
Instead , feed it on porridge with salt , and creek water .
Your nigger will supplement its diet with whatever it finds in the fields , other niggers , etc .
Experienced nigger owners sometimes push watermelon slices through the bars of the nigger cage at the end of the day as a treat , but only if all niggers have worked well and nothing has been stolen that day .
Mike of the Old Ranch Plantation reports that this last one is a killer , since all niggers steal something almost every single day of their lives .
He reports he does n't have to spend much on free watermelon for his niggers as a result .
You should never allow your nigger meal breaks while at work , since if it stops work for more than ten minutes it will need to be retrained .
You would be surprised how long it takes to teach a nigger to pick cotton .
You really would .
Coffee beans ?
Do n't ask .
You have no idea.MAKING YOUR NIGGER WORK.Niggers are very , very averse to work of any kind .
The nigger 's most</tokentext>
<sentencetext>Congratulations on your purchase of a brand new nigger!
If handled properly, your apeman will give years of valuable, if reluctant, service.INSTALLING YOUR NIGGER.You should install your nigger differently according to whether you have purchased the field or house model.
Field niggers work best in a serial configuration, i.e.
chained together.
Chain your nigger to another nigger immediately after unpacking it, and don't even think about taking that chain off, ever.
Many niggers start singing as soon as you put a chain on them.
This habit can usually be thrashed out of them if nipped in the bud.
House niggers work best as standalone units, but should be hobbled or hamstrung to prevent attempts at escape.
At this stage, your nigger can also be given a name.
Most owners use the same names over and over, since niggers become confused by too much data.
Rufus, Rastus, Remus, Toby, Carslisle, Carlton, Hey-You!-Yes-you!, Yeller, Blackstar, and Sambo are all effective names for your new buck nigger.
If your nigger is a ho, it should be called Latrelle, L'Tanya, or Jemima.
Some owners call their nigger hoes Latrine for a joke.
Pearl, Blossom, and Ivory are also righteous names for nigger hoes.
These names go straight over your nigger's head, by the way.CONFIGURING YOUR NIGGEROwing to a design error, your nigger comes equipped with a tongue and vocal chords.
Most niggers can master only a few basic human phrases with this apparatus - "muh dick" being the most popular.
However, others make barking, yelping, yapping noises and appear to be in some pain, so you should probably call a vet and have him remove your nigger's tongue.
Once de-tongued your nigger will be a lot happier - at least, you won't hear it complaining anywhere near as much.
Niggers have nothing interesting to say, anyway.
Many owners also castrate their niggers for health reasons (yours, mine, and that of women, not the nigger's).
This is strongly recommended, and frankly, it's a mystery why this is not done on the boatHOUSING YOUR NIGGER.Your nigger can be accommodated in cages with stout iron bars.
Make sure, however, that the bars are wide enough to push pieces of nigger food through.
The rule of thumb is, four niggers per square yard of cage.
So a fifteen foot by thirty foot nigger cage can accommodate two hundred niggers.
You can site a nigger cage anywhere, even on soft ground.
Don't worry about your nigger fashioning makeshift shovels out of odd pieces of wood and digging an escape tunnel under the bars of the cage.
Niggers never invented the shovel before and they're not about to now.
In any case, your nigger is certainly too lazy to attempt escape.
As long as the free food holds out, your nigger is living better than it did in Africa, so it will stay put.
Buck niggers and hoe niggers can be safely accommodated in the same cage, as bucks never attempt sex with black hoes.FEEDING YOUR NIGGER.Your Nigger likes fried chicken, corn bread, and watermelon.
You should therefore give it none of these things because its lazy ass almost certainly doesn't deserve it.
Instead, feed it on porridge with salt, and creek water.
Your nigger will supplement its diet with whatever it finds in the fields, other niggers, etc.
Experienced nigger owners sometimes push watermelon slices through the bars of the nigger cage at the end of the day as a treat, but only if all niggers have worked well and nothing has been stolen that day.
Mike of the Old Ranch Plantation reports that this last one is a killer, since all niggers steal something almost every single day of their lives.
He reports he doesn't have to spend much on free watermelon for his niggers as a result.
You should never allow your nigger meal breaks while at work, since if it stops work for more than ten minutes it will need to be retrained.
You would be surprised how long it takes to teach a nigger to pick cotton.
You really would.
Coffee beans?
Don't ask.
You have no idea.MAKING YOUR NIGGER WORK.Niggers are very, very averse to work of any kind.
The nigger's most</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073460</id>
	<title>Woo-hoo!</title>
	<author>Lord Bitman</author>
	<datestamp>1265736840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Now that the #1 Superficial complaint about gimp has been taken care of, maybe when people continue to not use it, the developers will realize the actual horrible UI decisions they made in the past, and fix those. I suspect the current conversation goes something like this:</p><p>[Gimp developer] What UI improvements would you like to see in Gimp?<br>[Average Joe] Well, to start with, I'd love it if it didn't have all these windows everywhere. Different parts of the interface keep covering each-other! I can't work at all!<br>[Gimp developer] Okay, that's actually the Window Manager's fault. What else?<br>[Average Joe] I don't know, I couldn't actually figure out anything because I couldn't see anything half the time.</p><p>Now, finally, after years of waiting, the conversation can be upgraded to:</p><p>[Gimp developer] What UI improvements would you like to see in Gimp?<br>[Average Joe] (actual problems with gimp go here)<br>[Gimp developer] *dies of old age before Average Joe is finished talking*</p></htmltext>
<tokenext>Now that the # 1 Superficial complaint about gimp has been taken care of , maybe when people continue to not use it , the developers will realize the actual horrible UI decisions they made in the past , and fix those .
I suspect the current conversation goes something like this : [ Gimp developer ] What UI improvements would you like to see in Gimp ?
[ Average Joe ] Well , to start with , I 'd love it if it did n't have all these windows everywhere .
Different parts of the interface keep covering each-other !
I ca n't work at all !
[ Gimp developer ] Okay , that 's actually the Window Manager 's fault .
What else ?
[ Average Joe ] I do n't know , I could n't actually figure out anything because I could n't see anything half the time.Now , finally , after years of waiting , the conversation can be upgraded to : [ Gimp developer ] What UI improvements would you like to see in Gimp ?
[ Average Joe ] ( actual problems with gimp go here ) [ Gimp developer ] * dies of old age before Average Joe is finished talking *</tokentext>
<sentencetext>Now that the #1 Superficial complaint about gimp has been taken care of, maybe when people continue to not use it, the developers will realize the actual horrible UI decisions they made in the past, and fix those.
I suspect the current conversation goes something like this:[Gimp developer] What UI improvements would you like to see in Gimp?
[Average Joe] Well, to start with, I'd love it if it didn't have all these windows everywhere.
Different parts of the interface keep covering each-other!
I can't work at all!
[Gimp developer] Okay, that's actually the Window Manager's fault.
What else?
[Average Joe] I don't know, I couldn't actually figure out anything because I couldn't see anything half the time.Now, finally, after years of waiting, the conversation can be upgraded to:[Gimp developer] What UI improvements would you like to see in Gimp?
[Average Joe] (actual problems with gimp go here)[Gimp developer] *dies of old age before Average Joe is finished talking*</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073610</id>
	<title>Will it EVER actually be released?</title>
	<author>phobos512</author>
	<datestamp>1265737320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I first heard about this over 6 mos ago and still they're talking about it coming soon.  Starting to feel like it's never actually going to come out.  I mean, release version is only on the 2.6 branch and they're talking the 2.8 branch.  Grr!  Do want, now!</htmltext>
<tokenext>I first heard about this over 6 mos ago and still they 're talking about it coming soon .
Starting to feel like it 's never actually going to come out .
I mean , release version is only on the 2.6 branch and they 're talking the 2.8 branch .
Grr ! Do want , now !</tokentext>
<sentencetext>I first heard about this over 6 mos ago and still they're talking about it coming soon.
Starting to feel like it's never actually going to come out.
I mean, release version is only on the 2.6 branch and they're talking the 2.8 branch.
Grr!  Do want, now!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31077150</id>
	<title>I'm on the verge of stop using GIMP allready</title>
	<author>Anonymous</author>
	<datestamp>1265706840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>They allready</p><p><nobr> <wbr></nobr>... stupified the menues and made them longer and slower to work with (right click or the menue-key give you a menue that cant be shown in full if you are anywhere near the screens bottom edge) and you have to wade through lots of alternatives.</p><p><nobr> <wbr></nobr>...placed document commands in the same menues as the application commands, making the interface really confusing: "Oops, did I do something with the image? WTF"</p><p><nobr> <wbr></nobr>...made the panes invisible within the windowing system, you can't get to the panes through your usual means in the windowing system, making keyboard navigation impossible.</p></htmltext>
<tokenext>They allready ... stupified the menues and made them longer and slower to work with ( right click or the menue-key give you a menue that cant be shown in full if you are anywhere near the screens bottom edge ) and you have to wade through lots of alternatives .
...placed document commands in the same menues as the application commands , making the interface really confusing : " Oops , did I do something with the image ?
WTF " ...made the panes invisible within the windowing system , you ca n't get to the panes through your usual means in the windowing system , making keyboard navigation impossible .</tokentext>
<sentencetext>They allready ... stupified the menues and made them longer and slower to work with (right click or the menue-key give you a menue that cant be shown in full if you are anywhere near the screens bottom edge) and you have to wade through lots of alternatives.
...placed document commands in the same menues as the application commands, making the interface really confusing: "Oops, did I do something with the image?
WTF" ...made the panes invisible within the windowing system, you can't get to the panes through your usual means in the windowing system, making keyboard navigation impossible.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31080522</id>
	<title>Re:Much more important features missing</title>
	<author>scdeimos</author>
	<datestamp>1265722620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I agree: Gimp's graphics engine is seriously in need of upgrading. Who actually cares about the UI when you can get add-ins like GimpShop if you want to feel "more at home" as an ex-Photoshop user?</p><p>Top of my list is 16-bit channel support, especially in filters. It bugs me that I can open 16-bit files but they have to be downgraded to 8-bit to work with any of the filters. I do a lot of work with astronomy imagery and, unfortunately, Gimp just cannot do this so I have to use Photoshop. I'd rather use Gimp. Getting more mainstream, though, how many digital photographers do you think are out there wanting to process RAW files from their camera which are typically 10, 12, 14 or 16-bits per channel?</p><p>While it's not important in my work, having worked in the print industry before I know that additional colour spaces such as CMYK would be extremely useful to graphics professionals in the print industry. I could see Gimp getting a foothold in such places as budgets are typically tight (read: non-existent) and a free (workable) alternative to Photoshop would be welcomed with open arms.</p></htmltext>
<tokenext>I agree : Gimp 's graphics engine is seriously in need of upgrading .
Who actually cares about the UI when you can get add-ins like GimpShop if you want to feel " more at home " as an ex-Photoshop user ? Top of my list is 16-bit channel support , especially in filters .
It bugs me that I can open 16-bit files but they have to be downgraded to 8-bit to work with any of the filters .
I do a lot of work with astronomy imagery and , unfortunately , Gimp just can not do this so I have to use Photoshop .
I 'd rather use Gimp .
Getting more mainstream , though , how many digital photographers do you think are out there wanting to process RAW files from their camera which are typically 10 , 12 , 14 or 16-bits per channel ? While it 's not important in my work , having worked in the print industry before I know that additional colour spaces such as CMYK would be extremely useful to graphics professionals in the print industry .
I could see Gimp getting a foothold in such places as budgets are typically tight ( read : non-existent ) and a free ( workable ) alternative to Photoshop would be welcomed with open arms .</tokentext>
<sentencetext>I agree: Gimp's graphics engine is seriously in need of upgrading.
Who actually cares about the UI when you can get add-ins like GimpShop if you want to feel "more at home" as an ex-Photoshop user?Top of my list is 16-bit channel support, especially in filters.
It bugs me that I can open 16-bit files but they have to be downgraded to 8-bit to work with any of the filters.
I do a lot of work with astronomy imagery and, unfortunately, Gimp just cannot do this so I have to use Photoshop.
I'd rather use Gimp.
Getting more mainstream, though, how many digital photographers do you think are out there wanting to process RAW files from their camera which are typically 10, 12, 14 or 16-bits per channel?While it's not important in my work, having worked in the print industry before I know that additional colour spaces such as CMYK would be extremely useful to graphics professionals in the print industry.
I could see Gimp getting a foothold in such places as budgets are typically tight (read: non-existent) and a free (workable) alternative to Photoshop would be welcomed with open arms.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31081958</id>
	<title>Adobe Photoshop is for pros only.</title>
	<author>UrduBlake</author>
	<datestamp>1265735580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why bother? Let's face facts here, a tool as unpolished as the Gimp can never approach the market share of the Photoshop franchise. With Photoshop Elements and even an iPhone app available widely now, there is no excuse for not embracing Photoshop, no matter how poor you are. Friends don't let friends use the Gimp.


50 cents per post.</htmltext>
<tokenext>Why bother ?
Let 's face facts here , a tool as unpolished as the Gimp can never approach the market share of the Photoshop franchise .
With Photoshop Elements and even an iPhone app available widely now , there is no excuse for not embracing Photoshop , no matter how poor you are .
Friends do n't let friends use the Gimp .
50 cents per post .</tokentext>
<sentencetext>Why bother?
Let's face facts here, a tool as unpolished as the Gimp can never approach the market share of the Photoshop franchise.
With Photoshop Elements and even an iPhone app available widely now, there is no excuse for not embracing Photoshop, no matter how poor you are.
Friends don't let friends use the Gimp.
50 cents per post.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078468</id>
	<title>Re:Forget the UI, change the name</title>
	<author>westlake</author>
	<datestamp>1265712120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days</i> </p><p>Gimp - as slang for lame or crippled - has been around at least since 1925. Pulp Fiction simply brought out its explicitly sexual connotations.</p><p>The more interesting question is to ask is why no one saw the problem - or did anything anything about it - before the app was ported to other platforms.</p></htmltext>
<tokenext>Every once in a while , I forget , and most people associate GIMP or " The GIMP " with Pulp Fiction these days Gimp - as slang for lame or crippled - has been around at least since 1925 .
Pulp Fiction simply brought out its explicitly sexual connotations.The more interesting question is to ask is why no one saw the problem - or did anything anything about it - before the app was ported to other platforms .</tokentext>
<sentencetext>Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days Gimp - as slang for lame or crippled - has been around at least since 1925.
Pulp Fiction simply brought out its explicitly sexual connotations.The more interesting question is to ask is why no one saw the problem - or did anything anything about it - before the app was ported to other platforms.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071834</id>
	<title>a usable GIMP is one of the</title>
	<author>wardk</author>
	<datestamp>1265729880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>signs of impending apocalypse</p></htmltext>
<tokenext>signs of impending apocalypse</tokentext>
<sentencetext>signs of impending apocalypse</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071590</id>
	<title>Who cares about UI, but 16 bit per color...</title>
	<author>tapanitarvainen</author>
	<datestamp>1265728500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Me, I don't care much about the UI - I'll get used to whatever way it goes.
The significant change, to me, is left at the very end of the article: GEGL and proper high-bit-depth color support it brings.</htmltext>
<tokenext>Me , I do n't care much about the UI - I 'll get used to whatever way it goes .
The significant change , to me , is left at the very end of the article : GEGL and proper high-bit-depth color support it brings .</tokentext>
<sentencetext>Me, I don't care much about the UI - I'll get used to whatever way it goes.
The significant change, to me, is left at the very end of the article: GEGL and proper high-bit-depth color support it brings.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072770</id>
	<title>About Fricken Time</title>
	<author>Anonymous</author>
	<datestamp>1265734320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I tried GIMP, really I did, but it just didn't have the options I needed (like say the ability to add text to an image, really is that so hard?), and the interface just... pained me.</p><p>It would have been bearable if clicking on a picture window brought up the editor window as well, but having to bring both up manually just grated on me.</p></htmltext>
<tokenext>I tried GIMP , really I did , but it just did n't have the options I needed ( like say the ability to add text to an image , really is that so hard ?
) , and the interface just... pained me.It would have been bearable if clicking on a picture window brought up the editor window as well , but having to bring both up manually just grated on me .</tokentext>
<sentencetext>I tried GIMP, really I did, but it just didn't have the options I needed (like say the ability to add text to an image, really is that so hard?
), and the interface just... pained me.It would have been bearable if clicking on a picture window brought up the editor window as well, but having to bring both up manually just grated on me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071282</id>
	<title>Not really a surprise.</title>
	<author>dsavi</author>
	<datestamp>1265726820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Not only have there been rumors about this for months, but I've seen at least one confirmation from a developer. Easy way to get a story on<nobr> <wbr></nobr>/., huh?

But of course I support this decision and think it's a great move away from the UIs of yesterday and all the rest of it.</htmltext>
<tokenext>Not only have there been rumors about this for months , but I 've seen at least one confirmation from a developer .
Easy way to get a story on /. , huh ?
But of course I support this decision and think it 's a great move away from the UIs of yesterday and all the rest of it .</tokentext>
<sentencetext>Not only have there been rumors about this for months, but I've seen at least one confirmation from a developer.
Easy way to get a story on /., huh?
But of course I support this decision and think it's a great move away from the UIs of yesterday and all the rest of it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072274</id>
	<title>Re:Why?</title>
	<author>kikito</author>
	<datestamp>1265732220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Trolls also drag their knuckles.</p></htmltext>
<tokenext>Trolls also drag their knuckles .</tokentext>
<sentencetext>Trolls also drag their knuckles.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071698</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072288</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Anonymous</author>
	<datestamp>1265732340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The millions, er, dozens of people that use <a href="http://www.horde.org/" title="horde.org" rel="nofollow">Horde</a> [horde.org] won't be fond of renaming GIMP to IMP.</p></htmltext>
<tokenext>The millions , er , dozens of people that use Horde [ horde.org ] wo n't be fond of renaming GIMP to IMP .</tokentext>
<sentencetext>The millions, er, dozens of people that use Horde [horde.org] won't be fond of renaming GIMP to IMP.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072242</id>
	<title>Re:Forget the UI, change the name</title>
	<author>kampangptlk</author>
	<datestamp>1265732040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Damn kids these days.
The correct name should be GNU's Not UNiplexed's Not UNiplexed's Not UNiplexed Image Manipulation Program.
And for you GNOME lovers GNU's Not UNiplexed's Not UNiplexed's Not UNiplexed Image Manipulation Pgrogram Tool Kit Network Object Model Environment.</htmltext>
<tokenext>Damn kids these days .
The correct name should be GNU 's Not UNiplexed 's Not UNiplexed 's Not UNiplexed Image Manipulation Program .
And for you GNOME lovers GNU 's Not UNiplexed 's Not UNiplexed 's Not UNiplexed Image Manipulation Pgrogram Tool Kit Network Object Model Environment .</tokentext>
<sentencetext>Damn kids these days.
The correct name should be GNU's Not UNiplexed's Not UNiplexed's Not UNiplexed Image Manipulation Program.
And for you GNOME lovers GNU's Not UNiplexed's Not UNiplexed's Not UNiplexed Image Manipulation Pgrogram Tool Kit Network Object Model Environment.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072250</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Luke has no name</author>
	<datestamp>1265732100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>GIPP: GNU Image Photoshop Program<br>GIEP: GNU Image Editing Program</p><p>OR! OR!</p><p>Don't FUCKING USE AN ACRONYM.</p><p>Give it a name.</p></htmltext>
<tokenext>GIPP : GNU Image Photoshop ProgramGIEP : GNU Image Editing ProgramOR !
OR ! Do n't FUCKING USE AN ACRONYM.Give it a name .</tokentext>
<sentencetext>GIPP: GNU Image Photoshop ProgramGIEP: GNU Image Editing ProgramOR!
OR!Don't FUCKING USE AN ACRONYM.Give it a name.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071698</id>
	<title>Why?</title>
	<author>eno2001</author>
	<datestamp>1265729160000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext><p>OK, I know the project is trying to appease the knuckle draggers who can't use their brains to learn how to use a GUI.  But, I'm hoping they retain fullscreen with the ability to basically hide all tools.  When you're someone who actually knows what they're doing with image manipulation you want the maximum amount of space to work in.  The toolbars and menus should be nearly non-existent until you need them.  GIMP has done this for a LONG time.  The idea of having a massive, ugly mess of toolbars "docked" is simply to cater to moronic users who have poor memory skills.  So be it.  The fact is that about 80\% of the computer user base is moronic, so there IS mind share there which will only improve GIMP's adoption.  But don't take away vital functionality for users who actually *think*.</p><p>TT</p></htmltext>
<tokenext>OK , I know the project is trying to appease the knuckle draggers who ca n't use their brains to learn how to use a GUI .
But , I 'm hoping they retain fullscreen with the ability to basically hide all tools .
When you 're someone who actually knows what they 're doing with image manipulation you want the maximum amount of space to work in .
The toolbars and menus should be nearly non-existent until you need them .
GIMP has done this for a LONG time .
The idea of having a massive , ugly mess of toolbars " docked " is simply to cater to moronic users who have poor memory skills .
So be it .
The fact is that about 80 \ % of the computer user base is moronic , so there IS mind share there which will only improve GIMP 's adoption .
But do n't take away vital functionality for users who actually * think * .TT</tokentext>
<sentencetext>OK, I know the project is trying to appease the knuckle draggers who can't use their brains to learn how to use a GUI.
But, I'm hoping they retain fullscreen with the ability to basically hide all tools.
When you're someone who actually knows what they're doing with image manipulation you want the maximum amount of space to work in.
The toolbars and menus should be nearly non-existent until you need them.
GIMP has done this for a LONG time.
The idea of having a massive, ugly mess of toolbars "docked" is simply to cater to moronic users who have poor memory skills.
So be it.
The fact is that about 80\% of the computer user base is moronic, so there IS mind share there which will only improve GIMP's adoption.
But don't take away vital functionality for users who actually *think*.TT</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073296</id>
	<title>Re:Masks</title>
	<author>Anonymous</author>
	<datestamp>1265736300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Whoosh.</p></htmltext>
<tokenext>Whoosh .</tokentext>
<sentencetext>Whoosh.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071488</id>
	<title>Back to GIMPShop?</title>
	<author>amn108</author>
	<datestamp>1265728020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So, after years upon years, GIMP has suddenly heeded the message of GIMPShop - That some features are simply good to have? I am talking about the monotone MDI background here, which does not distract people from editing their images as opposed to doing so with a desktop background and a dozen of icons behind.</p></htmltext>
<tokenext>So , after years upon years , GIMP has suddenly heeded the message of GIMPShop - That some features are simply good to have ?
I am talking about the monotone MDI background here , which does not distract people from editing their images as opposed to doing so with a desktop background and a dozen of icons behind .</tokentext>
<sentencetext>So, after years upon years, GIMP has suddenly heeded the message of GIMPShop - That some features are simply good to have?
I am talking about the monotone MDI background here, which does not distract people from editing their images as opposed to doing so with a desktop background and a dozen of icons behind.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071876</id>
	<title>Re:Much more important features missing</title>
	<author>Anonymous</author>
	<datestamp>1265730240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>GIMP is always compared to photoshop. There are some key features missing in GIMP</p></div></blockquote><p>Agreed</p><blockquote><div><p>adjustment layers (which GEGL is suppose to eventually bring about, but it's been a long wait)</p></div></blockquote><p>Adjustment layers are a messed up paradigm from being stuck in a 1D compositing 'stack'.  A node-based compositing workflow, however...</p><blockquote><div><p>proper 16 and 32 bit image editing</p></div></blockquote><p>cinepaint seems to have gone nowhere particular fast simply because not enough people (read: businesses) were/are interested in this.  It's sad, but there you go.</p><blockquote><div><p>and LAB and CYMK modes.</p></div></blockquote><p>Seems pretty far off the priority list for most "serious artists".. unless the only serious artists are those who print their work and have it exhibited.  Let's face it - most Photoshop users, and I admit I'm including all the warez kiddies and the family members they installed Photoshop for - will only ever used Photoshop to make images suitable for display on monitors; LCD ones at that.. they won't be bothering with even calibrating their display and making sure Photoshop uses that color profile information.  By the time they do want a print - they'll either send it off to one of the many online printing services who have excellent staff who deal with RGB-&gt;CMYK(and then some) conversion if their machines flag out-of-gamut results, or they'll just send it to their own inkjet/color laser printer and not really care if the colors are a bit off.</p><blockquote><div><p>I'm greatful for GIMP and thankful for the developer's efforts but I'd rather they focus on these things than dicking around with windowing. The truth is once you get use to it, GIMP's windowing isn't THAT bad.</p></div></blockquote><p>You shouldn't have to 'get used to it' - although I agree that there's other areas that need love more than how one manages their windows; although 'losing' your layer window under some other non-GIMP-related because it's separate from everything else, or being fooled once again and trying to do a color adjustment in image A but ending up doing it in image B because you forgot that each window has its own little menu for doing these things.. can get quite annoying.</p><p>Now.. a unified transform tool and a macro recorder (not every artist wants to dive straight into script-fu.. which in itself isn't exactly the most human-readable of languages) - that's what I've been making donations for; although perhaps I should hire a programmer instead and pray to the OSS gods that they'll actually include the code, as I haven't seen any headway made into these areas.. just years and years of discussions.<br>At least there's a bit of a push for GEGL so maybe it won't be so swaptastic to work on large images anymore.</p></div>
	</htmltext>
<tokenext>GIMP is always compared to photoshop .
There are some key features missing in GIMPAgreedadjustment layers ( which GEGL is suppose to eventually bring about , but it 's been a long wait ) Adjustment layers are a messed up paradigm from being stuck in a 1D compositing 'stack' .
A node-based compositing workflow , however...proper 16 and 32 bit image editingcinepaint seems to have gone nowhere particular fast simply because not enough people ( read : businesses ) were/are interested in this .
It 's sad , but there you go.and LAB and CYMK modes.Seems pretty far off the priority list for most " serious artists " .. unless the only serious artists are those who print their work and have it exhibited .
Let 's face it - most Photoshop users , and I admit I 'm including all the warez kiddies and the family members they installed Photoshop for - will only ever used Photoshop to make images suitable for display on monitors ; LCD ones at that.. they wo n't be bothering with even calibrating their display and making sure Photoshop uses that color profile information .
By the time they do want a print - they 'll either send it off to one of the many online printing services who have excellent staff who deal with RGB- &gt; CMYK ( and then some ) conversion if their machines flag out-of-gamut results , or they 'll just send it to their own inkjet/color laser printer and not really care if the colors are a bit off.I 'm greatful for GIMP and thankful for the developer 's efforts but I 'd rather they focus on these things than dicking around with windowing .
The truth is once you get use to it , GIMP 's windowing is n't THAT bad.You should n't have to 'get used to it ' - although I agree that there 's other areas that need love more than how one manages their windows ; although 'losing ' your layer window under some other non-GIMP-related because it 's separate from everything else , or being fooled once again and trying to do a color adjustment in image A but ending up doing it in image B because you forgot that each window has its own little menu for doing these things.. can get quite annoying.Now.. a unified transform tool and a macro recorder ( not every artist wants to dive straight into script-fu.. which in itself is n't exactly the most human-readable of languages ) - that 's what I 've been making donations for ; although perhaps I should hire a programmer instead and pray to the OSS gods that they 'll actually include the code , as I have n't seen any headway made into these areas.. just years and years of discussions.At least there 's a bit of a push for GEGL so maybe it wo n't be so swaptastic to work on large images anymore .</tokentext>
<sentencetext>GIMP is always compared to photoshop.
There are some key features missing in GIMPAgreedadjustment layers (which GEGL is suppose to eventually bring about, but it's been a long wait)Adjustment layers are a messed up paradigm from being stuck in a 1D compositing 'stack'.
A node-based compositing workflow, however...proper 16 and 32 bit image editingcinepaint seems to have gone nowhere particular fast simply because not enough people (read: businesses) were/are interested in this.
It's sad, but there you go.and LAB and CYMK modes.Seems pretty far off the priority list for most "serious artists".. unless the only serious artists are those who print their work and have it exhibited.
Let's face it - most Photoshop users, and I admit I'm including all the warez kiddies and the family members they installed Photoshop for - will only ever used Photoshop to make images suitable for display on monitors; LCD ones at that.. they won't be bothering with even calibrating their display and making sure Photoshop uses that color profile information.
By the time they do want a print - they'll either send it off to one of the many online printing services who have excellent staff who deal with RGB-&gt;CMYK(and then some) conversion if their machines flag out-of-gamut results, or they'll just send it to their own inkjet/color laser printer and not really care if the colors are a bit off.I'm greatful for GIMP and thankful for the developer's efforts but I'd rather they focus on these things than dicking around with windowing.
The truth is once you get use to it, GIMP's windowing isn't THAT bad.You shouldn't have to 'get used to it' - although I agree that there's other areas that need love more than how one manages their windows; although 'losing' your layer window under some other non-GIMP-related because it's separate from everything else, or being fooled once again and trying to do a color adjustment in image A but ending up doing it in image B because you forgot that each window has its own little menu for doing these things.. can get quite annoying.Now.. a unified transform tool and a macro recorder (not every artist wants to dive straight into script-fu.. which in itself isn't exactly the most human-readable of languages) - that's what I've been making donations for; although perhaps I should hire a programmer instead and pray to the OSS gods that they'll actually include the code, as I haven't seen any headway made into these areas.. just years and years of discussions.At least there's a bit of a push for GEGL so maybe it won't be so swaptastic to work on large images anymore.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31086954</id>
	<title>Re:Masks</title>
	<author>vuffi\_raa</author>
	<datestamp>1265045340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>wtf dude, for anyone that is used to using well.... any other graphic application known to man, a single window mode makes more sense. Sorry their redesigned square wheel bugs you but you will get used to a round one.</htmltext>
<tokenext>wtf dude , for anyone that is used to using well.... any other graphic application known to man , a single window mode makes more sense .
Sorry their redesigned square wheel bugs you but you will get used to a round one .</tokentext>
<sentencetext>wtf dude, for anyone that is used to using well.... any other graphic application known to man, a single window mode makes more sense.
Sorry their redesigned square wheel bugs you but you will get used to a round one.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071318</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078476</id>
	<title>Screenshot of the final interface:</title>
	<author>Hurricane78</author>
	<datestamp>1265712120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have found a <a href="http://pictureisunrelated.com/2009/10/16/remember-to-plug-your-gimp-in-at-night/" title="pictureisunrelated.com">screenshot of what they have planned as the final interface for GIMP</a> [pictureisunrelated.com].<nobr> <wbr></nobr>...weird... but definitely better than what they had before.<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>I have found a screenshot of what they have planned as the final interface for GIMP [ pictureisunrelated.com ] .
...weird... but definitely better than what they had before .
; )</tokentext>
<sentencetext>I have found a screenshot of what they have planned as the final interface for GIMP [pictureisunrelated.com].
...weird... but definitely better than what they had before.
;)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31077186</id>
	<title>Re:Forget the UI, change the name</title>
	<author>bill\_mcgonigle</author>
	<datestamp>1265707020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think once 2.8's UI is out, there will be a real opportunity for somebody to setup a SourceForge page offering a re-branded GIMP, and market that.  I think you're probably right, but it's not a hard experiment to run.</p><p>If it's successful and the GIMP folks are convinced, redirect the test site.</p></htmltext>
<tokenext>I think once 2.8 's UI is out , there will be a real opportunity for somebody to setup a SourceForge page offering a re-branded GIMP , and market that .
I think you 're probably right , but it 's not a hard experiment to run.If it 's successful and the GIMP folks are convinced , redirect the test site .</tokentext>
<sentencetext>I think once 2.8's UI is out, there will be a real opportunity for somebody to setup a SourceForge page offering a re-branded GIMP, and market that.
I think you're probably right, but it's not a hard experiment to run.If it's successful and the GIMP folks are convinced, redirect the test site.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31070992</id>
	<title>Masks</title>
	<author>Anonymous</author>
	<datestamp>1265725200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>Will GIMP finally get support for masks?</htmltext>
<tokenext>Will GIMP finally get support for masks ?</tokentext>
<sentencetext>Will GIMP finally get support for masks?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073808</id>
	<title>I hope it will work better on osx</title>
	<author>shadowrat</author>
	<datestamp>1265737980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I hate having to click a window once to bring it into focus, then again to select something within it.

<br> <br>
Hopefully if it's all one window it will bypass osx's quirky window focusing behavior.</htmltext>
<tokenext>I hate having to click a window once to bring it into focus , then again to select something within it .
Hopefully if it 's all one window it will bypass osx 's quirky window focusing behavior .</tokentext>
<sentencetext>I hate having to click a window once to bring it into focus, then again to select something within it.
Hopefully if it's all one window it will bypass osx's quirky window focusing behavior.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31083348</id>
	<title>Re:Much more important features missing</title>
	<author>jcupitt65</author>
	<datestamp>1265019000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
All these features are coming with GEGL. Hopefully, just another year.</p></htmltext>
<tokenext>All these features are coming with GEGL .
Hopefully , just another year .</tokentext>
<sentencetext>
All these features are coming with GEGL.
Hopefully, just another year.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071394</id>
	<title>Nice to have the choice.</title>
	<author>LaminatorX</author>
	<datestamp>1265727600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Multi-window is nice if you've got a ginormous wide-screen or multiple monitors.  Multi-window on a smaller screen, or god forbid a laptop, is a real pain unless you live in it day-in day-out.  Kudos for letting users choose the right tool for the job.</p></htmltext>
<tokenext>Multi-window is nice if you 've got a ginormous wide-screen or multiple monitors .
Multi-window on a smaller screen , or god forbid a laptop , is a real pain unless you live in it day-in day-out .
Kudos for letting users choose the right tool for the job .</tokentext>
<sentencetext>Multi-window is nice if you've got a ginormous wide-screen or multiple monitors.
Multi-window on a smaller screen, or god forbid a laptop, is a real pain unless you live in it day-in day-out.
Kudos for letting users choose the right tool for the job.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071520</id>
	<title>Re:I love Gimp... but not on OS X</title>
	<author>kidgenius</author>
	<datestamp>1265728140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Besides the obvious graphical shortcomings (doesn't use Cocoa), you also have to click in each window first to activate it, then you can select your tool, activate your layer or what have you. This is so non-intuitive, and so not part of the usual routines, that I just don't use Gimp anymore on OS X.</p></div><p>That's actually quite easy to fix.  There is an option in the xserver on how to change that behavior.  It ticked me off to no end also.

defaults write org.x.x11 FocusFollowsMouse -string YES

Type that into the terminal and you should be good. (it was the 4th hit on google btw)</p></div>
	</htmltext>
<tokenext>Besides the obvious graphical shortcomings ( does n't use Cocoa ) , you also have to click in each window first to activate it , then you can select your tool , activate your layer or what have you .
This is so non-intuitive , and so not part of the usual routines , that I just do n't use Gimp anymore on OS X.That 's actually quite easy to fix .
There is an option in the xserver on how to change that behavior .
It ticked me off to no end also .
defaults write org.x.x11 FocusFollowsMouse -string YES Type that into the terminal and you should be good .
( it was the 4th hit on google btw )</tokentext>
<sentencetext>Besides the obvious graphical shortcomings (doesn't use Cocoa), you also have to click in each window first to activate it, then you can select your tool, activate your layer or what have you.
This is so non-intuitive, and so not part of the usual routines, that I just don't use Gimp anymore on OS X.That's actually quite easy to fix.
There is an option in the xserver on how to change that behavior.
It ticked me off to no end also.
defaults write org.x.x11 FocusFollowsMouse -string YES

Type that into the terminal and you should be good.
(it was the 4th hit on google btw)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078044</id>
	<title>Re:Forget the UI, change the name</title>
	<author>Anonymous</author>
	<datestamp>1265710620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>All that's wrong with the name is it should have been GINP - <i>GINP Is Not Photoshop</i>. That might have helped.</p><p>After that, I don't care. If anything am troubled by alleged adults who display schoolyard inflexibility over a project's name. But even that carries the advantage of marking them out to be respected less and avoided more.</p></htmltext>
<tokenext>All that 's wrong with the name is it should have been GINP - GINP Is Not Photoshop .
That might have helped.After that , I do n't care .
If anything am troubled by alleged adults who display schoolyard inflexibility over a project 's name .
But even that carries the advantage of marking them out to be respected less and avoided more .</tokentext>
<sentencetext>All that's wrong with the name is it should have been GINP - GINP Is Not Photoshop.
That might have helped.After that, I don't care.
If anything am troubled by alleged adults who display schoolyard inflexibility over a project's name.
But even that carries the advantage of marking them out to be respected less and avoided more.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074010</id>
	<title>Fix it.</title>
	<author>clone53421</author>
	<datestamp>1265738640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I love having a free alternative to PhotoShop. I really do. GIMP does well and I&rsquo;m satisfied with it.</p><p>The interface, however, did need improvement. I would almost say it was awful.</p><p>In version 2.6, every toolbox was its own window. This cluttered your taskbar, but it&rsquo;s nice to be able to have them off to the sides while working on your image. Of course, to minimize/restore GIMP, all of the toolboxes had to be minimized separately and restored separately, which was a hassle.</p><p>Somewhere after 2.6.0, they changed the toolbox windows into non-standard windows that didn&rsquo;t have minimize buttons. I hated this. As soon as you need to get to an icon on the desktop (which is conveniently positioned near the edge of the screen where you can hit it as long as nothing is maximized), the toolbox is covering it, and the toolbox won&rsquo;t go away. You have to slide the toolbox to somewhere else to get to the icon, and put it back afterward.</p><p>It had a very irritating flaw, though: some hotkeys only work when an image window is selected. If you click a layer or tool and then hit the hotkey, nothing happens. You have to click the title bar of the image window before the hotkey will work again. I wish they would fix this. (I can&rsquo;t reproduce it in 2.6.0, so maybe they introduced this glitch at the same time they changed the window type of the toolboxes.)</p><p>My own personal two cents:</p><ul> <li>Toolbox windows should not have taskbar buttons. Image windows should.</li><li>Toolboxes should be always-on-top dialogs that are <em>visible only when the application has focus</em>. When I minimize GIMP, or click the desktop, or Word, or Firefox... all of the GIMP toolboxes should go away! But when GIMP has focus, all of the toolboxes should be visible, on top, where I can get to them.</li></ul><ul><li>Make the hotkeys work globally (no matter which GIMP window or dialog has focus, hotkeys should act on the last image that was selected &ndash; the one which is being inspected in the layers, channels and paths toolbox).</li> </ul><p>These few improvements alone would be a vast improvement in the interface. I really can&rsquo;t think of a way to improve on the interface any further if they would just do these things.</p></htmltext>
<tokenext>I love having a free alternative to PhotoShop .
I really do .
GIMP does well and I    m satisfied with it.The interface , however , did need improvement .
I would almost say it was awful.In version 2.6 , every toolbox was its own window .
This cluttered your taskbar , but it    s nice to be able to have them off to the sides while working on your image .
Of course , to minimize/restore GIMP , all of the toolboxes had to be minimized separately and restored separately , which was a hassle.Somewhere after 2.6.0 , they changed the toolbox windows into non-standard windows that didn    t have minimize buttons .
I hated this .
As soon as you need to get to an icon on the desktop ( which is conveniently positioned near the edge of the screen where you can hit it as long as nothing is maximized ) , the toolbox is covering it , and the toolbox won    t go away .
You have to slide the toolbox to somewhere else to get to the icon , and put it back afterward.It had a very irritating flaw , though : some hotkeys only work when an image window is selected .
If you click a layer or tool and then hit the hotkey , nothing happens .
You have to click the title bar of the image window before the hotkey will work again .
I wish they would fix this .
( I can    t reproduce it in 2.6.0 , so maybe they introduced this glitch at the same time they changed the window type of the toolboxes .
) My own personal two cents : Toolbox windows should not have taskbar buttons .
Image windows should.Toolboxes should be always-on-top dialogs that are visible only when the application has focus .
When I minimize GIMP , or click the desktop , or Word , or Firefox... all of the GIMP toolboxes should go away !
But when GIMP has focus , all of the toolboxes should be visible , on top , where I can get to them.Make the hotkeys work globally ( no matter which GIMP window or dialog has focus , hotkeys should act on the last image that was selected    the one which is being inspected in the layers , channels and paths toolbox ) .
These few improvements alone would be a vast improvement in the interface .
I really can    t think of a way to improve on the interface any further if they would just do these things .</tokentext>
<sentencetext>I love having a free alternative to PhotoShop.
I really do.
GIMP does well and I’m satisfied with it.The interface, however, did need improvement.
I would almost say it was awful.In version 2.6, every toolbox was its own window.
This cluttered your taskbar, but it’s nice to be able to have them off to the sides while working on your image.
Of course, to minimize/restore GIMP, all of the toolboxes had to be minimized separately and restored separately, which was a hassle.Somewhere after 2.6.0, they changed the toolbox windows into non-standard windows that didn’t have minimize buttons.
I hated this.
As soon as you need to get to an icon on the desktop (which is conveniently positioned near the edge of the screen where you can hit it as long as nothing is maximized), the toolbox is covering it, and the toolbox won’t go away.
You have to slide the toolbox to somewhere else to get to the icon, and put it back afterward.It had a very irritating flaw, though: some hotkeys only work when an image window is selected.
If you click a layer or tool and then hit the hotkey, nothing happens.
You have to click the title bar of the image window before the hotkey will work again.
I wish they would fix this.
(I can’t reproduce it in 2.6.0, so maybe they introduced this glitch at the same time they changed the window type of the toolboxes.
)My own personal two cents: Toolbox windows should not have taskbar buttons.
Image windows should.Toolboxes should be always-on-top dialogs that are visible only when the application has focus.
When I minimize GIMP, or click the desktop, or Word, or Firefox... all of the GIMP toolboxes should go away!
But when GIMP has focus, all of the toolboxes should be visible, on top, where I can get to them.Make the hotkeys work globally (no matter which GIMP window or dialog has focus, hotkeys should act on the last image that was selected – the one which is being inspected in the layers, channels and paths toolbox).
These few improvements alone would be a vast improvement in the interface.
I really can’t think of a way to improve on the interface any further if they would just do these things.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074576
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071520
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31076878
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072278
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31080522
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31075690
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073808
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072430
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073034
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071318
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31070992
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071616
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31086954
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071318
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31070992
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074320
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072106
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31083348
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074864
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071228
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072256
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072116
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072230
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071228
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078044
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072288
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31081726
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072698
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078468
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31077186
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072274
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071698
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072250
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074640
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_02_09_027217_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071698
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072274
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074010
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071008
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071394
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071436
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073610
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071148
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073808
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31075690
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073460
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071856
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072316
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071162
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074640
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071520
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071616
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071550
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074320
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071876
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072256
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072430
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31083348
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072278
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31081726
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31080522
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072698
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071178
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31070992
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071318
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073296
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31086954
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071228
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074864
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072230
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071590
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072770
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_02_09_027217.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31071766
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31074576
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072288
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073800
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31077186
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072116
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072250
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072242
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078044
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31073034
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31078468
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31072106
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_02_09_027217.31076878
</commentlist>
</conversation>
