[tw] Re: Auto link to file in Wiki folder

[Stephan Hradek]

Use relative paths like "Pictures/picturenam.png"

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: A View Mode Editor and a simple Calcualtor

[Vincent Yeh]

The removal of jQuery and the resulting debugging took a lot longer than I 
expected. Finally I've got it done and tested with all the Examples given 
in TiddlySpot  (or in TiddlySpace 
).

   - Major changes
  - Said goodbye to jQuery -- now *they may not work in old browsers*.
  - major bug fixes -- old bugs that were sleeping long and new ones 
  from rewriting
  - better partial refreshing -- better performance for large tiddlers.
  
You are welcome to try and give feedback! See Release Note in TiddlySpot 
 (or in TiddlySpace 
) for download 
links and more details.

Have fun!
Vincent

On Saturday, October 11, 2014 10:58:26 AM UTC+8, Vincent Yeh wrote:
>
> Hi Yakov,
>
> Thanks for asking. The removal of jQuery dependencies is almost done and 
> quite some bugs are fixed. The next release shall come out soon.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Auto link to file in Wiki folder

[Daniel Sandström]

Hi.
I've begun embedding pictures into my wiki and I like the way a picture 
tells a thousand words. 

At the moment I have the "Wiki" folder, containing the actual TiddlyWiki 
file and an subfolder, "Pictures", containing various images. Now, 
everything works fine - at the moment. But I'm quite sure me or someone 
else will move the folder around in the future. So is there a command to 
extract the TiddlyWiki file path, remove TiddlyWiki.html ending and append 
\Pictures and then actual picture filename. Obviously I'd like everything 
to work as normal, regardless location, as long as we move the whole "Wiki" 
folder as one.

Thanks!

PS. Still going CLASSIC on this one.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Stephan Hradek]

Am Dienstag, 18. November 2014 23:47:59 UTC+1 schrieb Tobias Beer:
>
>
> Any idea why using the variable as declared in the set widget won't work 
> with the list widget?
>

Yes. Variables don't work there. You need an additional macrocall. 
Additionally you forgot the brackets arounf the variablename: $(field)$

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] XMLHttpRequest error code: 404

[JimyKK]

Hello again,

So I am using Nginx to host my Tiddlywiki Node.js install in a subdriectory 
i.e. https://mysite.com/wiki/

It works fine and I can access, edit and save everything but every-time I 
load the wiki I get a XMLHttpRequest error code: 404 popup (See attached 
image)

>From my understanding nginx isn't passing the XMLHttpRequest properly. 
Anyone know the appropriate configuration to fix this? My Google-fu has 
failed me on this one.

My simplistic config setup:
location  /wiki/ {

proxy_pass http://127.0.0.1:8001/;

}




-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Iterate fields

[Tobias Beer]

>
> http://tb5.tiddlyspot.com/#Listing%20Fields
>

Which makes me ask whether *core-version* and *module-type* are not, in 
fact, yet undocumented core fields.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Iterate fields

[Tobias Beer]

 Hi Danielo and Jeremy,

Maybe it's helping, maybe not... here are some attempts on listing fields...

http://tb5.tiddlyspot.com/#Listing%20Fields

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Tobias Beer]

Hi Stephan,
 

>  Not at the moment. I simply don't feel like it.


Sure thing, was just curious if that existed.

Any idea why using the variable as declared in the set widget won't work 
with the list widget?

<$set name="field" value="title">
<$list filter="[[$:/language/Docs/Fields]] [[$field$]] +[join[/]]">
$field$: <$view field="title"/>



The timelinemacro seems to use variables in its filter just fine...
http://tiddlywiki.com/#TimelineMacro

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: GSD5 Release 0.3beta

[Roma Hicks]

>
>
> Just to show you some of my ideas already working I set up a small space: 
> http://gsd5customizations.tiddlyspot.com/ 
> 
>
>
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 
> 
>
> 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 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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5][BUG] Camel case on system tiddlers

[Tobias Beer]

>
> Hello Tobías that's because none of the links contains camel case


of course ^_^

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: On the fly completions/suggestions

[Tobias Beer]

I think I'd much rather prefer an extensible toolbar that allows inserting 
all kinds of content, e.g. macro skeletons.

For example, with the ui to add a new tag being (a bit more of) a generic 
thing, it could be reused to...

   1. open the popup using an "insert link" button
   2. filter tiddler titles rather than just tags
   - perhaps with an option to search all tiddlers, including system & 
  shadows
  3. insert a [[link]] at the end of the textfield

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Stephan Hradek]

Am Dienstag, 18. November 2014 22:59:47 UTC+1 schrieb Tobias Beer:
>
> Any chance you'd up this and alike codebits to a GitHub repo of yours? 
> Where?
>
> Not at the moment. I simply don't feel like it.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: On the fly completions/suggestions

[Danielo Rodríguez]

