Linked by David Adams on Tue 28th Sep 2010 21:58 UTC
Permalink for comment 443131
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2010-03-08
Mistake 2 : Well, I'm not sure that I agree with him on this one. He seems to disagree with use of the layer/selection/path paradigm in GIMP because it's too complicated and he thinks that it was only introduced for photoshop compatibility.
But there's a reason why photoshop is using this paradigm : though difficult to learn, it's powerful in the end. AFAIK, a UI paradigm for these tasks that's at the same time simpler and just as powerful has not been found yet.
Maybe the author means that GIMP should switch to a simpler paradigm (like that of MSpaint) at the expense of image editing power. But then I disagree : casual editing is not the main usage pattern envisioned by gimp designers, so they should remain consistent with that, even if it alienates casual users. Alas, software design is about choice.