from:"NT"

Hey Mat, you are a good observer. Indeed I am interested in using the wiki 
in a semantic way, in a RDF-like style. Would be awesome if you could do 
deductive reasoning over the connections of some more tiddlers. Semantic 
tagging could lift this a step further to realisation. 
But I am still at the beginning, trying to figure out first whats possible 
and what structuring makes sense just with the normal tags or normal 
fields. But sure, typed fields would make this more straight-forward to 
realize, e.g. a "same as" field with other tiddler names inside. But cleary 
this is introducing more complexity into the whole wiki. And more 
complexity always lead to more problems. Thats why I am a friend of 
minimalism as far as possible. So I'll keep exploring what kind of 
information structuring is possible just with the normal wiki for the next 
days. 
But as soon as the limits are clear to me, I'll be trying the GenTags 
Plugin. I am quite curious about it. I already found some bits, but if you 
- or somebody - have more information available about semantics / RDF 
connected to TiddlyWiki I would be very happy to hear about - even persons 
busy in this field would be of interest for me. A bigger talking about that 
we should shift to another place where it is not off-topic. Thanks for the 
hint, really :-)

Am Donnerstag, 1. September 2016 14:56:45 UTC+2 schrieb Mat:
>
> NT, you might be interested in tiddlywizard @Jed / @inmysocks "Gen Tags 
> <https://groups.google.com/forum/#!msg/tiddlywiki/qBnuMYXXxWw/8SpZJF2dAgAJ;context-place=forum/tiddlywiki>".
>  
> It aims to solve the recurring request for different *types *of tags 
> ("typed tags", "sematic tagging", and more names).
>
> <:-)
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5a6e43c1-4c40-4661-a65d-7a1d47b1c91d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Show a list of all tags without "companion" tiddler

Oh nice - great stuff, Danielo! Special Thx for this effort. 
The code is always less than I expect it would be. I have to get back more 
into Wiki syntax again.
For now this topic is solved for me.
Thanks to everyone.

