Planarium. 10,000 tasks.

So we survived until the first small anniversary - a 10-thousand task was created on the project.
We decided not to be idle and, in honor of such a momentous event, be renewed.

Appearance

We nevertheless decided on this cardinal step and redesigned the “plan for the future” page, now we don’t need to roll back and forth, but we can drag the task today out of chaos.

For tomorrow

Yes Yes Yes. This is also done. Although we are against this approach, we have nevertheless made it possible for you to drag and drop assignments right away for tomorrow or the next week.

Formatting in notes

There you can now use textile .
')

Work with the archive

Now you can watch not only tasks, as well as notes to them. Another opportunity to delete or restore jobs from the archive.

Bot upgrade

He now has a lot of things.
Here is the updated list of commands:
* today <case name>; <name of the second case>; ... <name of the n-th case>
* for tomorrow <case name>; <name of the second case>; ... <name of the n-th case>
* for the week <case name>; <name of the second case>; ... <name of the n-th case>
* for the next week <case name>; <name of the second case>; ... <name of the n-th case>
* in chaos <case name>; <name of the second case>; ... <name of the n-th case>
* what to do?

As you can see, added batch mode. Now you can add tasks at once in a crowd.
The “what to do?” Command also appeared - it will display the entire list of tasks for today. Thanks to Chernyshevsky for providing the text =)

A separate paragraph would like to note the function of synonyms.
Many of you complained that the commands are long and it is not convenient to enter from the phone. We fixed it. Now you yourself can assign bot commands. Those.:
You do not like the team for today, you would like to replace it with "today". Easy!
-> today
Everything, now with the today team today bot will create a task for today.

Empty synonyms are also supported. Do you want to enter tasks at once into the bot window without commands? Forward!
->
after the arrow is empty. It's not a mistake.
The only restriction is that synonyms should consist of one word.

PS A little bit about technology (habr still =)

I would like to share with the young rubists experience. Many of you know that the previous bot was case-sensitive. And it enraged many. Therefore, I decided to deal with this problem.

At first I thought that garbage. We add the key “i” to the regulars and that's it. But it was not there. Ruby 1.8 is not exactly friendly with UTF-8. And the “i” key works fine with the English language, and with the Russian substitution, the interpreter simply ignored it.

Began to understand, poking, picking. I thought to postpone until the moment Ruby 1.9 was finished (more precisely, the circle would be finished to Ruby 1.9) or the teams should be changed to English, but in the end the decision was found - oniguruma.

do gem install oniguruma , then connect it to require 'oniguruma' , and then create regular patterns in a slightly perverted way:
Oniguruma::ORegexp.new( "()", {:options => Oniguruma::OPTION_IGNORECASE, :encoding => Oniguruma::ENCODING_UTF8} )
This is how you can beat the register for the Russian language in Ruby 1.8.
In 1.9 such perversions will not.