[tw] Thanks for the Buttery Goodness - Question about linking images with images in TW5

[RichShumaker]

First I wanted to say THANKS again to Everyone involved in TW 
development!!
I have used TW for a long time.
I am on again, off again depending on what I am doing or using it for.
Since I am posting I am on again using TW5 and it is amazing what it can do.

I have a simple question(at least I think it is simple)

I am trying to use an image I imported into TW5 in a 'Gallery' and to link 
to the BIG version.
So here is how I am putting the images in a 'Gallery'
[img width=192 [ Image.jpg ]] - The Image has been imported into the TW5 
already, this is not a link to a website.
The weird spacing is because I use a Spreadsheet to do several images at 
once, it works so I have not 'fixed' the formatting.
So this shows the images on a single page and works well.

I wanted to link the small images in the gallery to the big images I 
imported.
Here is Pseudo Code for what I am trying to do - [Image Small Preview 
Size[Link to Image in TW]]

I have been doing some 'minor' poking around the TW Groups.
Saw a question about bringing 'Noobs' into the fold, being a long time user 
I am still a Noob for TW5.

I have always liked the idea of creating TW's that Teach TW.
Create several levels each building on the past and getting harder as you 
go.
TW1 - Very Basic TW and it guides you using the 'Follow The Adventure 
Style' Books
With each TW level should be videos that could be linked in the TW itself
TW2 - Build on what you learned in TW1 and use the same basic construct of 
Follow This Adventure
TW3 - Part of TW3 is showing someone TW1 - TW3 builds on previous lessons 
for yourself to learn more - Why Teach others? Teaching others is the best 
way to learn yourself and it helps expand the group
TW4 - Teach more people either TW1/2/3 and Follow the Adventure for more 
complex learning
TW5 - Quizes and Tests for the first 4 TW levels - Once you submit your 
final answers you are 'CERTIFIED'
As a certified TW5 user you can list this on a Resume and help others to 
create and use TW / Help Companies and individuals become TWer's

So the goal would be to take the concepts that can come up and decide 'is 
this easy' or 'is this complicated'
Rate each concept and then build the levels with all of the concepts 
divided between levels.
Just because something is complicated doesn't mean it should not be shown 
in TW1, you just make sure you explain anything complicated very well.

Non Linear Learning can be complicated, SO make it easy by leading them 
along a path.
Just because it is Non Linear doesn't mean you can create a LINE.
If someone veers off the line they can EASILY reset the system and start 
over.

Currently this is what I am using TW5 for?
My Book
My Website
Myself to help others and help myself at the same time
My Videos
As a Dream Machine
Long Term Memory for my projects

I have to mention that I just started using Google Keep and I find the 
combination between TW5 and Google Keep amazing.
It is my short term and long term memory together.
If you use Google Keep - Create a TW5 Note and send it over to me we can 
start working on stuff together.

If you have not used Google Keep it is a 'basic' notes system that can take 
single notes for audio, pictures, and words.
You can then share that note with others and it works across platforms.
So I use it on my phone and on my computer.

Thanks Jeremy for all your hard work, as well as all the other developers.

Rich Shumaker

-- 
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] Taskgraph BETA is out on github and nightly demo is available

[Danielo Rodríguez]

Hello again,

Maybe this is already recorded on github, but... the inability to type on 
the tag field of the taskgraph is intended?
Also, take a look on how looks like your plugin imported into my personal 
wiki:

Notice those blue arrows?




El domingo, 23 de noviembre de 2014 17:46:58 UTC+1, Danielo Rodríguez 
escribió:
>
> Hello Félix 
>
> I was trying on the online version. Now is working. Maybe is a problem on 
> my Mac, on my mobile it's working. I'll check it out.

-- 
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] in a macro: achieve if / else

[Matabele]

Hi

I used a slightly different mechanism for my button widgets -- in this 
case, the test case resulted in different widget messages being issued. 
Don't know if this idea will be of any use.

See the <$iftid> and <$iftref> widgets at: http://gwiz.tiddlyspot.com/

regards

On Sunday, November 23, 2014 2:20:00 PM UTC+2, Tobias Beer wrote:
>
> Hi everyone,
>
> I'd like to be able to follow optional routes in a macro, for example...
>
>- *if *it's value is defined take *<>*
>- *else* take *$parameter$*
>
> I can certainly play with options to achieve this and
> once I figured something out myself, I will post here.
>
> Regardless, I'd love to know the possible ways
> you know or can think of in which to tackle this problem, so...
>
> If you've have something new in in mind,
> start your reply with a line that summarizes your concept:
>
> "CONCEPT: use foo bar..."
>
> That way it's easier to spot possible solutions.
>
> Could even be an idea for a new widget that doesn't even exist yet, e.g. 
> IfElseWidget...
> sketch out the design for it, someone might just jump at its 
> implementation.
>
> 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

[Alex Hough]

Thanks Tobias,

tb5 is very useful btw - I'm also flattered to see my workflow in there.
the references filter is inspired.

I have a few more workflows in progress. I think they are important things
to share.


Alex

On 23 November 2014 at 23:43, Tobias Beer  wrote:

> This...
>
> [[<$transclude field="title" mode="block"/>]]
>
> ...doesn't work as it should try to wikify all the inner *<$foo bar/>*
> into an internal link.
>
> What you want to do is use the <$link> widget
>  like so...
>
> <$link><$transclude field="title" mode="block"/>
>
> or, in short...
>
> <$link>{{!!title}}
>
> ...assuming that you don't really need block-mode.
>
> 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.
>

-- 
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] New Feature Moratorium

[Jed Carty]

Erwin,

I was hoping to restart the dedicated documentation mailing list trying out 
the ideas discussed here 
https://groups.google.com/forum/#!topic/tiddlywiki/F0dnmWrOuxg 

The other mailing list is 
https://groups.google.com/forum/#!forum/tiddlywikidocs and I put up a post 
briefly discussing how I hope it will work. The sort of guidelines you are 
working on look like they would definitely help a lot and give a good 
structure for people who would like to contribute. I hope to have changes 
discussed on the other mailing list and demonstrated on the cloned wikis 
like the example I made here 
https://groups.google.com/forum/#!topic/tiddlywikidocs/X0GeGiiPMAw 
That way we could have a relatively small group of people who have to 
actually use github while everyone who can comment on the mailing list 
could contribute ideas or content.

-- 
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] External individual tiddlers via iframes?

[Mat]

One more thing:

Arbitrary, community initiated lists dedicated to *topics*, opens up to 
focus on *content* in addition to tw itself. I hear mortals care about such 
matters.

Think we're on to something... 


(...just great, another 3 hour sleep night).

<:-)



On Monday, November 24, 2014 2:36:39 AM UTC+1, Mat wrote:
>
> Must go to bed but this is just so cool.
>
> I just realized an iframe is only necessary if you want to preview the 
> tiddler/s. You're just searching a local tiddler with a list, in your own 
> TW! And I even think you don't even need to involve proxy stuff or strict 
> assuming the already existing import feature can be made to identify urls 
> from each item in the list. The structure could maybe be very loose.
>
> But if nicely laid out, and the, say, plugin author follows some standard, 
> including providing multiple urls to things like tumbnail and description, 
> *the 
> list tiddler could be designed to apper just like any other 
> 
>  
> plugin site! And we have the import feature already so a Install button 
> next to each. And it's all in your own tw!!!*
>
> *...AND the idea can be used for almost anything!* Themed such lists; 
> "the plugin list" "the beginners toolkit list" themes, mathstuff, sex, 
> drugs and rock'nroll - whatever naturally arises. If Jeremy doesn't like 
> rock'nroll on the official site, there could be *one* single agreed upon 
> place place hosting all "unofficial lists". The only type of stuff I see 
> need for some thinking is for more collaborative stuff, like core 
> documentation to get a consistent style, avoid redundence etc.
>
> On tw.com, instead of loads of actual plugins or loads of links to 
> arbitrary tiddlywikis in the wild, there are a few tiddlers with mere 
> lists! Sure, there may pop up lists in the wild but that's no problem at 
> all because contrary to the current problem with plugins and websites in 
> unknown places, an item on a list can be on multiple lists!
>
> Surprisingly simple. As far as I can tell, the only real difficulty is how 
> people should add to the list and not mess it up. Kind of the same problem 
> as discussed for documentation in the other threads. But then, for some 
> lists maybe there will be list moderators who take care of lists with 
> subjects they care for. The rate stuff is added is probably not very high 
> for an average list so maybe the moderator could even accept list 
> contributions via email (as I think pmario suggested for documentation). An 
> ambitious moderator could even make the list tiddler snazzy with other 
> stuff for his little special interest group. And it's in the interest of 
> the special interest group to keep their favourite list updated.
>
> Hm, why didn't we come up with this a long time ago. Just a few silly list 
> that someone moderates and gives to Jeremy so it can be downloaded from 
> tw.com. Am I missing something?
>
> <:-)
>
>
> On Monday, November 24, 2014 12:10:33 AM UTC+1, Tobias Beer wrote:
>>
>> Hi Mat,
>>
>> While doing baby-steps in terms of actual traveling and 
>> destination-like-specs... your idea definitely has it's appeal... stuffing 
>> metadata 
>> into the core (or even fetching them from someplace) and use some 
>> remote-rendering voodoo to fetch the applicable contents either via 
>> intermediary iframes or directly, in the sense of what Jeremy suggested, as 
>> a proxy-server-kind-of thing to request and access actual contents.
>>
>> The critical part being the actual MetaData authoring process... which 
>> could be yet anohter GitHub repo with a meaningful folder structure and a 
>> chron-job that mangles all the meta-bits every now and then into a 
>> *tiddlymeta.json* type of thing to be loaded / updated by the click of a 
>> button.
>>
>> 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] External individual tiddlers via iframes?

[Mat]

Must go to bed but this is just so cool.

I just realized an iframe is only necessary if you want to preview the 
tiddler/s. You're just searching a local tiddler with a list, in your own 
TW! And I even think you don't even need to involve proxy stuff or strict 
assuming the already existing import feature can be made to identify urls 
from each item in the list. The structure could maybe be very loose.

But if nicely laid out, and the, say, plugin author follows some standard, 
including providing multiple urls to things like tumbnail and description, *the 
list tiddler could be designed to apper just like any other 

 
plugin site! And we have the import feature already so a Install button 
next to each. And it's all in your own tw!!!*

*...AND the idea can be used for almost anything!* Themed such lists; "the 
plugin list" "the beginners toolkit list" themes, mathstuff, sex, drugs and 
rock'nroll - whatever naturally arises. If Jeremy doesn't like rock'nroll 
on the official site, there could be *one* single agreed upon place place 
hosting all "unofficial lists". The only type of stuff I see need for some 
thinking is for more collaborative stuff, like core documentation to get a 
consistent style, avoid redundence etc.

On tw.com, instead of loads of actual plugins or loads of links to 
arbitrary tiddlywikis in the wild, there are a few tiddlers with mere 
lists! Sure, there may pop up lists in the wild but that's no problem at 
all because contrary to the current problem with plugins and websites in 
unknown places, an item on a list can be on multiple lists!

Surprisingly simple. As far as I can tell, the only real difficulty is how 
people should add to the list and not mess it up. Kind of the same problem 
as discussed for documentation in the other threads. But then, for some 
lists maybe there will be list moderators who take care of lists with 
subjects they care for. The rate stuff is added is probably not very high 
for an average list so maybe the moderator could even accept list 
contributions via email (as I think pmario suggested for documentation). An 
ambitious moderator could even make the list tiddler snazzy with other 
stuff for his little special interest group. And it's in the interest of 
the special interest group to keep their favourite list updated.

Hm, why didn't we come up with this a long time ago. Just a few silly list 
that someone moderates and gives to Jeremy so it can be downloaded from 
tw.com. Am I missing something?

<:-)


On Monday, November 24, 2014 12:10:33 AM UTC+1, Tobias Beer wrote:
>
> Hi Mat,
>
> While doing baby-steps in terms of actual traveling and 
> destination-like-specs... your idea definitely has it's appeal... stuffing 
> metadata 
> into the core (or even fetching them from someplace) and use some 
> remote-rendering voodoo to fetch the applicable contents either via 
> intermediary iframes or directly, in the sense of what Jeremy suggested, as 
> a proxy-server-kind-of thing to request and access actual contents.
>
> The critical part being the actual MetaData authoring process... which 
> could be yet anohter GitHub repo with a meaningful folder structure and a 
> chron-job that mangles all the meta-bits every now and then into a 
> *tiddlymeta.json* type of thing to be loaded / updated by the click of a 
> button.
>
> 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] New Feature Moratorium

[Erwan]

On 23/11/14 17:17, Jeremy Ruston wrote:

Hi Erwan

> I tried to develop these ideas and to imagine how things could work 
globally in a more detailed proposition, in case that helps: 
http://tw-doc-ideas.tiddlyspot.com


Terrific stuff, thank you Erwan. You've done a great job of 
summarising the situation and the ideas that are floating around.


Perhaps some of your material could be structured as a pull request to 
start fleshing out the contribution guidelines in tw5.com 
?


Thank you Jeremy,

I'd be happy to do it, but I don't know exactly how: I'm relatively 
familiar with git but not so much with TW node.js version, and the 
tw5.com edition looks like a complex case of node.js (with tiddlers in 
different subdirectories). I was able to open it locally under node.js 
but not to save my changes, is there something special to do?


About the content: currently it is written like a proposition (with some 
"I think", "in my opinion", ...), should I leave it like that or rewrite 
it another way? And which parts are interesting/useful?


Regards
Erwan





I realised earlier when I made the following changes that the "house 
style" of tiddlywiki.com  is not explicitly 
stated, providing another hurdle for contributors:


https://github.com/Jermolene/TiddlyWiki5/commit/4134392841862830fd4c5cf3b3d6512b30bc885f

Best wishes

Jeremy

https://github.com/Jermolene/TiddlyWiki5/commit/4134392841862830fd4c5cf3b3d6512b30bc885f




On Sun, Nov 23, 2014 at 4:33 PM, Erwan > wrote:



Hi everyone,

as this is my first post here, I'd like to start by thanking
Jeremy and everyone who contributes to TW, from core development
to helping make the community so engaging. I've discovered TW only
a few months ago (I was lucky to arrive just for the birth of the
official TW5), and I've been hooked by both the great tool that TW
is and the good atmosphere of knowledge sharing in the community.

I agree with Jeremy and everybody in this thread that improving
the documentation process (including the great potential for
community knowledge) becomes more and more important, especially
in the perspective of attracting newcomers.

In general my thoughts on the topic are similar to what most
people have said here. I would like to suggest maybe a couple of
points that I think deserve some attention. Indeed, people with
technical skills tend to focus on the technical side of a problem,
and obviously there are highly skilled people here ;) While this
is important, there can be other angles to look at:

