Hello Roma Just to show you some of my ideas already working I set up a small space: http://gsd5customizations.tiddlyspot.com/
El martes, 18 de noviembre de 2014 16:51:27 UTC+1, Roma Hicks escribió: > > The blank drop-list is also a result of the same bug. A similar fix will > correct that too. https://github.com/roma0104/gsd5/issues/16 > > Ok. I will wait for that fix and let you know if I still experiencing any problem. > I will get the conversion action/project planned for another release. I > do see the merit of having that built-in. > > Nice! > Can you reword/re-describe your issue with identifying which project a > task belongs to? So far: Action lists can be grouped by project, per your > request. And action tiddlers have drop-list identifying its parent > project; plus a link to jump to the parent project. Where are you having > trouble identifying an action's project? I keep reading two blended ideas > in that paragraph. > > Hello, maybe you're right and I blended two ideas. What I was triying to express is, when you are on an action tiddler, and you want to set the depends on field the list you get is an inmense list of task. What I propose is to use optgroups to group task by project. I made a pull request with my proposal: https://github.com/roma0104/gsd5/pull/24 Even if you don't want to implement it that way in the core, I created some plugin-like add-in. The problem is that I can not remove the current one without editing the shadow-tiddlers. You can see this customization on the mentioned space. > The cascade mechanism is not something I am planning on doing. Not at > this time anyhow. I wanted to avoid recreating a bunch of widgets. > Perhaps tagging might fit the usage you are describing better than changing > realms often? I specifically avoided using tags to power the "behind the > scenes" mechanism. This was to allow users the freedom to tag without > cluttering tiddlers with lots of tags that only the GSD5 plugin cares about > or can decipher. > > I also like your "avoid tags" politic. The implementation seems cleaner. > I think of Realms as more static constructs that are assigned at creation > and rarely changed. I rarely decide maintenance on my work vehicle no > longer belongs in my Personal realm and instead in my Professional realm; > if that is how one uses Realms. > Your right, and maybe my problem comes from the fact that I was using realms in the wrong way. > Actions can now be further sorted into categories and be done by > context. > How? > Would this meet you requirements better? If so, I do plan on creating > such a feature and has been on the meta-to-do-list as well. Contexts will > probably use the tagging feature of TiddlyWiki as tags would be both > important to the plugin and allow quick reference by the user. > > Yes, it will fit better my use case. > Your last suggestion might definitely be a plugin. It did make me think > about another tag-API that would allow such a list, so thank you. > Actually I setup a small list-view using your plugin mechanism. You can see it at the mentioned tiddlyspace. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
