esAperezA / pomodairo

Automatically exported from code.google.com/p/pomodairo
0 stars 0 forks source link

arrange the task hierarchically #96

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Pomodairo is super nice so far, simplicity and its features make it great tool.
Here is a feature request that could make it even better.

Give the posibility to arrange the items in a tree like manner. Ex:

Project 1
    Design
        Do mockup main page
        Do mockup options page
    Testing
        Test new features added
Project 2
    Bugs
        Fix bug 1
        Check why bug 2 was reopen
... etc

The ideea behind this is to allow the user to organize the tasks somehow.
When working on multiple projects/domain in the same day the user should be 
able to browse the tasks on the domain he is currently working. We should avoid 
to make the user read all the list an choose from the task list which tasks he 
can take next.
When the tasks are organized in a hierarchical manner the user can directly 
skip the categories that have no interest in that moment.

Some other ideas: 
- Allow expand / collapse on the parent nodes
- The EPUI columns for a parent node could sum the values on their children.
- Order hierarchically the tasks by Drag & Drop them to their parents
- Adding of a parent node proposals:
    - The adding of a parent could be done simply by adding a drop down menu inside Add New button. This actually opens a new small menu with one menu item that presents a new action for the add button: Add as child to selected item. If the currently selected item is a task with 0 pomodoros, then it can become a parent node.
    - Or, the dropdown menu in the Add New button could present the option: Add new category (parent). The popup of the new task will only show the textbox for the parent name, hiding the estimated textbox which is not needed in this case.
    - Or, another ideea of adding a new node would be to indentize / deintentize a task. When a task is indented then the first task from above would become the parent node.

I'm sure this is not an easy request, as it involves a lot of effort. I hope it 
will make it to Pomodairo :).

Thank you.
Lucian

Original issue reported on code.google.com by luculu...@gmail.com on 4 Dec 2010 at 6:59

GoogleCodeExporter commented 8 years ago
It is a nice idea, like you say not very easy to add perhaps but interesting 
none the less. I think the key for this would be still have a clean GUI. IMHO 
it is too easy to start adding more buttons and gadget and you end up with an 
application that is confusing to user ;)

Thank you for some great feedback =)

Original comment by fredrikj...@gmail.com on 6 Dec 2010 at 6:47

GoogleCodeExporter commented 8 years ago
I love the way this is implemented in google tasks. You can create the 
hierarchy in a simple text-based manner by simply using the Tab key. Very clean 
and intuitive. Pomodario's tasks area may have the same notepad-like 
environment (also good for adding new tasks). It is also fine as it is since 
original Pomodoro method doesn't have sub-tasks.

By the way thank you for this great application. I've tested almost all 
Pomodoro software on PC and Pomodario is definitely the best one.

Original comment by ozgung...@gmail.com on 7 Dec 2010 at 12:54

GoogleCodeExporter commented 8 years ago
I should probably take a look at Google Tasks. I have not used it before so 
good suggestion!

Original comment by fredrikj...@gmail.com on 4 Jan 2011 at 9:54

GoogleCodeExporter commented 8 years ago
Just got another idea: instead of building hierarchies to categorize the tasks, 
the user could simply attach some tags to a task:

- task 1 (my secret proj, testing)
- task 2 (other secret proj, design)

Then somehow filter by one or more tags at the same time, should give the user 
a nice filtering feature.

I personally find this one as more light and simple. And probably more easy to 
develop.

Cheers,
Lucian

Original comment by luculu...@gmail.com on 27 Jan 2011 at 9:22

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I think the tag solution is a good one. For my point of view your day to day 
tasks list is not organized by project hierarchy. Project hierarchy is 
interesting to follow your global achievement. I work on multi-projects / 
domains environment. What I do: I add something like a tag in front of my task 
descriptions to identify the associated project as follow:
[proj1] Task 1 description…
[proj1] Task 2 description…
[proj3] Task 15 description…
[proj2] Task 4 description…
…
That's why I like the tagged approach. But a hierarchal view could be 
attractive for follow up.

If I can associate my project tag (or my task) with a Bugtracker tool URL then 
it will be also great too. In fact, I need more than one bug tracker and 
therefore I need to identify the different origines of my task in a line.

I love pomodario and I’m looking forward to see the next greet features.

Regards,
Romain

Original comment by romain.g...@gmail.com on 3 May 2011 at 6:50