Nope, at least not here in Sweden... in fact, just the other day I wanted to take out money and couldn't because Dr. Norton had popped up and was waiting for someone to reboot. Luckily the grocery store where I buy my food accepts my bank card! ---
Re:Another Version ? I'M BEGINING TO FEEL SICK!
on
KDE 1.1.1 is out
·
· Score: 3
No one is forcing you to upgrade. Do you upgrade your Linux kernel everytime a new version comes out? Judging from your post, I'd say that you probably don't. There is no need to upgrade your kernel everytime a new release comes out, unless it fixes something that you have had problems with. If you are not having any problems with your KDE software, then there is no need for you to upgrade. If, on the other hand, there have been fixes that would benefit you, then you should upgrade.
It is all about choice, you have the choice to upgrade if you need to. With many other systems (such as Winblows) you do not have that choice. You are at the mercy of the company that sells the product to come out with a fix (called upgrade) for problems (sometimes very serious problems) with the product. Sometimes you may have to wait months, or even years for these fixes. I, for one, prefer the way that many Open Source projects work... release quickly and release often! ---
He doesn't have to, because they have agreed to place their code under Version X or later... so any new version could be applied without violating the initial license. ---
Last timne I checked the design was much more important than the actual code. You can teach a monkey to hack in code, but not many people can come up with a good design. ---
And how is Kedeh pronounced? I've already mentioned this several times, but I think it is very important that the name is easily remembered and easy to pronounce. This includes both native English speakers as well as people from other countries.
No offence to you Coolo, but I don't recall a vote on this yet on the mailing list. I really thing that kongi or kongy is a bad name... it makes me think of klunky! There has been some discussion and it appears that several people like this name, but there are also several other names being considered. Also, the fact that the new kfm is code named konqi I think this would be a bad idea. It would give the impression that this particular componenet IS KDE. But KDE is much more than that. The name of the mascot will have a large impact on the effect it will have on the public and I think that it is important that a name is chosen so that it is easy to remember and reminds them of something they would call a pet...
Personally I still like my original suggestion of "Puff":o)
The noble Dragon, perfect mascot for KDE!
on
KDE Gets a Mascot
·
· Score: 2
I know this is like a fish going after a worm on a hook, but I guess I'll bite...
Here is my response to your 3 points: 1) First of all I personally don't find KDE to be ugly. The opinion of one single person, however, is meaningless, so I guess I should also mention that the 150+ students in our department that use KDE on a daily basis also like it. The majority students that we have that also run Linux at home are running KDE as their desktop.
2) Again, refer to point 1 for a discussion of esthetics. As for resource use, I would have to argue that KDE actually does a very good job of using minimal resources for the amount of services that it offers. It obviously will consume more resources that a plain vanilla window manager, but KDE is not just a window manager, it is an entire desktop environment. It offers services such as drag and drop, integrated task bar, etc. I'm sure if you were to compare KDE with other systems with similar functionality you would see that KDE is no worse than the others when it comes to resource usage.
3) I personally use KDE, but don't see why there needs to be a "competition" between Gnome and KDE. There is no reason why the two can not coexist happily. Variety is one of the things that makes Linux so nice to use. KDE and Gnome have different design goals and focus on different areas. By having both KDE and Gnome there is a better chance that _both_ will be better. The exchange of ideas between the two projects can only improve the situation rather than making it worse.
Well, I probably should have just left the bait alone, but I snapped, so lets see if I get reeled in now.
I don't see why there needs to be any story behind it. It is cute and gives KDE a personality. Just like any other mascot does. Do you know why your highschool football team had a particular mascot? Did it matter why you had that particular mascot? When I went to college in the states our mascot was Vic the Demon which is kinda ironic considering the school originally started at as a school for nuns...
This is NOT a logo, it is a mascot!
on
KDE Gets a Mascot
·
· Score: 2
There are already several comments about the image saying it is too complex for a logo, or it is too for a logo... the fact is that this little guy (doesn't have a name yet) is NOT a replacement for the Gear logo used by KDE, in fact it isn't a logo at all. It is intended to be a mascot and as such does not suffer from the same constraints that a logo has.
Mirror plus announcement of Theme support...
on
KDE Gets a Mascot
·
· Score: 3
And in other KDE news. The first version of the KDE style plugin interface (aka Theme support) has been released. You can find more information about it here.
I had become a big fan of CORBA and the potential that it has. One of the things that I was anxiously awaiting was their new Component model. In my opinion the decision to drop language independence is a Bad Thing[tm].
I really hope they change their mind on this matter. I do agree with the article though that the proposal in its current state is just too large and complex. I guess that is one of the major drawbacks of design by committee, you end up with huge, bloated specifications... they should go back to the idiom of KISS.
Well, considering that was the price for OEM's to Beta test the product it isn't all that bad... once they start mass producing them the price would drop (otherwise they don't really have a chance at selling them).
Looks like they don't know how to spell kernel at Caldera. Check out their whitepaper and you will notice in the the bookmark list on the left that they missed this typo.
Also, the documentation contains several other typos... have they actual proofread this stuff? Besides the petty mistakes I am pointing out here, this looks like it could be a really nice distribution!
Bugging them doesn't seem to help. I've sent several emails to their tech support regarding my Quickcam VC that I also foolishly bought a while back. I actually sent the first email when it was still Connectix and have sent two since Logitech bought out the cameras. I have a REGISTERED product and never received a response from their customer support. The least they could have done was write me back saying, "Sorry, we have no plans to support you."
1) Not supporting Win 3.1 A lot of people still aren't running Win 95/Win98.
And you seriously think that a 3.1 user would WANT to use a program of this size? There would be no way to support 3.1 users and still make a product worth using for the rest of us. You can't go on supporting legacy platforms forever, that just results in worthless programs.
2) Trying to force people people to use GCC 2.8 to compile mozilla, especially Linux users. How many people actually have bothered installing it when you still can't really use it under Linux?
Just because you have problems getting gcc 2.8 to work for you, don't generalize for the rest of us!
Slashdot Mirror
Nope, at least not here in Sweden... in fact, just the other day I wanted to take out money and couldn't because Dr. Norton had popped up and was waiting for someone to reboot. Luckily the grocery store where I buy my food accepts my bank card!
---
... and it is called H.323. Check out http://www.openh323.org/.
---
No one is forcing you to upgrade. Do you upgrade your Linux kernel everytime a new version comes out? Judging from your post, I'd say that you probably don't. There is no need to upgrade your kernel everytime a new release comes out, unless it fixes something that you have had problems with. If you are not having any problems with your KDE software, then there is no need for you to upgrade. If, on the other hand, there have been fixes that would benefit you, then you should upgrade.
It is all about choice, you have the choice to upgrade if you need to. With many other systems (such as Winblows) you do not have that choice. You are at the mercy of the company that sells the product to come out with a fix (called upgrade) for problems (sometimes very serious problems) with the product. Sometimes you may have to wait months, or even years for these fixes. I, for one, prefer the way that many Open Source projects work... release quickly and release often!
---
Why is that so hard to believe? There are lots of servers that have never been upgraded simply because "if it ain't broke, don't fix it".
---
Hey CT,
:o)
Why not download the patches instead! (Of course,
I'm one to be talking since I'm connected to my school's network which has 100mbs to Sunet
---
He doesn't have to, because they have agreed to place their code under Version X or later... so any new version could be applied without violating the initial license.
---
Last timne I checked the design was much more important than the actual code. You can teach a monkey to hack in code, but not many people can come up with a good design.
---
And how is Kedeh pronounced? I've already mentioned this several times, but I think it is very important that the name is easily remembered and easy to pronounce. This includes both native English speakers as well as people from other countries.
Didn't you read any of the other posts? This is NOT a logo... it is a mascot. Read the previous posts for a full explanation why this matters.
Koffice is using XML.
No offence to you Coolo, but I don't recall a vote on this yet on the mailing list. I really thing that kongi or kongy is a bad name... it makes me think of klunky! There has been some discussion and it appears that several people like this name, but there are also several other names being considered. Also, the fact that the new kfm is code named konqi I think this would be a bad idea. It would give the impression that this particular componenet IS KDE. But KDE is much more than that. The name of the mascot will have a large impact on the effect it will have on the public and I think that it is important that a name is chosen so that it is easy to remember and reminds them of something they would call a pet...
:o)
Personally I still like my original suggestion of "Puff"
I know this is like a fish going after a worm on a hook, but I guess I'll bite...
Here is my response to your 3 points:
1) First of all I personally don't find KDE to be ugly. The opinion of one single person, however, is meaningless, so I guess I should also mention that the 150+ students in our department that use KDE on a daily basis also like it. The majority students that we have that also run Linux at home are running KDE as their desktop.
2) Again, refer to point 1 for a discussion of esthetics. As for resource use, I would have to argue that KDE actually does a very good job of using minimal resources for the amount of services that it offers. It obviously will consume more resources that a plain vanilla window manager, but KDE is not just a window manager, it is an entire desktop environment. It offers services such as drag and drop, integrated task bar, etc. I'm sure if you were to compare KDE with other systems with similar functionality you would see that KDE is no worse than the others when it comes to resource usage.
3) I personally use KDE, but don't see why there needs to be a "competition" between Gnome and KDE. There is no reason why the two can not coexist happily. Variety is one of the things that makes Linux so nice to use. KDE and Gnome have different design goals and focus on different areas. By having both KDE and Gnome there is a better chance that _both_ will be better. The exchange of ideas between the two projects can only improve the situation rather than making it worse.
Well, I probably should have just left the bait alone, but I snapped, so lets see if I get reeled in now.
I don't see why there needs to be any story behind it. It is cute and gives KDE a personality. Just like any other mascot does. Do you know why your highschool football team had a particular mascot? Did it matter why you had that particular mascot? When I went to college in the states our mascot was Vic the Demon which is kinda ironic considering the school originally started at as a school for nuns...
Here is another mirror: http://www.linuxbox.org/~sean/kde/
There are already several comments about the image saying it is too complex for a logo, or it is too for a logo... the fact is that this little guy (doesn't have a name yet) is NOT a replacement for the Gear logo used by KDE, in fact it isn't a logo at all. It is intended to be a mascot and as such does not suffer from the same constraints that a logo has.
dragon1.jpg
dragon2.jpg
dragon3.jpg
dragon4.jpg
And in other KDE news. The first version of the KDE style plugin interface (aka Theme support) has been released. You can find more information about it here.
I had become a big fan of CORBA and the potential that it has. One of the things that I was anxiously awaiting was their new Component model. In my opinion the decision to drop language independence is a Bad Thing[tm].
I really hope they change their mind on this matter. I do agree with the article though that the proposal in its current state is just too large and complex. I guess that is one of the major drawbacks of design by committee, you end up with huge, bloated specifications... they should go back to the idiom of KISS.
Well, considering that was the price for OEM's to Beta test the product it isn't all that bad... once they start mass producing them the price would drop (otherwise they don't really have a chance at selling them).
Qt is not a WM, Qt is framework for creating crossplatform applications. Checkout the Qt homepage
Also, the documentation contains several other typos... have they actual proofread this stuff? Besides the petty mistakes I am pointing out here, this looks like it could be a really nice distribution!
Bugging them doesn't seem to help. I've sent several emails to their tech support regarding my Quickcam VC that I also foolishly bought a while back. I actually sent the first email when it was still Connectix and have sent two since Logitech bought out the cameras. I have a REGISTERED product and never received a response from their customer support. The least they could have done was write me back saying, "Sorry, we have no plans to support you."
I've been using Google.com very happily for some time now. It has increased my research productivity by leaps and bounds!
And you seriously think that a 3.1 user would WANT to use a program of this size? There would be no way to support 3.1 users and still make a product worth using for the rest of us. You can't go on supporting legacy platforms forever, that just results in worthless programs.
2) Trying to force people people to use GCC 2.8 to compile mozilla, especially Linux users. How many people actually have bothered installing it when you still can't really use it under Linux?
Just because you have problems getting gcc 2.8 to work for you, don't generalize for the rest of us!
Comparing their format to PDF is like comparing apples and oranges, the two have nothing to do with each other.
// _Stryker
sean@sks-pc [17:56:52] /home/sean> whois microsoft.com
[rs.internic.net]
No match for "MICROSOFT.COM".