This is a non trivial request since it requires parsing what you are writing on 
each key press. Code mirror can do this,but is not implemented in the current 
plugin and it is not easy to implement.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Tobias Beer]

Hi Stephan,
 

> Just wrote it. 5minutes including testing.
>

Kudos! Any chance you'd up this and alike codebits to a GitHub repo of 
yours? Where?

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Stephan Hradek]

Am Dienstag, 18. November 2014 22:54:39 UTC+1 schrieb Tobias Beer:
>
> Here is a generic "join" filter:
>>
>
> Did you just write that or did it come from an already brighter place? ^_^
>
 
Just wrote it. 5minutes including testing.
 

> Would it be sufficient to give the above code tiddler a *type* of 
> *application/javascript* so as to have it run after restart?
>

Type and field are listed in the tiddler. After setting those and 
restarting you're ready to go.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5][BUG] Camel case on system tiddlers

[Danielo Rodríguez]

Hello Tobías that's because none of the links contains camel case

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Tobias Beer]

>
> Here is a generic "join" filter:
>

Did you just write that or did it come from an already brighter place? ^_^

Would it be sufficient to give the above code tiddler a *type* of 
*application/javascript* so as to have it run after restart?

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: if tiddler is a tag ...then list tags

[Alex Hough]

It is useful to me as I follow a Bairdian 'new here' methodology from
taggly tagging land. Not all the time mind... New here is great for making
lists...

Mario, you are right, the info is under infomation, but I want to read the
last without clicking - Tobias is right too.

I like the Idea of check boxes to give the option of displaying info in
tiddler

Alex

On Tuesday, 18 November 2014, Tobias Beer  wrote:

> I've wondered about introducing checkboxes to allow optional view template
>> segments to be switched in. We could upgrade all of the tiddler info tabs
>> to be independently selectable as view template segments.
>>
>
> I can imagine that ViewTemplate sections will require slightly different
> contents & styling. I might prepare some demo wiki(s) shocasing how to
> turn (all) info-sections into viewtemplate contents...
>
>- as simple sections
>- or using sliders
>
> ...with some configuration panel allowing to turn them on / off by setting
> the appropriate tag.
>
> Tobias.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5][BUG] Camel case on system tiddlers

[Tobias Beer]

Hi Danielo and Stephan,
 

> As you can see navigation fails. In the first case it goes to a different 
> tiddler. In the second case it reports the tiddler as non existing.
>

Mhhh, not sure what's the difference but in my wiki it works just fine...

List Links Via Macro Or Widget 


(see last example)

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5][BUG] Camel case on system tiddlers

[Tobias Beer]

Or use the list-links macro altogether...

<>

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Stephan Hradek]

Here is a generic "join" filter:

/*\
title: $:/core/modules/filters/join.js
type: application/javascript
module-type: filteroperator

Filter operator that concatenates all tiddlers from the current list, using the 
operator as the seperator

\*/
(function(){

/*jslint node: true, browser: true */
/*global $tw: false */
"use strict";

/*
Export our filter function
*/
exports.join = function(source,operator,options) {
var result = '';
source(function(tiddler,title) {
result+=operator.operand + title;
});
return [ result.substr(operator.operand.length) ];
};

})();



Example for usage:

<$list filter="[[$:]] [[language]] [[Docs]] [[Fields]] [all[current]] 
+[join[/]]">
<$view field="title"/>


Or shorter:

<$list filter="[[$:/language/Docs/Fields]] [all[current]] +[join[/]]">
<$view field="title"/>





-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Tobias Beer]

Hi Stephan,

The usecase wasn't actually that generic, after all. ;-)

http://tb5.tiddlyspot.com/#Listing%20Fields

See tab "*standard*".

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Stephan Hradek]

Remember that there seems to be a problem with unnamed parameters and the 
$macrocall widget. As far as I know, it's not possible to use it without 
specifying parameter names.

But if the macro should be generic, I think you should go for a javascript 
macro with unlimited parameters.


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Tobias Beer]

Hi Stephan,

Thanks, I was hoping I could avoid using an extra macro just to concatenate 
the two.
 

> \define languageDocsFields() $:/language/Docs/Fields/$(currentTiddler)$
>
 
I guess it's going to be a generic *concat* macro instead.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Concatenated Widget Parameters

[Stephan Hradek]

\define languageDocsFields() $:/language/Docs/Fields/$(currentTiddler)$

<$link to=<>><$view field="title"/>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5][BUG] Camel case on system tiddlers

[Stephan Hradek]

I think it's a known problem. At lest I read that several times.

Try this:

<$list filter="[all[]tag[test]]">


*<$link><$view field="title"/>



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] button formating

[Stephan Hradek]

you can assign any class(es), not just the one you found and define CSS for 
them.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] button formating

[Andreas]

Hi,
I use the button widget to create a new tiddler. This works fine.

<$button message="tm-new-tiddler" param="TemplateTask">New Task

