I like open source!

Yup, that's true! I like open source, today I just get a mail with a beautiful ZIP file with outlook express import support for MyOE. Yesterday it was an RSS component made for MyOE. That's the kind of things I won't get with a closed source project...

So this post was just to say thanks to Hervé Poussineau and Weber Wang for their code... and to the rest of the very small MyOE community that becomes a bit less small everyday.

I'm just still troubled by something: I don't get that much feature request, that's strange, at first sight I'd thought I would get lot of request, and only a few actual development. That's almost the opposite. Feel free to post any feature request, to drop your idea and give us feedback!

Spelling in MyOE!

I get a first version of spelling in MyOE working. You can look the screenshot to get the idea... but even better, you can download and install the daily build in order to play with it.

MyOE daily binaries!

I made it! MyOE debug build binary, everyday, so you'll be able to see what's up with myoe. The binaries are build everyday at 5am CET.

You need the .NET 1.1 runtime and MDAC version 2.6 or higher. Currently the setup doesn't test the installation of those requirements. (basically if you have myoe 0.5 or older running on your system, you'll be able to run this build).

And euh... yes the build is available from http://myoe.sourceforge.net/daily/MyOEDailyBuild.exe

Feedback about the current build is of course very appreciated!

Spelling in MyOE?

NetSpell seems rather interresting to add into myoe... but myoe need inline "as you type" spelling, not only a spelling dialog.

I'm currently implementing as you type spelling, and I'll even try to include it in the netspell project.

In short: MyOE will get basic spelling very soon.

The question of the day is... does inbox synchronization with your PDA is of any usage?

Codename MyOE.NET Development blog

Yuhuu, I have a working synchronization implementation, for now, I only do weekly recurrence, and recurrence can't be created from the GUI (but can be created from the pocket pc :p)... but it works, I've the perfect copy of my pocket outlook schedule inside myoe, and if I add something in myoe, it's added on the pocket pc.

Source will be commited soon (lot of changes as you guess, no revolution, myoe still works the same way).

I'm working on recurrent event today (well, I'm sick, so it's more something like: I'll try to work on recurrence :/).

I wonder what kind of recurrence is needed? It seems obvious that we need common: every n days/week/month/year stuff, and be able to limit the recurrence to a number of ocurence or an end date... but what else? do you need something else?

Personnaly, I'd like to add the "period" concept: for instance, you'll define a period called "hollydays" and define an event as "every monday except during my hollydays".

The main problem imho, will be syncing it with external device (or other PIM), vCal doesn't contains such things, pocketpc doesn't (and I think palm doesn't), so syncing will implies some kind of lost.

So the question is: is it worth? The fact is that you'll get at least what a pocket oulook PDA can do, is more worthful?

Want to see how MyOE.NET schedule looks now? Follow this link.

"Why being modest?"©® ;)

I'm testing Thunderbird... and I'm very happy to discover this mail client... it's slow (I'm syncing my trash account for 3 hours now... only 15.000 mails ;), lot of things that myoe does can't be done with this client (well I guess it does lot of things that myoe doesn't... but hey! you know that my judgement is biased ;).

In short, I thought at first that I would find "a product that maybe one day myoe will reach", it's more "another project in development".

Well... on the other side, I'm not the perfect end user, so please if you use thunderbird, tell me why! If I can borrow some great idea from a project like this one... myoe will just be better.

I took some times for myoe...

I'm currently rewriting the calendar view, in order to show a "true" schedule with hours instead of a "list of events". You're now able to drag your mouse from 2pm to 4pm to create a 2 hour meeting.

PocketPC synchronization will come soon (I rewrote the calendar in order to get my PDA events in myoe), after periodic events will be implemented.

I was like... busy the last two month. The good news is that I've an enhanced myoe built almost ready for release... the bad news is that I need time (or help...) to test it "out of the box".

Other things will come: shared calendar using FTP, pocket pc synchronisation, a new spam filter, ...

Again, I need more time or help, or both...

I wish MyOE 0.6 could come ... today, but it won't, maybe next monday, unless someone can help me to test the current release.

Lot of bugfix, performance enhancement, working set reduction... broken thing... and nothing really new is what you will get.

I wish MyOE 0.6 could come ... today, but it won't, maybe next monday, unless someone can help me to test the current release.

Lot of bugfix, performance enhancement, working set reduction... broken thing... and nothing really new is what you will get.

I wish MyOE 0.6 could come ... today, but it won't, maybe next monday, unless someone can help me to test the current release.

Lot of bugfix, performance enhancement, working set reduction... broken thing... and nothing really new is what you will get.

Goodbye Magic! I'm currently rewriting some part of myoe to be independant of magic library, it's still works in progress... but it should let us with more control on our sourcecode and maybe some not so common feature (I'm think about an easy way to define shortcut keys).

MyOE 0.5 released!

And I'm already working on next version:
- basic mail archiving (got too much spam, want to archive them ;).
- mail list update themselve during synchronization.
- ...

I want to do things like:
- Allow filter to have more than one action (change category to X, move to folder Y and mark as read).
- Implement "database plugin" in order to use something else than access.
- Make archive accessible in some myoe functionnalities (search for instance).
- Move spam informations to a database (text file sux).
- Mail threading for mailing list discussion. (any idea of a suitable algo?)
- Notes, like post it, on ... everything (mail, event, etc...). I need to think about that.
- Welcome wizard to match "user profile".
- Lot of other things.

In the category "stupid fun facts": current myoe code counts 73.217 lines of code and the new plugin interface dll counts 5.367 line of codes). Of course, some code were generated (but not that much).

That's also a quick demonstration of the interrest of the new plugin architecture: someone who want to create a plugin for myoe should need to understand ~5000 loc instead of the +70.000 of myoe... so what are you waiting? code! ;)

Download Mentalis.org Security Library cool! I guess myoe will get SSL support soon! (sourceforge can be a test NNTP server). In fact, the best would be to setup a "socket plugin" component, to allow:
- to externalize socket management
- to add more stuff like proxy, secure connection, ssh tunneling, whatever from outside myoe.

I think something like a dll implementing a ISocket factory (ISocket will be the myoe interface used) could do the job. We'll also need a way to add settings to specific items, like adding stuff to ServerItem configuration, FolderItem, etc... this could REALLY makes plugins more powerfull. For now extending UI is only supported to add configuration page to host configuration dialog.

Plugins are on the way, database will be plugins soon (I want to be able to switch database in some click, to archive data, etc...). Message sorting/filtering rules are being rewritten from scratch to be more flexible, more powerful and faster. Later plugins will be able to integrate themselves in more part of myoe, the idea is still the same: make a rock solid core with tons of plugins around, the core should remains stable in the worst condition.

The whole myoe design switch from many classes to some visible interfaces.

The question is: will it be used by third party one day? will you develop plugins? I've seen lot (really;) of people interrested in myoe, some of them proposed their help, but only a few did... I'm changing myoe design to make the "get into the code" step easier and at least it will make development easier, even for me, but making a plugin architecture if it's not used, does it worth the effort?

MyOE sources (daily) and plugin sources available here!.