Action Categories

[roma0104]

Allow actions to be divided into categories or contexts for completing said actions.

[danielo515]

I prefer the context term.

[roma0104]

I am fielding alternative implementations of action contexts.

Ideally, I would like to avoid as much custom widget design as possible. Using list fields seems like a logical solution but dynamically adding elements to the list with existing widgets seems to be a barrier. Does anyone have a solution I am not seeing?

If we are willing to entertain the idea of using tags for some aspects, tags would definitely adhere to KISS and make implementation much easier.

I personally am leaning towards using tags for contexts, however, as always I can be talked out of my position.

[roma0104]

Possible basic concept on creating dynamic list-fields.
https://groups.google.com/forum/#!searchin/tiddlywiki/list$20field/tiddlywiki/8Ux4QO5ZOIA/8I7wkP0EEOgJ

[danielo515]

Hello @roma0104

I'm not sure what are you trying to say. Could you please elaborate?

[roma0104]

I wanted to know if anyone had any better ideas on how to implement contexts.

If we wanted to avoid using tags, we can use a similar ability that is used by list-fields. I think I have come up with a solution using this method, prompted by the link. I just haven't started implementing the idea yet.

Otherwise, if we were not totally against using tags for some of the GSD5 mechanics, we could use tags for labeling contexts. Using tags would be extremely simple but strays a bit from the limited tag usage we had discussed before.

[danielo515]

What I don't know is how do you expect the context to work. Anyway using tags is one of the basic mechanism of tiddlywiky, used in many parts of the core, so in my opinion there is nothing wrong with it. Users have to understand that some tags are used by the core. It is tied to tiddlywiky concept.

[roma0104]

Contexts are meant to further refine actions or projects. If an action or
project is meant to apply to certain context then you can make note of
this.

Example being: If I have the action, "Design egress proposal for city
codes.". This action might only apply during my bi-weekly department
meetings. I can can categorise some of my actions with the tag,
"Departmental Meeting". When my department meeting starts, I can pull up
all actions with the tag and set my meeting agenda with the actions.

It is a strategy that is touched on in the readings of the book and seems
relevant. I personally thought tags best suit this role. It seems you
don't have no strong feelings on the implementation. I will go ahead with
the tag implementation, there is nothing that cannot change.

On Wed, Dec 17, 2014 at 1:57 PM, danielo515 notifications@github.com
wrote:

What I don't know is how do you expect the context to work. Anyway using
tags is one of the basic mechanism of tiddlywiky, used in many parts of the
core, so in my opinion there is nothing wrong with it. Users have to
understand that some tags are used by the core. It is tied to tiddlywiky
concept.

—
Reply to this email directly or view it on GitHub
#15 (comment).

Roma Quintin Hicks

[roma0104]

Added context support.
95e5b6d