About emesene 2

This post will explain a little about what emesene 2 is all about, what e3 is and what is the relation with amsn 2.

The status of emesene 2 (at December 31 2008):

Login window with auto completion and remember settings.

The main window with a simpler and nicer layout.

main window with search enabled (pressing ctrl+F or pressing the search button)


The conversation window with conversation theme and emoticon support.

it's in early alpha development, so no bug reports yet, no crying and only use it if you are an extreme sport fan :P

There are still a lot of things to do, I expect to release a usable alpha or beta on the first days of February.

Why I'm developing emesene 2?

I had a lot of ideas about how the next version should be, and amsn2 had an architecture already defined, a MSN library already defined and other things that didn't led me try new ideas, so I started emesene 2 to test this ideas. (read more on the "what about amsn2?" part).

For instance, now the gui is really separated from the protocol library, and the protocol api is well defined so I can work on jabber support on the future.

All the protocol stuff runs on different threads, so the main thread only works on GUI stuff, so no more GUI freezing :)

The code is well structured, documented and validated using pylint and following the PEP-8 guidelines, also I will post some documentation for starters on this page to help people know where to start.

what about e3?

since I coded emesenelib I wanted to rewrite it from scratch, I thought the design of e3 a long time ago, and the idea was to make it multithreaded and with a clean API. I think I'm getting there right now and I'm happy with it.

what about amsn2?

Since the beginning our commitment was to provide a GTK gui, so all the gui code on emesene 2 is separated from the logic. That means that they can take the code of the GUI and with minimal cleanup have a complete GTK frontend for amsn2.

I also coded other modules with reusability in mind, like the theme, configuration and xml parsers, so if they find it useful, they can take it and use it (it's GPL code :D).

that's all for now, I will keep posting when new things come. The next post will be about the structure of the code.