Am Donnerstag, 1. September 2016 13:44:52 UTC+2 schrieb Danielo Rodríguez:
>
> I have edited my previous answer, but in case anyone is reading the 
> emails, here is the correct filter:
>
>
> <$list filter="[tags[]is[missing]!is[system]]">
> {{!!title||$:/core/ui/TagTemplate}}
> 
> <$list filter="[tag]">
> {{!!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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/cd303a70-8d0d-41c2-b354-b27c63b4f44a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Show a list of all tags without "companion" tiddler



Am Donnerstag, 1. September 2016 12:00:37 UTC+2 schrieb NT:
>
> Eucaly, that's perfect so far. Thank you, man. 
>
> I know the "system" filter, but I didn't know the "missing" keyword. Are 
> there others keywords as well? Is somewhere a list of keywords?
>

Ok, by trying to answer the question for a list of keywords on my own my 
best guess would be http://tiddlywiki.com/#is%20Operator 


> If the list would consist of tagpills instead of pure links then - with a 
> click - you could see the tiddlers using each tag - and you would have more 
> context about the meaning of the tag - what would it make easier to tag the 
> tag itself into a certain category.
> Another even better approach would be a nested list, where the tiddlers 
> would be already listed under each tag - indented of course.
> But that's another task. If you really like to, you guys can also give me 
> advice about that and I would be very pleased. But I know there are 
> resources out there to fiddle that out on my own if I find some time.
> Thanks again!
>
>
> Am Mittwoch, 31. August 2016 13:54:21 UTC+2 schrieb Eucaly J:
>>
>> maybe 
>> [tags[]is[missing]]
>> or
>> [tags[]is[missing]!is[system]]
>>
>> PMario ...：
>>
>>> you can use: 
>>> <> .. to show all used tags. *Those, that 
>>> are shown in italic don't have a corresponding tiddler. *
>>>
>>> <>  to list all tiddlers, that are 
>>> untagged.
>>>
>>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/53eb3abb-413b-439a-9245-8f8912c96f37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Show a list of all tags without "companion" tiddler

Eucaly, that's perfect so far. Thank you, man. 

I know the "system" filter, but I didn't know the "missing" keyword. Are 
there others keywords as well? Is somewhere a list of keywords?

If the list would consist of tagpills instead of pure links then - with a 
click - you could see the tiddlers using each tag - and you would have more 
context about the meaning of the tag - what would it make easier to tag the 
tag itself into a certain category.
Another even better approach would be a nested list, where the tiddlers 
would be already listed under each tag - indented of course.
But that's another task. If you really like to, you guys can also give me 
advice about that and I would be very pleased. But I know there are 
resources out there to fiddle that out on my own if I find some time.
Thanks again!


Am Mittwoch, 31. August 2016 13:54:21 UTC+2 schrieb Eucaly J:
>
> maybe 
> [tags[]is[missing]]
> or
> [tags[]is[missing]!is[system]]
>
> PMario ...：
>
>> you can use: 
>> <> .. to show all used tags. *Those, that 
>> are shown in italic don't have a corresponding tiddler. *
>>
>> <>  to list all tiddlers, that are 
>> untagged.
>>
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9f9fdb26-82d0-4040-8a83-adb2cf956ad5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Show a list of all tags without "companion" tiddler

Oh Danielo, you're right - have not seen this. Thanks a lot.

Am Donnerstag, 1. September 2016 08:25:22 UTC+2 schrieb Danielo Rodríguez:
>
> Hello NT, 
>
> Take a look at Eucaly's answer 
>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2661c916-e0bd-4ec4-8a3c-ae62ec7bf58a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Show a list of all tags without "companion" tiddler

2016-08-31 Thread NT



Am Mittwoch, 31. August 2016 13:46:53 UTC+2 schrieb PMario:
>
>
> you can use: 
> <> .. to show all used tags. *Those, that 
> are shown in italic don't have a corresponding tiddler. *
>
> <>  to list all tiddlers, that are 
> untagged.
>
> You may also have a look at the *right sidebar: More: Tags* tab. and the 
> TagManager which links from there.
>
> see: 
> http://tiddlywiki.com/#untagged%20Operator:%5B%5Buntagged%20Operator%5D%5D%20%5B%5Buntagged%20Operator%20(Examples)%5D%5D%20%5B%5Btags%20Operator%20(Examples)%5D%5D%20%5B%5Btags%20Operator%5D%5D
>  
>

Mario, thanks for showing up possibilities. I know the right sidebar and 
the tag manager, but I find them not really helpful for my problem. The 
list of all tags is not really handy for me as well, since I have a lot of 
tags - around 500. Also the italic markup is a bit hard to recolgnize in 
between. I really would appreciate a list ONLY with the tags without 
tag-tiddler since I have to repeat this process of review from time to time 
and don't want to scroll through a growing number of tags again and again. 
Is it possible to put just another filter that shows just the italic tags 
or something similar? How would that look like? Thanks for help, everyone!


-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/20395690-b8ec-4771-9e4c-37844542abb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Show a list of all tags without "companion" tiddler

2016-08-31 Thread NT

As a prerequisite I want the notion to be clarified. Not every tag has a
tiddler with the identical name, automatically - you have to create it.
Since also not for every tiddler there is a tag with the same name, a
tiddler with a name of a tag must be some kind of a special tiddler - is
it? So what is the offical naming of these kind of tiddlers? Companion
tiddler?

Let's come to the initial purpose of this post. In my wiki I try to make a
companion tiddler for every "normal" tag - just to be able to structure /
cluster / aggregate the tags by tagging them again with some "higher meta
tags". And because you can't tag other tags directly, you have to create a
companion tiddler first and then tag this one. This is the solution that
came to my mind - if you have other / better suggestions to strructure your
tags just tell me, please.

So from time to time I forget to create a companion tiddler for a tag. Then
it is kind of hard work to find the tags without companion tiddler,
manually.

So here I am asking for a suggestion / example for some code / a macro to
get a list of those tags. Would be awesome if this would be a list of tag
pills, then you could click on them to open / create the companion tiddler.
But the essential part it the filtering.

Any hints? Thanks for reading.

--
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/08638466-0ca0-46dd-a355-fb0820ba5f49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How to resolve a (currentTiddler) variable when in use as a parameter for a js macro?

2015-12-15 Thread NT

Thank you Eric, this was the solution for me and your short summary was 
quite informative.

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/70526ded-333a-4f0a-a1b3-1aa5eb4ef3ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How to resolve a (currentTiddler) variable when in use as a parameter for a js macro?

2015-12-05 Thread NT



Am Samstag, 5. Dezember 2015 00:47:03 UTC+1 schrieb BJ:
>
> HI NT, try this:
>
>  <$macrocall $name="pathtype" filename="<>"/>
>
> all the best
> BJ
>

Hey BJ, thanks for suggestions!

OK, this works partly, but I spotted a strange behavior.
If I just return the filename inside the js function your solution works 
fine and the currentTiddler variable is resolved to it's value.

But if I want to return something from the js function like 

"[img[" + path + filename + ".jpg" + "]]" 
(the variable concatenated inside a string)

the result is something like 

[img[./path/<>.jpg]]

so again the variable is not resolved.
Seems I have to change something inside the js function or the way I return 
it.
Can you tell me what or how to do 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f213-9b87-474f-9857-e1b33775bb25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: problems to make a javascript macro work

2015-12-04 Thread NT

I adapted the javascript for my purpose and it worked - partly.
When I call the javascript function with a string as parameter it works 
fine, when I call the javascript function with a wikitext variable the 
wikitext variable it not "solved" into it's "value".
I'll open a new issue for that.
Thank you all for your help so far!

-- 
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/77c4b327-39fc-419a-90ca-4482dcad2e39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] How to resolve a (currentTiddler) variable when in use as a parameter for a js macro?

2015-12-04 Thread NT

What works:

1.

A "normal" macro

\define d1jpg(filename) 
[img[./path/$filename$.jpg]]
\end

called like this

<>

where "$(currentTiddler)$" is replaced by the title of the calling tiddler.

2.

A javascript macro 

/*\
title: $:/macros/mine/pathtype.js
type: application/javascript
module-type: macro
<>
Example:
<>
\*/
(function(){
/*jslint node: true, browser: true */
/*global $tw: true */
"use strict";
exports.name = "pathtype";
exports.params = [
  { name: "filename" }
];
/*
Run the macro
*/
exports.run = function(filename) {
return filename;
};
})();


called with a "normal" string as parameter like this

<>

--

What's not working (or not working as expected / wanted):

A js macro like the above called with wikitext variable (currentTiddler) 
like

<>

because the variable is not resolved to it's value, but it's name treated 
as string.

--> Question: What to change either in the call or in the js-macro so that 
the currentTiddler variable is resolved to the title of the tiddler within 
the js function?
Thanks for your patience, I am still struggling with the wiki syntax.
Kind 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/143c155b-5999-4a96-8f18-c95009ddc94b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: problems to make a javascript macro work

Hi BJ

Am Dienstag, 1. Dezember 2015 16:26:03 UTC+1 schrieb BJ:
>
> Hi NT,
> you may be missing the fields 
>
> type: application/javascript
> module-type: macro
>
> you can set the type by editing the tiddler and selecting 
> 'application/javascript' from the dropdown list,
>
thanks, I did this before.

you can add a field 'module-type' from the drop down list and then add the 
> value 'macro'
>
YES, that's the thing I expected I could do. But there is no 'module-type' 
in the drop down list!!! I am using TiddlyWiki5.1.9


> As Mario said, if you say what you are trying to achieve then we can 
> advise you if this is the right track,
>
Yes, please see my answer to Mario. But I am also interested to get a 
javascript macro working. 

>
> all the best 
>
> BJ
>
>
Thanks, could you give further advice to the module-type?! 

-- 
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/b6e8b30f-ee45-4d2c-a632-7dfbf1cdc5ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: problems to make a javascript macro work



Am Dienstag, 1. Dezember 2015 18:51:52 UTC+1 schrieb Eric Shulman:
>
> On Tuesday, December 1, 2015 at 9:40:00 AM UTC-8, NT wrote:
>>
>> you can add a field 'module-type' from the drop down list and then add 
>>> the value 'macro'
>>>
>> YES, that's the thing I expected I could do. But there is no 
>> 'module-type' in the drop down list!!! I am using TiddlyWiki5.1.9
>>
>
> "module-type" *is* in listed in the "field name" drop list... scroll down 
> to the "system fields" section... and you will find it after "library" and 
> before "name".
>

no, sorry it's not. at least not in my freshly downloaded empty wiki 5.1.9
between "library" and "name" there's "list" in the list.
please see my appended wiki!


> Note: if a desired field name is not in the list, you can just enter it 
> directly in the input field.
>

Yes, I knew and I did, but it did not made the javascript macro work.
Maybe this manual entry didn't worked out or there was another problem left.
I don't know. Feel free to check out the appended wiki and try yourself.
Thank you very much!
 

>
> -e
>
>

-- 
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/23e30c93-f38b-40b3-983a-a90c31079088%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: problems to make a javascript macro work



Am Dienstag, 1. Dezember 2015 18:59:21 UTC+1 schrieb BJ:
>
>
>
> On Tuesday, December 1, 2015 at 5:40:00 PM UTC, NT wrote:
>>
>> Hi BJ
>>
>> Am Dienstag, 1. Dezember 2015 16:26:03 UTC+1 schrieb BJ:
>>>
>>> Hi NT,
>>> you may be missing the fields 
>>>
>>> type: application/javascript
>>> module-type: macro
>>>
>>> you can set the type by editing the tiddler and selecting 
>>> 'application/javascript' from the dropdown list,
>>>
>> thanks, I did this before.
>>
>> you can add a field 'module-type' from the drop down list and then add 
>>> the value 'macro'
>>>
>> YES, that's the thing I expected I could do. But there is no 
>> 'module-type' in the drop down list!!! I am using TiddlyWiki5.1.9
>>
>>
>>> As Mario said, if you say what you are trying to achieve then we can 
>>> advise you if this is the right track,
>>>
>> Yes, please see my answer to Mario. But I am also interested to get a 
>> javascript macro working. 
>>
>>>
>>> all the best 
>>>
>>> BJ
>>>
>>>
>> Thanks, could you give further advice to the module-type?! 
>>
>
> you can type it in - see attached 
>

Yes BJ, I know, please see my answer to Eric.

-- 
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/748de8d4-e2bf-46f9-94db-9c10a1c9482f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: problems to make a javascript macro work



Am Dienstag, 1. Dezember 2015 19:21:55 UTC+1 schrieb BJ:
>
> important!
> It is necessary to reload you tw after making changes to a javascript 
> tiddler
>
>>
>> Yes I knew and I did, thanks for trying harder :-) 
But I will repeat it to be sure!

