Evolution 2.0 Released, Screenshots

comforteagle writes "This seems to be slow getting out, but since Novell hasn't updated their site ... Evolution 2.0.0 has been released. Most importantly it has built in JunkFilter support with SpamAssassin, web calendars, and NNTP support. Oh, and some bugfixes. I've posted some screenshots today as well."

Comments

Remarkably

[Anonymous Coward]

Evolution 2.0 was created in a mere 7 days (with 1 of them being for rest).

Re:Remarkably

[EnronHaliburton2004]

I'm not sure I want to think about monkeys banging their typewriters...

Needs more cowbell.

[Anonymous Coward]

Actually, this looks so gray and bland compared to Outlook -- needs some color to spice it up -- even on the default theme.

New feature list...

[dmayle]

It wasn't in the new feature list, but Evolution 2.0 is the one that's supposed to include the GPL'ed Exchange connector, as well as support for Novell's mail server (I forget the name.)

Any Chance of

[mwagner_00]

Getting this ported to Windows??? I know alot more people would be using it if they did that.

_some_ screenshots

[Laxitive]

OSDir.com Apps Slideshow Back [ 2 of 84 ] Next

84? Yeah I suppose some people might refer to that as "some screenshots". May I suggest
"A fuck of a lot" as an alternate quantifier?

:)

-Laxitive

Re:Mono?

[oxymor00n]

Yeah, rewrite a whole application just for the sake of it. Good idea, really ;)

Document the EDS!!

[IGnatius T Foobar]

All this new configurability and extensibility in Evo 2.0 is great, but what I'd really like to see is some better documentation for the "Evolution Data Server" (basically the Camel and Wombat API's). Ximian/Novell are hoping that the community will be excited about writing "snap-ins" to extend Evo's functionality, but what about those of us who would like to, for example, connect it to other back-end data stores? There's a "connector" for Groupwise and a "connector" for Exchange ... what if I want to write a "connector" for some other groupware server? (I'm asking this question because I do want to do exactly that.) These API's are barely documented. You have to reverse-engineer the existing connector code to get anything done with it. I'd like to see some real docs.

But at what cost?

[Anonymous Coward]

It would be great for folks to realize that writing apps cross-platform is one of the single best ways to get TONS of adoption, and ease any eventual transitions to Linux.

Yes, but as OS's (like OS/2 fer instance) found out, having that application compatibility can be a double edged sword. You might ease the transition, but you also potentially negate one of the motivating factors as well as providing your competition (i.e. MS) with a marketing edge (why switch because you can still run your "free" apps on Windows) and (Windows has tons of Windows only apps, PLUS it'll run the open source apps that count).

Re:I use it, like it

[kundor]

If you want small apps that do one thing, you really should be using KDE. Gnome apps tend to be big monolithic things far more often, whereas with KParts, KDE is entirely made of small one-function apps that embed eachother.

Re:Kmail

[KeyserDK]

Yes, not inline(!) though. Which most other mailers seem to use.

Re:Linux apps on Windows

[daVinci1980]

God, I totally agree. I would use Evo in a heartbeat if it were available on Windows. (And no, I cannot switch, I develop products for x86/Windows).

To the other poster who suggests that it would not be possible, desirable, or easy to support cross platforms... That's total bunk. I used to develop commercial apps that ran on Windows, Linux, Mac/OS9 and OSX. It *does* require a bit more work, but in practice, it's actually not much more work than supporting one OS.