![]() Not a proper coder at all, if I were rich I'd start learning but. Suggestions, and I would love to hear them from you. We need toĪnyway, these are the initial approaches that I can see so far.Īlthough I tend to go for #1, I'm sure you guys have lots of ideas and Would users mark a task as done', and things like that. There are unresolved problems to implementations #1 and #2 like 'how Track task execution would suffer from the lack of a common API for Huge GUI mess, which is obviously not good at all. This unlimited freedom, however, inevitably leads to a The timer window so they could implement task management in any way With this approach we would let plugins add their own UI components to Provide no built-in support for tasks at all. ![]() Would be created are questions that need to be answered.ģ. Suppose she does not choose any existing task, by committing Types in a task name so she could choose from an existing task if An auto-suggest list would appear as the user Things above, the user would be able to change the current task name This is simply an improvement over the 1st idea. Let users arbitrarily change the current task name in the timer window. Often good from the user's point of view.Ģ. To implement task management/selection on their own way, which is Standardization comes at the cost of limiting the freedom for plugins Track of task execution regardless of the task source. Including that it would make life easier for plugins that want to keep This implementation has the advantage of providing standardized APIĪnd GUI for task management, which is good for some obvious reasons, Plugins would also be able to customize the task list byĪdding context menu items and buttons (ie. Sources' from which the task list would retrieve tasks that populate Would always carry the current task object along with them.ĭuring system bootstrap, plugins would register their own 'task 'current task changed' event would be issued. Generic, built-in task list would show up and the user would select By clicking on a button near the task name, a The current task name would appear somewhere on the timer window Force the user to pick a task from a list of predefined tasks. Management/tracking stuff and realized there are a number of different Since your last reply, I was thinking a lot about the task ![]() Let's call it simply "task name" from now on. Yeah, I meant "the name of the task", so "tag" is definitely not the > If not, then perhaps just refer to the text string as "the name of the task" > indicated as your simple intention, which I think is on track. > If that is what you mean, I think perhaps it's ambitious, more than what you > view all objects grouped together by that tag, perhaps filter "all with this > - as being an attribute attached to an object, allowing the user to then > Re the term "tag" - I usually identify the word - outside of markup contexts Showing a dialog window asking the user to describe the tag. Then plugins could listen to tagĬhange events and optionally take an action like, for instance, So, I will close those issues in the issue tracker that mention theįor a start, I thought that the user could type a tag name in the main All Tomighty needs toĭo is to provide the user with a means of naming the task she isĬurrently working on and let plugins take care of the rest. They must be, as you said, handled by plugins. Means the built-in task list manager is not in the plans anymore. To be a small, basic core that can be extended with plugins, which Manager in the past but that was a long time ago. I did consider making a built-in task list ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |