Slashdot Mirror
Evolution 0.99, Release Candidate Out
savaget writes "Evolution 0.99 (Release Candidate 1) is out!
"Yes, you read that right: the release candidate for Evolution 1.0 hit the wires this evening. After two years of hard work and more than 700 thousand lines of code written, the sleepless hackers at Ximian are finally getting to the long-awaited 1.0 release of Evolution, the GNOME groupware suite."" One of the most important projects in the open source world today. Best of luck to the monkey boys @ Ximian squashing any last minute arrivals.
Full annoucement here
http://www.ximian.com/products/ximian_evolution/
http://www.ximian.com/products/ximian_evolution/
So, as noted:
- In this build only, Palm-OS sychronization is temporarily disabled. It will return in the next release.
- Under certain rare circumstances, IMAP connections over SSL can hang Evolution. We expect to have this issue resolved shortly.
Just in case these things are important to you.
"It is a greater offense to steal men's labor, than their clothes"
Hmm, I've found Evolution to be far more stable and usable than KMail. In particular, Evolution's IMAP support is superb. KMail, despite claims to the contrary, does not seem to be happy with large IMAP folders at all, and I have watched it crash and burn once or twice, but it was really the extremely slow startup time while rechecking the entirety of my large IMAP folders. It's just too damned slow on startup. I have used it just fine with POP in the past though, I just think it has a ways to go on the back end support before it is as good as Evolution.
Ok, BIG difference. With Pop3 you simply download the email into a local folder. With IMAP the emails stay on the server and you are browsing folders remotly. A goot IMAP client with make local copies of the mail also, so that you don't have to redownload everytime you want to look at a piece of mail. Think Webmail, without the web :)
Why do people insist on posting bug reports to slashdot? If you want your issue to be addressed, there's a proper forum for that.
pop3 is a _very_ simple protocol that allows mail to be read, retrieved, or deleted from a server by a client. It's a had a few features added in later days, and might support simple management like password changing, but that's about it.
The main weakness of pop3 is that it treats the server end as a dumb, unorganised list of messages, and expects all cleverness (mailboxes, sorting, filtering, etc) to be done client side. This means it is a pain to change clients, and nearly impossible to manage one mail account from two clients (e.g. one at home, one at work).
The main strength of pop3 is that it works.
IMAP is a protocol that allows a client to manipulate a server side data store. All the useful information (what messages are read, which folders they are in etc) is on the server, so if you change IMAP clients, all the data is just read of the server, and away you go.
However, AFAIK IMAP is a rather complex protocol. I have never come across a client that implements it very well, all of them struggle with large numbers of messages, handling of attachments and so on. In addition, it's still possible for a client to implement client-side only add-on features that are then incompatibile with other IMAP clients.
Outlook is the only client I've used that seems to handle server-centric email well, and it probably does with in proprietary extensions. Of course Outlook's handling of SMTP is rather dire, but hey.
-----
Yes, you could build and run Evolution under Windows, but currently ONLY under Cygwin + an X11 server (this is still local on the Windows box). A Cygwin setup can be accomplished by a newbie. See links below for running GNOME under Cygwin on a Windows box.
Much of GNOME will not build natively, although the libraries themselves are designed to be portable, and GTK is working just fine as Win32 (see GIMP).
There are two kinds of Windows ports... X11 display based, and true "native" Win32. The former is easy to do; the latter is not yet possible (tho you can help!). It's likely that a "native GNOME for Windows" will be much easier, once GTK 2.0 is released.
Links regarding running GNOME or compiling under a local X11 display:c ygwin.html
http://news.gnome.org/976323862/index_html
http://xfree86.cygwin.com/screenshots/
http://www.geocities.co.jp/SiliconValley/1596/en/
From the GNOME FAQ, regarding native GNOME for M$ Windows:h tml
http://canvas.gnome.org:65348/gnomefaq/html/x359.
A lot of people want to port GNOME and GTK apps over to Windows. To conquer the enemy they say, you have to enter their territory, then sway them to your culture (OS). ;-)
Without symbols, I'm told the main binary package is around 6 or 7 MB. This is still bigger than sylpheed, sure, but it also does calendaring, tasks, and addresbook stuff. So... take your pic.
IAAL,BIANLY
when will linux itself be come something that non-technical people can use
Last summer, my step-father, fed up with Windows, asked me what I use on my computers - I told him I use Linux (Slackware) and that I'd be happy to come over and install it, and show him how to use it. In August (without my knowledge), he went out and bought Mandrake 8. He wiped windows from the machine, and installed Mandrake.
He uses his computer every day to chat with friends, surf the web, do email, and maintain his journal. He's VERY non-technical, and had no problems using it at all.
When he used windows, I used to receive at least two "support calls" per month from him. When he installed Mandrake, I got a one call about the UI differences (icons in the "k" menu, instead of on the desktop), but since then, he's had no problems, and I have recieved no calls for support.
Judging from this, I'd say that Linux already is something that non-technical people can use - much more so than Windows.
>Heck, as far as a I know (And I could be really
>wrong here) it's not even like it loads modules
>or something like that. It's just one massive
>700,000 line program.
You're really wrong. Aside from being a mail and groupware client, Evolution has also been one of the primary testbeds for Bonobo.
The actual program itself is just a shell that loads components to do all the dirty work:
/usr/bin/evolution
/usr/bin/evolution-addressbook
/usr/bin/evolution-addressbook-clean
/usr/bin/evolution-addressbook-export
/usr/bin/evolution-addressbook-import
/usr/bin/evolution-alarm-notify
/usr/bin/evolution-calendar
/usr/bin/evolution-calendar-importer
/usr/bin/evolution-elm-importer
/usr/bin/evolution-executive-summary
/usr/bin/evolution-gnomecard-importer
/usr/bin/evolution-ldif-importer
/usr/bin/evolution-mail
/usr/bin/evolution-move-tasks
/usr/bin/evolution-netscape-importer
/usr/bin/evolution-pine-importer
/usr/bin/evolution-vcard-importer
First just a comment saying that C and OO approaches are not mutually exclusive. You can have an OO approach in C (as gtk does). It is ugly as hell, and really doesn't make things that much easier to maintain than traditional C code, but it is possible. Not really defending this, just saying OO can be implemented in practically any language, just some can do it better than others..
As to why it is still in C++, I'll guess to make it consistent with the rst of Gnome (obvious) Why was Gnome done in C? Probably partially out of language bigotry. But some somehwat more valid reasons:
1) Give programmers maximum choice. It is easier to call C libraries from C++ apps than vice-version. If it had been based in C++, the C wrappers would be needed for any functionality, while C++ can call native C code without problems (usually)
2) A belief that C++ cannot be as fast as C. There is a little bit of overhead in C++, somewhat blown out of proportion by anti-C++ people, and therefore people think C++ is inefficient. Not really enough of a performance problem to justify this, but it is an explanation.
3) To this day g++ has been wishy-washy with how C++ code should be compiled. With gcc-3, hopefully we are coming to the end of those days. libstdc++ has changed so many times in terms of ABI, that programs compiled for one distro have little hope of making it on another. For maximum binary and source portability, C code was, especially at the beginning of gnome, the only choice.
There may be others, but these occur to me right off..
XML is like violence. If it doesn't solve the problem, use more.
Apparently you've never read or even touched evolution.
Suppose Evolution split its calender and email (and whatever else it does) features into seperate smaller, efficient programs. Programs that "do one thing and do it well". Evolution Mail, Evolution Calendar, Evolution Addressbook, and so on could still totally interface with each other using, e.g., Unix pipes.
Evolution IS made up of many smaller programs that communicate through CORBA. I'm not sure how "splitable" they are, but from my work on the calendaring component, it's not impossible. (I've been working on Calendar printing).
Pan
I said no... but I missed and it came out yes.