faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Sigh...
by Ian Monroe on Saturday 26/Jan/2008, @11:01
|
I'm quite glad that Dragon Player is in kdemultimedia, but the value of being in a KDE module is often overstated. For instance in KDE3, I guess under your theory Kaboodle was the official KDE video player. The reality is that most KDE-distros shipped Kaffeine as their default player. The KDE modules do serve as a way of raising awareness of KDE apps, especially within the project. But its mostly a form of release management.
Anyways don't knock Dragon Player until you've tried it. It has a simple user-interface, that's a lot different then being ultra-basic. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Sigh...
by gerd on Saturday 26/Jan/2008, @11:29
|
The name sounds really bad.
|
[
Reply To This | View ]
|
Re: Sigh...
by Peter on Saturday 26/Jan/2008, @11:45
|
name sounds bad? im happy to see a move away from Kthis and Kthat with KDE4. plasma, dolphin, amarok, phonon, dragon player, etc. etc. all show a move in naming, and its great. The Kapplications is not only ugly, also its inconvenient in menus to look through.
|
[
Reply To This | View ]
|
Re: Sigh...
by Anon on Saturday 26/Jan/2008, @15:24
|
Agreed that it's an improvement to drop the Kthis, Kthat, but "Dragon player" sounds like a game not a media application. Just "Dragon" would be fine though. Given there is some talk of applications being listed with descriptions in the menu listings, the extra descriptiveness isn't needed: it is "just a name" after all..
If the menus go that way, we'll have: "Dragon Player (Movie Player)" ...which is a bit redundant...
Kopete Chatter (IM Client)
Konqueror Browser (Web Browser)
Kmail Emailer (Email Client)
See what I mean?
Looks good, name aside.
|
[
Reply To This | View ]
|
Re: Sigh...
by Woe on Sunday 27/Jan/2008, @02:34
|
I think 'Dragon' itself is a good name, however the name is not that much of a problem. It is that Dragon by itself does not necessarily mean anything in terms of what the application can do, but I do not think a name should do that anyways. Consider how people of a given profession were addressed ever so long ago, a person could be "titled" John (Black)smith and while his name would 'John' his profession would be a blacksmith. The same could be applied here; the name is Dragon and the profession-if you will-is a media player so it could be titled Dragon media-player. That way people know what it does while giving it a unique name. Also for instances like the 'Kmenu' only the name would have to be displayed resulting in something like Dragon (Media Player) so no redundancy. :)
|
[
Reply To This | View ]
|
Re: Sigh...
by MamiyaOtaru on Sunday 27/Jan/2008, @13:20
|
Because it's really obvious what Okteta is for. KHexEdit was just too obscure.
Why K*appname* gets slammed when G*appname, i*appname* and Win*appname* get a relatively free pass is beyond me. I appreciate a name that tells me at a glance what it does, and for which OS/environment it is created.
I think the move away from such names it the latest mass hysteria to strike KDE, in the same vein as the widespread love at the time for Keramik. Given time, perhaps this move will be seen as something other than a bright idea, the same way Keramik was tossed into the junk heap.
|
[
Reply To This | View ]
|
Re: Sigh...
by olahaye74 on Monday 28/Jan/2008, @02:40
|
+1
in freshmeat, if an app name is unknown to me, then
if its name starts with a k I give alook at it as it is highly probable that it'll be a kde app that takes benefit of the integrated desktop.
else I skip as if it's a graphical app, it won't take benefit of the tight integration, thus: useless.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