But now I want to put some color in the hole story. The only thing I found 
is, but makes the button very big, unfortunately:

class="tc-btn-big-green"

Are there more possibilities to change the color of the button?

Thanks, Andreas



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Concatenated Widget Parameters

[Tobias Beer]

Is there any way on how to achieve something like this...

<$link to="*$:/language/Docs/Fields/{{!!title}}*">{{!!title}}

?

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5][BUG] Camel case on system tiddlers

[Danielo Rodríguez]

How to reproduce the problem:

Go to tiddlywiki.com

Create two tiddlers tagged as test:

 $:/CamelCase
 $:/test/OtherCase


Create a third tiddler with this content:

<$list filter="[all[]tag[test]]">


*<$link to={{!!title}}>{{!!title}}



As you can see navigation fails. In the first case it goes to a different 
tiddler. In the second case it reports the tiddler as non existing.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: GSD5 Release 0.3beta

[Danielo Rodríguez]

Hello Roma

Just to show you some of my ideas already working I set up a small 
space: http://gsd5customizations.tiddlyspot.com/


El martes, 18 de noviembre de 2014 16:51:27 UTC+1, Roma Hicks escribió:
>
> 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.
 

> I will get the conversion action/project planned for another release.  I 
> do see the merit of having that built-in.
>
> Nice!
 

> 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

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.
 

> 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 also like your "avoid tags" politic. The implementation seems cleaner.
 

> 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. 
>
Your right, and maybe my problem comes from the fact that I was using 
realms in the wrong way.

 

>  Actions can now be further sorted into categories and be done by 
> context.  
>

How?
 

> 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.
>
> Yes, it will fit better my use case.
 

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

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki Hangout #69 on Tuesday 18th November at 4pm GMT

[Jeremy Ruston]

TiddlyWiki Hangout #69 is about to start.

Watch and post questions at:

https://plus.google.com/events/cv5b80i86jvnnkvj1g9ufq6vork

Or join in at:

https://plus.google.com/hangouts/_/hoaevent/AP36tYdUdzN-GekkJzanJ3ePNAIzI_fSjUdQFelmXurKmGMt7U9Abw

Best wishes

Jeremy.

On Thu, Nov 13, 2014 at 6:36 PM, Jeremy Ruston 
wrote:

> TiddlyWiki Hangout #69 will be on Tuesday 18th November at 4pm GMT.
> Details here:
>
> https://plus.google.com/events/cv5b80i86jvnnkvj1g9ufq6vork
>
> You can post questions for the hangout using the Q&A button on the video
> preview at the above link. You'll then need to click the "grid" icon at the
> top right and choose the Q&A button.
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> mailto:jeremy.rus...@gmail.com
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: GSD5 Release 0.3beta

[Roma Hicks]

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 
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
> 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.
> 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 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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: GSD5 Release 0.3beta

[Seann Hamilton]

Hey Roma, that delay was my fault.  I was away from email, and the group is 
set up to require approval for one's first post (cuts down on spam).  You 
shouldn't have that issue ever again.  GSD5 is looking good, btw!  

~ Seann

On Sunday, November 16, 2014 10:15:09 PM UTC+1, Roma Hicks wrote:
>
> Getting-Stuff-Done 5 (GSD5) Plugin
> Version 0.3beta
>
> Introducing GSD5 v0.3beta!  I posted this a few days ago an the GTD group 
> but it has to be approved before posted.  It has been a few days so I will 
> post it first here.
>
> *Download:* http://gsd5.tiddlyspot.com/
>
> *Added Features*
>
>
>- A References list. Provide a means of viewing references without 
>going through the project tiddler.
>- The pseudo-realm 'all'. Allows all actions and project to be viewed 
>at once regardless of assigned realm.
>- Allow the user to toggle the display of the realm selector on the 
>Dashboard.
>
> Corrected Bugs
>
>- Newly created action/projects/contact/reference/realm trigger 
>autosave.
>- Projects and actions that are marked completed trigger autosave, 
>after dependent actions/projects are properly resolved.
>
>
> *Bugs/Issues*
>
> Any bugs/issues please visit the projects page at:
> https://github.com/roma0104/gsd5/issues
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] widget to Goto Ranomized Tiddler

[Jeremy Ruston]

Hi Tobias

OK, I can only reiterate what I've said above. If you want to do stuff like
that then the current state of the random number needs to be stored in a
tiddler so that it will be available across refreshes. There needs to be a
specific trigger to change the random number (eg starting up, or clicking a
button). What you are asking for is possible, but I don't think the
alternative implementations that you've proposed would not work.

Best wishes

Jeremy.



On Tue, Nov 18, 2014 at 3:20 PM, Tobias Beer  wrote:

