On Tuesday, November 11, 2014 4:00:49 PM UTC+1, Tobias Beer wrote:
>
> To me, a graph displays relations between tiddlers and the overhead of 
> having to use dedicated tags to relate tiddlers to a given view seems 
> redundant, to some extend bloating a tiddlers metadata.
>

At first, I had the same feeling. But not anymore. ... 
As our TWs tend to grow, imo we need to add more tags anyway to group our 
tiddlers. Since TW filters can be very complex, I think it's possible to 
have good control. 

I actually like the additional (curated) edge layer. It acts like an index 
and gives as very fast access to tiddlers with a special attribute, without 
the need, to modify the tiddler. 
On the other hand, it introduces some syncing problems for export / import 
and in an multi user, multi wiki environment. (But we can deal with this 
later :)

If the TW is new, and has just some tiddlers, actually _no_ tag/filter is 
needed at all. We can work with the whole set. ... As discussed in the last 
hangout #68 [2] the vis library even has a clustering function [1]. IMO 
it's not used at the moment. ... but it's there. So it should be possible 
to handle a large ammount of tiddlers in the same view, if needed.

There is one more thing, I'm interested in. ... It's the TWs "hidden 
structure". 

By "hidden structure" I mean ... references, tags, tagging. This structure 
is created automatically, when tiddlers are added and refactored. 
References may change, if you rewrite tiddler content. Tiddlers may be 
splitted .... I'd like to make this structure visible. We also did discuss 
this a little bit at hangout #68. ...

So I'm looking forward to mess with the code ;)


@Felix, 
Don't be scared :) by the number of requests that pop up from all sides. 
That happens if you create something interesting :) As I said in the 
hangout. Make *your core thing *work. Extensions can be made later.

IMO it's good that you expose a lot of configuration data as json tiddlers. 
We can mess around with them. 
As Jeremy said, the core may provide easy UI access for those parameters, 
because the core also needs this feature. 
So you can focus on the vis.js stuff at the moment :)

have fun!
mario

[1] http://visjs.org/docs/graph.html#Clustering
[2] https://www.youtube.com/watch?v=H8G6BEQpvW0

-- 
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.

Reply via email to