* For example, about the fact that some people are not comfortable
using github, a very simple way to overcome the problem would be
to have a few volunteers who know git who would receive the
contributions and make the pull request for them. I guess
something similar could be done for other things, like
translating, so that someone who can translate doesn't need to
have any technical skills.

* Imho, one of the problems with contributing to the official
documentation is that there is no clear guidelines about the
structure or the type of content. I think that it would be very
helpful to think about a detailed plan and identify the missing
parts: this way it would be easier for people who want to
contribute to know what to do, and eventually for newcomers to
find their way in the documentation.

I tried to develop these ideas and to imagine how things could
work globally in a more detailed proposition, in case that helps:
http://tw-doc-ideas.tiddlyspot.com

Regards,
Erwan




On 23/11/14 13:21, Jeremy Ruston wrote:

Thanks everyone for their contributions. There are a bunch of
good suggestions in the thread which I'll try to pick up in the
hangout on Tuesday.

A big topic is clearly how we improve the contribution process
for the documentation. I have a couple of thoughts:

* We could initiate a TW5 community space on tiddlyspace along
the lines of tiddlywiki.org  - it's a
proven way to work. It would be good to try out TW5's support for
TiddlySpace in a multiuser setting (since it's not been done
before I think there may be some wrinkles to be ironed out).
* We should support documentation contributions by people taking
a copy of tiddlywiki.com  onto tiddlyspot
and making their edits there. I could easily build a batch file
that pulls down their changes and applies them to the repo, so
that I can convert their changes to a pull request (I don't think
there's any avoiding needing a moderation step for tiddlywiki.com
)
* An alternative workflow for accepting those contributions would
be to support visual diffing in the import manager

I've also got a couple of clarifications.

> 

Re: [tw] [TW5] XMLHttpRequest error code: 404

[JimyKK]

Sorry, I accidentally deleted the image (damn thing synced to my phone 
grumble grumble google+ rant...) Here is an imgur copy.

No url's actually "fail" it's a yellow error box generated by tiddly wiki 
not the browser. From the developer network tools it looks like it's 
atempting to connect to https://mysite.com/status/
instead of https://mysite.com/wiki/status/

I paused when writing and just had a play around with rewrites:

location  /wiki/ {

proxy_pass http://127.0.0.1:8001/;

}

location /status {
rewrite ^/status $scheme://$server_name/wiki$uri permanent;
}

location /recipes/ {
rewrite ^/recipes/ $scheme://$server_name/wiki$uri 
permanent;
}

This looks like it's working. I am a bit of a noob when it comes to writing 
this stuff and I have no doubt there is a better way of doing this.

On Sunday, 23 November 2014 23:58:39 UTC+8, Jeremy Ruston wrote:
>
> Hi JimyKK
>
> Apologies for the late reply.
>
> > every-time I load the wiki I get a XMLHttpRequest error code: 404 popup 
> (See attached image)
>
> The image hasn't come through. What's the URL that fails? Do you see any 
> useful information in your browser developer tools "network" tab?
>
> Best wishes
>
> Jeremy
>
> On Wed, Nov 19, 2014 at 3:48 AM, JimyKK > 
> wrote:
>
>> 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+...@googlegroups.com .
>> To post to this group, send email to tiddl...@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...@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] Yet another documentation idea

[Jed Carty]

Thank you!

-- 
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] 5.1.5 prerelease - Passing the output of $count to a macro as a number

[Jed Carty]

That is still passing <$count filter='[all[]]'/> as a string. It is the 
same thing as this code will set myField to the string <$count 
filter='[all[]]'/> not the numeric value.

\define getCount() <$count filter='[all[]]'/>

<$button><$action-setfield $field=myField $value=<>/>Set 
field

If there isn't a way to assign the output of something like this to a field 
without I may look into making a macro or widget to do it. I have to learn 
more javascript than I had planned.

-- 
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] Yet another documentation idea

[Daniel Baird]

That was me.  I've approved Jed's post and made Jeremy a group manager.  I
recommend we keep the first-post moderation, especially for lower volume
groups it's easy to end up more spam than content.

Cheers
;Daniel


On 24 November 2014 at 05:57, Jeremy Ruston  wrote:

> >  I submitted a post to that list suggesting using the method discussed
> here, but it needs to be approved
>
> It turns out that I'm not the owner of the group, and so can't approve
> posts. I have a dim memory that Dave Gifford might have been involved in
> forming the group; I've copied Dave in.
>
> Best wishes
>
> Jeremy.
>
> On Sun, Nov 23, 2014 at 6:33 PM, Jed Carty  wrote:
>
>> I think using the old documentation list would be best so that people
>> writing documentation wouldn't be spamming this list and wouldn't need to
>> dig through things here to find proposed changes. I submitted a post to
>> that list suggesting using the method discussed here, but it needs to be
>> approved. Can we make that list open like this one? I don't want to
>> discourage people from posting requests for documentation there.
>>
>> --
>> 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.
>



-- 
Daniel Baird
objoke: I had a problem and decided to solve it with threading. Now,
have problems. two I

-- 
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] New Feature Moratorium

[Tobias Beer]

Hi Mat,
 

> On a need basis perhaps? I.e if a part can be reused, then it is 
> tiddlified to avoid redundance in the system. Not sure how to deal with if 
> there's later a wish to change it in one context but not the other. Or 
> maybe clone+change is obvoius solution?
>

Yes, but that introduces a few questions, like...

   - What name should that new tiddler get?
   - Does it need tagging?
   - Any fields?
   - Where do I need to link it?
   - How do I put it into context?
   - Does it need ordering in some list?
   - etc...

Whereas I could simply do some section magic 
, reference 
that bit form anywhere, have it neatly displayed in a clickable toc... and 
all those things that make not really big tiddlers not nessessarily smaller 
than they have to be.

Let me put it slightly differently: there is a too small... in the sense 
of: "smaller than is perhaps good for ya"... omg, all the uncertainty that 
comes with the quantum-approach to anything. ^^

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

[Tobias Beer]

This...

[[<$transclude field="title" mode="block"/>]]

...doesn't work as it should try to wikify all the inner *<$foo bar/>* into 
an internal link.

What you want to do is use the <$link> widget 
 like so...

<$link><$transclude field="title" mode="block"/>

or, in short...

<$link>{{!!title}}

...assuming that you don't really need block-mode.

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] Quoting formatting characters

[Tobias Beer]

Hi Ken,

If I am not mistaken, make it a feature request...

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

Since TWc offered

"""nowiki"""

...I don't see why TW5 should not, even if these constructs 
...

"""
hard 
line
breaks
"""

...should be unaffected as we're dealing with a block-level declarations 
here and not any...

"""inline escaping"""

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] 5.1.5 prerelease - Passing the output of $count to a macro as a number

[Tobias Beer]

Of all the things Stephan tried to tech me these past few days, one was to 
use that helper macro...

\define getCount() <$count filter='[all[]]'/>
<>

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] How to make sure filter has only unique items?

[Tobias Beer]

Jeremy, Evolena,

Thank you both for your patience and helping resolve this mystery!
 

> I don't see the problem, I'm afraid. Visiting 
> http://tb5.tiddlyspot.com/#%24%3A%2Fstyles%2Ftb5 I see the plain text 
> version of the tiddler as expected.
>

Yes, stylesheets do work as expected as they actually are set to the css 
content type.
What didn't work were macros under *$:/macros/...*

once by the $:/template/summary (<$view tiddler={{!!title}} 
> format="text"/>) because it is a macro (<$list 
> filter="[all[current]tag[$:/tags/Macro]]">), which may not be what you 
> intended to do


At some point it was intended... *blushing*. :)

When I put some *foo* into *$:/template/view-template* and seing it 
rendered twice, I thought it must have something to do with that template.

Yet, for a mystery I am too tired to solve today, the issue was quite 
another.

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] External individual tiddlers via iframes?

[Tobias Beer]

Hi Mat,

While doing baby-steps in terms of actual traveling and 
destination-like-specs... your idea definitely has it's appeal... stuffing 
metadata 
into the core (or even fetching them from someplace) and use some 
remote-rendering voodoo to fetch the applicable contents either via 
intermediary iframes or directly, in the sense of what Jeremy suggested, as 
a proxy-server-kind-of thing to request and access actual contents.

The critical part being the actual MetaData authoring process... which 
could be yet anohter GitHub repo with a meaningful folder structure and a 
chron-job that mangles all the meta-bits every now and then into a 
*tiddlymeta.json* type of thing to be loaded / updated by the click of a 
button.

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: ListField seems expect distinct values in the list

[Tobias Beer]

>
> Lists are (or at least were) nasty as they sometimes behave as sets (no 
> duplicates) sometimes as lists - at least that's my experience when I did 
> some plugins using "lists".
>

That's some interesting detail to be aware of, the specifics of this 
hopefully ending up explained somewhere.

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] node.js post install — http 403 forbidden

[Tobias Beer]

 Mhhh, if I just go to http://127.0.0.1, I see this...


Seems like IIS is running, too for whatever reason ... possibly owed to my 
never used express editions of the visual studio family. Will check up on 
those running services an get back.

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] in a macro: achieve if / else

[Tobias Beer]

>
> \if param (equals:<)
>

\if param (equals:<>)
 
;-)

-- 
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] in a macro: achieve if / else

[Tobias Beer]

>
> The simplest proposal is for new \ifdef and \ifndef pragmas...
>

Have not thought about that but pragmas offer a door to making structured 
code principles available, be they if / else or other.

Maybe that's more simplistic than we can make use of...

\ifdef param

Instead, we could do things like...

\if param (mode:value)

for example...

\if param (equals:<)

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] Quoting formatting characters

[Ken]

I am trying to include a URL  in the format '//hostname/folder' in a 
Tiddler. Tiddlywiki sees the '//' as a request to format the text in 
italics. How do I "quote" the '//' so they appear as part of the rendered 
text rather than as formatting characters? 

In V2, I would use triple double quotes, or the  tag, but neither 
of these appears to work in V5. The triple backtick quotes the characters, 
but I really don't want to display the URL in "code" format.

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: if tiddler is a tag ...then list tags

[Alex Hough]

Dear All,

I have the tiddlers, but would like to render them as links. Here's the
code adapted from tb5:

<$list filter="[all[current]tagging[]]">
<$transclude field="title" mode="block"/>


My instinct was first to try

<$list-link filter [...]

then

[[<$transclude field="title" mode="block"/>]]

and finally

<$link-to

instead of trasclude

@Mario mentioned that the links were under the "i" - so I presumed the
answer lies somewhere in my TW already.
 $:/core/ui/TiddlerInfo/Tagging contains

template="$:/core/ui/ListItemTemplate"

I added this to my conditional template: still no joy.

I've reached the point where I need some help: thanks in advance


Alex





Alex

On 18 November 2014 at 21:49, Alex Hough  wrote:

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

Re: [tw] Re: [TW5] New Feature Moratorium

[Mat]

On Sunday, November 23, 2014 9:40:32 PM UTC+1, Richard Smith wrote:
>
> With regards to the documentation specifically then, how should we think 
> about, for example "Introduction to Filters 
> " - 
> should it be split into ~13 different tiddlers and those tiddlers then 
> re-combined?
>

On a need basis perhaps? I.e if a part can be reused, then it is tiddlified 
to avoid redundance in the system. Not sure how to deal with if there's 
later a wish to change it in one context but not the other. Or maybe 
clone+change is obvoius solution?

<:-)

-- 
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] 5.1.5 prerelease - Passing the output of $count to a macro as a number

[Jed Carty]

I made a javascript macro that will return a random number in a given range 
using a given step size, I would like to be able to pass the output of 
<$count filter='[all[]]'/> to the macro as a parameter. Everything I have 
tried results in the whole thing being passed as a string instead of the 
numeric output being passed.

I thought I had seen this same problem addressed in a post here recently, 
but I can't find a solution. 

A demonstration of the problem with some more explanation is here 
http://zorklike.tiddlyspot.com/#Random%20Value%20Test

-- 
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] How to make sure filter has only unique items?

[Evolena]

You see twice the code of $:/template/view-template because it is tagged 
with $:/tags/ViewTemplate, so it applies the template to itself once 
because it is displayed "inside itself", and once because it is displayed 
as any other tiddler (see any other ViewTemplate tiddler, for example 
$:/core/ui/ViewTemplate/title).

You see twice the code of $:/macros/... (except source) because it is 
displayed:

   - once by the $:/template/view-template (<$view 
   tiddler=<> format="text"/>)
   - once by the $:/template/summary (<$view tiddler={{!!title}} 
   format="text"/>) because it is a macro (<$list 
   filter="[all[current]tag[$:/tags/Macro]]">), which may not be what you 
   intended to do.

Others tiddlers display it only once for what I see.

-- 
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] External individual tiddlers via iframes?

[Mat]

On Sunday, November 23, 2014 2:55:49 PM UTC+1, Tobias Beer wrote:
>
> http://tb5.tiddlyspot.com/#Widget%20Browser
>
> It allows you to select an entry from a dictionary and then have the url 
> constructed from that. 
>

Brilliant! Could let you have a list with document titles and, assuming 
they are in reality titled 

"$:/documentation//tutorial/beginner/widgets/"

i.e using the introduced "titlepath" policy, there could be a dropdown menu 
for each "level" in the titlepath. Or a multi level popup where you're 
presented a new sublevel after each selection. In this context I think 
multilevel popups would actually make sense - you're spelling out the 
titlepath (and url). Because the acutal iframe content can't be evaluated, 
this setup would require hardcoded titles to all potential tiddlers in the 
(e.g) Documents category on tw.com.

Another variant would be a search box that, if dedicated to documentation, 
is preset with a filter and thereafter use the user query. I.e the user 
types in query "browsewidget" and because he has previously stated he is a 
beginner (perhaps in Controlpanel where he wrote his signature name) and 
because the searh box is dedicated to documentation, he gets a resulting 
list filtered on all those three values. (ie the documents on browserwidget 
for beginners).

Could also be used for e.g plugins or anything!. For the sake of this 
discussion, take plugins: Each plugin on source tw (presumably tw.com) is 
namelisted in the users tw but with attached meta data. The user writes, 
say, "navigation" and all titles containing that metadata are filtered out. 
Add to query and... you get it.

And the list of plugin names would be a thing continously updated by the 
community! A plugin developer adds his plugin url plus a lot of meta data 
to include it. Users updates his source database tiddler whenever. 

...and other users can add meta data to this plugin too!

It would take some place where people can add nothing more but the source 
url and the meta data into a list or table of some sort. Could maybe done 
in a plublic google docs document I think. I've set this google doc 

 
to public and "anyone can comment" but I'm not sure how comments appear - 
can you add stuff to the fields, but not delete? That's what I'm hoping 
for. This would mean anyone can just copy paste it into their local source 
title list tiddler to update it. Ideally something more elegant than a 
google doc, perhaps something that you throw away an email to and it's 
added automatically.