-- 
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/015d424e-2515-4b6d-b07d-45503043a078%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Build a dynamic link with variables

Thank you Tobias, that solved the problem for me :-)

However, I found that a wikitext macro could not be sufficient for my 
purpose.
So I tried to make a javascript macro. Another question came up and I 
opened a new topic for 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/86a58f43-39ff-45ed-aa00-3e97401ad411%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] problems to make a javascript macro work

Hi there, 
I wanted to make a string replacement and found no other possibility as to 
do it with a javascript macro.
So I found at http://tw5magick.tiddlyspot.com/ the following source code:



/*\
title: $:/macros/skeeve/mysamplemacro.js
type: application/javascript
module-type: macro

<>

Example:
<>
<>
<>

\*/
(function(){

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

/*
Information about this macro
This is the mysamplemacro of Tiddly Wiki 5 written in JavaScript 
*/

exports.name = "mysamplemacro";

exports.params = [
{ name: "character" },
{ name: "address" }
];

/*
Run the macro
*/
exports.run = function(character, address) {
if( !character) character = "Bugs Bunny";
if( !address) address = "Rabbit Hole Hill";
var output ="Hi, I'm " + character + " and I live in " + address;
return output;
};

})();



I just copied to my wiki and named it $:/macros/skeeve/mysamplemacro.js 
like it was before.
Then I tried to call it within a tiddler named jsTest:


