Hi ihm,
> WOW!!! A few things! hehehehehehehehe
>
They are GREAT ideas!!! I am going through them and will work on the
> low-hanging fruit ASAP. There are others that are difficult.
>
Low hanging fruits are tasty. :D
I really like the idea of node templates, I think I might target that first.
>
Great!
> You would be able to add images, etc. However, Sylvain had requested
> vertical layout. I think vertical layout is much more difficult to do than
> the node templates. I will definitely skip reverse layouts for now :) only
> South and East are in my radar screen at the moment.
>
I sure see how that's the most difficult part in terms of abstracting and
refactoring and figuring out algorithms that would cater all cases in one.
> As for the node templates, what do you think about the following:
>
> 1. A nodetemplate attribute which is applied to all nodes *unless* :
>
Yes.
> 2. the node has a field called tgr-node-template indicating the template
>
Yep.
> 3. After choosing the base template from rules 1&2:
>
> 3.1. If a node template exists with the base template name followed by
> a number (eg. my-node-template-1) then it will be applied for nodes at
> that level otherwise the base template is used.
>
Even better, but perhaps postpone until the basics work, e.g. 1 first and
then 2. This may get complicated, unless it isn't then go ahead.
Also: Every template that has a tgr-css-class field will override the CSS
> class for the node in question.
>
Good thinking. I think it needs to be override, as the basic template
already has a load of graphic features, e.g. dropshadows. So, you wouldn't
want to override that but rather start from scratch.
> I will keep the node title attribute and extend it to specify a list of
> fields instead of just one field. The first one with a value will be used
> (if nodetemplate is not defined).
>
As I said, I would really use a {{||template}}... that way you don't define
anything and users are free to stick into the node whatever they want,
content-wise.
> e.g. "caption mynicetitle title" will use caption if it exists, otherwise
> mynicetitle and title as last resort.
>
That would be for an individual template to implement. But, I would not
burden myself with anticipating useful templates. Instead, being able to
define a custom template allows to fully control the presentation.
> Edge Templates
> For edge templates I have to think about that one a lot, that is much much
> more difficult to do in a proper extendable way because there is a lot of
> computations involved to calculate the edges and the average user will have
> to code javascript to do it. Might not be a good idea, but I'll keep
> thinking about it.
>
I understand. I have not looked at your code close enough to understand
what's involved or if that's even doable (without js).
Plugin config name standard
> BTW, what is the standard naming convention for plugin configuration
> tiddlers?
> is it $:/config/plugins/<plugin-name>/....
> or is it $:/config/<plugin-maker>/<plugin-name>/....???
>
Tbh, I don't think there are tight conventions. Possibly, the config should
even be under the plugin namespace. But yes, having the username be part of
it makes sense, so either:
*$:/config/plugins/ihm/tidgraph/config*
or perhaps actually better:
*$:/plugins/ihm/tidgraph/config*
> Custom modes
> This one is easy to do by using configurable filters like you suggested,
> what use-cases did you have in mind?
>
Aplenty, for starters, the reverse of the two that are given, so links and
tags. And then also "listed" or "listing" in a given field.
Thanks for all your help!
>
You're very welcome. It's a great (actually quite little) plugin with big
potential.
What would you think about me opening up a bunch of issues in your repo
with my suggestions, so you can further chunk them up or give code-related
feedback, talk details, etc.?
Best wishes,
— tb
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/ff7f56d4-71dd-4c68-ac5e-e63ae4ed64ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