<:-)


-- 
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: ListField seems expect distinct values in the list

[Richard Smith]

Hi Stephan,

I'm sorry if you genuinely don't understand that the language construction 
you used can be interpreted as confrontational. Perhaps you could have a 
think about why that might be the case. 

WHY I expected different behaviour was pretty clear in the difference 
between the examples that I gave and I think Jeremy's answer implies that 
the documentation for this feature does need to be updated to make clear 
that the list filter operator behaves differently when it is negated and 
that when combining it with other operators it should be at the start of 
the expression in order to behave as expected (yes, by me).

Hopefully you will be able to find a 'middle ground' in future between 
ignoring me and talking to me like an idiot, as much of what you've posted 
here has been useful for me.

Regards,
Richard

-- 
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] New Feature Moratorium

[Richard Smith]

Hi all,

With regards the "Philosophy of Tiddlers 
".

I read some of Tobias' and Jeremy's recent conversations about sections in 
Tiddlers. Although I don't understand some of the complexities, I do think 
the goal of 'smallest semantically meaningful' is a good one. It's also 
true that splitting a long tiddler into multiple smaller ones when those 
smaller ones will never appear anywhere else adds little value for the 
necessary work.

With regards to the documentation specifically then, how should we think 
about, for example "Introduction to Filters 
" - should 
it be split into ~13 different tiddlers and those tiddlers then re-combined?

Regards,
Richard

-- 
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] node.js post install — http 403 forbidden

[Jeremy Ruston]

Hi Tobias

TiddlyWiki itself never generates 403 errors, so I think you might have
some middleware or virus protection that's blocking the connection.

Best wishes

Jeremy.


On Sun, Nov 23, 2014 at 7:47 PM, Tobias Beer  wrote:

> Following this guide..
>
> http://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js
>
> ...after (re)installing node.js and the tiddlywiki for node.js package on
> windos 8.1, then starting the server as said, I get a...
>
> HTTP-Fehler 403.14 - ForbiddenDer Webserver ist so konfiguriert, dass der
> Inhalt dieses Verzeichnisses nicht aufgelistet wird.
>
> Now, that is some German, but I think it's clear what it says at
> http://127.0.0.1:8080.
>
> What to do / check?
>
> 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] in a macro: achieve if / else

[Jeremy Ruston]

We've already got facilities for conditional rendering via the reveal and
list widget; we may need to extend them but they've been sufficient so far.

The proposal here is for macro definitions that include conditional
elements. It's important that we implement this at the right layer.

Using the <$reveal> widget as suggested by Stephan in another thread has
the disadvantage of incurring a rendering penalty. Ideally, we'd
incorporate the new conditional syntax in the macro definition syntax.

The simplest proposal is for new \ifdef and \ifndef pragmas:

\define myMacro(param)
\ifdef param
The parameter is defined as $param$
\else
The parameter is not defined
\endif
\end

That syntax has the benefit of great simplicity. Tobias's original example
could be done like this:

\define myMacro(param)
\ifdef param
<$set name="myvariable" value="""$param$""">
\else
<$set name="myvariable" value=<>>
\endif
The value of myvariable is <>


What do you think?

Best wishes

Jeremy



On Sun, Nov 23, 2014 at 7:36 PM, Stephan Hradek 
wrote:

> First problem first including pseudo code:
>
> \define macro(foo)
> <$reveal type="nomatch" state=" non existing
> tiddlre " text="$foo$">
> do this
> 
> <$reveal type="match" state=" non existing tiddlre "
> text="$foo$">
> <$reveal type="nomatch" state=" non
> existing tiddlre " text="$(foo)$">
> do that
> 
> <$reveal type="match" state=" non existing
> tiddlre " text="$(foo)$">
> otherwise this
> 
> 
> \end
>
> ! No Param, No Var
>
> <>
>
> ! Param, No Var
>
> <>
>
> <$set name="foo" value="foo var">
>
> ! No Param, Var
>
> <>
>
> ! Param, Var
>
> <>
>
>
>
> Note: Despite the fact that I used blanks as first and las character in
> the stet tiddler's name, this does not keep help the " non existing tiddler
> "  from being created as the state tiddler's name gets trimmed by
> tiddlywiki. So the whole logic will fail as soon as you have a non-empty
> tiddler called "non existing tiddler".
>
> --
> 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] Yet another documentation idea

[Stephan Hradek]

Am Sonntag, 23. November 2014 20:55:31 UTC+1 schrieb Jeremy Ruston:
>
> > Would a perl script help you?
>
> Thank you Stephan, I'd actually prefer something in bash or JavaScript if 
> possible.
>

Okay… Then I'm out. Bash I don't like because you have to use so many other 
programs (cut, grep, sed...) that it's better to stick with something that 
has it built-in (i.e. perl). My bash - or better sh-scripts usually contain 
one or more included perl scripts anyway :D instead of calling awk, sed or 
cut.

JavaScript might be possible but then I do not have enough experience with 
node.js.
 

> Have you seen how the file paths for the tiddlers are stored in tw5.com? 
> Look at $:/config/OriginalTiddlerPaths.
>
Not yet. 

-- 
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] Yet another documentation idea

[Jeremy Ruston]

>  I submitted a post to that list suggesting using the method discussed
here, but it needs to be approved

It turns out that I'm not the owner of the group, and so can't approve
posts. I have a dim memory that Dave Gifford might have been involved in
forming the group; I've copied Dave in.

Best wishes

Jeremy.

On Sun, Nov 23, 2014 at 6:33 PM, Jed Carty  wrote:

> I think using the old documentation list would be best so that people
> writing documentation wouldn't be spamming this list and wouldn't need to
> dig through things here to find proposed changes. I submitted a post to
> that list suggesting using the method discussed here, but it needs to be
> approved. Can we make that list open like this one? I don't want to
> discourage people from posting requests for documentation there.
>
> --
> 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] Yet another documentation idea

[Jeremy Ruston]

> Would a perl script help you?

Thank you Stephan, I'd actually prefer something in bash or JavaScript if
possible. Have you seen how the file paths for the tiddlers are stored in
tw5.com? Look at $:/config/OriginalTiddlerPaths.

Best wishes

Jeremy


On Sun, Nov 23, 2014 at 7:49 PM, Stephan Hradek 
wrote:

>
>
> Am Sonntag, 23. November 2014 16:13:23 UTC+1 schrieb Jeremy Ruston:
>>
>> Just to clarify, I have not yet written the scripts needed to
>> automatically unpack a tiddlywiki HTML file and put the tiddler files in
>> the correct locations. So any contributions in this way right now will need
>> to be manually processed.
>>
>
> Would a perl script help you?
>



-- 
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] Yet another documentation idea

[Mat]

On Sunday, November 23, 2014 6:58:11 PM UTC+1, Jed Carty wrote: 

> [...]
>
> We just need to make sure that we coordinate in the pinned thread so we 
> don't get a bunch of people submitting the same thing a bunch of times. 
>

If we get a bunch of submitting people for anything we should probably just 
be happy ;-)
Setting up the infrastructure is just the premise for 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.

Re: [tw] [TW5] How to make sure filter has only unique items?

[Jeremy Ruston]

I don't see the problem, I'm afraid. Visiting
http://tb5.tiddlyspot.com/#%24%3A%2Fstyles%2Ftb5 I see the plain text
version of the tiddler as expected.

Best wishes

Jeremy


On Sun, Nov 23, 2014 at 6:37 PM, Tobias Beer  wrote:

> The fix is to add "+[limit[1]]" to the end of the filter expression.
>>>
>> Of course, so simple! :)
>>
>
> Or, so I thought. Actually, I still don't get it to work...
>
> http://tb5.tiddlyspot.com...
> 
>
> <$list filter="[all[current]tag[$:/tags/ShowSource]] 
> [all[current]prefix[$:/template]][all[current]prefix[$:/macro]!field:type[application/javascript]]-[[$:/macros/source]]+[limit[1]]">
> <$view tiddler=<> format="text"/>
> 
>
> 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] [TW5] Yet another documentation idea

[Stephan Hradek]

Am Sonntag, 23. November 2014 16:13:23 UTC+1 schrieb Jeremy Ruston:
>
> Just to clarify, I have not yet written the scripts needed to 
> automatically unpack a tiddlywiki HTML file and put the tiddler files in 
> the correct locations. So any contributions in this way right now will need 
> to be manually processed.
>

Would a perl script help you? 

-- 
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] Yet another documentation idea

[Mat]

Tobias tiddlyspot suggestion - great idea!!!

One detail is that #4 has to be done via, specifically, Chrome the first 
time, if I understand things.

<:-)

-- 
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] node.js post install — http 403 forbidden

[Tobias Beer]

Following this guide..

http://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js

...after (re)installing node.js and the tiddlywiki for node.js package on 
windos 8.1, then starting the server as said, I get a...

HTTP-Fehler 403.14 - ForbiddenDer Webserver ist so konfiguriert, dass der 
Inhalt dieses Verzeichnisses nicht aufgelistet wird.

Now, that is some German, but I think it's clear what it says at 
http://127.0.0.1:8080.

What to do / check?

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] New Feature Moratorium

[Mat]

On Sunday, November 23, 2014 5:33:40 PM UTC+1, Erwan wrote:
>
> http://tw-doc-ideas.tiddlyspot.com
>

Hear, hear! I particularly like that you brought up the need for different 
types of documentation, and probably for different levels of expertise. 
BTW, this will, to say the least, be one tough test of manhood to see to 
what extent we can use the philosophy of tiddlers 
!

<:-)

-- 
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] Yet another documentation idea

[Tobias Beer]

> I think using the old documentation list would be best so that people 
> writing documentation wouldn't be spamming this list and wouldn't need to 
> dig through things here to find proposed changes.
>

+1

...if that workflow is indeed a way to go, as compared to the bells and 
whistles of GitHub.

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] in a macro: achieve if / else

[Stephan Hradek]

First problem first including pseudo code:

\define macro(foo)
<$reveal type="nomatch" state=" non existing 
tiddlre " text="$foo$">
do this

<$reveal type="match" state=" non existing tiddlre " 
text="$foo$">
<$reveal type="nomatch" state=" non existing 
tiddlre " text="$(foo)$">
do that

<$reveal type="match" state=" non existing tiddlre 
" text="$(foo)$">
otherwise this


\end

! No Param, No Var

<>

! Param, No Var

<>

<$set name="foo" value="foo var">

! No Param, Var

<>

! Param, Var

<>



Note: Despite the fact that I used blanks as first and las character in the 
stet tiddler's name, this does not keep help the " non existing tiddler "  
from being created as the state tiddler's name gets trimmed by tiddlywiki. 
So the whole logic will fail as soon as you have a non-empty tiddler called 
"non existing tiddler".

-- 
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] NameSpaceWidget — Drawing Board

[Tobias Beer]

>
> Have you considered creating a suite of macros to cover your needs:
>
> <>
> <>
> <>
>
 
I have and it quickly felt like macros are not only by far too inflexible 
but also way to redundant in terms of code. And they sure won't yield those 
breadcrumbs or the namespace toc.

And even if macros could somewhat yield all that, I think the widget code 
will be a ton less spaghetti than those macros.

So, I see that widget as a hub for the features described... whether it 
actually leverages other widgets or not... would that be a problem? ...I 
sure don't have to rebuild primitives if other widgets already work the 
subfeature magic, in a well defined sense that is.

Similarly, I would approach / think of / design a <$section> widget 
.


There could actually be a namespace filter that does some of the magic...

a) get parent tiddler

[ns:parent:0[tiddler]]

of level x, 0 being the outermost

[ns:parent:x[tiddler]]

b) get children of set

[ns:children[]]

a) go to toplevel parent

[ns:crumbs[]]

get crumbs for set, e.g.

[foo / bar / baz][ns:crumbs[]]

could return the list

   - foo
   - foo / bar
   - foo / bar / baz
   
...this would, of course only work with a default delimiter, or perhaps

[foo / bar / baz][ns:crumbs: / []]

etc...

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] in a macro: achieve if / else

[Jed Carty]

Tobias,

Your first example seems like it would require some sort of type checking, 
I have no idea how you would achieve that or if it is really possible.

For the second part I think that you could get that functionality with 
something like the reveal widget that is able to send widget messages based 
on the reveal state. In your example, if I understand correctly, you would 
take the input and immediately send a widget message to set a state field, 
then the if/else statements would act similarly to the reveal widget based 
on this field. The problem is that this sort of message that isn't tied to 
an event like a button press may get sent many times as the wiki refreshes 
and could be sending conflicting messages.

If this makes any sense:

\define macro(foo)
<$action-setfield field='stateField' value=$foo$/>
<$if state='stateField' type='match' value='bar'>
do this

<$if state='stateField' type='nomatch' value='bar'>
<$if state='stateField' type='match' value='baz'>
do this other thing

<$if state='stateField' type='nomatch' value='baz'>
   do yet another thing



To get a real if/else sort of widget that fits with the current wikitext 
syntax I think you would need something like:

<$ifelse state=<> condition=<> 
match=<> nomatch=<>/>

The problem with both of those is that unless there is a way to allow 
widget messages or something similar without a triggering event I don't 
think they can be done. And allowing messages without a triggering event 
may break everything. Like having a select widget that sets a field, and a 
button that sets the field to a value that isn't allowed by the select 
widget. If you have some function that depends on the state of the select 
widget pressing the button will just break it. And if you allow the field 
to be set without the button or select widget than the two will both try to 
edit the same thing simultaneously.

If in your second example you disallow content that would violate this than 
you are left with something identical to using nested reveal widgets.

I would like to find a way around this, but because the wiki may be 
re-rendered unpredictably I don't think that you could define consistent 
behaviour in these cases.

-- 
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] and sections ...revisited (sorry, long post :)

[Tobias Beer]

Some toying with what could be a *$section* widget...

a) create link to section...

<$section link="tiddler§§section"/>

b) render section toc for tiddler here...

<$section toc="render"/>

c) build section toc assuming a previous <$section toc="render"/> widget 
exists in the context (would be placed in a global viewtemplate section 
after the body

<$section toc="build"/>

d) provides a button that opens a section editor

<$section edit="tiddler§§section"/>


Or a *[section[]]* filter...

e) lists all summary sections up until the next heading, regardless of its 
level (TWc)

<$list filter="[section[summary]]"/>

f) lists all summary sections up until the next heading of the same level

<$list filter="[section:full[summary]]"/>

etc...

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] in a macro: achieve if / else

[Tobias Beer]

Ok, I fear I wasn't quite clear about the idea and I don't even know 
whether any of those patterns make much sense the way I liked to play it 
through, but here it goes...

