Ajax Checklist won't lend itself well as a cck field, since it's an input format. This module does, however, and I'm hoping to tackle it myself -- would you accept a submodule patch (todolist_field.module)? Looks like List is doing the same thing as Todolist, and I mentioned that at #795032: Difference with Todolist? in hopes of a joint effort. In anycase, I think this would be *great* as a cck field -- one could add tasks to cases in OpenAtrium, say if the task is so small it doesn't warrant a new case altogether. ClockingIT does just this, and it determines the percent-complete for a case from the amount of todos completed/open in that case. Actually really handy for clients.
As I'm creating this todolist_field submodule, I'm finding it might actually make more sense to just replace the original. The big reason is that the best way to handle these multiple todo-tasks in cck database land is via cck's multi-value-handling functions, and storing tasks as deltas using cck's api. Would require a complete overhaul. It wouldn't be a big loss to the original module, because you can just direct users to (1) create a "Todo List" content-type first, then (2) add this field. Adding 2 steps, but net result would be the same, plus added flexibility.
I'm not sure about dropping support to the actual way of making todolist's(by static content type from code), but I would really want to commit you patch when it's ready :-)
It's fine to follow your progress at github, but please update this issue about decisions you're taking/general discussion about implementation.
BTW a little suggestion about using git: IMHO you must just version what you need to version, I mean avoid versioning all drupal tree, just version todolist_field.
For sure, I'll post updates/questsions here, as well as patches once the module starts getting somewhere. I'm just putting the drupal instance up for myself temporarily, syncing the install between 3 machines (I should using git submodules, but overkill for this quickie). Once I get the module to a workable state, the repo will just be the module & not the whole drupal instance.
Yeah, I'm not sure myself about dropping the original way (static content-type), was wondering what your thoughts are on that regarding how CCK handles multi-value fields vs how todolist custom-handles multi-value fields. We wouldn't want the two methods storing in the database differently. An alternative would be that for the todolist field, adding multiple entries (via cck) would actually add multiple lists (rather than tasks), so that todolist could handle its own multi-value processing for each list-field.
Also, one argument in favor of replacing the current todo database schema + multi-value handling, is that using CCK's method will be make this easily compatible with views, tokens, & the like.
So this got pushed to a later phase in the project I'm working on, won't be looking at it again for a while. Have it if anyone wants to get started, else I'll be back later
Posted by wackadoodle on August 29, 2010 at 9:34pm
I've been searching for hours for an appropriate module - hope this one is it but I'm not holding my breath. I'll download it and play a bit. What I am trying to accomplish is provide a "to-do" checkbox as a conditional field to a profile question. My specific example goes like this:
Have you been pre-qualified for a mortgage? YES / NO
On selecting NO, a checkbox drops in conditionally tied to the NO response and is labeled "add to my TO DO list". This way the user can simply add this task to their to do list and concentrate on completing the form. Once they submit their form, they can navigate to their to do list and focus on each of those items....
I'm surely open to hearing any brilliant work-arounds...!
Comments
#1
@marvil07: agreed - check out this post from a different module (Ajax Checklist) - i post here for cross referencing,
http://drupal.org/node/349682#comment-1997948
Also, because Todolist module seems (hopefully?) farther along, perhaps efforts can merge here.
#2
Ajax Checklist won't lend itself well as a cck field, since it's an input format. This module does, however, and I'm hoping to tackle it myself -- would you accept a submodule patch (todolist_field.module)? Looks like List is doing the same thing as Todolist, and I mentioned that at #795032: Difference with Todolist? in hopes of a joint effort. In anycase, I think this would be *great* as a cck field -- one could add tasks to cases in OpenAtrium, say if the task is so small it doesn't warrant a new case altogether. ClockingIT does just this, and it determines the percent-complete for a case from the amount of todos completed/open in that case. Actually really handy for clients.
#3
As I'm creating this todolist_field submodule, I'm finding it might actually make more sense to just replace the original. The big reason is that the best way to handle these multiple todo-tasks in cck database land is via cck's multi-value-handling functions, and storing tasks as deltas using cck's api. Would require a complete overhaul. It wouldn't be a big loss to the original module, because you can just direct users to (1) create a "Todo List" content-type first, then (2) add this field. Adding 2 steps, but net result would be the same, plus added flexibility.
Anyway, my progress will be on Github
#4
Great to see some interest about this.
I'm not sure about dropping support to the actual way of making todolist's(by static content type from code), but I would really want to commit you patch when it's ready :-)
It's fine to follow your progress at github, but please update this issue about decisions you're taking/general discussion about implementation.
BTW a little suggestion about using git: IMHO you must just version what you need to version, I mean avoid versioning all drupal tree, just version todolist_field.
#5
For sure, I'll post updates/questsions here, as well as patches once the module starts getting somewhere. I'm just putting the drupal instance up for myself temporarily, syncing the install between 3 machines (I should using git submodules, but overkill for this quickie). Once I get the module to a workable state, the repo will just be the module & not the whole drupal instance.
Yeah, I'm not sure myself about dropping the original way (static content-type), was wondering what your thoughts are on that regarding how CCK handles multi-value fields vs how todolist custom-handles multi-value fields. We wouldn't want the two methods storing in the database differently. An alternative would be that for the todolist field, adding multiple entries (via cck) would actually add multiple lists (rather than tasks), so that todolist could handle its own multi-value processing for each list-field.
Also, one argument in favor of replacing the current todo database schema + multi-value handling, is that using CCK's method will be make this easily compatible with views, tokens, & the like.
#6
So this got pushed to a later phase in the project I'm working on, won't be looking at it again for a while. Have it if anyone wants to get started, else I'll be back later
#7
Subscribe, very interested in this!
#8
I've been searching for hours for an appropriate module - hope this one is it but I'm not holding my breath. I'll download it and play a bit. What I am trying to accomplish is provide a "to-do" checkbox as a conditional field to a profile question. My specific example goes like this:
Have you been pre-qualified for a mortgage? YES / NO
On selecting NO, a checkbox drops in conditionally tied to the NO response and is labeled "add to my TO DO list". This way the user can simply add this task to their to do list and concentrate on completing the form. Once they submit their form, they can navigate to their to do list and focus on each of those items....
I'm surely open to hearing any brilliant work-arounds...!