<>
<>
<>



But this did not work, there was no output.

So what went wrong???


I have read this: http://tiddlywiki.com/dev/index.html#JavaScript%20Macros

I wondered where to find and to set the module type.

Is this just done by putting one line in the macro source code like 
"module-type: macro"?

As there is the speaking of a module-type "field" I expected to find it at the 
bottom of a tiddler in "Edit"-Mode between the System fields like 
current-tiddler, library or plugin type.

Also it is not clear to me if I have to tag the js-macro with $:/tags/Macro as 
the normal wikitext macros.

Also the naming convention is not clear to me. I want this macro globally 
accessible, but not mixed up in between the system macros. 


I would be happy about suggestions to why my js macro is not working as I found 
the documentation about that a bit limited.

Thank you very much!

-- 
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/80fa8613-993d-4ed8-af62-c75619980e32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: problems to make a javascript macro work

Ok, that's a point. So I'll split the solution I want to have in two parts. 
First, a direct solution, second a solution with help of a javascript macro.
First things first:
I have a "normal" macro that works. It's:

\define d1jpg(filename) 
[img[./_new/Scout/$filename$.jpg]]
\end

That macro gets a uri filename like: 20150331_195734.mp4#t=0,17
The purpose of the macro is to store a path (./_new/Scout/) and to generate 
a valid image name out of the incoming filename.
But because of "#t=0,17" this is not trivial any more. So what I want now 
is to remove ".mp4#".
Since I did not know how to do it with wikitext my idea was to use a 
javascript macro instead of the macro above.
What shall be returned in this example would be 20150331_195734t=0,17.jpg 
as an image link like above.

