Note: An alternative skin, TW4MW (work in progress), is available from the user preferences.

Talk:TeamTasks

TiddlyWiki Community Wiki

Jump to: navigation, search

Contents

[edit] General Comments

Brilliant job - I love it! -- FND 17:20, 30 October 2007 (UTC)

[edit] Bug Reports

This section needs to be reviewed and/or refactored to comply with TiddlyWiki.org's quality standards.
Please improve the article, or discuss the issue on the talk page.

[edit] Visuals

the red bar at the top looks a little odd

[comments here]

the buttons' color in the Listings menu doesn't quite fit in

[comments here]

the MainMenu's slider labels need to be visually differentiated from the slider contents

[comments here]

the task tiddlers' layout breaks (sort of) when there's lengthy tiddler contents:
the taskControls "column" is just a box in the lower right then - so you either need a top border there, or use equal-height columns

Equal-height columns can be very tricky - contact me if you're interested.

To be fair though, if a task tiddler is "overflowing" like that, its contents should probably be moved to separate tiddlers.

-- FND 10:30, 4 November 2007 (UTC)

[edit] Functionality

  • the control bar is missing a save button (it’s only accessible via the backstage area)
  • listings (e.g. the Timeline) are not refreshed automatically (the respective parent cotainer probably needs the refresh="content" attribute)
  • TaskViews are not refreshed automatically
  • UserDefinitions does not seem to support wiki markup ([[PrettyLinks]] in particular might be useful for non-CamelCase names - but the brackets are visible in the selection lists then)

[edit] Presets

  • AllOpenTasks should be corrected from <<TaskViewBuilder !StatusDefinitions_Complete>> to <<TaskViewBuilder !StatusDefinitions=Complete>> (underscore should an equals sign); the same applies to AllTasksByPriority
  • TeamTasks tiddler: [[about|About]] should be [[about|About TeamTasks]]

[edit] Suggestions

This section needs to be reviewed and/or refactored to comply with TiddlyWiki.org's quality standards.
Please improve the article, or discuss the issue on the talk page.
  • In addition to the New Task button, maybe there should also be a New TaskView button (using the NewTiddler macro preloaded with a boilerplate TaskViewBuilder macro call).
  • Using tags instead of extended fields for the field values might be the better, more flexible and future-proof solution.
    The tags could use the slices format (field:value), making the whole concept pretty much universal and easily extensible.
    The issue of potentially “spamming” the list of tags is not a huge concern here, since TeamTasks TiddlyWikis (T3W?) will probably not be used for storing regular content.
  • TaskViewBuilder
    • wizard/UI for building TaskViews (e.g. offering a selection list of available fields/definitions and their respective values)
    • instead of just listing the tiddler titles, a table should be created with a column for each field (scope, priority, assigned to, status)
    • instead of using field=value, it might make sense to use field:value (i.e. slices) - the parsing for such parameters is already built into TW
  • additional (though optional) fields
    • dates (e.g. start, due) and duration
      eventually (in v3.0+), that might result in some sort of automatically-constructed Gantt chart
      • Is it possible to have "tasked raised", "task assigned", "task completed", "task due" fields for a task (Dates picked using a calendar widget would be great but just input boxes would do to start). I'd use this to prioritise the work order for tasks assigned to me, create reports on progress on tasks per user, scope, priority, status etc. -- Dahukanna 13:37, 2 November 2007 (UTC)
    • parent projects; a project (or realm?) could contain several sub-projects/scopes (e.g. for a student, "uni" would be a project/realm, which has his study subjects "Computer Science" and "Business Studies" as scopes)
I am currently using "project:scope" (or rather, "scope:project"?) as a workround (e.g. "Dev:TiddlyWiki", "Dev:MediaWiki") -- FND 09:21, 4 November 2007 (UTC)
  • dependencies: a task could be inactive until a previous task has been completed (or started?)
  • from UserDefinitions, add a "Create User" link to UserSetupWizard
  • field definitions / selection list values should (optionally) be sorted alphabetically

[edit] Miscellaneous

This section needs to be reviewed and/or refactored to comply with TiddlyWiki.org's quality standards.
Please improve the article, or discuss the issue on the talk page.
  • A sample task on the "front page" would be nice to illustrate the concept.
  • There should be an empty file with just the barebones functionality (i.e. just the plugins and basic structure - but no introduction or help)
  • Changing a value (in one of the taskControls select boxes) feels a tiny bit sluggish; there’s a very brief pause before the TiddlyWiki becomes responsive again (likely caused by the internal updating of the store - not sure whether or how this could be optimized though).
  • Can users somehow re-order the task fields (scope, priority, assigned to, status), or even add new ones? (Modifying TaskDefinitions by adding a line "DummyField" and then creating a "DummyField" tiddler tagged with "TaskDefinitions" doesn't work.)
  • In the future, maybe(!) there could be multiple projects (scopes) and/or assignees for a singe task.
  • Aside: For some scenarios, the TiddlerNotesPlugin might be a good addition.
Retrieved from "http://www.tiddlywiki.org/wiki/Talk:TeamTasks"
Personal tools