Re: "Kooka and kmrml are removed completely."

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: "Kooka and kmrml are removed completely."
by Aaron Seigo on Tuesday 19/Jun/2007, @09:34

more than anything else, keep it simple. it doesn't need docks, it doesn't need galleries, it doesn't need a separate image viewer space ... simplicity. if the user wants all of those things, they can use gweview or krita. preview, crop/select, rotate and save: that's all that's needed.

second, do it fast. there were a number of things kooka tried to automate or handle "smartly" that made the app a bit slow.

third, don't try and manage the image results automagically. kooka tried quite bravely to keep automated galleries around. imho the scanner app should treat the scans as documents (think kate, kwrite, kword, etc) and not try and auomatically mange them.

that's just mho though, and to be fair i've used kooka for years and have got a lot of utility out of it. so it's a good app. but we can probably do even better by learning from it.

Related Links

·   Articles on Developer
·   Also by Aaron Seigo
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: "Kooka and kmrml are removed completely."
by MamiyaOtaru on Thursday 28/Jun/2007, @22:50

OK, I'll happily admit this is better than whining about kooka disappearing. If a better scanning app comes out of this it's a win.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"World domination doesn't come by itself." -- Ralf Nolden
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.