But yes Mario, maybe you are right and there is a more simple solution to 
that than a javascript macro.
Thanks for your support!

-- 
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/aaf2d5bf-ef31-4960-a9e7-680320cdaf18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Build a dynamic link with variables

2015-11-13 Thread NT

Eric, thanks very much for your help! 

Unfortunately I needed several hours of research to find out that the 
"\end" at the end of the macro is necessary, even if it is a oneliner.

Did you test the code yourself?
I used your first example 
\define mylink(filename) [ext[./_new/something/$filename$]]
I am using TiddlyWiki 5.1.9 in Firefox/Windows.

Thing is, even if I use "\end" in the second line or somewhere else (end of 
1st or 3rd), the "\end" is visible (shown) when I saved the tiddler - and 
yes, I tagged the tiddler correctly as a macro with "$:/tags/Macro" (like 
the core macros).
This is strange, because the other macros I have in $:/core/macros don't 
show anything (of course, because they are macros and no text tiddlers).
So the macro still does it's work, with "\end" shown in the tiddler, but I 
think it's not how it's meant to be like this.

I made a test and copied a core macro to macro made by myself - no 
problems, all fine, nothing shown when the tiddler is saved.
When I combine the macro with my link macro in the same tiddler, a lot of 
code is shown after saving.
So the only difference seems to be the link, because there are no links in 
the core macros.

The link used in a macro seems to break something. Is that normal? Is that 
a bug? 
Is it naturally necessary to mask the link somehow to avoid this problem?
If yes, how to mask a link in a macro?

Thanks for patience and also comments from other users are welcome :-)

Am Donnerstag, 12. November 2015 20:46:01 UTC+1 schrieb Eric Shulman:
>
> On Thursday, November 12, 2015 at 11:22:06 AM UTC-8, NT wrote:
>>
>> Hello, sorry for asking, maybe this is simple with some hours of 
>> research, but I am out of time, currently. 
>> I want to build an external link with a dynamic and a static part.
>> ...
>>
> I want to make many tiddlers (>100) like B with one link each, but the 
>> name of the mp4 file (see above) changes from tiddler to tiddler.
>> The directory should always remain the same in all tiddlers.
>> But when I want to rename or move the directory some day, I don't want to 
>> change all the tiddlers by renaming the link.
>> Then I only want to rename the value of one directory variable, living in 
>> an own tiddler (A).
>>
>
> To combine static text and values, you can define a *macro*, like this:
> \define mylink(filename) [ext[./_new/something/$filename$]]
> Place the macro definition in a tiddler and tag that tiddler with 
> $:/tags/Macro.  This will make the macro available for use in other 
> tiddlers, which is invoked like this:
> <>
> Then, in the future, if you want to change the directory, you can just 
> edit the macro definition.
>
> Note: if you want to define the directory in a separate tiddler, you can 
> define something like this:
> \define mylink_internal(path,filename) [ext[$path$/$filename$]]
> \define mylink(filename) <$macrocall name="mylink_internal" path={{
> TiddlerContainingPath}} filename="""$filename$""">
>
> The <> macro is invoked the same as before, but instead 
> of simply outputting the external link, the macro retrieves the path from a 
> tiddler, and then passes two parameters to another "internal" macro that 
> does the actual assembly of the output.
>
> That should do it.
>
> enjoy,
> -e
> Eric Shulman
> ELS Design Studios
> TiddlyTools - "Small Tools for Big Ideas!"
> InsideTiddlyWiki: The Missing Manuals
>
> YOUR DONATIONS ARE VERY IMPORTANT!
> HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...
>http://TiddlyTools.github.com/fundraising.html#MakeADonation
>
> Professional TiddlyWiki Consulting Services...
> Analysis, Design, and Custom Solutions:
>http://www.TiddlyTools.com/#Contact
>
>
>
>

