Re: Model KWrite after GEdit, keep Kate for geeks

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Model KWrite after GEdit, keep Kate for geeks
by A KDE advocate on Tuesday 15/Apr/2008, @15:33

Hey, why would someone use a text editor for notes while there is such a mind-blowing mighty world-domination like KDE's basKet? http://basket.kde.org/

Related Links

·   Articles on Community and Events
·   Also by A KDE advocate
·   Contact author

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

Re: Model KWrite after GEdit, keep Kate for geeks
by Matthew Woehlke on Tuesday 15/Apr/2008, @17:37

Well, that's obvious; because plaintext is very nearly the lowest common denominator of computer file formats and is useful on just about anything :-). (And if you forget devices with no basic text editor and the odd EBCDIC-speaking machine, you can pretty well remove the word "nearly" from that sentence.)

I should probably try basKet some day :-), but much of my jotting is still done on the Windows machine I have to have for various reasons.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by A KDE advocate on Wednesday 16/Apr/2008, @02:28

There are export functions included (HTML in 1.x) and I think it would be pretty easily to add a text export. A who said basKet can't be used on Windows machines? ;) It can import text-files, though.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Chaoswind on Wednesday 16/Apr/2008, @00:44

> Hey, why would someone use a text editor for notes while there is such a
> mind-blowing mighty world-domination like KDE's basKet?

Because, Basekt sucks. It's not easy, it's dosn't scale anywhere, it's to heavy and complicated. IMHO it's a protocase for a good idea, which is detroyd by simple usability sin's. Yes, it's useful, but that's plaintext-files also, and they are also independent from the application and platform, and more flexibel for things like scripting.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by A KDE advocate on Wednesday 16/Apr/2008, @02:32

In my opinion, basKet is easy to use and not at all complicated. If you have specific improvements in mind, why don't you at least file bugs or talk to the development mailling list?

There exists import and export functions (for non-world-dominated platforms) and it certainly could be improved as well.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Chaoswind on Wednesday 16/Apr/2008, @08:56

> In my opinion, basKet is easy to use and not at all complicated.

Every opinion is based on knowledge and preferences ;)

> If you have specific improvements in mind, why don't you at least file bugs or
> talk to the development mailling list?

While baskets development ist dead, afaik. Also, there was an project to improve the usability already, which will (of course) not be realized.

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Morty on Wednesday 16/Apr/2008, @13:07

Don't look dead too me.

http://basket.kde.org/news.php
http://basket.kde.org/svnaccess.php

[ Reply To This | View ]

Re: Model KWrite after GEdit, keep Kate for geeks
by Chaoswind on Thursday 17/Apr/2008, @08:53

> http://basket.kde.org/news.php

Nice, it's reanimated, again, in only seven short months.
Well, we'll see how useful the kde4-version will be.

[ Reply To This | View ]

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


		"Ok guys, I'll implement focus-follows-mind next time and ship a magic patch." -- Matthias Ettrich
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.