April 26th 2013 : Latest Releases - posted by Dean
Yeah, I've been slack. I've been doing other projects as well as lots of personal things. My wife and I are going through an adoption currently and I've picked up whitewater kayaking as a hobby as well as learning to play the guitar. So, I've spent a lot of my free time doing these things.
However, if you would like the latest releases including bug fixes, please checkout the source from GitHub. There are instructions on how to get the content and compile it on that page.
Pretty much, all you need to do is this:
git clone --recursive https://github.com/deanproxy/eMail.git
October 31st 2010 : New Version! - posted by Dean
Version 3.1.3 has been released. It has some minor bug fixes that have been introduced in the repository over the last few months. Keep in mind that the repository over at GitHub has the latest fixes and it is open for anyone to commit changes to. So, if you have a patch or something, fix it up and throw it in the repo at Github!
September 20th 2010 : Now on github.com - posted by Dean
Today eMail was moved to github.com. You can find the project here.
I am hoping that this will open some collaboration and since it is read/write, allow the open source community to make the project better.
So, start writing some code for it already!
November 1st 2009 : Groovy? - posted by Dean
So, I was considering ruby fir the porting language, but after a recommendation, I'm now thinking of going with Groovy. This all depends, however. I want good IDE support for it and while I was granted an open source license for a great ruby/rails IDE called RubyMine, their groovy support is in their larger IDE and I'm not sure if I qualify for it. However, I'm applying and we will see. As for using Eclipse, well, have you looked at the support fir groovy? Terrible.
So, I am submitting the application and we will see... Groovy it may be...
October 28th 2009 : Porting and name changing... - posted by Dean
So, over the years I have really started to part ways with the C programming language. I use it at work mostly but I have been using other more modern languages such as Java, Ruby, etc... Everytime I go back to writing C, I think to myself "This would be so much nicer in language, well... any other language than C"
For a program such as eMail, things would not only work better (in my opinion), but it would be easier for me to develop in a more modern language. I'm continuously getting feature requests and bug reports from everyone and I feel that I would be better suited to tackle these features in a modern language.
Also, let's face it, this is an open source project and quite honestly has always been out there not just to benefit the end user, but to expand my knowledge in my down time. This project has been going on since 2001 and I have learned a lot of neat things along the way, but these days, there are newer and brighter things to be learning.
While I don't have any issues with C Programming for certain purposes, I just feel it's time for me to learn more modern languages and with my recent trails with Ruby, I have become very excited by it. It is an outstanding language and I would like to begin porting to this language in my spare time.
A lot of people may suspect that this is a bad move. I obviously don't see it that way. Sure, Ruby is interpreted, it's slower, etc, etc... But the benefits is that I spend less time code, more time adding features and testing and the time I do spend coding, I actually enjoy it because I'm avoiding all of the boilerplate coding that I have grown to dislike in C (and even Java). I also believe that the resources used by the ruby interpreter aren't going to cause any issues... or at least it hasn't on my small server box (only 512M of memory and a 1.2Ghz processor) for all of the ruby apps (including many rails apps) I have running on it.
With that being said, I have decided to port eMail to Ruby. If you would like to discourage me in doing so, please let me know what you think and why it would effect you. I will be leaving the C code in its current state in the repo as well as having a release available. I plan on continuing bug fixes on the C version for a while (probably not always, of course) but new features will be implemented in the Ruby version. I will also move the C version over to a Git repo at some point.
On another note, I am going to change the name of the project as well. I've had many complaints about the name over the years but I'm a stubborn man and can't seem to figure out a good name for it. I'm still not sure what I'm going to rename it to... but when the Ruby port happens, it will happen under a new name. Stay tuned.