This post is just a wide joke…
Time to explain why: on the 30th august, I merged donebox asap branch with master, so that put a little change mainstream:
"Today" section become "ASAP" section. ASAP of course stand for "As soon as possible".
Why that change?
Just because I realized that a task (at least in my work) often long for more than a day, and specify
for common users, it’s just the "Today" section renamed "ASAP" section. For coders, a task is now more semanticly linked to its due_task timestamp, with a new field "kind" to distinguish :later from ;asap (standard task with deadline keep this field to nil).
Now, why is that a wide joke? Just because between the merge and this post, 45 days passed and each time I try to finish it, I restart from scratch. But not tonight.
This post is for donebox users: I want to rewrite models to take advantage of named_scope, that means that donebox will no longer be Rails 1.x compatible.
I’d like to know if there’s still donebox user in Rails 1.x who don’t want to migrate to Rails 2.x. I’m pretty sure I only have a comment from Marc-André saying that’s ok, but just to be sure…
Thank you for your answers.
Yesterday, sunny noticed that [category] require 4 keystrokes to add the brackets surrounding a category on an AZERTY keyboard, an other part a category is mostly made of only one word, so he suggested the @category notation.
So, I think it’s ridiculous to refuse good idea, so since this morning, donebox offer the @category syntax. Note that if you type @my_category, the underscore will be translated as a space, as if you typed [my category].
Hoping that notation will help your laziness :)
Just a little announcement about donebox: between commits 8df5e6a10bfe29a41e989635cce9867a128a044c (categories detachment from tasks) and 53ca27f1ffcce5ca3f4c3a52e6986fdc2da020e3, I introduced an ugly bug: when editing a specific task, every categories were displayed. Not really a problem if you were running your own donebox instance, but if you shared yours with complete strangers that was a real problem.
My apologies to everyone who meet a problem about it.
So, my donebox instance is now patched and running.
A last word: the next improvment to donebox will be a simple administration panel. Here the list of the features:
- possibility to design administrators
- possibility to block user registration
- possibility to delete a user
- possibility to lock a user
Next steps will be a plugin attempt (RailsEngine or Desert? I haven’t decided yet: every tips are welcome), then the last improvments to "donebox-core" will take place. You can stay in touch with the plans through my redmine instance.
Oh, by the way: have a merry christmas and an happy new year!
I’m still alive!
What happened last month? I just done a job switching. Bye bye CSC, welcome Ciblo! The main difference between these two jobs is that Ciblo require far more work, and rather all this work is around Ruby on Rails. My formation is not finished, but I’m already feeling far more efficient in RoR.
So, just imagine how impatient I am to find out two or three hours to work on donebox to put the final touch to the "root" donebox application, and finally get running the plugin system.
No! Donebox development is not really stopped, it’s just a real life pause. In few weeks, you’ll see some new cool commits.
Last august, I put on github the marvelous to-do list manager (using RoR1) written last year by Marc-André Cournoyer (who released thin v1.0, great job, guy!). I just named: donebox (truly, the best to-do list manage EVER).
At this time, my only objective was to adapt it for Ruby on Rails 2.0 and fix a behavior or two. Now, I want to enhance donebox to open its horizon.
Here the main ideas:
- Move categories as a Model to add useful features as sorting, hiding, etc.
- Add hooks or plugin capabilities to permit non-intrusive extensions
- Develop greats plugins for every body use
Of course, I’m open to every suggestion to enhance it.
BTW, a great THANK YOU to Marc-André Cournoyer, his work is just marvelous.