In a way, I wanted to make *a macro* agnostic to whether or not it is fed a 
variable or a parameter... don't ask me why, that was the ball being played 
:)

Something like (watch out, pseudo-syntax)...

\define macro(foo)
<$if $foo$>
do this
<$else>
<$if <>>
do that
<$else>
otherwise this




\end

...but that other usecase where a single variable or parameter has 
different values is a lot more interesting...

\define macro(foo)
<$if match="$foo$" value="bar">
do this
<$else>
<$if match="$foo$" value="baz">
do that
<$else>
otherwise this




\end

So, that's two entirely different games being played :)

Something tells me that that's almost like the reveal widget, except that 
reveal only works by checking against states, rather than checking a param 
or variable against something 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.

Re: [tw] [TW5] How to make sure filter has only unique items?

[Tobias Beer]

>
> The fix is to add "+[limit[1]]" to the end of the filter expression.
>>
> Of course, so simple! :)
>

Or, so I thought. Actually, I still don't get it to work...

http://tb5.tiddlyspot.com... 


<$list filter="[all[current]tag[$:/tags/ShowSource]] 
[all[current]prefix[$:/template]][all[current]prefix[$:/macro]!field:type[application/javascript]]-[[$:/macros/source]]+[limit[1]]">
<$view tiddler=<> format="text"/>


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] Yet another documentation idea

[Jed Carty]

I think using the old documentation list would be best so that people 
writing documentation wouldn't be spamming this list and wouldn't need to 
dig through things here to find proposed changes. I submitted a post to 
that list suggesting using the method discussed here, but it needs to be 
approved. Can we make that list open like this one? I don't want to 
discourage people from posting requests for documentation there.

-- 
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] How to make sure filter has only unique items?

[Tobias Beer]

>
> The fix is to add "+[limit[1]]" to the end of the filter expression.
> 
>

Of course, so simple! :)

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] concatenating title and textreference into a filter operand

[Tobias Beer]

Thanks Stephan, that worked perfectly :)

Will be thinking of using helper macros from now on for preprocessing vars.

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] NameSpaceWidget — Drawing Board

[Jeremy Ruston]

Hi Tobias

It looks like the widget will in many cases generate further widgets (eg
when you want it to list children of the current tiddler you're presumably
not going to attempt to duplicate the logic of the list widget).

Although widgets can generate other widgets it does provide a hint that the
operations being performed are quite high level, compared to the sort of
primitives that usually comprise widgets.

Have you considered creating a suite of macros to cover your needs:

<>
<>
<>

Best wishes

Jeremy


On Sun, Nov 23, 2014 at 6:03 PM, Tobias Beer  wrote:

> Hi everyone,
>
> I was playing
> 
> with pseudo-sections  that follow simple
> naming conventions, e.g.:
>
>- El Libro
>- El Libro / Capitulo 01
>- El Libro / Capitulo 01 / 001
>- El Libro / Capitulo 02
>- El Libro / Capitulo 02 / Notes
>
> This reminded me an awful lot of what I did some time ago for TWc, namely
> this fairly underdocumented goodie...
>
> http://namespace.tiddlyspace.com/#Explore
> 
>
> So, now I am thinking I'd like to officially make this my first TW5 plugn
> project
> and turn all that into a *$namespace* widget.
>
> Here's the rough concept...
> (keep the kind of things in mind that you see in the tiddlyspace above)
>
>
> http://namespace.tiddlyspot.com/#NameSpaceWidget:NameSpaceWidget%20GettingStarted
>
> Now, I didn't start any development yet, so I'm inclined to ask you for
> some preliminary feedback on the design idea.
>
> Also, for Jeremy and others with some TW5 coding experience, please be so
> kind and give me some pointers for...
>
>- skeletons to start from
>- reference implementations that might be relevant
>- utilities and components that I might need
>- specific core knowledge that I might want to read up on
>- conventions to follow
>
> All of this will surely be an evolutionary process... so, if you feel like
> you can, please help me start on a solid foundation.
>
> 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] How to make sure filter has only unique items?

[Jeremy Ruston]

Hi Tobias

The problem is that you're using the list widget as a kind of selective
reveal to decide whether to show the monospaced tiddler text. Sometimes
your filter is returning more than one result, and that's why the content
of the list widget is rendered multiple times.

The fix is to add "+[limit[1]]" to the end of the filter expression.

Best wishes

Jeremy


On Sun, Nov 23, 2014 at 6:05 PM, Tobias Beer  wrote:

> Hi Jeremy,
>
>
>> Can you post the example?
>>
>
> Of course...
>
> <$list filter="[all[current]tag[$:/tags/ShowSource]] 
> [all[current]prefix[$:/template]]  
> [all[current]prefix[$:/macro]!field:type[application/javascript]] 
> -[[$:/macros/source]] -[[$:/macros/static]]">
> <$view tiddler=<> format="text"/>
> 
>
>
> 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] Yet another documentation idea

[Jeremy Ruston]

Hi Jed

> mild dyslexia means I have to either spend time checking every word or
deal with lots and lots of spelling errors, this generally prevents me from
contributing too much to documentation

It's pretty well hidden - I didn't spot any errors in the material you
posted.

> Could we have a pinned thread here

I'm not a huge fan of pinned threads, but I understand the motivation.

There is actually already an existing but dormant TiddlyWiki Documentation
mailing list which we could reactivate:

https://groups.google.com/forum/#!forum/tiddlywikidocs

(There's also a dormant group for core development at
https://groups.google.com/forum/#!forum/tiddlywikicoredev)

> My only other concern is that there may be some licensing issues if
someone has a cloned wiki for documentation and doesn't sign the license. I
have no idea if that would be a problem or not, but I thought I should
mention it.

Good point. Some projects have dropped using a CLA; maybe we should explore
it too.

Best wishes

Jeremy.





On Sun, Nov 23, 2014 at 5:58 PM, Jed Carty  wrote:

> Jeremy, Tobias,
> I like this idea. It would be particularly useful for people like me who
> can't really spell to have easier review than through the github process
> (mild dyslexia means I have to either spend time checking every word or
> deal with lots and lots of spelling errors, this generally prevents me from
> contributing too much to documentation.). Also it would make it easier for
> people who don't have time or aren't good at layout design to put up
> content and have someone else copy the tiddler to make it more readable.
>
> Could we have a pinned thread here to ask for review of tiddlers prior to
> sending a pull request? That way we would only be spamming one thread and
> people who only have a few minutes could find a list of potential changes
> and a way to give feedback on them. Also pull requests could be done the
> same way as they are done now. Go to the tiddler on tiddlywiki.com and go
> to github and copy/paste from the cloned tiddler on tiddlyspot.
>
> We just need to make sure that we coordinate in the pinned thread so we
> don't get a bunch of people submitting the same thing a bunch of times.
> My only other concern is that there may be some licensing issues if
> someone has a cloned wiki for documentation and doesn't sign the license. I
> have no idea if that would be a problem or not, but I thought I should
> mention it.
>
>
> On Saturday, November 22, 2014 6:24:54 PM UTC-7, Mat wrote:
>>
>> In another thread, apropos the need for documentation,
>>
>> pmario wrote:
>>
>>>  - With 5.1.5. it will be possible to export tiddlers in different
>>> formats.
>>> - So it's possible to edit content with TW. - export it - and send
>>> it to a developer (if jeremy is ok with this workflow)
>>>
>>
>> This is a very interesting idea from pmario. Imagine if it was possible
>> for visitors to edit the documentation *directly on tw.com
>> * (...actually a local temporary copy on the screen).
>> Export that single(!) tiddler to have it sent as a .tid file to tw.com.
>>
>> Then what? Well, I can imagine many options, The tid should probably be
>> sandboxed but it could be viewed from the original tiddler somehow (iframe
>> in slider, or whatever).
>>
>> ...new visitors can read this hopefully improved *draft* and give it
>> likes! When the number of likes reaches a threshold - voila, the original
>> tiddler gets auto-replaced with the proposed one!!! Alternatively, a
>> voluntary proofreader gets pinged at threshold for a final approval before
>> it is published.
>>
>> I'd think much documentation does not require deep technical competence
>> only familiarity with tw, Proofreaders could even get pinged only for their
>> favorite subjects if the tiddler is tagged.
>>
>> There could also be dislikes. Negative threshold reached - poof!
>>
>> The purpose is to have documentation as an ongoing activity spread out on
>> many people where even small, small contributions on the whim add up to
>> something meaningful. "... like tiddlers composing a full wiki" (ah, even
>> poetry)
>>
>>
>> <:-)
>>
>  --
> 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

[tw] Re: [TW5] in a macro: achieve if / else

[Stephan Hradek]

Should you want the other logic: Use the variable as a fallback:

\define otherlogic(parameter)  <$list filter="[[$parameter$]]"><$view field=
"title">$(variable)$

<$set name="variable" value="Variable used">

!No Parameter
<>

!With Parameter
<>


Please note that the usual caveats in regards to square brackets in 
variable or parameter apply.

-- 
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] How to make sure filter has only unique items?

[Tobias Beer]

Hi Jeremy,
 

> Can you post the example?
> 
>

Of course...

<$list filter="[all[current]tag[$:/tags/ShowSource]] 
[all[current]prefix[$:/template]]  
[all[current]prefix[$:/macro]!field:type[application/javascript]] 
-[[$:/macros/source]] -[[$:/macros/static]]">
<$view tiddler=<> format="text"/>



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] in a macro: achieve if / else

[Stephan Hradek]

Schould you want the other logic: Use the variable as a fallback:

\define otherlogic(parameter)  <$list filter="[[$parameter$]]"><$view field=
"title">$(variable)$

<$set name="variable" value="Variable used">

!No Parameter
<>

!With Parameter
<>


Please note that the usual caveats apply: No double square brackets in 
variable or parameter.


-- 
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] NameSpaceWidget — Drawing Board

[Tobias Beer]

Hi everyone,

I was playing 
 with 
pseudo-sections  that follow simple naming 
conventions, e.g.:

   - El Libro
   - El Libro / Capitulo 01
   - El Libro / Capitulo 01 / 001
   - El Libro / Capitulo 02
   - El Libro / Capitulo 02 / Notes
   
This reminded me an awful lot of what I did some time ago for TWc, namely 
this fairly underdocumented goodie...

http://namespace.tiddlyspace.com/#Explore 


So, now I am thinking I'd like to officially make this my first TW5 plugn 
project
and turn all that into a *$namespace* widget.

Here's the rough concept...
(keep the kind of things in mind that you see in the tiddlyspace above)

http://namespace.tiddlyspot.com/#NameSpaceWidget:NameSpaceWidget%20GettingStarted

Now, I didn't start any development yet, so I'm inclined to ask you for 
some preliminary feedback on the design idea.

Also, for Jeremy and others with some TW5 coding experience, please be so 
kind and give me some pointers for...

   - skeletons to start from
   - reference implementations that might be relevant
   - utilities and components that I might need
   - specific core knowledge that I might want to read up on
   - conventions to follow

All of this will surely be an evolutionary process... so, if you feel like 
you can, please help me start on a solid foundation.

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] in a macro: achieve if / else

[Stephan Hradek]

Try this: 

\define tobilogic(parameter)  <$list filter="[[$(variable)$]]"><$view field=
"title">$parameter$

!variable not defined
<>

!variable defined
<$set name="variable" value="OK! variable defined">
<>




-- 
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] Yet another documentation idea

[Jed Carty]

Jeremy, Tobias, 
I like this idea. It would be particularly useful for people like me who 
can't really spell to have easier review than through the github process 
(mild dyslexia means I have to either spend time checking every word or 
deal with lots and lots of spelling errors, this generally prevents me from 
contributing too much to documentation.). Also it would make it easier for 
people who don't have time or aren't good at layout design to put up 
content and have someone else copy the tiddler to make it more readable.

Could we have a pinned thread here to ask for review of tiddlers prior to 
sending a pull request? That way we would only be spamming one thread and 
people who only have a few minutes could find a list of potential changes 
and a way to give feedback on them. Also pull requests could be done the 
same way as they are done now. Go to the tiddler on tiddlywiki.com and go 
to github and copy/paste from the cloned tiddler on tiddlyspot.

We just need to make sure that we coordinate in the pinned thread so we 
don't get a bunch of people submitting the same thing a bunch of times. 
My only other concern is that there may be some licensing issues if someone 
has a cloned wiki for documentation and doesn't sign the license. I have no 
idea if that would be a problem or not, but I thought I should mention it.

On Saturday, November 22, 2014 6:24:54 PM UTC-7, Mat wrote:
>
> In another thread, apropos the need for documentation,
>
> pmario wrote:
>
>>  - With 5.1.5. it will be possible to export tiddlers in different 
>> formats.
>> - So it's possible to edit content with TW. - export it - and send it 
>> to a developer (if jeremy is ok with this workflow)
>>
>
> This is a very interesting idea from pmario. Imagine if it was possible 
> for visitors to edit the documentation *directly on tw.com 
> * (...actually a local temporary copy on the screen). 
> Export that single(!) tiddler to have it sent as a .tid file to tw.com.
>
> Then what? Well, I can imagine many options, The tid should probably be 
> sandboxed but it could be viewed from the original tiddler somehow (iframe 
> in slider, or whatever).
>
> ...new visitors can read this hopefully improved *draft* and give it 
> likes! When the number of likes reaches a threshold - voila, the original 
> tiddler gets auto-replaced with the proposed one!!! Alternatively, a 
> voluntary proofreader gets pinged at threshold for a final approval before 
> it is published.
>
> I'd think much documentation does not require deep technical competence 
> only familiarity with tw, Proofreaders could even get pinged only for their 
> favorite subjects if the tiddler is tagged.
>
> There could also be dislikes. Negative threshold reached - poof!
>
> The purpose is to have documentation as an ongoing activity spread out on 
> many people where even small, small contributions on the whim add up to 
> something meaningful. "... like tiddlers composing a full wiki" (ah, even 
> poetry)
>
>
> <:-)
>

-- 
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] textarea autoresize is annoying.

[Jeremy Ruston]

Hi Danielo

In the current TW version (5.1.4) it's not possible to deactivate the auto
> resizing feature.
>
> On the most recent (5.1.5) it's possible to deactivate the auto resizing,
> but you have to set it on every widget call. This can be a Paine. I would
> prefer to use CSS and classes.
>

Ah, I see what you mean. Why do you want to disable the auto resizing? The
edit-text widget could use a configuration variable to provide the default
for whether to autoresize.

Best wishes

Jeremy.



>
> 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] How to make sure filter has only unique items?

[Jeremy Ruston]

Hi Tobias

Can you post the example?

Many thanks,

Jeremy

On Sun, Nov 23, 2014 at 5:34 PM, Tobias Beer  wrote:

