[TW5] Tidgraph - Easy tiddler graphs - New release 0.9.5

[ih...@newsfromgod.com]

Hi,

This is a new version of Tidgraph with enhancements and bug fixes:

Version 0.9.5:

* SVG collapse/expand button (thanks Tobias)
* Mode subfilter can be specified directly in mode attriute
* Doc update
* Eliminate unneeded console messages
* Fix arrow stroke size (regression)
* Dashed style for edges outside main tree

You can find the installation here:
https://ihm4u.github.io/tw5plugs/#Tidgraph%20-%20Easy%20tiddler%20graphs%20for%20TW5

For those that don't know, Tidgraph draws a graph of the relationships
between your tiddlers using tags, links or custom filters (called
modes).You can see a demo on the web page above.

Thanks!!

[Tobias Beer]

Hi ihm,

Now, that's some eye-candy. Great stuff!

One little thing that may spark ideas with users:

For the demo showing the mode="field[]",

perhaps also use a little custom template that actually shows:

''field-name''<br>field-value

...so you have a basic idea of all the things you can do with node-templates.

Hah, trying to do just that I find that I can't and why a simple filter won't do, after all...

So, here's what's needed for a mode:

• a filter, obviously
• a variable equivalent to that in the list widget, set to the item title
• most importantly, leaving <<currentTiddler>> as whatever it was
• unless no variable is specified, then it's overwritten
• which, most often, doesn't appear to be a good idea

If you want it in the attribute directly, you could do something like:

mode="variable-name=>field[]"

Not sure how the widget tree actually pans out in tidgraph,

but those variables should theoretically also be available

in the scope of any child-nodes and their node-templates,

so as to be "parent-aware".

~

It appears some links in the docs are now (or have always been?) rendered as external links.

I guess that's owed to the fact that the basic param table is also ship with the plugin.

Best wishes,

— tb

[Tobias Beer]

Hi ihm,

Oha, those variables turn out more tricky than I thought.

After all, the node template is applied to all nodes, not just the child nodes.

Anyhow, trying this simple test:

title: VariableDemo

<$vars tid=<<currentTiddler>>>
<$tidgraph start="Faith" mode="fields[]" nodetemplate="dump"/>
</$vars>

With:

title: dump

<<dumpvariables>>

I do not see any tid variable anywhere. How is that?

Perhaps you're not actually creating widgets, but basic html elements,

which might explain why the variable references don't get passed along.

Possibly that's due to a limitation in the current core code,

which perhaps expects widgets to be children of widgets, not html elements...

So, to look for (and inherit) variables from a parent widget,

it may need to look further out? Not sure.

Perhaps somewhere here, the variable retrieval doesn't find ...a parentNode:

https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/widgets/widget.js#L183

?

Best wishes,

— tb

[ih...@newsfromgod.com]

Hi Tobias,

> Possibly that's due to a limitation in the current core code,
> which perhaps expects widgets to be children of widgets, not html elements...

Yes, that is the reason. The template is included in HTML tags...
Thanks

[Matthew Petty]

Hi,
I really like tidgraph and use it for several structures in my TW5.

I can't seem to figure out Custom Modes though. I'm using GSD5, which is a GTD task manager, and it uses fields to store all the task data. A subproject has the field "gsd_project" which contains the title of the parent project. Similarly, an action with the field "gsd_action" which contains a title of another action, needs that action to be done first.

How can I use a custom mode to produce a project tree and a dependent action tree?

[HC Haase]

Hi
[featurer request]

Tidgraph is simple and awsome. It would be cool if one could:

make a mode that could make graphs from nested list in twmarkup (or/and markdown). This way I could fast have a flowchart just by writing a nested list.

• it would be fast to work with - less clicking

• it would limit the number of tiddlers. If I want a flowchart but don’t want to populate my wiki with tiddlers only relevant for that chart.

what do you think? is this possible? is it realistic?

thanks

[Stephen Wilson]

Hi Ihm, 

Not sure if your still around but if you are...

Love tidgraph...feature request?

Would it be possible to have a tidgraph open in a collapsed or partially collapsed state?

Stephen

[Pit.W.]

Stephen,

I wanted something similar and found a solution which is not elegant but ... well it works for me:

you can use the maxdepth attribute, set it to 1; then you add a conditional template which has a selector for the maxdepth, which you store in a field

1. This is what the tidgraph call looks like:

<$tidgraph start={{!!title}} maxdepth={{!!maxdepth}} startat={{!!startat}} />

2. This is what the relevant element of the conditional template look like:

                <$list filter="[all[current]search[<$tidgraph]]">

3. Here you select the maxdepth:

<$select field='maxdepth'>
<option value="1">1</option>
<option value="2">2</option>
<option value="10">10</option>
</$select>

Note that the value is stored in a field of the tiddler which calls the tidgraph, so it is persistent.
Note: this works with ALL the other attributes (like startat) as well.

Regards

Pit

--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d5b07d4c-f0f9-4780-9cdb-c1a8e63be17b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.