MAR
25
2001

Kernel Cousin KDE Issue #3 is Out

This week in KC KDE, Aaron J. Seigo summarises 10 threads, including coverage of the new powerful Kant editor in kdebase, Palm Pilot ioslaves, KDE sockssupport, a new font selection widget with font previews, and more. Get your fix here.

Comments

Good stuff as usual. This issue seems to be missing the archive links though.... ;)


By KDE User at Sun, 2001/03/25 - 6:00am

Yes, I forgot to include the archive links. Will do so in Issue #4 (or maybe i'll start a tradition and only put them in even numbered issues?).

I forgot it was Friday until somewhere around midnight. Seeing as I try and get the new issue in sometime around noon Saturday and I do most of the actual writing Friday, I was a bit behind and rushed. And in the hurry, guess what I missed? blah.


By Aaron J. Seigo at Sun, 2001/03/25 - 6:00am

Thanks for your hard work! I'm enjoying the results.


By kdeFan at Sun, 2001/03/25 - 6:00am

There seems to be discussion of getting rid of KWrite.. While I totally agree that Kant shld replace KWrite, why isn't Kant being renamed to kwrite??? Think of those millions of users of KDE who are used to Ctrl-F2 kwrite ! When will they know of kant? and if kant is sucessor of kwrite, then why not rename kant to kwrite...

And "kant" means what?? its such a non-obvious name for an editor!

If you agree with me, please write to the authors to make this point.. KDE shld keep strict naming of its popular products.

One more application is kbear.. why isn't it called kftp? Why was ktop renamed? It seems KDE is moving away from obvious names and putting in names which are most difficult to remember!

sarang


By sarang at Sun, 2001/03/25 - 6:00am

Ctrl-F2 kwrite

OOPS.. i meant Alt-F2 kwrite ;)


By sarang at Sun, 2001/03/25 - 6:00am

There will be a "kwrite" frontend to "kant" as far as I know to keep backwards compatibility.


By KDE User at Sun, 2001/03/25 - 6:00am

I don't mind having all of kant's functionality in kwrite.. there is no need to keep the current kwrite as it is.. thats why i am suggesting to rename kant to kwrite.. Those who need a simple editor always have kedit!


By sarang at Sun, 2001/03/25 - 6:00am

the idea seems to be that KWrite will remain a "seperate" program... basically just kant w/out all the kant stuff =) (a shell for the kantpart editor, really) ... it will even still be referred to as KWrite (for now)

Kant (i think named after the philosopher?) will have the light-ide type bells 'n whistles (project management, etc...)


By Aaron J. Seigo at Sun, 2001/03/25 - 6:00am

There's also the point that Kant is a swear word in London (cockney pronunciation of c*nt), so will probably cause a few snickers dahn sarf.


By rogue at Sun, 2001/03/25 - 6:00am

"There's also the point that Kant is a swear word in London (cockney pronunciation of c*nt), so will probably cause a few snickers dahn sarf."

Poor old Immanuel.
I don't think this name can be used for pronounciation reasons.

Northern Europeans should only use the name "KWrite" in the presence of people with english as their native language. The developers have probably only communicated in writing.


By reihal at Sun, 2001/03/25 - 6:00am

Erm, being from london, I can assure you that
Kant is *not* going to get mixed up with c*nt.

So shut it! ;-)


By RObert at Mon, 2001/03/26 - 6:00am

this has got to be the most idiotic discussion i've read in a long time


By khunt at Tue, 2005/12/06 - 6:00am

