> > > Just to show you some of my ideas already working I set up a small space: > http://gsd5customizations.tiddlyspot.com/ > <http://www.google.com/url?q=http%3A%2F%2Fgsd5customizations.tiddlyspot.com%2F&sa=D&sntz=1&usg=AFQjCNGFNW41UQm5wyVdDiRjgCYuteRNFA> > > Yeah I think that might work great for a plugin. I don't know if that might belong in the core; I want to treat the core more as a bonsai tree. Prune any extra but leave it with enough content to produce a beautiful system of plugins that don't look awkward (unless you really abuse it, ha). But I am very interested in seeing how editing shadow tiddlers from the gsd5 plugin works. To my knowledge, you cannot control plugin loading order and I am not sure even what order boot.js even does it in. Ideally I would rather see a good API that allows multiple plugins without overwrites for obvious reasons.
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. > > So you know, I noted it at very bottom of my previous post. No fanfare. I patched that and the build is already up as v0.3.1b. > >> 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 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Froma0104%2Fgsd5%2Fpull%2F24&sa=D&sntz=1&usg=AFQjCNFU56F2eXam5LNOgLKiDFUIesiAYQ> > > 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. > > I think that might be a usability improvement and could benefit the core in general. I will try it out and consider it. > Actions can now be further sorted into categories and be done by >> context. >> > > How? > Excuse me, I meant conceptually, from the reading in the book. I haven't implemented it yet. That would be the goal of issue #15. 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. > The ProjectViewBody isn't API ready yet. It is still hard-coded together. I want it more like the Dashboard. In this situation you would simple tag *your* new Subproject list with the right tag and... it is in the ProjectViewBody. Might need some more options so we can hide the stock Subproject. -- 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.