-- 
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/0882f98f-c257-42b4-a2f5-e9367d4a13af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Build a dynamic link with variables

2015-11-12 Thread NT

Hello, sorry for asking, maybe this is simple with some hours of research,
but I am out of time, currently.
I want to build an external link with a dynamic and a static part.

example:

tiddler B:
[ext[./_new/something/20150331_145600.mp4]]

where "_new/something" should be the value of a variable X, so that I can
write something like
[ext[./<>/20150331_145600.mp4]]

tiddler A:
something like:
<$set name=X value="_new/something">

Why that? What is my goal?
I want to make many tiddlers (>100) like B with one link each, but the name
of the mp4 file (see above) changes from tiddler to tiddler.
The directory should always remain the same in all tiddlers.
But when I want to rename or move the directory some day, I don't want to
change all the tiddlers by renaming the link.
Then I only want to rename the value of one directory variable, living in
an own tiddler (A).

So I hope you got my intend.
Defining a string in one tiddler.
Get access to that string in another tiddler and if necassary concatenate
that string with a filename, before I make a link of it.
It is also not clear to me how the link must be look like, then.

Maybe someone could post an example??
Thanks a lot!!

--
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/562a61a3-c845-4119-9a9f-156f25a54343%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: An Idea for syncing TiddlyWiki



Am Dienstag, 27. Januar 2015 12:05:09 UTC+1 schrieb PMario:


 - a session would mean here that you start with a synced wiki (copies) and 
 do handshakes by determining the name (convention) of the syncStatus file 
 considering the current cloud conditions


 If you use your file based handshake, you need to sync the handshake = 
 lock file. ... But this is a chicken / egg problem.
 To trigger the 3rd party syncing action you need to delete the lock file 
 on side A. - syncing is triggered, but doesn't work - So you are out of 
 sync.


Big sorry, i didn't got your point. I think my word handshake is not 
luckily chosen here. What I mean with handshake here is just an agreement 
between (2) parties how to communicate. The agreement just consists of the 
names of the syncfiles. 
!! And the important point I may have forgotten to mention explicitely is 
that the information about the syncfile of A is told to B in a meta way. 
Which means that the name of the syncfile of A is told B per comment / chat 
/ social functionality of the sync carrier (the cloud service). In a case 
where you have a single wiki in a directory in sync over a cloud service 
you have to exchange this meta information only once! In theory the meta 
thing might be not elegant. In reality it would be highly practical, 
because you only have to exchange the meta information when your team 
changes or the cloud service does - that would be really convenient.
 

  

A thinks I'm ok
 B thinks A is still locked ... The problem here is the 3rd party 
 transport. Because you can't trust it. So the locking mechanism needs to be 
 more sophisticated. ...

 - after the sync the syncfile of A has to be deleted by B and A is not 
 allowed to write a new syncfile while the old syncfile exists


 This is a typical condition for a dead lock, where both sides are 
 locked, because the delete action didn't work, for some unknown reason. 


Sorry, I did not understood that as well, perhaps my explanation above 
about the meta information brings some clarification?

  


-- 
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: An Idea for syncing TiddlyWiki



Am Dienstag, 27. Januar 2015 12:05:09 UTC+1 schrieb PMario:


 - after the sync the syncfile of A has to be deleted by B and A is not 
 allowed to write a new syncfile while the old syncfile exists


 This is a typical condition for a dead lock, where both sides are 
 locked, because the delete action didn't work, for some unknown reason. 

 -m

 
I don't see the deadlock with the information provided regarding the meta 
information exchange. 
If there is a syncfile from tw A for tw B, then tw B should delete it after:
- the syncfile was recognized (tw B could check every 10 seconds) and
-- tw B updated itself according to the syncfile from A
-- tw B does nothing, because it's already in sync

-- 
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: An Idea for syncing TiddlyWiki

Of course, separating data  logic is a meaningful thing in most scenarios, 
but that does not answer my current questions.

Ok, to be a bit more constructive some minds on sync from my side...