Hi,
I am the maintainer of Kant/KWrite and have some notes:
1. An old KWrite style app using KantPart will still exist for all users who love the old KWrite app :)
2. Renaming Kant to KWrite seems not to be such a good idea, Kant is much more than KWrite (I don't really know how Kant is pronounciated, sorry).
3. I am open for other nice names ;)
4. Kant has a plugininterface and all extended features like project stuff, ... are moved to plugins (Kant shouldn't be an IDE, but plugins can make it to whatever you want ;)

cu and thx for the nice feedback


By Christoph Cullmann at Wed, 2001/03/28 - 6:00am

Your Kernel Cousins are so darn good, Aaron! I'm glad, not only because there _is_ a KC KDE, but because they are so nicely put together.


By matt at Sun, 2001/03/25 - 6:00am

I can only agree, they are a great summary of what's going on, nicely put together.

Thanks a lot, Aaron.


By Carsten Pfeiffer at Sun, 2001/03/25 - 6:00am

Will the font selection widget have support for displaying the last few fonts you've selected at the top of the list?


By Carbon at Sun, 2001/03/25 - 6:00am

No! I hate that. At least the way MSWord does it. Having the same font in two places in the same list is nothing but bad UI, IMHO.


By matt at Sun, 2001/03/25 - 6:00am

Sorry, but I have to disagree. Normally, I only use about 3 fonts in my normal texts. Picking those out of a list of approx. 50 or s.th. is a hassle. But once used, I can switch between those fonts easily with the top 3 entries of the font selection box, disregarding the rest of the list.

Thanks a lot for KC. Helps a lot to keep up with the latest development when you don't have the time to read the mailing lists. Chris


By Chris Naeger at Sun, 2001/03/25 - 6:00am

I can see your point about it being bad interface design, but it does save lots of time. If I'm typing a report in msword, I tend to use symbol and times, nothing else. If I have to go down the list to select these two each time, it's a pain.

How about the font selection widget shows fonts in use in the document at the top, and then you must click on 'other fonts' to show a complete list of fonts or something. That cleans up the UI design and maintains the advantage for those of us who like to have currently used fonts at the top.

Paul


By Paul Mitcheson at Sun, 2001/03/25 - 6:00am

I like this idea the best. This would really get rid of all the problems that MS word has, please dont add YAOTTOTF (yet another option to turn on/off this feature). that just makes the UI too overwhelming...

really though, It would be nice to see one of the 2 suggestions implemented. It would be a huge time saver.


By anon at Sun, 2001/03/25 - 6:00am

"I can see your point about it being bad interface design, but it does save lots of time."

I submit that an interface that makes a common task take longer than it has to is an example of bad interface design. If the problem is having the same font listed more than once, why not simply move the most recently used font entries to the top of the list? That breaks "alphabetical order", but if the user is looking for one of the fonts that is out of order they will be immediately apparent at the top of the list.

Kyle


By Kyle Haight at Sun, 2001/03/25 - 6:00am

The big thing here seems to be the problem with listing something in two places, and breaking alphabetical order. How about this : The last 5 or so used fonts will be highlighted, (but remain in their location in the klist) and the tab order will jump to those fonts before going on to the next ones?


By Carbon at Mon, 2001/03/26 - 6:00am

Even better, how about having the font size and decoration remembered on "OK" or "Apply", and having a *completely seperate* drop down of the recently used (most commonly used?) fonts.

For instance, I often use 18pt Times New Roman Italic, 11pt Arial Bold, 11pt Times New Roman and 10pt Courier New Bold. If the dialog could remember those four settings and allow me to pick them quickly (with size and other formatting settings), then it would not only save me picking out from the list of fonts, it would also save me clicking option boxes and setting point size.

And yes, often this should be done with styles, but even I, who use styles all the time, often just set the font manually for letters or memos.

--
Evan


By Evan "JabberWok... at Mon, 2001/03/26 - 6:00am

I'm not sure I follow. What dialog? What OK or Apply?


By Carbon at Mon, 2001/03/26 - 6:00am

Hmm, just compared the idea I submitted earlier below, and I have to say I like your idea better. Espeically, since it displays the font's currently in the document, instead of the last few selected, you can quickly open a new document, and immediately see which fonts are in use throughout the entire thing. Also, how about expanding this quick list to also include font sizes? Could this be done properly at all?


By Carbon at Mon, 2001/03/26 - 6:00am

Why not have 2 pull down menus 1 with all the fonts in alphabetical order another with the last 5 used.


By robert at Mon, 2001/03/26 - 6:00am

I'll admit that I've liked this feature when I've been forced to use Microsoft Word, but I really prefer the approach used in FrameMaker, which allows the user to define character styles that include font, size, color, and probably other characteristics (it has been awhile since I've used FrameMaker and I don't have access to a copy right now). I've found that with a good selection of paragraph and character styles in a FrameMaker document or template, I very seldom need to use the font selection menu, and it has the added advantage that if I want to change the font associated with a particular style throughout the document, I can apply the change to all uses of that style without searching through the document to find where it was used.


By Allen Crider at Mon, 2001/03/26 - 6:00am

You mean that we would include the style definition as part of the document? That sounds like a good idea, then, say, a business could build templates and include the sizes and fonts they want their employees to use as a part of the document.


By Carbon at Tue, 2001/03/27 - 6:00am