> I am trying to show the source-code for certain tiddlers, e.g. macros...
>
> However, my ORing filter operators seems to yield duplicate results as the
> source is shown twice.
>
> [[$:/template/view-template]] [[$:/macros/describe-element]]
> 
>
> Any ideas what's wrong with the filter?
>
> 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.

[tw] [TW5] How to make sure filter has only unique items?

[Tobias Beer]

I am trying to show the source-code for certain tiddlers, e.g. macros...

However, my ORing filter operators seems to yield duplicate results as the 
source is shown twice.

[[$:/template/view-template]] [[$:/macros/describe-element]] 


Any ideas what's wrong with the filter?

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] in a macro: achieve if / else

[Jed Carty]

I have been trying to find a way to do this as well. I think that there may 
be a way to do this using the updated set widget in the prerelease and 
something like the combination lock in the Safe tiddler in the interactive 
fiction thing I am working on (http://zorklike.tiddlyspot.com/). I haven't 
had any success in actually getting it to work, but I have been poking it.

The tiddler EventTriggerTemplate from the zork-like wiki has an example of 
some simple nested reveal widgets that could probably be modified by using 
set, and you could put them in a macro that allows them to take different 
parameters. 
You can use this to put if/elseif/else functionality into displayed content 
using reveal widgets by using a filter and set to pick the state used by 
the reveal widget. But this is just for revealing content.

That is my progress on the problem, I have been lazily learning javascript, 
hopefully I will just make a plugin. So if you do get a good structure for 
the widget worked out I will at least try to implement it. It would be a 
good thing to learn with, but I just started teaching myself so don't 
expect anything too amazing. 

On Sunday, November 23, 2014 5:20:00 AM UTC-7, Tobias Beer wrote:
>
> Hi everyone,
>
> I'd like to be able to follow optional routes in a macro, for example...
>
>- *if *it's value is defined take *<>*
>- *else* take *$parameter$*
>
> I can certainly play with options to achieve this and
> once I figured something out myself, I will post here.
>
> Regardless, I'd love to know the possible ways
> you know or can think of in which to tackle this problem, so...
>
> If you've have something new in in mind,
> start your reply with a line that summarizes your concept:
>
> "CONCEPT: use foo bar..."
>
> That way it's easier to spot possible solutions.
>
> Could even be an idea for a new widget that doesn't even exist yet, e.g. 
> IfElseWidget...
> sketch out the design for it, someone might just jump at its 
> implementation.
>
> 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] New Feature Moratorium

[Jeremy Ruston]

Hi Erwan

> I tried to develop these ideas and to imagine how things could work
globally in a more detailed proposition, in case that helps:
http://tw-doc-ideas.tiddlyspot.com

Terrific stuff, thank you Erwan. You've done a great job of summarising the
situation and the ideas that are floating around.

Perhaps some of your material could be structured as a pull request to
start fleshing out the contribution guidelines in tw5.com?

I realised earlier when I made the following changes that the "house style"
of tiddlywiki.com is not explicitly stated, providing another hurdle for
contributors:

https://github.com/Jermolene/TiddlyWiki5/commit/4134392841862830fd4c5cf3b3d6512b30bc885f

Best wishes

Jeremy

https://github.com/Jermolene/TiddlyWiki5/commit/4134392841862830fd4c5cf3b3d6512b30bc885f




On Sun, Nov 23, 2014 at 4:33 PM, Erwan  wrote:

>
> Hi everyone,
>
> as this is my first post here, I'd like to start by thanking Jeremy and
> everyone who contributes to TW, from core development to helping make the
> community so engaging. I've discovered TW only a few months ago (I was
> lucky to arrive just for the birth of the official TW5), and I've been
> hooked by both the great tool that TW is and the good atmosphere of
> knowledge sharing in the community.
>
> I agree with Jeremy and everybody in this thread that improving the
> documentation process (including the great potential for community
> knowledge) becomes more and more important, especially in the perspective
> of attracting newcomers.
>
> In general my thoughts on the topic are similar to what most people have
> said here. I would like to suggest maybe a couple of points that I think
> deserve some attention. Indeed, people with technical skills tend to focus
> on the technical side of a problem, and obviously there are highly skilled
> people here ;) While this is important, there can be other angles to look
> at:
>
> * For example, about the fact that some people are not comfortable using
> github, a very simple way to overcome the problem would be to have a few
> volunteers who know git who would receive the contributions and make the
> pull request for them. I guess something similar could be done for other
> things, like translating, so that someone who can translate doesn't need to
> have any technical skills.
>
> * Imho, one of the problems with contributing to the official
> documentation is that there is no clear guidelines about the structure or
> the type of content. I think that it would be very helpful to think about a
> detailed plan and identify the missing parts: this way it would be easier
> for people who want to contribute to know what to do, and eventually for
> newcomers to find their way in the documentation.
>
> I tried to develop these ideas and to imagine how things could work
> globally in a more detailed proposition, in case that helps:
> http://tw-doc-ideas.tiddlyspot.com
>
> Regards,
> Erwan
>
>
>
>
> On 23/11/14 13:21, Jeremy Ruston wrote:
>
> Thanks everyone for their contributions. There are a bunch of good
> suggestions in the thread which I'll try to pick up in the hangout on
> Tuesday.
>
>  A big topic is clearly how we improve the contribution process for the
> documentation. I have a couple of thoughts:
>
>  * We could initiate a TW5 community space on tiddlyspace along the lines
> of tiddlywiki.org - it's a proven way to work. It would be good to try
> out TW5's support for TiddlySpace in a multiuser setting (since it's not
> been done before I think there may be some wrinkles to be ironed out).
> * We should support documentation contributions by people taking a copy of
> tiddlywiki.com onto tiddlyspot and making their edits there. I could
> easily build a batch file that pulls down their changes and applies them to
> the repo, so that I can convert their changes to a pull request (I don't
> think there's any avoiding needing a moderation step for tiddlywiki.com)
> * An alternative workflow for accepting those contributions would be to
> support visual diffing in the import manager
>
>  I've also got a couple of clarifications.
>
>  > Perhaps there's a way to display a sticky above the github issues.
>
>  We don't want to discourage people from suggesting and discussing new
> features, but lets see how it goes and I can add a banner to the "new
> issue" page if needed.
>
>  > 4. You may think about a two level plugin list: the top part would
> list the plugins that are officially sanctioned and compatible with the
> latest release. The bottom part could be a growing list of webpages where
> individuals have stored there plugins and goodies they have created for TW
> but that may or may not continue to be compatible.
>
>  That's pretty much what we've got:
>
>  * Plugins listed in http://tiddlywiki.com/#Plugins are the officially
> maintained and distributed plugins. They will be automatically upgraded
> when using http://tiddlywiki.com/upgrade.html
> * Community plugins are listed in http://tiddlywiki.com/#Res

Re: [tw] [TW5] textarea autoresize is annoying.

[Danielo Rodríguez]

Hello Jeremy, 

In the current TW version (5.1.4) it's not possible to deactivate the auto 
resizing feature. 

On the most recent (5.1.5) it's possible to deactivate the auto resizing, but 
you have to set it on every widget call. This can be a Paine. I would prefer to 
use CSS and classes. 

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] Re: [TW5] Taskgraph BETA is out on github and nightly demo is available

[Danielo Rodríguez]

Hello Félix 

I was trying on the online version. Now is working. Maybe is a problem on my 
Mac, on my mobile it's working. I'll check it out.

-- 
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] Yet another documentation idea

[Tobias Beer]

>
> Just to clarify, I have not yet written the scripts needed to 
> automatically unpack a tiddlywiki HTML file and put the tiddler files in 
> the correct locations. So any contributions in this way right now will need 
> to be manually processed.
>

Added that to...

http://tb5.tiddlyspot.com/#Documentation

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] New Feature Moratorium

[Erwan]

Hi everyone,

as this is my first post here, I'd like to start by thanking Jeremy and 
everyone who contributes to TW, from core development to helping make 
the community so engaging. I've discovered TW only a few months ago (I 
was lucky to arrive just for the birth of the official TW5), and I've 
been hooked by both the great tool that TW is and the good atmosphere of 
knowledge sharing in the community.


I agree with Jeremy and everybody in this thread that improving the 
documentation process (including the great potential for community 
knowledge) becomes more and more important, especially in the 
perspective of attracting newcomers.


In general my thoughts on the topic are similar to what most people have 
said here. I would like to suggest maybe a couple of points that I think 
deserve some attention. Indeed, people with technical skills tend to 
focus on the technical side of a problem, and obviously there are highly 
skilled people here ;) While this is important, there can be other 
angles to look at:


* For example, about the fact that some people are not comfortable using 
github, a very simple way to overcome the problem would be to have a few 
volunteers who know git who would receive the contributions and make the 
pull request for them. I guess something similar could be done for other 
things, like translating, so that someone who can translate doesn't need 
to have any technical skills.


* Imho, one of the problems with contributing to the official 
documentation is that there is no clear guidelines about the structure 
or the type of content. I think that it would be very helpful to think 
about a detailed plan and identify the missing parts: this way it would 
be easier for people who want to contribute to know what to do, and 
eventually for newcomers to find their way in the documentation.


I tried to develop these ideas and to imagine how things could work 
globally in a more detailed proposition, in case that helps: 
http://tw-doc-ideas.tiddlyspot.com


Regards,
Erwan



On 23/11/14 13:21, Jeremy Ruston wrote:
Thanks everyone for their contributions. There are a bunch of good 
suggestions in the thread which I'll try to pick up in the hangout on 
Tuesday.


A big topic is clearly how we improve the contribution process for the 
documentation. I have a couple of thoughts:


* We could initiate a TW5 community space on tiddlyspace along the 
lines of tiddlywiki.org  - it's a proven way to 
work. It would be good to try out TW5's support for TiddlySpace in a 
multiuser setting (since it's not been done before I think there may 
be some wrinkles to be ironed out).
* We should support documentation contributions by people taking a 
copy of tiddlywiki.com  onto tiddlyspot and 
making their edits there. I could easily build a batch file that pulls 
down their changes and applies them to the repo, so that I can convert 
their changes to a pull request (I don't think there's any avoiding 
needing a moderation step for tiddlywiki.com )
* An alternative workflow for accepting those contributions would be 
to support visual diffing in the import manager


I've also got a couple of clarifications.

> Perhaps there's a way to display a sticky above the github issues.

We don't want to discourage people from suggesting and discussing new 
features, but lets see how it goes and I can add a banner to the "new 
issue" page if needed.


> 4. You may think about a two level plugin list: the top part would 
list the plugins that are officially sanctioned and compatible with 
the latest release. The bottom part could be a growing list of 
webpages where individuals have stored there plugins and goodies they 
have created for TW but that may or may not continue to be compatible.


That's pretty much what we've got:

* Plugins listed in http://tiddlywiki.com/#Plugins are the officially 
maintained and distributed plugins. They will be automatically 
upgraded when using http://tiddlywiki.com/upgrade.html

* Community plugins are listed in http://tiddlywiki.com/#Resources

Perhaps we should maintain a catalogue of community plugins that is 
separate from the general resources list.


> Will 1.1.5 and the export feature make release before the moratorium 
begins?


Yes, the moratorium would start after 5.1.5's release.

Best wishes

Jeremy


On Sat, Nov 22, 2014 at 6:43 PM, 'Mark S.' via TiddlyWiki 
mailto:tiddlywiki@googlegroups.com>> wrote:


Whenever you have an open web page, you end up with spammers
trying to create link drops.

Probably a real wiki (with authentication) or even just a special
thread on this forum would be better. I believe the better wiki
systems track history, so changes can be rolled back when
something useful has been overwritten.

I feel the github process discourages documentation. The problem
is that it's the same system of review for documentation as for
code. Which m

Re: [tw] [TW5] Iterate fields

[Jeremy Ruston]

Hi Tobias

> core-version and module-type are not, in fact, yet undocumented core
fields

Good catch. They've ended up being undocumented because they only occur on
shadow tiddlers on tiddlywiki.com (in SystemTags we display the fields in
the wiki via a filter that doesn't include shadow tiddlers).

Best wishes

Jeremy.


On Wed, Nov 19, 2014 at 12:34 AM, Tobias Beer  wrote:

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



-- 
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] XMLHttpRequest error code: 404

[Jeremy Ruston]

Hi JimyKK

Apologies for the late reply.

> every-time I load the wiki I get a XMLHttpRequest error code: 404 popup
(See attached image)

The image hasn't come through. What's the URL that fails? Do you see any
useful information in your browser developer tools "network" tab?

Best wishes

Jeremy

On Wed, Nov 19, 2014 at 3:48 AM, JimyKK  wrote:

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



-- 
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] New Feature Moratorium

[David Gifford]

Yay! Thanks, Jeremy