If we speak about distribution on file level (in the cloud) the question is 
if it's neccessary to do that separation of data  logic on file level as 
well. One would think so. 
But I like the 1 file approach of tw5 very much and would not like to give 
it up if it's not really neccessary - it makes things very handy at all.

If somebody would ask me for a blueprint of file level syncing of TW5 in a 
efficient but also simple way I would suggest the following:
- keep things simple with the single file approach - over disadvantages it 
has many advantages

- on sync side A:
-- use the TW5 autosave capabilities to do not a save but an export of a 
file (call it syncStatusA) that has the following contents
--- the logic to say what has changed (tiddler updated)
--- the data that changed (tiddler data)
-- the exported file will be automatically synced (if thats possible) by 
the cloud service client you are using (it's possible in mine)
- on sync side B:
-- use the TW5 autosave logic to do an import (read) instead of an export 
(if that's possible???)
-- look for a exported file that has also been synced in the current file 
space (the syncStatusA file) and import it 
-- maybe a file naming convention for the syncStatus file is neccessary  
sufficient here, but a property inside tiddlywiki describing the exact name 
of the import file for the current session would do it

- if you don't want to think about the implications by working with both 
wikis on sides A  B on one and the same syncStatus file, then you have to 
choose a different name for the import and the export file of one wiki - or 
respectively, choose a different name of the syncStatus import/export file 
on both sides A  B - then you have a handshake, don't you?!
- naming the import  export file different would be meaningful to make the 
sync robust for the unknown conditions of the cloud service (sometimes 
there's automatic file versioning, etc.)
- so finally, the names of the files could be syncStatusA and syncStatusB 
and they would be synced by the cloud service and carry the information and 
data what has changed and will be imported automatically 
- and with minimal manual interaction of an handshake for a session you 
could have a synced tw5
- a session would mean here that you start with a synced wiki (copies) and 
do handshakes by determining the name (convention) of the syncStatus file 
considering the current cloud conditions
- after the sync the syncfile of A has to be deleted by B and A is not 
allowed to write a new syncfile while the old syncfile exists
-- that would work for a little number (10?) of team members, at least for 
2, wouldn't it?
- if you are more than 2 - say 10 - and you need for technical tw reasons 
not the naming convention but the exact name of the syncStatus file, then 
you would need the possibility to tell your tw not only one import/export 
naming convention of the syncfile, but 10 
- in this case after updating a tiddler on side A nine (9) syncfiles will 
be created for the team members
- so sync should be possible this way for small teams and I think you could 
put that functionality into a plugin
- this would keep things quite handy for a 3 person team and would be a 
large benefit in workflow

Perhaps Jeremy has a another comment on that?
Regards, NT

-- 
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: An Idea for syncing TiddlyWiki


Am Dienstag, 27. Januar 2015 11:09:29 UTC+1 schrieb PMario:

 2. That the inconsistent (conflict) file is brought up by seafile is nice, 
 but do you get noticed about that?


 You don't. If you reload the page, you'll see, that there are conflicting 
 files. ... But TW doesn't have an easy mechanism to see the differences. 
 ... So some manual work needs to be done, resolving the conflicts.
  

 2.1 Say you have 300 tiddlers aka 300 files - you'll not be able to 
 discover on your own when a new conflict file will appear among them. So do 
 you get a notice of the conflict?


 Page reload.


Sorry, I was speaking here about the seafile service and not about tw. But 
I think you mean a page reload inside seafile as well. That's what I mean 
is a problem.
1. you have to do a page reload
2. i don't think that you recognize one more file (the conflict file) among 
300 other files in meaningful time without to get noticed by seafile. 
Do you get noticed be seafile??

 

 3. Another question regarding node.js and multiple files - is that 
 working on ios and android as well?


 I don't think, that nodejs works on IOS. I'm not sure about android. ... 
 IMO If you need mobile access, you can use TW apps. There are some of them, 
 but I don't know the links. ... There is no server side atm, to sync and 
 resolve conflicts.

 
Then is mobile use not possible on side B when on side A there is the 
node.js version running with multiple files getting synced to A??
I am using TW apps for mobile access right now, but i am working with the 
single file tw at the moment - and it's quite handy.

-- 
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: An Idea for syncing TiddlyWiki

Mario, please have a look at my comment to Tobias post as well. Thanks :)

-- 
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: An Idea for syncing TiddlyWiki