Posted by Aren Cambre on June 3, 2009 at 1:21am
2 followers
Jump to:
| Project: | Time Track |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This is a request to merge efforts with Time Track to prevent feature duplication.
Comments
#1
I would have appreciated it if the module author for Time Track contacted me prior to creating yet another new module. Our UI and views support needed help, but our underlying architecture is more flexible, so his efforts could have been win-win.
I wrote time as an extensible class-based module because we want to support more use cases than sticking time entries onto nodes:
* We needed the capacity to associate each entry with different "tracking profiles", which may have different activity codes and billing backends.
* We needed to be able to take the base time tracking module and extend it for other use cases. The Quickbooks module, for example, uses the same UI, workflow and views support, but stores some extra data and integrates with the Quickbooks module. You could do the same for any other accounting package.
* Similarly, we'd like to extend the profiles for other use cases, such as time estimates, credits or other accounting-oriented storage.
* We needed to be able to create time tracking entries without associating them to a node at all.
If the author of the Time Track module is interested in helping to clean up the time entry forms and/or views support, we'll gladly accept patches and everyone will come out ahead!