On Sunday, November 23, 2014 7:31:33 AM UTC-6, Jeremy Ruston wrote:
>
> Hi Dave
>
> > And 5.1.5 will be released this week, right Jeremy?
>
> Yes, there's nothing else big planned, but it'll still be a couple of days 
> before the release. In particular there's quite a few contributions 
> awaiting merging on github.
>
> Best wishes
>
> Jeremy.
>
>
> On Sun, Nov 23, 2014 at 1:29 PM, David Gifford  > wrote:
>
>> And 5.1.5 will be released this week, right Jeremy? I am really eager to 
>> have this update. It's got some great stuff in it. Also I am eager because 
>> I have used some of the define newhere bits you  emailed me, but they don't 
>> seem to work in 5.1.4, only in my copy of the prerelease of 5.1.5. This new 
>> version HAS been in the works for a while, so don't keep us in suspense 
>> forever! :-)
>>
>> Dave
>>
>> On Sun, Nov 23, 2014 at 7:21 AM, Jeremy Ruston > > wrote:
>>
>>> Thanks everyone for their contributions. There are a bunch of good 
>>> suggestions in the thread which I'll try to pick up in the hangout on 
>>> Tuesday.
>>>
>>> A big topic is clearly how we improve the contribution process for the 
>>> documentation. I have a couple of thoughts:
>>>
>>> * We could initiate a TW5 community space on tiddlyspace along the lines 
>>> of tiddlywiki.org - it's a proven way to work. It would be good to try 
>>> out TW5's support for TiddlySpace in a multiuser setting (since it's not 
>>> been done before I think there may be some wrinkles to be ironed out).
>>> * We should support documentation contributions by people taking a copy 
>>> of tiddlywiki.com onto tiddlyspot and making their edits there. I could 
>>> easily build a batch file that pulls down their changes and applies them to 
>>> the repo, so that I can convert their changes to a pull request (I don't 
>>> think there's any avoiding needing a moderation step for tiddlywiki.com)
>>> * An alternative workflow for accepting those contributions would be to 
>>> support visual diffing in the import manager
>>>
>>> I've also got a couple of clarifications.
>>>
>>> > Perhaps there's a way to display a sticky above the github issues.
>>>
>>> We don't want to discourage people from suggesting and discussing new 
>>> features, but lets see how it goes and I can add a banner to the "new 
>>> issue" page if needed.
>>>
>>> > 4. You may think about a two level plugin list: the top part would 
>>> list the plugins that are officially sanctioned and compatible with the 
>>> latest release. The bottom part could be a growing list of webpages where 
>>> individuals have stored there plugins and goodies they have created for TW 
>>> but that may or may not continue to be compatible.
>>>
>>> That's pretty much what we've got:
>>>
>>> * Plugins listed in http://tiddlywiki.com/#Plugins are the officially 
>>> maintained and distributed plugins. They will be automatically upgraded 
>>> when using http://tiddlywiki.com/upgrade.html
>>> * Community plugins are listed in http://tiddlywiki.com/#Resources
>>>
>>> Perhaps we should maintain a catalogue of community plugins that is 
>>> separate from the general resources list.
>>>
>>> > Will 1.1.5 and the export feature make release before the moratorium 
>>> begins?
>>>
>>> Yes, the moratorium would start after 5.1.5's release.
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>> On Sat, Nov 22, 2014 at 6:43 PM, 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com > wrote:
>>>
 Whenever you have an open web page, you end up with spammers trying to 
 create link drops.

 Probably a real wiki (with authentication) or even just a special 
 thread on this forum would be better. I believe the better wiki systems 
 track history, so changes can be rolled back when something useful has 
 been 
 overwritten.

 I feel the github process discourages documentation. The problem is 
 that it's the same system of review for documentation as for code. Which 
 means that you may have to wait a week or so before changes get applied, 
 Sure, CODE needs to be thoroughly vetted so that TW doesn't break. But, 
 unlike code, poor documentation is usually better than NO documentation, 
 and it can be peer-reviewed and tweaked as time goes along. It's an odd 
 quirk of human psychology that people tend to like to correct things that 
 are already in place rather than creating new content in the first place. 
 So getting something in place quickly (even if not 100% perfect) is more 
 important than getting it publisher-ready on the first draft.

 Mark

 On Friday, November 21, 2014 6:37:16 PM UTC-8, Jed Carty wrote:
>
> I think that we could try making a public tiddlywiki on tiddlyspot and 
> make a list of topics people want documentation for the most, then 
> collect 
> explanations and examples from people and hopefully get someone who is 
> good 
> at technical writing or design to collect 

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

[Jeremy Ruston]

[all[]] is a shortcut for [all[tiddlers]].

Most filters are executed in a context where there is an implicit
`[all[tiddlers]]` at the start of each run of filter operators. There are
some places where the "source" of the filter is a specific set of tiddlers,
rather than `[all[tiddlers]]` (eg filtering changed tiddlers in the saver
manager).

Best wishes

Jeremy.


On Wed, Nov 19, 2014 at 12:17 PM, Tobias Beer  wrote:

> have a look here: http://tiddlywiki.com/#Introduction%20to%20Filters
>> sections: Filter Operators, ORing Multiple Filter Operators, ANDing
>> Multiple Filter Operators
>>
>> Additional examples would make sense there. IMO pull requests are
>> welcome.
>>
>
> Yes, thank you. ^_^
> What I meant was is that it's not clear to me if only specific filters
> start from *[all[]]* or if all do.
>
> 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] textarea autoresize is annoying.

[Jeremy Ruston]

Hi Danielo

I'm not quite sure what you're asking.

> Since this is better than the current implementation, it forces you to
define it on every textarea

What is better than the current implementation? What do you have to define
on every textarea?

> Textareas re-sizes  themselves by default

HTML textareas do not dynamically resize themselves to fit their content.

TiddlyWiki automatically resizes textareas in order to avoid nested
scrollbars.

Best wishes

Jeremy




On Wed, Nov 19, 2014 at 1:26 PM, Danielo Rodríguez 
wrote:

> Triying to fix a very annoying issue on 5.1.4 today I went to github and I
> found:
>
>   EditTextWidget.prototype.fixHeight = function() {var self =
> this,domNode = this.domNodes[0];if(this.editAutoHeight
> && domNode && !domNode.isTiddlyWikiFakeDom && this.editTag === "textarea")
> {
>
>
> Since this is better than the current implementation, it forces you to
> define it on every textarea. This is against every UI design guidelines I
> can think about. I expect to be able to specify this kind of things on the
> CSS and I think the average user too. I don't understand why this is
> hardcoded into the edit-text widget. Textareas re-sizes  themselves by
> default, and you can deactivate this if you need it by CSS. Could someone
> explain me the need for specify this at node level?
>
>
>  --
> 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] # breaks test references

[Jeremy Ruston]

Hi Danielo

This has been fixed for 5.1.5:

https://github.com/Jermolene/TiddlyWiki5/commit/1f82ebc7c3a31cfb36b86e31d14b0c4533950723

There's a prerelease at http://tiddlywiki.com/prerelease for you to test,

Best wishes

Jeremy


On Wed, Nov 19, 2014 at 2:19 PM, Danielo Rodríguez 
wrote:

> If you include # in the title of a tiddler it can not be referenced like
> this
> {{the#tittle!!text}}
>
> You can reproduce the problem importing the tiddlers in the json file
> attached
>
> --
> 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] Yet another documentation idea

[Jeremy Ruston]

Hi Tobias

> Don't overdo edits (i.e. number of tiddlers), unless you know what you're
doing or have discussed major restructuring beforehand. Otherwise expect
the review to be tougher to manage for Jeremy & co.

Just to clarify, I have not yet written the scripts needed to automatically
unpack a tiddlywiki HTML file and put the tiddler files in the correct
locations. So any contributions in this way right now will need to be
manually processed.

Best wishes

Jeremy




On Sun, Nov 23, 2014 at 3:08 PM, Tobias Beer  wrote:

> I think there's a much easier way that we could accept contributions to
>> the documentation.
>>
>
> Real easy, indeed!
>
>1. create a tiddlyspot  for your documentation
>changes
>2. go to tiddlywiki.com / *ControlPanel / Saving* tab
>3. set *Wiki Name* and *Password* according to your tiddlyspot
>
>4. click save on tiddlywiki.com
>5. open your tiddlyspot 
>6. make edits => all done?
>7. notify => here in the groups
> or via new GitHub
>issue 
>8. *wait*
>9. accepted and imported? => verify changes to tiddlywiki.com => back
>to 4, next topic
>10. not accepted? => improve or back to 4, next topic
>
> Don't overdo edits (i.e. number of tiddlers), unless you know what you're
> doing or have discussed major restructuring beforehand. Otherwise expect
> the review to be tougher to manage for Jeremy & co.
>
> I also put the above here...
>
> http://tb5.tiddlyspot.com/#Documentation
>
> 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] [TW5] Yet another documentation idea

[Tobias Beer]

>
> I think there's a much easier way that we could accept contributions to 
> the documentation. 
>

Real easy, indeed!

   1. create a tiddlyspot  for your documentation 
   changes
   2. go to tiddlywiki.com / *ControlPanel / Saving* tab
   3. set *Wiki Name* and *Password* according to your tiddlyspot 
    
   4. click save on tiddlywiki.com
   5. open your tiddlyspot  
   6. make edits => all done?
   7. notify => here in the groups 
    or via new GitHub 
   issue 
   8. *wait*
   9. accepted and imported? => verify changes to tiddlywiki.com => back to 
   4, next topic
   10. not accepted? => improve or back to 4, next topic

Don't overdo edits (i.e. number of tiddlers), unless you know what you're 
doing or have discussed major restructuring beforehand. Otherwise expect 
the review to be tougher to manage for Jeremy & co.

I also put the above here...

http://tb5.tiddlyspot.com/#Documentation

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] limit with macrocall for timeline ignored?

[Jeremy Ruston]

Hi Tobias

> any limit parameter for the macrocall of the timeline macro gets ignored

The limit parameter isn't ignored. It's used to choose the tiddlers whose
dates become headings in the timeline. Then all the tiddlers for each of
those days are listed. It's done that way for performance; the speed of the
recent tab has a big impact on the page refresh cycle time.

To fix the timeline macro to work in the expected way we'll need a bit more
flexibility in the way that lists are handled. In particular, the
setvariable widget needs to be extended to allow the results of a filter to
be assigned to a variable. Then we need a couple of new filter operators
for working with variables containing lists: one to select all of the
entries in the list and one to filter the current list according to whether
each item is listed.

I've made a ticket:

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

Best wishes

Jeremy.


On Thu, Nov 20, 2014 at 12:06 PM, Tobias Beer  wrote:

> Hi Evolena,
>
>
>> That's because the limit parameter applies to the outer list (ie the
>> dates), and not to the number of results of the inner list (the tiddlers
>> modified at that date).
>>
>
> While that's one way to implement it, it's really not the kind of behavior
> I would expect or actually hope for.
> What I really want is to manage the size of the overally list.
>
> So, this raises an interesting question / use-case:
> How to limit the overall results of nested lists?
>
> 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.

[tw] Re: [TW5] Taskgraph BETA is out on github and nightly demo is available

[Felix Küppers]

Hi Danielo,

Did you noticed that is not possible to add fields?


Hmm, it works fine for me. I mean, in the end, everything I create is a 
tiddler and my plugin does not prevent you from entering more fields.

By the way. I frequently update the plugin at the moment. So for new 
features or bugfixes use the plugin provided at github or dragdrop it from 
the demo site.

Regards Felix 

-- 
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] Taskgraph BETA is out on github and nightly demo is available

[Tobias Beer]

>
> Did you noticed that is not possible to add fields?


Where's that? 

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] Concatenated Widget Parameters

[Tobias Beer]

 Hi Jeremy,

Thanks for taking the time to review, very helpful.
 

> Note that "$macroParameter$" and [[$macroParameter$]] are both really a 
> combination of two bits of syntax: double square brackets and double quotes 
> to quote a tiddler title that might contain spaces, and the $dollar$ 
> notation for substituting a macro parameter.
>

Yes, that is indeed obvious. My intention was to provide a quick visual 
that that's indeed the case to provoke an "sure thing" effect.
 

> You've listed {{transclusion}} under "within macros" which might be 
> misleading: there's no special handling for {{transclusion}} processing 
> within macros; the transclusion is just part of the output of the macro and 
> gets wikified at that point.
>

Yes, thank you. I have moved it to the "general wikitext" section and 
mentioned that it, of course, applies to a macro body just the same.

Similarly, listing <$widget param="$macroParameter$"/> as a way to pass 
> widget parameters; it's again a compound syntax, whereas the other examples 
> in that section are basic variants of the attribute syntax.
>

Good to know and be reminded that it's not just about widgets, but any html 
element attribute. I have renamed that section accordingly
 

> If we teach people that <$widget param="$macroParameter$"/> is an 
> out-of-the-box syntax then they risk missing that they can do things 
> like <$widget param="mytiddlertitleprefix-$macroParameter$"/>. The key is 
> to gain an understanding of the two layers involved.
>

Yes, so that is actually an very good example which I have now added, 
although surely important to know that the same does not work for macro 
parameters.

I have restructured the whole thing now and put it here for reference...

general wiki text, including macros» <>» {{transclusion}}» 
, "", [[]]general html element attributes, 
including widgets, e.g. $macrocall» <$widget attribute=<>/>» <$widget 
attribute=<>/>» <$widget 
attribute={{transclusion}}/>» <$widget attribute="prefix-<>"/>» 
<$widget 
attribute=[[prefix-<>]]/>» <$widget 
attribute="prefix-{{transclusion}}"/>within macro body» $macroParameter$, 
"$macroParameter$", [[$macroParameter$]]» $(variable)$ (references a 
variable from the context of the calling macro)» <$widget 
attribute="prefix-$macroParameter$"/>» <$widget attribute=$macroParameter$/> 
(unsafe 
when having spaces)» $variable$, "$variable$", [[$variable$]]macro parameter
» <> (only inside macro)» <> >>» <>" >>» <> >>» 
<>» <>in filters» 
[$macroParameter$] (only filters within macros)» [tag] (no inner 
square brackets!)» [tag{transclusion}] (only single curly brackets!)» 
[tag[$(variable)$]]» [tag[$(variable)$]]

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] Taskgraph BETA is out on github and nightly demo is available

[Danielo Rodríguez]

Hello Félix 

Did you noticed that is not possible to add fields?

-- 
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: ListField seems expect distinct values in the list

[Stephan Hradek]

Am Sonntag, 23. November 2014 12:13:33 UTC+1 schrieb Richard Smith:
>
> Also, the way you ask "why do you expect that when..." is quite rude and 
> I've noticed you doing this to people repeatedly. 
>

Sorry, I'm not a native english speaker. I don't know what sounds rude and 
what not. I was just curious. You expected something that isn't expressed 
in the documentation. So if you tell WHY you expected it, the documentation 
could get enhanced.
 

> I'd rather you just didn't answer, if you're going to talk to me like I'm 
> an idiot, to be honest.
>

Okay. I'm going to ignore you if that's what you want. 

-- 
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: Table of Contents inside a tiddler

[Tobias Beer]

Hi Jeremy,
 

> I think we need a mechanism for more flexibly configuring conditions under 
> which the default body rendering should be hidden.
>

We could have shadows like...

   - $:/config/ui/hide/ViewTemplate/body
   - $:/config/ui/hide/ViewTemplate/tags
   - $:/config/ui/hide/ViewTemplate/toolbar
   - $:/config/ui/hide/PageTemplate/sidebar
   - etc..

...to specify a filter that would hide the elements for matching tiddlers 
and then the logic in the templates to work the magic.

Or the other way around defaulting to a meaningful filter for when to show 
things ;)

   - $:/config/ui/show/ViewTemplate/body
   - $:/config/ui/show/ViewTemplate/tags
   - $:/config/ui/show/ViewTemplate/toolbar
   - $:/config/ui/show/PageTemplate/sidebar
   - etc...

As for that source view, that could directly be part of the body template 
as it needs not be a customized thing, conditionally triggered via 
*$:/tags/ViewTemplate*.

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] External individual tiddlers via iframes?

[Tobias Beer]

Hi Jeremy,
 

> What we really need is "remote transclusion", where TiddlyWiki dynamically 
> loads remote content as tiddlers. That means that the remotely loaded 
> content will be available to list widgets and so on. All we need is a CORS 
> enabled server to make this work.
>
> There are a couple of techniques we can use to do that, and it's 
> definitely on my list.
>

That would indeed be a whole different ballpark, to have some server serve 
or relay remote tiddlers, even lazily loaded.

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] External individual tiddlers via iframes?

[Tobias Beer]

Here is another example of using iframes...

http://tb5.tiddlyspot.com/#Widget%20Browser

It allows you to select an entry from a dictionary and then have the url 
constructed from that.
Have a look at the bottom of that tiddler.

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] New Feature Moratorium

[Jeremy Ruston]