> Perhaps it would be helpful if I understood your underlying use case. What
>> are you trying to achieve with random number generation?
>>
>
> There are plenty usecases for outputting a random list of tiddlers
> matching a given filter along with a template...
>
>- show: 10 random unanswered / wrongly answered quiz questions
>- show a random quote
>- show a "Did you know?" section listing interesting content
>- ...
>
> Best wishes, Tobias.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] widget to Goto Ranomized Tiddler

[Tobias Beer]

>
> Perhaps it would be helpful if I understood your underlying use case. What 
> are you trying to achieve with random number generation?
>

There are plenty usecases for outputting a random list of tiddlers matching 
a given filter along with a template...

   - show: 10 random unanswered / wrongly answered quiz questions
   - show a random quote
   - show a "Did you know?" section listing interesting content
   - ...

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Iterate fields

[Jeremy Ruston]

Hi Danielo

>
> Easy if you know those fields (not documented in any place) and currently.
> In the future they may be more fields.
>

Well, we could provide a shortcut that returns all the core fields, but the
problem would then become which core fields should be included. Would you
want "caption" included? What about the draft fields?

If you just want to exclude the fields that are handled by the core edit
template segments then you can use the same technique as the core itself
and look up the values in the config tiddlers with the prefix
`$:/config/EditTemplateFields/Visibility/`.

Best wishes

Jeremy




>
> Thank you for your answer Jeremy.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Iterate fields

[Danielo Rodríguez]

>
> > The problem is that you have to specify a prefix for all your custom 
> fields. Maybe the core fields should be prefixed with core_ ?
>
> You can remove the core fields easily enough:
>
> [all[tiddlers]fields[]] -title -text -modified -modifier -created -creator 
> -tags
>

Easy if you know those fields (not documented in any place) and currently. 
In the future they may be more fields.

Thank you for your answer Jeremy. 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] TW5: appendTo / prependTo / insertAfter / insertBefore

[Jeremy Ruston]

Hi Tobias

It sounds like you were expecting "list-before" and "list-after" to work
differently than they do. They affect the ordering of tiddlers that carry a
particular tag, and are not a mechanism for arbitrarily inserting content
after specified tiddlers.

> That got me thinking that it might be quite powerful to be able to define
some tiddler as to be rendered whenever certain other (shadow) tiddlers are
being rendered / transcluded.

It sounds like monkey patching.

> I can imagine that there might be a performance impact to this, but it
would sure make customizing the output a whole lot more flexible.

Well, it's a solution to a problem that is already solved in the TiddlyWiki
core, and I'm not sure whether this is any better. It makes it easier to
customise things that haven't been engineered with a system tag, but that
seems to me to just increase dependencies between user markup and core
markup. Better to engineer the right adaptation points I think.

Best wishes

Jeremy.




On Thu, Nov 13, 2014 at 5:37 PM, Tobias Beer  wrote:

