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
I will get the conversion action/project planned for another release. I do see the merit of having that built-in. 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. 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 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. In "Getting Things Done" there is a section about contexts, and this is even implemented in mGSD. Actions can now be further sorted into categories and be done by context. 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. 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. @Seann Thanks for the update. I understand the level of security. I had thought I posted that group a while back but is obvious that I did not. *** Finally, I believe I have the blank-list and realm mismatch bug corrected and v.0.3.1b is already available. http://gsd5.tiddlyspot.com Thank you to everyone getting involved on the project page. On Mon, Nov 17, 2014 at 3:12 PM, Danielo Rodríguez <[email protected]> wrote: > I knew I was forgetting something. > > Would you consider adding a button (or something else) to turn a task into > a project? As far as I saw is just a matter of changing the gsd_type field. > > Other annoying thing is not knowing to which project a task belongs when > you are selecting it, for example, on depends on. I suggest to order the > tasks based on: first current project task, after other projects task with > project title. > > Other suggestion: Why not displaying sub-projects under its parent project > with some indentation? This can be on the Dashboard. And it could be cool > to see the task of a subproject within the project view. I suppose those > things will be possible implement with your API system, right? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/SQtnSfTHQoI/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- Roma Quintin Hicks -- 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.
