Slashdot Mirror
More on KDE Groupware
e8johan writes "The KDE PIM Team will integrate all their applications into one common interface and create an Outlook-like application.This is being done in the Kroupware project commissioned by the German government. There is a prototype of KOrganizer with KMain embedded into it (shots 1, 2), and another prototype with KMain running as a KPart in Kaplan (shot 1, 2, 3). This looks hopeful and if they manage to build the application as flexible and modular as other KDE projects this will hopefully mature into something great." Kroupware is a catchy name, but I wonder if the KDE team is aware of the English word croup.
I've been seeing people say 'this is the last step' or similar things, about some type of 'outlook killer' app for Linux. It won't be the last step. By the time there is something that is workable/usable for the majority of companies, there will be some other roadblock/obstacle which people start saying 'we have to have or we can't switch'. I'm not saying I necessarily even know what that is at this point, but it'll happen.
First it was web browsers.
Then an office suite.
Now an 'outlook' killer.
What next? `
Personal security/prefs setting ala 'passport'? Though that hasn't seemed to have taken off as pervasively (or publicly) as might have been. Honestly I can't think of what it might be, but there'll no doubt be some other area of corporate culture MS gets embedded into quickly, which will take years to wean people away from (if in fact they want to get weaned away - if it works for them, just let it be).
creation science book
If we all stopped at the point where somebody says "It's been done before" we wouldn't have Linux, KDE or GNOME and I'd be posting to /. in IE.
Why not compete? I bet with a little pride on the line, Kroupware and Ximian could take turns leap-frogging each other, possibly resulting in having TWO products that outstrip Outlook!
Height: 38U, Weight: 0 Newtons, Eyes: #0000FF, OS: Gray Matter 1.0 (Alpha)
Is it the governments job to take tax-money payed by all of us and put them into projects that competes (unfairly) with the products we make?
Is the government supposed to squander our tax money on over-priced software produced by a company constantly in court due to anticompetitive business practices and abuse of its monopoly? I see where you're coming from but it's not that simple. Frankly I'd rather compete against open source apps in a truly open market than compete with microsoft.
What makes you think that twice as many developers on one app will make that app come out twice as fast or twice as good?
.NET - they are putting *everything* behind it - if they drop the ball with it, it isn't going to work. If we fuck up (*cough cough* united linux *cough*) at least we have other distros/apps/forks/etc to fall back on.
And what if all the developers work on one app and it sucks? The net result is we will be even further behind Outlook. If we have two or more projects in development at least if one sucks, others will come out on top.
We have that much over Microsoft - if they fuck up, they're fucked. Look at
Robots are everywhere, and they eat old people's medicine for fuel.
The different "modules", i.e. the mailer part, the calendering part, etc, are implemented as KParts. This means that you will be able to specify which KPart you want to embed for what functions (similar to how you can choose which text editing widget you want to use, KVim as Konqueror's textarea anyone?).
:)
It also means it is mostly "just" a shell around existing components, not another re-invented wheel. Not more bloated than running the components seperately (probably less overhead even, because you only need one KApplication instance).
In a sense it is tying existing technologies together (think back-end here too, using Open Source tech) into a slick package.
You don't *have* to use it, but corporate settings will probably like it.
As for your tax money (you live in Germany?) paying for the development, would you rather see the money go to Microsoft and get a product in return which will need upgrading eventually? Oh, and *you* personally don't get anything out of it, whereas now you get to use this development to your heart's content. And even if you don't like to use it personally, you'll be able to deploy it for your clients so they can at least use open technology).
To loosely quote Miguel de Icaza: it's not about making money, it's about *solving the problem*.
Personally, I'd happily pay 1% extra taxes to Germany (and I don't even live there!) to be used on similar projects because they benefit *everyone* (read below before you say "except software companies").
You see, times change. It used to be good business selling boxed software, but it's becoming less and less so. The trick now lies in providing a *service*. There will always be a need for skilled IT people, but to provide services, not simply products. I.e. a company specifies what their infrastructure needs to do, what requirements there are, etc, and you implement it using open source technology. There are no purchase or license fees (apart from specialised high-end software) and the value is in how well you set things up. It works for me
I dont ever need to use two PIM client (outlook clone) that has identical functionality but with two different set of configuration files and stores my information differently.
Oops. I forgot to comment on this. I agree with you here - we need a standard format (open good, standard better). Different apps, same storage format. Ain't gonna happen but it would be nice.
Robots are everywhere, and they eat old people's medicine for fuel.
Nonsense! They've already invented words like 'kmail', 'killustrator', and now 'kroupware'. They've just begun!
do not read this line twice.
While you definately have a point, it's also the developer's choice. Most KDE development is in framework, i.e. you can embed the Kmail component into Kaplan. The requirement for this is that the component was designed with this framework in mind, or is ported to do so.
Application development with KDE is fast, because you get to build on a great framework with many components to choose from.
There is very little duplicate code in KDE, although much of the KDE code does the same as similar code in other projects. What you have to remember is that this KDE code can be plugged into any other KDE program, and KMail for example is a shell for the (now) KMail component which is built on SMTP, POP, IMAP, etc kio-slaves.
KDE's architecture is very advanced, and very well planned. To make full use of it, it needs to be considered from the start. Hence re-doing something for KDE as opposed to slapping KDE menu's on an existing program.
The reason KMail is part of KDE is that any KDE app can embed and control KMail components and vice versa. If you need IMAP in your application, it's trivial to add it.
The reason Xchat is part of Gnome is that it uses Gtk and some other Gnome libs. If you want to include IRC in your Gnome app (along with all Xchat functionality), is it also trivial?
There's a difference. And no this does not say anything about wether Gnome or KDE is better, bless both projects. I'm just pointing out there *are* others reasons than NIH.
As much as I hate Microsoft and dislike Outlook, I must admit that the meeting planner in Outlook is a "must have" application in business.
The one serious flaw in the planner is the human factor. All too often people wouldn't keep their calendar up to date or wouldn't bother to reply to a meeting notice.
-- Will program for bandwidth