> Hi Jeremy,
>
> After you showed me
>  how
> to use *insert-after* to render conditional content with
> *$:/tags/ViewTemplate*, I tried to experiment a little rendering
> something *non-intrusively* at the bottom of the sidebar below
> *$:/core/ui/SideBarLists*.
>
> http://tb5.tiddlyspot.com/#%24%3A%2Ftemplate%2FAfterSidebar
>
> Turns out, that didn't quite work, as I realized that the *ListField* for
> *$:/tags/PageTemplate* only entails the toplevel elements, so that
>
> *list-after => $:/core/ui/**SideBarLists*
>
> ...won't have any effect as it's not part of the *ListField*. So,
> *list-after* and *list-before* really only apply to the *ListField*, not
> DOM elements or tiddlers being rendered.
>
> ———
>
> That got me thinking that it might be quite powerful to be able to define
> some tiddler as to be rendered whenever certain other (shadow) tiddlers are
> being rendered / transcluded.
>
> Here is how that could work:
>
>1. give *the tiddler* the tag of the corresponding *shadow tiddler*
>2. define the field *render*
>3. set the field value for *render* to either of *appendTo*,
>*prependTo*, *insertAfter*, *insertBefore*
>4. transclude *the tiddler* accordingly whenever the *shadow tiddler*
>being referred to is rendered
>
> I can imagine that there might be a performance impact to this, but it
> would sure make customizing the output a whole lot more flexible.
>
> ———
>
> As it is in the context of tagging, the documentation
>  on *list-after* and *list-before *doesn't
> say too much about how it is being used for templating, e.g.:
>
>- what system-tags is this relevant for
>- how to figure out the rendering order / elements / available
>placeholders
>- etc...
>
> I think it would be good to find some details on this at...
>
> http://tiddlywiki.com/#SystemTags
>
> Best wishes, Tobias.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5][BUG] Cloning on TW5.1.5 removes the tags

[Jeremy Ruston]

Thanks Danielo, fix coming shortly,

Best wishes

Jeremy

On Tue, Nov 18, 2014 at 2:07 PM, Danielo Rodríguez 
wrote:

> Hello,
>
> Cloning a tiddler on TW5.1.5 does not respect the original tags of the
> cloned tiddler. When I clone a tiddler I expect everything to be copied.
>
> I opened a github issue:
>
>
> https://github.com/Jermolene/TiddlyWiki5/issues/1097
>
>
> Regards.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Iterate fields

[Jeremy Ruston]

Hi Danielo

You can iterate over the fields of a tiddler the "fields" filter operator:

http://tiddlywiki.com/#FilterOperator%3A%20fields

For example:

[[HelloThere]fields[]] - returns names of fields on "HelloThere"

[all[tiddlers]fields[]] - returns fields used on all non-shadow tiddlers

> The problem is that you have to specify a prefix for all your custom
fields. Maybe the core fields should be prefixed with core_ ?

You can remove the core fields easily enough:

[all[tiddlers]fields[]] -title -text -modified -modifier -created -creator
-tags

Best wishes

Jeremy.


On Tue, Nov 18, 2014 at 2:11 PM, Danielo Rodríguez 
wrote:

> Hello,
>
> Is possible to iterate over tiddler fields? It will be very useful to
> construct dynamic tables and UIs.
>
> Regards.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Iterate fields

[Danielo Rodríguez]

Yes it is:

http://tiddlywiki.com/prerelease/#FilterOperator%3A%20fields

But this iterates over all the fields. Maybe using the prefix operand you 
can select a sub selection of fields. The problem is that you have to 
specify a prefix for all your custom fields. Maybe the core fields should 
be prefixed with core_ ?

El martes, 18 de noviembre de 2014 15:11:31 UTC+1, Danielo Rodríguez 
escribió:
>
> Hello,
>
> Is possible to iterate over tiddler fields? It will be very useful to 
> construct dynamic tables and UIs.
>
> Regards.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Iterate fields

[Danielo Rodríguez]

Hello,

Is possible to iterate over tiddler fields? It will be very useful to 
construct dynamic tables and UIs.

Regards.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5][BUG] Cloning on TW5.1.5 removes the tags

[Danielo Rodríguez]

Hello,

Cloning a tiddler on TW5.1.5 does not respect the original tags of the 
cloned tiddler. When I clone a tiddler I expect everything to be copied.

I opened a github issue:


https://github.com/Jermolene/TiddlyWiki5/issues/1097


Regards.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Adjust sameday filter results for time zone

[Jeremy Ruston]

Hi cmari

The explanation is in this ticket:

https://github.com/Jermolene/TiddlyWiki5/issues/190

The problem is that although dates and times are stored in UTC they are
displayed in the users local timezone. The sameday operator also works on
the local timezone.

Your workaround is sound but this should be fixed. I've created a new
ticket here:

https://github.com/Jermolene/TiddlyWiki5/issues/1096

Best wishes

Jeremy


On Sat, Nov 15, 2014 at 6:58 PM, cmari  wrote:

> For a long time I've been mystified by the fact that I could never get
> correct results when I experimented with what's described in
> http://tiddlywiki.com/#FilterOperator%3A%20sameday
> where it says
> [sameday[20140410]] Returns a list of the tiddlers modified on the 10th
> April 2014.
>
> I am 8 hours behind UTC, and I assumed that had something to do with
> things.  But sameday doesn't seem to look for the UTC date that I can see
> in the modification field.
> If I try sameday with today's date (November 15th, or 20141115), for
> example, I get only tiddlers that were modified on the 14th (with a
> modified field of, e.g., 20141114160205254).
> On the other hand, if I give tomorrow's date (20141116), I do see today's
> tiddlers (even though they have a modification date of, e.g.,
> 20141115152548000).
>
> After lots of trial and error, I discovered that I can get the correct
> results (I think!) if I append a number to the date that is equal to or
> larger than the number of hours by which my time zone is behind UTC.
> To get tiddlers I modified today (the 15th of November), I can use
> [sameday[201411158]]
> (this works even for tiddlers modified at night, when the date in the
> modification field date has already changed to the next day).
>
> Because I don't understand this, I am unfortunately not able to offer any
> assistance with updating documentation, but I do think it's confusing and
> I'm hoping that someone else might be able to insert some clarification
> into the sameday documentation.
>
> Thanks,
> cmari
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] widget to Goto Ranomized Tiddler

[Jeremy Ruston]

Hi Tobias

Just to be clear, a "[random[]]" filter is a dead duck with the current
architecture

> What is the benefit of that over a [random[n]] filter?

That it is possible for it to work! A random filter cannot work.

> First of all, I think there are usecases where a new random set at each
refresh is actually desired.

I don't think so. A refresh cycle can happen at any time, potentially many
times a second.

> Where that is not the case, does the DOM get entirely replaced or are
states preserved upon refresh?

The DOM is selectively updated, with parts of the tree being replaced as
required. It is not possible to store state in the DOM.

> What is important is that each instance of a [random[]] filter or a
filter making use of a random number needs to persist the initial draw
until a page reload.

We can use the stored random number as a seed for generating the numbers
that we need. We can also provide a "throw the dice" button that generates
a new random number.

Perhaps it would be helpful if I understood your underlying use case. What
are you trying to achieve with random number generation?

Best wishes

Jeremy


On Mon, Nov 17, 2014 at 9:37 AM, Tobias Beer  wrote:

> Widgets can be redrawn at any time, if the core detects changes in the
>> tiddler store. So whenever a tiddler, or a section of a tiddler is redrawn
>> and it contains the [random[]] filter, you'll get a new result. But that's
>> not what you want.
>>
>
> Then that means that such a "random state" is required for every instance,
> without the user necessarily being required to specify it. The question of
> whether or not there'd be a *[random[]]* filter seems independent of that
> requirement to me.
>
> Best wishes, Tobias.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Transclusion Parameters

[Tobias Beer]

>
> <$let param1="value1" param2="value2">
> {{title||template}}
> 
>

yes please ...perhaps even implement *$set* that way directly

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Tobias Beer]

I think the doc might need to mention basic guidelines as to what 
characters to best avoid as a tiddler title...

   - pipes
   - single- or double quotes
   - anything else?

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: On the fly completions/suggestions

[Alain Dutech]

Hello,
I am "upping" this topic again.

I am still looking for a way to suggest "link completions" in tiddler 
editing. 
For example, 
I'm typing "When we arrive at [[Hol"
the editor suggests "[[HolidayLocation]]" based on the existing tiddlers.
I type ENTER to validate and keep typing, or wave it out by keeping typing 
"lyday Inn" :o)

If this functionnality does not exists, could someone point me to some 
starting point. I'm even willing to help develop a plugin for this.

Alain

On Thursday, September 11, 2014 12:38:52 AM UTC+2, c pa wrote:
>
> Alain,
>
> (From the Tiddlywiki roadmap)
>
> Some important features were deferred to be added after the beta:
>
>- Keyboard snippet expansion in the text editor
>
> Chime in anyone if there is a plugin out there that does this
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Stephan Hradek]

Am Dienstag, 18. November 2014 11:48:36 UTC+1 schrieb Jeremy Ruston:
>
>
> We need to find a syntax that isn't currently valid to be confident that 
> we don't change the interpretation of existing wikitext, or we need to be 
> happy to break backwards compatibility.
>

I think a single pipe in a tiddler title would already break, so is not 
something we can consider proper syntax.

For example: If I define a tiddler "showjustme" containing "I'm the 
template" and then using this in another tiddler:

test me: {{test me||showjustme}}

test|me: {{test|me||showjustme}}

I don't get

test me: I'm the template

test|me: I'm the template

but

test me: I'm the template

test|me: {{test|me||showjustme}}


So my proposal would be to consider something like this

*{{* *title **|* *param**:**"**value**"* ... *|* *template **}}*

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Transclusion Parameters

[Stephan Hradek]

Am Dienstag, 18. November 2014 11:48:40 UTC+1 schrieb Tobias Beer:
>
> Mind explaining / referencing a thread about what a *$let* widget is (to 
> do)?
>

The let widget I once proposed and created is an abbreviation of multilevel 
set widgets.

So the previous example:

<$set name="param1" value="value1">
<$set name="param2" value="value2">
{{title||template}}



would reduce to

<$let param1="value1" param2="value2">
{{title||template}}


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Skeeve: Quick Tagging

[Tobias Beer]

Hi Jeremy,
 

> At the moment the action widgets only work immediately inside a button 
> widget. There are a few other widgets such as the link widget are also 
> candidates to support action widgets.
>
> I agree that the ability to generate multiple action widgets with the list 
> widget would be pretty useful, and I plan to support that by relaxing the 
> requirement for the button widgets to be immediate children of the button. 
> That change would also allow us to use the reveal widget to make action 
> widgets conditional.
> 
>

I second that, as I just tried...

<$list filter="[is[current]tag[task]!tag[archived]]">
set task status:
<$fieldmangler>
<$set name="statuses" value="[[next]] [[wait]] [[future]] [[done]] 
[[archived]]">
<$list filter=<>>
<$button>
<$list filter="<> - [all[current]]">
<$action-sendmessage $message="tm-remove-tag" 
param="<>"/>

<$action-sendmessage $message="tm-add-tag" param="<
>"/>
<>






See TaskTagger  and 
it's not quite working example usage at TaskOverview 
.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Jeremy Ruston]

Hi Tobias

>
> Looks rather backwards compatible to me.
>
> The trouble is that this is already valid wikitext:

{{title myVariable:"value" anotherVariable:"another" ||myTiddler}}

It transcludes the tiddler `myTiddler` with the current tiddler set to
`title myVariable:"value" anotherVariable:"another"`. You may say that that
is a ridiculous tiddler title but what about a tiddler called `macro
definition:"system-call"`?

We need to find a syntax that isn't currently valid to be confident that we
don't change the interpretation of existing wikitext, or we need to be
happy to break backwards compatibility.

Best wishes

Jeremy.



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Transclusion Parameters

[Tobias Beer]

Hi Stephan,

That's a perfect example, I'd say.
I think that's quite good enough in order to achieve parametric 
transclusion, even without a more concise syntax.

Mind explaining / referencing a thread about what a *$let* widget is (to 
do)?

Best wishes, Tobias.

On Tuesday, 18 November 2014 09:39:20 UTC+1, Stephan Hradek wrote:
>
> As a workaround/solution you could consider using the $set widget.
>
> <$set name="param1" value="value1">
> <$set name="param2" value="value2">
> {{title||template}}
> 
> 
>
> BTW: I still would like to have a $let widget.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Tobias Beer]

>
> perhaps it might be a good idea to implement a *core* field, after all, 
> indicating the core-version with which a tiddler was last saved
>

probably overkill

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Tobias Beer]

>
> The syntax I gave was perhaps a poor example. We couldn't implement it 
> without making it impossible to transclude tiddlers with spaces and colons 
> in their titles. So we'll need to figure out an extension to the existing 
> syntax that is backwards compatible.
>

Looks rather backwards compatible to me. Any basic transclusions as 
currently available should perfectly work in a newer version providing this 
type of parametric transclusion.

Of course, it won't work the other way around, which gets me to think that 
perhaps it might be a good idea to implement a *core* field, after all, 
indicating the core-version with which a tiddler was last saved... and thus 
be able to more easily spot issues, e.g. upon import.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Tagging Macro Problems

[Tobias Beer]

>
> <$set name="tid" value="" default="<>"/>
>
> So, there's an empty string being passed as the attribute "value". There's 
> no way for the set widget to distinguish that empty string as a missing 
> value that needs to be defaulted unless it regarded all empty strings as 
> missing values. The trouble with that is that often we want to be able to 
> assign an empty string to a variable. That could be accomplished by 
> assigning the empty string as expected if the "default" attribute is 
> missing.
>

I totally understand that, my suggestion was to alter the actual text 
substitution so as to pass down a literal "*<>"* or "*<>"* 
or any appropriate flag as a *string*, which of course would not be 
possible for use as an actual value.

So, instead we would be left with...

<$set name="tid" value="""<>""" default="<>"/>

...and the appropriate handling by the set widget.

Not if *<>* provides for a naming convention but something that 
doesn't leave us with an empty string... and widgets by default treating 
all of *<>*, *<>* or ** the same, except for 
when explicitly declared otherwise.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: if tiddler is a tag ...then list tags

[Tobias Beer]

>
> I've wondered about introducing checkboxes to allow optional view template 
> segments to be switched in. We could upgrade all of the tiddler info tabs 
> to be independently selectable as view template segments.
> 
>

I can imagine that ViewTemplate sections will require slightly different 
contents & styling. I might prepare some demo wiki(s) shocasing how to turn 
(all) info-sections into viewtemplate contents...

   - as simple sections
   - or using sliders

...with some configuration panel allowing to turn them on / off by setting 
the appropriate tag.

Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Jeremy Ruston]

Hi Tobias

The syntax I gave was perhaps a poor example. We couldn't implement it
without making it impossible to transclude tiddlers with spaces and colons
in their titles. So we'll need to figure out an extension to the existing
syntax that is backwards compatible.

Best wishes

Jeremy

On Tue, Nov 18, 2014 at 10:21 AM, Tobias Beer  wrote:

> Hi Jeremy,
>
>
>> There's no direct way to pass parameters to transclusions. As Stephan
>> says, at the widget level you can use variables to pass values through to
>> transclusions. We could introduce a higher level syntax to make it easier
>> to pass variable parameters to transclusions. Something like:
>>
>> {{myVariable:"value" anotherVariable:"another" ||myTiddler}}
>>
>> That syntax looks definitely more meaningful than my proposal above,
> perhaps with the (optional) addition of...
>
> {{title myVariable:"value" anotherVariable:"another" ||myTiddler}}
>
> If implemented, I think this will majorly enhance templating capabilities,
> as it did in TWc, without the increased complexity of having to wrap it all
> in ever more macro declarations.
>
> Best wishes, Tobias.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Tobias Beer]

Hi Jeremy,
 

> There's no direct way to pass parameters to transclusions. As Stephan 
> says, at the widget level you can use variables to pass values through to 
> transclusions. We could introduce a higher level syntax to make it easier 
> to pass variable parameters to transclusions. Something like:
>
> {{myVariable:"value" anotherVariable:"another" ||myTiddler}}
>
> That syntax looks definitely more meaningful than my proposal above, 
perhaps with the (optional) addition of...

{{title myVariable:"value" anotherVariable:"another" ||myTiddler}}

If implemented, I think this will majorly enhance templating capabilities, 
as it did in TWc, without the increased complexity of having to wrap it all 
in ever more macro declarations.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Tagging Macro Problems

[Jeremy Ruston]

Hi Tobias

Ok, so let's consider the hypothetical syntax fixed...
>
>>
> \define tagging(title)
> <$set name="tid" value="""$title$""" default="<>"/>
> <$list filter="[[<>]tagging[]]"/>
> \end
>
> The trouble is that in many situations an empty string is a valid value
>> that shouldn't be defaulted; what we really want here is a way to detect
>> missing parameters.
>>
>
> How and when are variables evaluated? Could the evaluation return some
> *<>* or *<>* value subsequently passed to the set widget
> in order to trigger using a default fallback?
>

The trouble is that the macro parameter is inserted into the macro body
using textual substitution. Thus if you don't pass the title parameter then
the first line of the macro body will be:

<$set name="tid" value="" default="<>"/>

So, there's an empty string being passed as the attribute "value". There's
no way for the set widget to distinguish that empty string as a missing
value that needs to be defaulted unless it regarded all empty strings as
missing values. The trouble with that is that often we want to be able to
assign an empty string to a variable. That could be accomplished by
assigning the empty string as expected if the "default" attribute is
missing.

I think it's less complicated to fix the issue by introducing transcluded
default values for macro definitions.

Best wishes

Jeremy.



>
> Best wishes, Tobias.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [tw5] CycleTags button in TW5?

[Jeremy Ruston]

Hi Tobias

> My pain point being that understanding and leveraging all this high-level
syntax correctly appears to require unveiling a lot more concealed,
under-the hood knowledge than a "trivial" js-script used to.

Yes, except that the "concealed, under-the-hood knowledge" is just poor
documentation.

Perhaps missing from the developer docs , what
> are the standards / recommendations for extending the system-tiddler
> namespace when it comes to plugin modules / components? Is the
> recommendation to simply put it all under
> *$:/plugins/githubuser/pluginname/*?
>

Yes, that's the best practice. It isn't enforced as a restriction because
there are some situations where a plugin needs to define a shadow tiddler
outside its namespace. For example, the core plugin defines
"GettingStarted", "$:/ControlPanel" etc. as shadow tiddlers. Other plugins
may want to provide defaults (eg visibility of toolbar buttons that they
include).

Best wishes

Jeremy.


>
> Best wishes, Tobias.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Custom Class Wrapper Swallowed

[Tobias Beer]

Thank you, Mario, 

...include the class parameter in the macro and create the HTML in the 
> macro. 
> IMO this is creates a much cleaner experience.
>
> <>
>

I had it already updated only just not the source code in the 
documentation. ;-)

http://tb5.tiddlyspot.com/#External%20Image%20Path

Best wishes, Tobias. 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: if tiddler is a tag ...then list tags

[Jeremy Ruston]

Hi Tobias

> I believe the answer to that is somewhat obvious: to make tagging as
prominent as it once was and avoid the two-click process.

I've wondered about introducing checkboxes to allow optional view template
segments to be switched in. We could upgrade all of the tiddler info tabs
to be independently selectable as view template segments.

Best wishes

Jeremy.


On Tue, Nov 18, 2014 at 8:34 AM, Tobias Beer  wrote:

> So why would you want to duplicate it.
>>
>
> I believe the answer to that is somewhat obvious: to make tagging as
> prominent as it once was and avoid the two-click process.
> A (deactive) core template for a viewtemplate tagging section tagging
> would also help overall UI consistency.
>
> Best wishes, Tobias.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Transclusion Parameters

[Jeremy Ruston]

Hi Tobias

There's no direct way to pass parameters to transclusions. As Stephan says,
at the widget level you can use variables to pass values through to
transclusions. We could introduce a higher level syntax to make it easier
to pass variable parameters to transclusions. Something like:

{{myVariable:"value" anotherVariable:"another" ||myTiddler}}

Best wishes

Jeremy.



On Tue, Nov 18, 2014 at 8:39 AM, Stephan Hradek 
wrote:

> As a workaround/solution you could consider using the $set widget.
>
> <$set name="param1" value="value1">
> <$set name="param2" value="value2">
> {{title||template}}
> 
> 
>
> BTW: I still would like to have a $let widget.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Transclusion Parameters

[Stephan Hradek]

As a workaround/solution you could consider using the $set widget.

<$set name="param1" value="value1">
<$set name="param2" value="value2">
{{title||template}}



BTW: I still would like to have a $let widget.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: if tiddler is a tag ...then list tags

[Tobias Beer]

>
> So why would you want to duplicate it.
>

I believe the answer to that is somewhat obvious: to make tagging as 
prominent as it once was and avoid the two-click process.
A (deactive) core template for a viewtemplate tagging section tagging would 
also help overall UI consistency.

Best wishes, Tobias.

-- 
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.
For more options, visit https://groups.google.com/d/optout.