Feedraider moved to beefier servers today. The long awaited update is still coming. There will definitely be a release this summer.
Labels: 2008
The last 6 weeks went into upgrading another project I began early 2006 leaving me no time for feedraider. The good news is that the project holds several technologies within that I needed done for feedraider.
I wanted a new feedraider release for December, but it does look like I'm not going to make it. I will try to prove myself wrong.
I wanted a new feedraider release for December, but it does look like I'm not going to make it. I will try to prove myself wrong.
October has been all about creating a solid foundation for the upcoming new feedraider. I threw away all open source 3rd party code, and spent the last four weeks on programming a setup that is smarter, less error-prone and gives me full control. The results of this work have been very promising and I'm certain all the extra time spent will pay itself back in the future as a higher quality service, keeping both me and you happier.
Labels: 2.0 upcoming
I ask myself at times; "I knew what I wanted to do in January, so, why am I still lacking an implementation in September?". This is the Web! What could be taking so long?
My favorite excuses include; learning to utilize a new MVC framework, looking into the abyss of patterns including the Active Record pattern, re-thinking the whole navigation, coming up with complementary paid services, creating something fresh and better, learning from software engineering best practices and putting them to actual use where fit, setting up a High-Availability cluster for the service data, saving user-generated files on a robust distributed file-system instead of having (only) backups, a bunch of other things I forgot, but most of all developing a platform that will be useful to you and me.
When will it be ready? October, maybe.
My favorite excuses include; learning to utilize a new MVC framework, looking into the abyss of patterns including the Active Record pattern, re-thinking the whole navigation, coming up with complementary paid services, creating something fresh and better, learning from software engineering best practices and putting them to actual use where fit, setting up a High-Availability cluster for the service data, saving user-generated files on a robust distributed file-system instead of having (only) backups, a bunch of other things I forgot, but most of all developing a platform that will be useful to you and me.
When will it be ready? October, maybe.
Labels: beauty, structural
Pushing hard throughout the weekend has FR's basic page functionality (add+edit) refactored in a finished state for classic pages (v1.x). It was a lot more work than I had anticipated.
A new UI.
Fixed remaining v1.x bugs...
New widget pages. IE gave a good scare while working them. Crash. S***! Sixty minutes later no crash, no blank pages, and I could breathe again...
All JS functionality moved/ported from prototype to mootools. Haven't moved to Dojo yet, but I fear I can't move to v0.9 due it not seemingly supporting all v0.4 features.
Summa summarum a lot of old does not only have a fresh coat of paint, but a lean & mean engine behind it. Still, a lot of work left.
A new UI.
Fixed remaining v1.x bugs...
New widget pages. IE gave a good scare while working them. Crash. S***! Sixty minutes later no crash, no blank pages, and I could breathe again...
All JS functionality moved/ported from prototype to mootools. Haven't moved to Dojo yet, but I fear I can't move to v0.9 due it not seemingly supporting all v0.4 features.
Summa summarum a lot of old does not only have a fresh coat of paint, but a lean & mean engine behind it. Still, a lot of work left.
...feels like 80% of total.
Last weekend I moved the new codebase over to the Agavi framework and took an admiring glance at the Deck and River views, which I've finished first out of the old three-view page setup. These will be known as the "Classic Page".
The most pleasant thing has been the ability to put my wack ideas into working code. The most important new features are not only on paper anymore, but working splendidly to my great relief. Especially the client-side javascript has been tricky. I'll write about the features in more detail as I get them polished for prime time.
NOTE! A decision was made to kill all anonymous pages to streamline the codebase. If you still have anonymously-made pages, please register to have them up when 2.0 launches!
The most pleasant thing has been the ability to put my wack ideas into working code. The most important new features are not only on paper anymore, but working splendidly to my great relief. Especially the client-side javascript has been tricky. I'll write about the features in more detail as I get them polished for prime time.
NOTE! A decision was made to kill all anonymous pages to streamline the codebase. If you still have anonymously-made pages, please register to have them up when 2.0 launches!
