Hi, Ken.
I would be totally thrilled to have MLO implement some tools for task automation. But I don't think that it should be an extension of the current filter definition scheme. I believe enhanced filters would be extremely beneficial to a small group of technically proficient, obsessively organized people like you and me and maybe Tom. It would probably be very expensive and time-consuming to build, and I would guess that nearly everyone who might benefit has already bought MLO, ensuring that there would be little if any return on this investment.
I would rather see MLO take these steps:
1. Build an HTML5 interface to view lists of tasks from your cloud file and maybe check off the completed ones. This could be used in conjunction with a Task-by-email facility with parsing enabled to open MLO to use by a large new base of potential customers. Security of the cloud file would need very significant enhancement.
2. Build an API that would provide access to the powerful task management capabilities of MLO via a browser app; Market the API to other developers as a way to bring the most powerful task management tools to other apps (note-takers, calendars, social media, email, etc.)
3. Use the web interface and the API to build integration with best-of-class task automation tools. If this were happening today I would suggest integration with IFTTT.
A well-designed MLO channel would not only allow you to star tasks that become due, but also flash your desk light red for 3 seconds, call your mobile phone and read the task note to you (but only if the task has a yellow flag) and raise the task urgency by 15 points. As well as creating a task out of every email you receive from an email address in the "customer" group and closing the @Yardwork context at sunset or if it starts to rain.
Much more powerful than what would come from enhancing filters, and with revenue opportunities at each of the three steps so that the vendor can remain solvent long enough to finish the job.
-Dwight
Mlo betazoid on Android sgn2