Hi Dave

> And 5.1.5 will be released this week, right Jeremy?

Yes, there's nothing else big planned, but it'll still be a couple of days
before the release. In particular there's quite a few contributions
awaiting merging on github.

Best wishes

Jeremy.


On Sun, Nov 23, 2014 at 1:29 PM, David Gifford  wrote:

> And 5.1.5 will be released this week, right Jeremy? I am really eager to
> have this update. It's got some great stuff in it. Also I am eager because
> I have used some of the define newhere bits you  emailed me, but they don't
> seem to work in 5.1.4, only in my copy of the prerelease of 5.1.5. This new
> version HAS been in the works for a while, so don't keep us in suspense
> forever! :-)
>
> Dave
>
> On Sun, Nov 23, 2014 at 7:21 AM, Jeremy Ruston 
> wrote:
>
>> Thanks everyone for their contributions. There are a bunch of good
>> suggestions in the thread which I'll try to pick up in the hangout on
>> Tuesday.
>>
>> A big topic is clearly how we improve the contribution process for the
>> documentation. I have a couple of thoughts:
>>
>> * We could initiate a TW5 community space on tiddlyspace along the lines
>> of tiddlywiki.org - it's a proven way to work. It would be good to try
>> out TW5's support for TiddlySpace in a multiuser setting (since it's not
>> been done before I think there may be some wrinkles to be ironed out).
>> * We should support documentation contributions by people taking a copy
>> of tiddlywiki.com onto tiddlyspot and making their edits there. I could
>> easily build a batch file that pulls down their changes and applies them to
>> the repo, so that I can convert their changes to a pull request (I don't
>> think there's any avoiding needing a moderation step for tiddlywiki.com)
>> * An alternative workflow for accepting those contributions would be to
>> support visual diffing in the import manager
>>
>> I've also got a couple of clarifications.
>>
>> > Perhaps there's a way to display a sticky above the github issues.
>>
>> We don't want to discourage people from suggesting and discussing new
>> features, but lets see how it goes and I can add a banner to the "new
>> issue" page if needed.
>>
>> > 4. You may think about a two level plugin list: the top part would list
>> the plugins that are officially sanctioned and compatible with the latest
>> release. The bottom part could be a growing list of webpages where
>> individuals have stored there plugins and goodies they have created for TW
>> but that may or may not continue to be compatible.
>>
>> That's pretty much what we've got:
>>
>> * Plugins listed in http://tiddlywiki.com/#Plugins are the officially
>> maintained and distributed plugins. They will be automatically upgraded
>> when using http://tiddlywiki.com/upgrade.html
>> * Community plugins are listed in http://tiddlywiki.com/#Resources
>>
>> Perhaps we should maintain a catalogue of community plugins that is
>> separate from the general resources list.
>>
>> > Will 1.1.5 and the export feature make release before the moratorium
>> begins?
>>
>> Yes, the moratorium would start after 5.1.5's release.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On Sat, Nov 22, 2014 at 6:43 PM, 'Mark S.' via TiddlyWiki <
>> tiddlywiki@googlegroups.com> wrote:
>>
>>> Whenever you have an open web page, you end up with spammers trying to
>>> create link drops.
>>>
>>> Probably a real wiki (with authentication) or even just a special thread
>>> on this forum would be better. I believe the better wiki systems track
>>> history, so changes can be rolled back when something useful has been
>>> overwritten.
>>>
>>> I feel the github process discourages documentation. The problem is that
>>> it's the same system of review for documentation as for code. Which means
>>> that you may have to wait a week or so before changes get applied, Sure,
>>> CODE needs to be thoroughly vetted so that TW doesn't break. But, unlike
>>> code, poor documentation is usually better than NO documentation, and it
>>> can be peer-reviewed and tweaked as time goes along. It's an odd quirk of
>>> human psychology that people tend to like to correct things that are
>>> already in place rather than creating new content in the first place. So
>>> getting something in place quickly (even if not 100% perfect) is more
>>> important than getting it publisher-ready on the first draft.
>>>
>>> Mark
>>>
>>> On Friday, November 21, 2014 6:37:16 PM UTC-8, Jed Carty wrote:

 I think that we could try making a public tiddlywiki on tiddlyspot and
 make a list of topics people want documentation for the most, then collect
 explanations and examples from people and hopefully get someone who is good
 at technical writing or design to collect everything into a nice tiddler we
 can submit for inclusion on the main page.

 Is there interest in a project like this? It would allow people to make
 small updates or suggestions for the documentation without having to do the
 entire tiddler by themse

Re: [tw] Re: [TW5] Concatenated Widget Parameters

[Jeremy Ruston]

Hi Tobias

>I did some updating and consolidation at the page below. Please, be so
kind to take a quick look, and let me know if anything's off...

> http://tb5.tiddlyspot.com/#Variables%20vs.%20Parameters

Note that "$macroParameter$" and [[$macroParameter$]] are both really a
combination of two bits of syntax: double square brackets and double quotes
to quote a tiddler title that might contain spaces, and the $dollar$
notation for substituting a macro parameter.

You've listed {{transclusion}} under "within macros" which might be
misleading: there's no special handling for {{transclusion}} processing
within macros; the transclusion is just part of the output of the macro and
gets wikified at that point.

Similarly, listing <$widget param="$macroParameter$"/> as a way to pass
widget parameters; it's again a compound syntax, whereas the other examples
in that section are basic variants of the attribute syntax.

You are analysing all the combinations of two layers of syntax where I
think it might be easier to understand if you instead focused on
understanding the way that those two layers work and interact.

The two layers are ordinary wikitext processing and the special processing
that occurs when macros are expanded. All of the complexity in your
examples arises from macro-related syntax interacting with wikitext
processing.

If we teach people that <$widget param="$macroParameter$"/> is an
out-of-the-box syntax then they risk missing that they can do things
like <$widget param="mytiddlertitleprefix-$macroParameter$"/>. The key is
to gain an understanding of the two layers involved.

Best wishes

Jeremy.







On Sat, Nov 22, 2014 at 6:36 PM, Tobias Beer  wrote:

> Hi Jeremy,
>
>
>> I find the table a bit confusing. The underlying situation is much
>> simpler:
>>
>> * Textual substitution for $parameters$ and $(variables)$ only takes
>> place within macro bodies
>> * Transcluding a variable with <> is a basic wikitext construct
>> that can also be used for widget/html element attributes
>> * Transcluding a tiddler text reference with {{title}} is a basic
>> wikitext construct that can also be used for widget/html element attributes
>> * Filters use [] for a variable transclusion, and [{title}] for
>> a tiddler transclusion
>>
>
> Thanks for the consolidated list! I will use it to try fill the above
> table with the expectated behavior and do some testing in...
>
> http://pv5.tiddlyspot.com
>
> Not sure where to place such a consolidated aggregation in tiddlywiki.com.
> Imho, it would be good if it were not just scattered all about different
> module documentations.
>
> I did some updating and consolidation at the page below. Please, be so
> kind to take a quick look, and let me know if anything's off...
>
> http://tb5.tiddlyspot.com/#Variables%20vs.%20Parameters
>
> I turned your excellent overview into an example wiki...
>>>
>>
>> You've been very productive recently! I'd like to link to your new TW5
>> stuff, what's the best base URL to use?
>>
>
> Yes, trying to catch up and using *tb5 *as a central hub for gathering
> tw5 know-how...
>
> http://tb5.tiddlyspot.com
>
> That's the place for me until that perhaps more distant moment where I
> might be doing some more segmented node.js-serving. Although I am doing
> that already, I might eventually split up contents into dedicated
> TiddlySpots to keep the load a bit at bay in tb5.
>
> 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] New Feature Moratorium

[David Gifford]

And 5.1.5 will be released this week, right Jeremy? I am really eager to
have this update. It's got some great stuff in it. Also I am eager because
I have used some of the define newhere bits you  emailed me, but they don't
seem to work in 5.1.4, only in my copy of the prerelease of 5.1.5. This new
version HAS been in the works for a while, so don't keep us in suspense
forever! :-)

Dave

On Sun, Nov 23, 2014 at 7:21 AM, Jeremy Ruston 
wrote:

> Thanks everyone for their contributions. There are a bunch of good
> suggestions in the thread which I'll try to pick up in the hangout on
> Tuesday.
>
> A big topic is clearly how we improve the contribution process for the
> documentation. I have a couple of thoughts:
>
> * We could initiate a TW5 community space on tiddlyspace along the lines
> of tiddlywiki.org - it's a proven way to work. It would be good to try
> out TW5's support for TiddlySpace in a multiuser setting (since it's not
> been done before I think there may be some wrinkles to be ironed out).
> * We should support documentation contributions by people taking a copy of
> tiddlywiki.com onto tiddlyspot and making their edits there. I could
> easily build a batch file that pulls down their changes and applies them to
> the repo, so that I can convert their changes to a pull request (I don't
> think there's any avoiding needing a moderation step for tiddlywiki.com)
> * An alternative workflow for accepting those contributions would be to
> support visual diffing in the import manager
>
> I've also got a couple of clarifications.
>
> > Perhaps there's a way to display a sticky above the github issues.
>
> We don't want to discourage people from suggesting and discussing new
> features, but lets see how it goes and I can add a banner to the "new
> issue" page if needed.
>
> > 4. You may think about a two level plugin list: the top part would list
> the plugins that are officially sanctioned and compatible with the latest
> release. The bottom part could be a growing list of webpages where
> individuals have stored there plugins and goodies they have created for TW
> but that may or may not continue to be compatible.
>
> That's pretty much what we've got:
>
> * Plugins listed in http://tiddlywiki.com/#Plugins are the officially
> maintained and distributed plugins. They will be automatically upgraded
> when using http://tiddlywiki.com/upgrade.html
> * Community plugins are listed in http://tiddlywiki.com/#Resources
>
> Perhaps we should maintain a catalogue of community plugins that is
> separate from the general resources list.
>
> > Will 1.1.5 and the export feature make release before the moratorium
> begins?
>
> Yes, the moratorium would start after 5.1.5's release.
>
> Best wishes
>
> Jeremy
>
>
> On Sat, Nov 22, 2014 at 6:43 PM, 'Mark S.' via TiddlyWiki <
> tiddlywiki@googlegroups.com> wrote:
>
>> Whenever you have an open web page, you end up with spammers trying to
>> create link drops.
>>
>> Probably a real wiki (with authentication) or even just a special thread
>> on this forum would be better. I believe the better wiki systems track
>> history, so changes can be rolled back when something useful has been
>> overwritten.
>>
>> I feel the github process discourages documentation. The problem is that
>> it's the same system of review for documentation as for code. Which means
>> that you may have to wait a week or so before changes get applied, Sure,
>> CODE needs to be thoroughly vetted so that TW doesn't break. But, unlike
>> code, poor documentation is usually better than NO documentation, and it
>> can be peer-reviewed and tweaked as time goes along. It's an odd quirk of
>> human psychology that people tend to like to correct things that are
>> already in place rather than creating new content in the first place. So
>> getting something in place quickly (even if not 100% perfect) is more
>> important than getting it publisher-ready on the first draft.
>>
>> Mark
>>
>> On Friday, November 21, 2014 6:37:16 PM UTC-8, Jed Carty wrote:
>>>
>>> I think that we could try making a public tiddlywiki on tiddlyspot and
>>> make a list of topics people want documentation for the most, then collect
>>> explanations and examples from people and hopefully get someone who is good
>>> at technical writing or design to collect everything into a nice tiddler we
>>> can submit for inclusion on the main page.
>>>
>>> Is there interest in a project like this? It would allow people to make
>>> small updates or suggestions for the documentation without having to do the
>>> entire tiddler by themselves. Using github isn't hard, but this may
>>> encourage more people to help out. That is if multi-user wikis are a viable
>>> solution, if not we would need someone to manage it, which may not be
>>> better than just using github the way it is now.
>>>
>>>
>>>  --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emai

Re: [tw] Re: [TW5] New Feature Moratorium

[Jeremy Ruston]

Thanks everyone for their contributions. There are a bunch of good
suggestions in the thread which I'll try to pick up in the hangout on
Tuesday.

A big topic is clearly how we improve the contribution process for the
documentation. I have a couple of thoughts:

* We could initiate a TW5 community space on tiddlyspace along the lines of
tiddlywiki.org - it's a proven way to work. It would be good to try out
TW5's support for TiddlySpace in a multiuser setting (since it's not been
done before I think there may be some wrinkles to be ironed out).
* We should support documentation contributions by people taking a copy of
tiddlywiki.com onto tiddlyspot and making their edits there. I could easily
build a batch file that pulls down their changes and applies them to the
repo, so that I can convert their changes to a pull request (I don't think
there's any avoiding needing a moderation step for tiddlywiki.com)
* An alternative workflow for accepting those contributions would be to
support visual diffing in the import manager

I've also got a couple of clarifications.

> Perhaps there's a way to display a sticky above the github issues.

We don't want to discourage people from suggesting and discussing new
features, but lets see how it goes and I can add a banner to the "new
issue" page if needed.

> 4. You may think about a two level plugin list: the top part would list
the plugins that are officially sanctioned and compatible with the latest
release. The bottom part could be a growing list of webpages where
individuals have stored there plugins and goodies they have created for TW
but that may or may not continue to be compatible.

That's pretty much what we've got:

* Plugins listed in http://tiddlywiki.com/#Plugins are the officially
maintained and distributed plugins. They will be automatically upgraded
when using http://tiddlywiki.com/upgrade.html
* Community plugins are listed in http://tiddlywiki.com/#Resources

Perhaps we should maintain a catalogue of community plugins that is
separate from the general resources list.

> Will 1.1.5 and the export feature make release before the moratorium
begins?

Yes, the moratorium would start after 5.1.5's release.

Best wishes

Jeremy


On Sat, Nov 22, 2014 at 6:43 PM, 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> Whenever you have an open web page, you end up with spammers trying to
> create link drops.
>
> Probably a real wiki (with authentication) or even just a special thread
> on this forum would be better. I believe the better wiki systems track
> history, so changes can be rolled back when something useful has been
> overwritten.
>
> I feel the github process discourages documentation. The problem is that
> it's the same system of review for documentation as for code. Which means
> that you may have to wait a week or so before changes get applied, Sure,
> CODE needs to be thoroughly vetted so that TW doesn't break. But, unlike
> code, poor documentation is usually better than NO documentation, and it
> can be peer-reviewed and tweaked as time goes along. It's an odd quirk of
> human psychology that people tend to like to correct things that are
> already in place rather than creating new content in the first place. So
> getting something in place quickly (even if not 100% perfect) is more
> important than getting it publisher-ready on the first draft.
>
> Mark
>
> On Friday, November 21, 2014 6:37:16 PM UTC-8, Jed Carty wrote:
>>
>> I think that we could try making a public tiddlywiki on tiddlyspot and
>> make a list of topics people want documentation for the most, then collect
>> explanations and examples from people and hopefully get someone who is good
>> at technical writing or design to collect everything into a nice tiddler we
>> can submit for inclusion on the main page.
>>
>> Is there interest in a project like this? It would allow people to make
>> small updates or suggestions for the documentation without having to do the
>> entire tiddler by themselves. Using github isn't hard, but this may
>> encourage more people to help out. That is if multi-user wikis are a viable
>> solution, if not we would need someone to manage it, which may not be
>> better than just using github the way it is now.
>>
>>
>>  --
> 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 ti

Re: [tw] Re: [TW5] Yet another reference for using TW5.

[Jon]

Hi Jed,

Really useful.

Thanks, Jon.

On Saturday, 22 November 2014 18:03:42 UTC, Jeremy Ruston wrote:
>
> Hi Jed
>
> > I made this so that some of my friends with absolutely no coding 
> experience could use some of the better features of TW5 without having to 
> learn much.
>
> This is pretty spectacular stuff, well done. You've gone into a lot of 
> detail, and the collection of hints is very extensive. You've obviously 
> gained a very good understanding of TiddlyWiki.
>
> I've added a link to the prerelease at http://tiddlywiki.com/prerelease
>
> It's great that you've also submitted an update for tiddlywiki.com, and I 
> hope you'll be able to bring more of this material across too.
>
> Best wishes
>
> Jeremy.
>
>
> On Thu, Nov 20, 2014 at 11:09 PM, Birthe C  > wrote:
>
>> Hi Jed Carty
>>
>> Charming collection. A beginner should be able to do something right away 
>> and find information for more. I really liked it. Have you thought of 
>> adding  tiddlyclip to make it easy for your friends to continue collecting 
>> tips on their own.
>>
>> I would like to hear how your friends get along.
>>
>>
>> Birthe
>>
>> Den torsdag den 20. november 2014 22.16.03 UTC+1 skrev Jed Carty:
>>
>>> I made this so that some of my friends with absolutely no coding 
>>> experience could use some of the better features of TW5 without having to 
>>> learn much. I am hopefully going to continue updating it as I learn new 
>>> things. There isn't really anything here that isn't available in plenty of 
>>> other places, but I figured that since I spent a while putting it together 
>>> and people keep saying that TW needs more documentation I would post it 
>>> here. Also I am pretty sure that I missed listing some references I used 
>>> for this, so if someone notices a place where I used ideas or examples and 
>>> didn't list the source in the Other Places to Look tiddler let me know so I 
>>> can add it.
>>>
>>> I think the only part that isn't explicitly shown elsewhere is the 
>>> settings part of the contacts tiddler. It isn't anything too fancy, but it 
>>> does demonstrate a nice use of template tiddlers. I will hopefully actually 
>>> write out tutorials for how each of the parts works at some point, but that 
>>> may be a while.
>>>
>>> Enjoy.
>>>
>>> http://inmysocks.tiddlyspot.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+...@googlegroups.com .
>> To post to this group, send email to tiddl...@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...@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] [TW5] in a macro: achieve if / else

[Tobias Beer]

Hi everyone,

I'd like to be able to follow optional routes in a macro, for example...

   - *if *it's value is defined take *<>*
   - *else* take *$parameter$*

I can certainly play with options to achieve this and
once I figured something out myself, I will post here.

Regardless, I'd love to know the possible ways
you know or can think of in which to tackle this problem, so...

If you've have something new in in mind,
start your reply with a line that summarizes your concept:

"CONCEPT: use foo bar..."

That way it's easier to spot possible solutions.

Could even be an idea for a new widget that doesn't even exist yet, e.g. 
IfElseWidget...
sketch out the design for it, someone might just jump at its implementation.

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: ListField seems expect distinct values in the list

[Jeremy Ruston]

Hi Olivier, Richard

The subtleties of the action of the list filter are as Richard has inferred:

If it is negated, it acts as a filter, removing any of the currently
selected titles that are present in the list field.

If it is not negated, it acts as a selector, replacing the currently
selected list with the content of the list field.

The filter operators include both filters (like "is") and selectors (like
"all").

> Why is there a way to AND the tag-filter with NOT the list but there
isn't a way to AND it with the list.

You can do it the other way around:

[list[]tag[mytag]]

But it is undoubtedly an oversight.

> Also, I don't really understand why it would be useful to replace the
whole list as part of a filter expression.

One would usually have the list filter operator as the first operator in a
run, using it to select the tiddlers to be filtered by subsequent operators.

Best wishes

Jeremy.




On Sun, Nov 23, 2014 at 11:13 AM, Richard Smith <
richardwilliamsmit...@gmail.com> wrote:

> I read that - but it doesn't make sense when you look at the behaviour of
> the negated example.
>
> Why is there a way to AND the tag-filter with NOT the list but there isn't
> a way to AND it with the list.
>
> Also, I don't really understand why it would be useful to replace the
> whole list as part of a filter expression.
>
> Also, I wasn't trying to solve a particular problem, but to contribute to
> a discussion, in response to Olivier's post, which would help me to better
> understand the filter syntax.
>
> Also, the way you ask "why do you expect that when..." is quite rude and
> I've noticed you doing this to people repeatedly. I'd rather you just
> didn't answer, if you're going to talk to me like I'm an idiot, to be
> honest.
>
> Regards,
> Richard
>
> --
> 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: Table of Contents inside a tiddler

[Jeremy Ruston]

Hi Tobias

>
> So, it would be nice, if tw5 would by default render tiddlers
> *$:/tags/Stylesheet* in a monospaced block rather than wikify the
> contents... or if one could easily make it so without modifying the
> ViewTemplate.
>

I do agree that the current stylesheet rendering is unhelpful at the
moment. The same problem also occurs with HTML templates such as
"$:/core/templates/static.template.html".

There would be two parts to addressing it:

* Hide the body of tiddlers tagged "$:/tags/Stylesheet". This would need to
be done in "$:/core/ui/ViewTemplate/body"
* Add a new view template segment that selectively displays the parsed
tiddler content as plain text

The trouble is the first part: we're in danger of embedding a lot of logic
in that "$:/core/ui/ViewTemplate/body" template. I think we need a
mechanism for more flexibly configuring conditions under which the default
body rendering should be hidden.

Note that we could also flip this around, and instead add a new control
panel tab that lists the active stylesheets in a select box, and allows
them to be selected and viewed as a plain text block.

Best wishes

Jeremy


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

[tw] Re: ListField seems expect distinct values in the list

[Richard Smith]

I read that - but it doesn't make sense when you look at the behaviour of 
the negated example.

Why is there a way to AND the tag-filter with NOT the list but there isn't 
a way to AND it with the list.

Also, I don't really understand why it would be useful to replace the whole 
list as part of a filter expression.

Also, I wasn't trying to solve a particular problem, but to contribute to a 
discussion, in response to Olivier's post, which would help me to better 
understand the filter syntax.

Also, the way you ask "why do you expect that when..." is quite rude and 
I've noticed you doing this to people repeatedly. I'd rather you just 
didn't answer, if you're going to talk to me like I'm an idiot, to be 
honest.

Regards,
Richard

-- 
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] External individual tiddlers via iframes?

[Mat]

On Sunday, November 23, 2014 9:55:42 AM UTC+1, Jeremy Ruston wrote:
>
> There are a couple of techniques we can use to do that, and it's 
> definitely on my list.
>

Absolutely super to hear!

As far as I can see, this will revolutionize TW somewhat like the internet 
revolutionazed the PC. The labour of arbitrary and manual copy-pasting 
files between PC's (analogous to how a TW user gets e.g plugins today) 
became instead more a labour of filtering and organizing among potential 
input.

<:-)

-- 
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] Zork-like game, now with an authoring tool (work in progress)

[Jeremy Ruston]

Hi Jed

On Sun, Nov 23, 2014 at 12:08 AM, Jed Carty  wrote:

> Here is an updated version of the zork-like game with the mostly complete
> authoring tool added. Click the button in the upper left to open the
> editing tiddler, everything I have designed so far can be done my filling
> in forms.
>

Terrific. I like the combination lock, not sure if that's new.


> This has actually been much more useful than I expected as far as learning
> what the wiki can do is concerned. I think that it would be possible to
> make a limited version of the wiki (like the reference one I posted here
> http://inmysocks.tiddlyspot.com/) that can be made and edited using only
> fillable forms. This would probably not be significantly easier to use than
> the normal wiki, but there seems to be less of a psychological barrier to
> filling out premade forms than using something like the editing options of
> the wiki. Maybe not, but it was one thing I thought of while making this.
>

Great. Sounds like an edition of TiddlyWiki for people making interactive
fiction games. That's the sort of thing I'd love to add to the stable on
tiddlywiki.com.


> First, I can't find a way to set one field based on another just based on
> the first field changing. The example for the game here is location based
> event triggers, so when the 'location' field of an item is set to a
> specific value it sets the text of a different tiddler to 'active'.
>
A similar problem is that I can't find a way to set two separate fields
> (same name, different tiddlers) to the same value using a single select
> widget. To do either of these things may require javascript, but I thought
> I would ask if anyone here.
>

Yes, both of those would be tricky at the moment. One thing that might help
is adding action widget support to the select widget. For example:

<$select tiddler="item" field="location">
<$action-setfield $tiddler="anothertiddler" $field="text"
$value={{item!!location}}/>
etc.


> Second, I don't think it is possible, but I would like to have a
> dynamically generated macro. The reset button in the game sets a bunch of
> fields back to their initial value, I would like to be able to generate
> this macro so that it is possible to define the initial location for an
> item and then when the reset button is pressed it sets the 'location' field
> of the item to that value. If this could be done so that it iterates
> through all the tiddlers tagged 'item' and then sets the 'location' field
> equal to the 'inital_location' field without having to explicitly write out
> each one that would be awesome. I haven't found a way to do this yet.
>

I think what's needed here is the ability to wrap action widgets inside the
list widget. Then you could generate one action widget for each of your
tiddlers tagged "item".


> Third I have no idea how I would go about dynamically generating the map
> based on arbitrary topology. I don't think it is possible without something
> like the taskgraph plugin (here http://wkpr.de/hosting/tmp/tw5/taskgraph/
> it looks awesome). I may look into that later.
>

That would definitely be cool.

Great stuff, Jed, thanks for sharing,

Best wishes

Jeremy

Because of these problems, and because I didn't have this in mind when I
> made it, the original version I posted doesn't have the same structure as
> the authoring tool uses. If I can find ways around the above problems I
> will update it at some point.
>
> There is very minimal documentation in the tiddler called Documentation,
> and the tiddler called Plan has what I hope to do in the future. There are
> also options for location based triggers that don't actually do anything
> because of the above problems. Hopefully I will get around to documenting
> what I did for this because I think that it could have application for
> things that are more useful than text-based games.
>
> Enjoy.
> http://zorklike.tiddlyspot.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.
>



-- 
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] Yet another documentation idea

[Jeremy Ruston]

Hi Mat

I think there's a much easier way that we could accept contributions to the
documentation.

Individuals could clone tiddlywiki.com to tiddlyspot (which is just a
couple of clicks), and make their edits there.

When they are ready to submit their changes they would notify a core
developer who could run a diff of their changes for review, and accept or
reject them individually. To do that we'd just need to add visual diffing
to the import mechanism, which is something that I'd like to do anyway.

They could also send a link to the discussion group for comment.

I don't think we can allow random contributions to be published on
tiddlywiki.com without review.

> Export that single(!) tiddler to have it sent as a .tid file to tw.com.

That's the trouble. What does it mean to send a .tid file to tw.com? Don't
forget that tiddlywiki.com is just a bunch of static web pages, there's no
application logic to handle uploads.

> new visitors can read this hopefully improved draft and give it likes!

Similarly, we've got no mechanism for recording likes.

Best wishes

Jeremy.







On Sun, Nov 23, 2014 at 1:24 AM, Mat  wrote:

> In another thread, apropos the need for documentation,
>
> pmario wrote:
>
>>  - With 5.1.5. it will be possible to export tiddlers in different
>> formats.
>> - So it's possible to edit content with TW. - export it - and send it
>> to a developer (if jeremy is ok with this workflow)
>>
>
> This is a very interesting idea from pmario. Imagine if it was possible
> for visitors to edit the documentation *directly on tw.com
> * (...actually a local temporary copy on the screen).
> Export that single(!) tiddler to have it sent as a .tid file to tw.com.
>
> Then what? Well, I can imagine many options, The tid should probably be
> sandboxed but it could be viewed from the original tiddler somehow (iframe
> in slider, or whatever).
>
> ...new visitors can read this hopefully improved *draft* and give it
> likes! When the number of likes reaches a threshold - voila, the original
> tiddler gets auto-replaced with the proposed one!!! Alternatively, a
> voluntary proofreader gets pinged at threshold for a final approval before
> it is published.
>
> I'd think much documentation does not require deep technical competence
> only familiarity with tw, Proofreaders could even get pinged only for their
> favorite subjects if the tiddler is tagged.
>
> There could also be dislikes. Negative threshold reached - poof!
>
> The purpose is to have documentation as an ongoing activity spread out on
> many people where even small, small contributions on the whim add up to
> something meaningful. "... like tiddlers composing a full wiki" (ah, even
> poetry)
>
>
> <:-)
>
> --
> 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] Yet another reference for using TW5.

[Tobias Beer]

Loads of interesting stuff to ponder, I can feel the journey. :)

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] External individual tiddlers via iframes?

[Jeremy Ruston]

iframes are cool and fun but the way that they embed content is limited.
Visually, iframed content appears as part of the parent document. However,
internally, it's wrapped up in an impermeable protective membrane that
makes it impossible for the host page to actually access the iframed
content.

What we really need is "remote transclusion", where TiddlyWiki dynamically
loads remote content as tiddlers. That means that the remotely loaded
content will be available to list widgets and so on. All we need is a CORS
enabled server to make this work.

There are a couple of techniques we can use to do that, and it's definitely
on my list.

Best wishes

Jeremy.



On Sun, Nov 23, 2014 at 7:10 AM, Alex Hough  wrote:

> Tobias,
>
> Mind boggling - there so much to see in the way you've done this
>
> Alex
>
> On 23 November 2014 at 04:30, David Gifford  wrote:
>
>> Is there a way to create an iframe that grabs only the title and text
>> fields of a tiddler?
>>
>>
>>
>> On Saturday, November 22, 2014 10:13:07 PM UTC-6, Tobias Beer wrote:
>>>
>>> I don't even know if iframes can nest, so maybe I'll hit a wall right
 away.

>>>
>>> Well, just try to iframe your iframing content and see what that
>>> brings...
>>>
>>> At some point, the browser will need to stop recusrively embed things,
>>> or 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.
>>
>
>  --
> 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.