[tw] Re: [TW5] Taskgraph BETA is out on github and nightly demo is available
If I move the whole graph and then move a node the graph is centred again. So the program works against the user :/ IMO there is no notification needed for: positions stored and graph centred message. https://github.com/felixhayashi/tw-taskgraph/issues/2 -- 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
Hi, What about this? $list filter=[[french]listed[courses]] $list filter=[[A2]listed[levels]field:titlecurrentTiddler] /$list /$list The only problem I see with nested list widgets like this is a potential performance problem. If the first widget gets 100+ results, then the second widget is executed 100+ times, which means retrieving the same exact list 100+ times. And its getting worth when we add more layers. But so far it works. Alberto -- 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
Am Samstag, 22. November 2014 02:01:16 UTC+1 schrieb Tobias Beer: Hi Stephan, Works pretty well, I'd say. Lesson learned: Why use one list if you can nest two? ^_^ The problem with this is: The complexity is O(n^2). The inner list needs to be executed for each member of the outer list again. I think with proper set operators and/or variables which could hold sets, stuff like this could be enhanced. !-- fictious example -- $set name=outer filter=[[french]listed[courses]] $set name=inner filter=[[A2]listed[levels] $list filter=[allouter] [allinner]/ /$set /$set -- 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] Hopefully NOT for the next 25 years!
Dear Richard, I think you are onto something here with tiered learning. Your observation about TiddlyWiki being used by people for personal and valuable information is a valuable one. There is a lot of emotion bound up in ones personal notes, and TiddlyWiki is the vehicle for connecting and grouping personal insights. One of TiddlyWiki's many joys is the way it gently pulls you into wanting to learn more about it. Thinking back to my first encounter I think it was editing a tiddler TiddlyWiki.com and making a link. It's the experience of using which got me hooked. Before long I wanted to change the colours - I then encountered the warmth of the community - some of which I now recognise as being part of many open source projects. It was my introduction to open source culture and looking back it has had a huge impact on the way I think about many things. Everything should be open source, everything should be run like TiddlyWiki: my car, house, kids school, local governant. Måns made an observation that tiddlng can be a therapeutic activity. I must not be the only one not totally focused on producing a set of notes for a groundbreaking use case (thanks to TiddlyWiki I now use words like ’use case') -- the activity of tending to my TiddlyWiki is to enter a mental zone where problems can be solved, people are diverse, interesting and polite. The diversity is especially interesting to me, and as an English person subject to a public discourse where anti-European sentiment is all pervasive, it's wonderful to find myself communicating with fellow Europeans. It's refreshing - so much of online culture and popular culture in general comes from the USA. TiddlyWiki culture has a certain feal about it. And it it TiddlyWiki worked 'too well' - nobody would have any problems and the side effect of an emerging culture would simply not occur. Back to tiered leaning... TiddlyWiki.com could host many TiddlyWikis, the one which new people see could be minimal. The user could simply edit a tiddler the download it. The simplicity of a new fresh TiddlyWiki on one URL - minimal beauty there to see and experience. A 'blank sheet of paper' ready for ideas --- so enticing a premise. (In the past if I had a new idea I'd go through the ritual of buying a new notebook, a new pen or something - now I get a new TiddlyWiki) After editing, and downloading, and getting comfortable with tagging, I think the next step is using a tag to change the appearance, using the style sheet tag. I though Stephan did something rather cool in an answer to a question. Rather than giving the answer he gave an example and encouragement to use it on TiddlyWiki.com. I thought that this was a breakthough - it reinforces the idea that once in the browser TiddlyWiki is yours and yours only - there is no server connection! And 'THERE IS NO SERVER CONNECTION' is quite a big thing to deal with... I think it takes a while for the penny to drop. It opend up a huge number of possibilities - being told that TiddlyWiki can be emailed, stored on a data peg or put in a drop box all follow on from this astounding fact. I'd emphasise that this is really a big thing for people I am introducing to tiddlywiki to understand. Even technical people don't see the benefits - rather they thing because its got no server then it's a toy for those dabbling in development. The latest step for me has been towards GitHub. I can see how beneficial it is. Again this is a big step, and it along wth TiddlyWiki offers more insight into coding culture - a culture which non coders can derive benefits. For example, academics are now using GitHub for colaboration on papers. GitHUb has jumped the gap. Having a TiddlyWiki with all the documentation available from GitHub could be something to concider. This would introduce the idea that documentation is part of the TiddlyWiki experience. If you want to delve deeper into TiddlyWiki the notion of co-creating knowledge and documenting it is part of being part of the community -- if you want. It's also an entry into 'how knowlege should be created' in more general terms. A learning practitioner should be engaged in reflective practice and sharing knowledge in a community - this is what academic publishing is all about, or should be about: it's lack or open source ethos is only just beginning to be adressed - most knowledge is behind the so called academic firewall. Einought for now--'real life' calls... Alex On Saturday, 22 November 2014, jb dallas...@gmail.com wrote: In terms of easing adoption for new users, one possibility would be to consider a loose notion of tiered-learning. There are a number of basic concepts needed to use TW as a personal wiki and note-store. The next tier might be use of tags, lists, macros. The next tier might be templates and interface customisation. +1 On Saturday, November 22, 2014 9:11:43 AM UTC+8, Richard Smith wrote: Thanks Alex, That's really interesting. Widening the bandwidth carries
[tw] Re: [TW5] Taskgraph BETA is out on github and nightly demo is available
If I move the whole graph and then move a node the graph is centred again. So the program works against the user :/ IMO there is no notification needed for: positions stored and graph centred message. https://github.com/felixhayashi/tw-taskgraph/issues/2 Yes I have to change that. The idea was if you drag a node in the widget mode far to the outside, then it tries to fit in the viewport again. But this is not intuitive and I will remove that behaviour. -- 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] Taskgraph BETA is out on github and nightly demo is available
Hi Felix Congratulations, great to see the plugin out, and it looks good. I'm sorry not to have responded yet to the coding issues you raised; I'll be on those over the weekend. Best wishes Jeremy. On Sat, Nov 22, 2014 at 9:18 AM, Felix Küppers felixkuepp...@hotmail.de wrote: If I move the whole graph and then move a node the graph is centred again. So the program works against the user :/ IMO there is no notification needed for: positions stored and graph centred message. https://github.com/felixhayashi/tw-taskgraph/issues/2 Yes I have to change that. The idea was if you drag a node in the widget mode far to the outside, then it tries to fit in the viewport again. But this is not intuitive and I will remove that behaviour. -- 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: Table of Contents inside a tiddler
Thanks Stephen, https://dl.dropboxusercontent.com/u/6651245/My%20ToC.html I'll play around with that a little. -- 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] Taskgraph BETA is out on github and nightly demo is available
Hello Jeremy, Congratulations, great to see the plugin out, and it looks good. :) yay! I also used your buttons in the actions menu as the meanings are the same (helps the user to quickly grasp the meaning). I think the symbolic semantics should be consistent and only if no icon exist to convey a meaning or if meanings differ, one should create a new one. Hope that is ok with you. I'm sorry not to have responded yet to the coding issues you raised; I'll be on those over the weekend. I absolutely respect your choice on how to spend your limited time. I just would be very glad to have the one issue with inverted tags solved before 5.1.5 release. 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: Table of Contents inside a tiddler
Did you tried to make the toc smaller and float left ? Also it's better if you use triple ticks to enclose the code on the explanation. 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
Servus Mario, Both your issues are fixed now: https://github.com/felixhayashi/tw-taskgraph/issues/2 https://github.com/felixhayashi/tw-taskgraph/issues/3 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
On Saturday, November 22, 2014 12:27:13 PM UTC+1, Felix Küppers wrote: Servus Mario, Both your issues are fixed now: https://github.com/felixhayashi/tw-taskgraph/issues/2 https://github.com/felixhayashi/tw-taskgraph/issues/2 https://github.com/felixhayashi/tw-taskgraph/issues/3 Hi Felix, Thanks a lot! ... This will be an extremely useful plugin for me and probably the number one dependency :) -mario -- 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] problem with $select widget and computed option values
I am trying to use the $select widget to select one of the available widgets and display static contents from tiddlywiki.com in an iframe. However, the select widget somehow choses to persist the computational basis for the option value in the state tiddler rather than the actual value being displayed. http://tb5.tiddlyspot.com/#Widget%20Browser What to do? Here's a dump of the current situation for reference... select a widget:action-navigateaction-sendmessageActionWidgets browsebuttoncheckboxcountdropzoneeditedit-bitmap edit-textencryptfieldmanglerfieldsimage importvariableskeyboardlinklinkcatcherlistmacrocall navigatorpasswordradiorevealscrollableselectset setvariabletexttiddlertranscludeview documentation on TiddlyWiki.com... iframe src=http://tiddlywiki.com/static/ActionNavigateWidget.html; style=height:600px; scrolling=yes/ Componentsdata$:/data/core/widgets http://tb5.tiddlyspot.com/#%24%3A%2Fdata%2Fcore%2FwidgetsstateThis is the problem $:/temp/widget-browser http://tb5.tiddlyspot.com/#%24%3A%2Ftemp%2Fwidget-browser: $view tiddler=$:/data/core/widgets index=action-navigate format=text/ How to only persist the value of the select box, not the code used to compute it?!?sourceWidget Browser http://tb5.tiddlyspot.com/#Widget%20Browser: \define getValue(data,index) $view tiddler=$(data)$ index=$(currentTiddler)$ format=text/ select a widget: $set name=data value=$:/data/core/widgets $select tiddler=$:/temp/widget-browser default=action-navigate $list filter='[dataindexes[]sort[title]]' option value=getValue currentTiddler /option /$list /$select /$set documentation on ~TiddlyWiki.com... $macrocall $name=static tiddler={{$:/temp/widget-browser}} height=600px scrolling=yes/ br !!Components ;data :[[$:/data/core/widgets]] ;state :@@color:red; This is the problem source [[$:/temp/widget-browser]]How to only persist the value of the select box, not the code used to compute it?!?@@ ;source :source Widget Browser 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] - VisualEditor needed
Hello Sylvain, El viernes, 21 de noviembre de 2014 00:28:25 UTC+1, Sylvain Naudin escribió: https://lh5.googleusercontent.com/-p_QhJYlednQ/VG54mSUNb2I/aIU/JKGbgwARftw/s1600/S%C3%A9lection_003.png https://lh4.googleusercontent.com/-NAoFOo2NZiU/VG53erP3uCI/aIM/RIoydOHLuQc/s1600/S%C3%A9lection_002.png Hi, Personally, I've adopt *KeyboardSnippets* from Danielo (thanks for this plugins !) : http://braintest.tiddlyspot.com/#keyboard-snippets I've play a little to add visual help reminder like this illustration (see img file) My weblog engine, Dotclear, use wiki syntax too. It have a wikibar to edit wiki text. Since I use KeyboardSnippets, I wondering if it will be to difficult to have a similar wikibar. What do you think Danielo if you read this post ? I opened a Github issue: https://github.com/danielo515/extendTextWidget/issues/3 -- 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
The only problem I see with nested list widgets like this is a potential performance problem. If the first widget gets 100+ results, then the second widget is executed 100+ times, which means retrieving the same exact list 100+ times. And its getting worth when we add more layers. I'm inclinded to put that in the speculative box for now. Meaning: it would need to be tested if this kind of usecase really does yield performance issues. I don't really think it would because the actual rendering is minimal, unless you have hundreds of results, too. 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
Hi Stephan, !-- fictious example -- $set name=outer filter=[[french]listed[courses]] $set name=inner filter=[[A2]listed[levels] $list filter=[allouter] [allinner]/ /$set /$set While that looks nice, it seems superfluous, as the core would have to be able to process the filter without those variables as well. 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] problem with $select widget and computed option values
Trying to turn the WikiLinks to each widget type into links pointing to the static tiddlers at tiddlywiki.com appears to yield similar problems. http://tb5.tiddlyspot.com/#Iterate%20DataTiddler%20Indexes 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] Preview of new export button
Hi Jeremy, not sure if this was asked before, but could you name the exported tiddler according to the tiddlersname (minus slashes and all these symbols that would cause conflicts with the os pathname). 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
Sure the variables are superfluouse here, with the operator. But here: !-- fictious example -- $set name=inner filter=[[A2]listed[levels] $list filter=[[french]listed[courses]] $list filter=[allinnerfield:titlecurrentTiddler] /$list /$list /$set I think it's useful as the inner loop need not go over all 1000+ tiddlers you have but already has a prefiltered list of th 100 A2-tiddlers. Additionally: I think these variables are on Jeremy's list. -- 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: Table of Contents inside a tiddler
Did you tried to make the toc smaller and float left ? http://tidtoc.tiddlyspot.com/#GettingStarted ;) 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
Hello Félix. I find too complicated to link two tiddlers. It requires a lot of scrolling on my tablet and my phone. It is even uncomfortable to me while on laptop. Maybe you can consider including some kind of plugin API on your plugin. Roma has included a very cool mechanism in his GSD5 plugin. That way I can customize the plugin without overriding any shadow tiddler. For example I may prefer to link a tiddler to another tiddler from a drop down menu on the first tiddler. Others may want different ways. Then all I have to do is to create a tiddler with my drop down list and tag it accordingly to which area of the ui I want to display it. 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: Table of Contents inside a tiddler
Very nice! I have to check it on my desktop computer to give you an opinion, but I like how it looks on my mobile too. Finally we gave a solution to all those people asking for a TOC. 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] Preview of new export button
I think is not possible because browser limitations. Maybe I'm wrong and it is possible. -- 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: Inside TiddlyWiki Jump Start Challenge
So happy to hear this Eric. I am not in a position to do much financially but do plan to do some. So instead, I have been sharing that link like crazy, I hope it helps! On Friday, November 21, 2014 7:08:21 PM UTC-7, Eric Shulman wrote: Wow! This is VERY exciting! The fundraiser for Inside TidlyWiki: The Missing Manual is off to a great start: after just 5 days of a 60 day campaign, it has already been viewed by people in over 33 countries, and the TiddlyWiki Community has so far raised $1,290 (17.2% toward the goal!) This includes generous contributions of $500 each from the first two official Partners of Inside TiddlyWiki -- ocalTW and HansWobbe -- as well as contributions from several new Friends of Inside TiddlyWiki. Based on this initial indication, it looks certain that the Inside TiddlyWiki campaign is going to be a huge success, and I'm currently planning on beginning actual work on the book in January or February, 2015, once the fundraising has been completed. However, with Indiegogo's Flexible Funding model, although contributions made by credit card are held until after the campaign ends on January 15th, contributions made through PayPal are transferred to me as soon as they are processed. This means that there is a possibility that I could begin work as early as the beginning of December rather than waiting until January/February! If we can raise just $2500 (33% of the goal) in Indiegogo contributions **paid through PayPal by the end of November** (10 days from now), then I can start work on writing Inside TiddlyWiki as soon as those funds are available. So, make your contribution (via PayPal) NOW, and we can Jump Start this project into high gear! https://www.indiegogo.com/projects/inside-tiddlywiki-the-missing-manual/x/8816263 -e Eric Shulman TiddlyWiki Classic Lead Developer TiddlyTools / ELS Design Studios Inside TiddlyWiki: The Missing Manual -- 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
Wow this is really cool! On Friday, November 21, 2014 12:24:57 PM UTC-6, Felix Küppers wrote: Hi folks, after almost a month of intensive coding the code is online and the plugins are bundled. The demo url is now: http://wkpr.de/hosting/tmp/tw5/taskgraph/ (demo updates on every commit; the demo is also found on github) I am sorry to tell you that no real documentation exists at the moment (and no screenshots). Any help is appreciated. Please have a look at the *roadmap tiddler* to get an idea of what tw-taskgraph is capable of (especially 0.5.0 brings many improvements). I also try to make a video of 0.5.0 You can also go to github and checkout the code (for example have a look at adapter.js which is used as layer between taskgraph and tw; or taskgraph_graph.js which is the widget used to draw and manage the graph). Some issues that I could not solve yet: https://github.com/felixhayashi/tw-taskgraph/issues/1 https://github.com/felixhayashi/tw-vis/issues/2 https://github.com/Jermolene/TiddlyWiki5/issues/1109 Have fun! 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: Table of Contents inside a tiddler
Very nice! I have to check it on my desktop computer to give you an opinion, but I like how it looks on my mobile too. Finally we gave a solution to all those people asking for a TOC. Actually, I think I'll be satisfied once I managed (to hire a crew to help me) to port SectionLinkPlugin http://www.tiddlytools.com/#SectionLinksPlugin to tw5. ;) Despite any dreaded performance concerns, there are just too many highly useful usecases involved with sections... - section-toc for tiddler *foo*, providing clickable links! (even back to the toc from the heading) - *$link* to section *foo*, from tiddler *bar*, too - *$list* section *foo* of tiddlers tagged *bar* - (edit section *foo*) 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] Preview of new export button
Hi Danielo, I think is not possible because browser limitations. Maybe I'm wrong and it is possible. Hmm, it should be possible because at one point the download is named tiddler.tid. https: //github.com/Jermolene/TiddlyWiki5/blob/master/core/wiki/macros/export.tid reads the filename from a field called filename... 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] Preview of new export button
https:// github.com/Jermolene/TiddlyWiki5/blob/master/core/wiki/macros/export.tid Ok I guess I misinterpreted the file but at some point it is decided how to name the download -- 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: Table of Contents inside a tiddler
I was JUST going to say that myself, that it is handy in and of itself, but what is really needed is the ability to create links to the sections within the toc. On Saturday, November 22, 2014 7:50:35 AM UTC-6, Tobias Beer wrote: Very nice! I have to check it on my desktop computer to give you an opinion, but I like how it looks on my mobile too. Finally we gave a solution to all those people asking for a TOC. Actually, I think I'll be satisfied once I managed (to hire a crew to help me) to port SectionLinkPlugin http://www.tiddlytools.com/#SectionLinksPlugin to tw5. ;) Despite any dreaded performance concerns, there are just too many highly useful usecases involved with sections... - section-toc for tiddler *foo*, providing clickable links! (even back to the toc from the heading) - *$link* to section *foo*, from tiddler *bar*, too - *$list* section *foo* of tiddlers tagged *bar* - (edit section *foo*) 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
Now I want the list of the teaching resources for her, but the following and similar filters doesn't work: $list filter=[[french]listed[courses]] +[[A2]listed[levels]]/ The action of the plus sign is probably not what you are expecting. Ordinarily, each run of a filter expression starts out with the source tiddlers being those prevailing where the filter is being evaluated, which is normally equivalent to [all[tiddlers]]. The plus sign causes the source tiddlers for the following run of filter operators to be the aggregate of all the results so far. So, in this case, including the plus sign makes the filter equivalent to: [[french]listed[courses][A2]listed[levels]] Isn't that the old regexp syntax that has been removed in 5.0.17? Indeed. I didn't know it was supposedly removed, its why I use it, and it still works in 5.1.5-prerelease. It turns that I forgot to remove the regexp support before the end of the beta (I did add the new regexp filter operator which is intended to replace it). I think now we'll have to keep the existing support. I think with proper set operators and/or variables which could hold sets, stuff like this could be enhanced. We're halfway there in 5.1.5. Variables can now contain lists, but there's not yet a syntax to retrieve a list from a variable and use it within a filter. Best wishes Jeremy On Sat, Nov 22, 2014 at 8:46 AM, Stephan Hradek stephan.hra...@gmail.com wrote: Am Samstag, 22. November 2014 02:01:16 UTC+1 schrieb Tobias Beer: Hi Stephan, Works pretty well, I'd say. Lesson learned: Why use one list if you can nest two? ^_^ The problem with this is: The complexity is O(n^2). The inner list needs to be executed for each member of the outer list again. I think with proper set operators and/or variables which could hold sets, stuff like this could be enhanced. !-- fictious example -- $set name=outer filter=[[french]listed[courses]] $set name=inner filter=[[A2]listed[levels] $list filter=[allouter] [allinner]/ /$set /$set -- 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] Preview of new export button
Hi Felix not sure if this was asked before, but could you name the exported tiddler according to the tiddlersname (minus slashes and all these symbols that would cause conflicts with the os pathname). Good idea, I've made the necessary changes here: https://github.com/Jermolene/TiddlyWiki5/commit/e6043b07b90e5da9dac07634326cda9498fb106d Note that some browsers ignore the filename that TiddlyWiki specifies, and give the downloaded file a random name. It works on Chrome and Firefox but not Safari in my tests. I've also uploaded a new prerelease: http://tiddlywiki.com/prerelease Best wishes Jeremy. On Sat, Nov 22, 2014 at 1:55 PM, Felix Küppers felixkuepp...@hotmail.de wrote: https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ wiki/macros/export.tid Ok I guess I misinterpreted the file but at some point it is decided how to name the download -- 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: Table of Contents inside a tiddler
Hello David, That's pretty easy with the use of links and anchors. I have plans to update my keyboard plugin so it will be very easy to create links to navigate to. 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] Direct links to a set of tiddlers with a specific field-value mapping
I've been racking my brain on this one, and I need a little help with this. I'm using todo.txt to manage my To-Do list, and I came up with an idea to attach notes to my todo list. I'm thinking of using a tag in my todo.txt list to link to a set of tiddlers that have related notes. The issue I'm having is that I can easily set a field and value (for example a uuid field with some UUID as a value, which I reference in my todo.txt file). However, I'd live to have a permalink that woul return all the tiddlers that have that have a specific uuid field value. I may be missing something completely, but is there a way to do this? Thanks, Mark Crichton -- 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
I was JUST going to say that myself, that it is handy in and of itself, but what is really needed is the ability to create links to the sections within the toc. That's pretty easy with the use of links and anchors. I have plans to update my keyboard plugin so it will be very easy to create links to navigate to. I think making the internal TOC entries link to their corresponding heading may actually be quite tricky. Using links and anchors will only work for tiddlers that are only displayed once. Transclusion or use of sidebars could cause multiple headings to appear with the same anchor name. Despite any dreaded performance concerns, there are just too many highly useful usecases involved with sections... section-toc for tiddler foo, providing clickable links! (even back to the toc from the heading) $link to section foo, from tiddler bar, too $list section foo of tiddlers tagged bar (edit section foo) That implies making sections behave exactly like tiddlers. That's problematic because it means that all the behaviours we've built for using and manipulating tiddlers need to be re-engineered to work with sections. In some cases that's extremely tricky. For example, how would you make a location hash link to a section (eg http://example.com/#my-section-12)? There's no syntax within the location hash to identify the string as being a section name and not a tiddler title. Another example, to use the $list widget to list all sections of tiddlers tagged bar would require us to be able to process section names within filters. That implies that sections would need unique IDs - once again, making them meet the definition of a tiddler. Basically, TiddlyWiki is a mechanism for manipulating tiddlers. Everything about it is predicated on the idea of a tiddler as the smallest unit of content. Your requirements describe something else: a mechanism for manipulating sections of monolithic hierarchical documents. I understand why these requests are framed in terms of implementing sections but I'd really like more insight into the underlying needs. Is the desire for tiddlers with long, hierarchically structured content because they are easier to edit as a single run of text? Or easier to import? Or is it because the single tiddler is easier to read on screen than a sequence of tiddlers? Best wishes Jeremy. On Sat, Nov 22, 2014 at 2:01 PM, David Gifford dgiff...@crcna.org wrote: I was JUST going to say that myself, that it is handy in and of itself, but what is really needed is the ability to create links to the sections within the toc. On Saturday, November 22, 2014 7:50:35 AM UTC-6, Tobias Beer wrote: Very nice! I have to check it on my desktop computer to give you an opinion, but I like how it looks on my mobile too. Finally we gave a solution to all those people asking for a TOC. Actually, I think I'll be satisfied once I managed (to hire a crew to help me) to port SectionLinkPlugin http://www.tiddlytools.com/#SectionLinksPlugin to tw5. ;) Despite any dreaded performance concerns, there are just too many highly useful usecases involved with sections... - section-toc for tiddler *foo*, providing clickable links! (even back to the toc from the heading) - *$link* to section *foo*, from tiddler *bar*, too - *$list* section *foo* of tiddlers tagged *bar* - (edit section *foo*) 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] Direct links to a set of tiddlers with a specific field-value mapping
Hi Mark The permaview syntax allows a filter to be used to specify the tiddlers to open in the story: http://tiddlywiki.com/#PermaLinks For example, to link to all tiddlers on tiddlywiki.com that have a caption field: http://tiddlywiki.com/#:[has[caption]] You can also specify before the colon the initial tiddler to navigate to: http://tiddlywiki.com/#Learning:[has[caption]] Best wishes Jeremy. On Sat, Nov 22, 2014 at 2:39 PM, Mark Crichton crich...@gmail.com wrote: I've been racking my brain on this one, and I need a little help with this. I'm using todo.txt to manage my To-Do list, and I came up with an idea to attach notes to my todo list. I'm thinking of using a tag in my todo.txt list to link to a set of tiddlers that have related notes. The issue I'm having is that I can easily set a field and value (for example a uuid field with some UUID as a value, which I reference in my todo.txt file). However, I'd live to have a permalink that woul return all the tiddlers that have that have a specific uuid field value. I may be missing something completely, but is there a way to do this? Thanks, Mark Crichton -- 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
I find too complicated to link two tiddlers. I second that. The command popup at one tiddler should directly provide the ability to select the target or source tiddler of the edge to link to, i.e. filter all tiddlers, click, done. 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] FILTER: [valueA]listed[field1] AND [valueB]listed[field2] ???
Hi Jeremy, Le samedi 22 novembre 2014 15:03:24 UTC+1, Jeremy Ruston a écrit : The action of the plus sign is probably not what you are expecting. Ordinarily, each run of a filter expression starts out with the source tiddlers being those prevailing where the filter is being evaluated, which is normally equivalent to [all[tiddlers]]. The plus sign causes the source tiddlers for the following run of filter operators to be the aggregate of all the results so far. So, in this case, including the plus sign makes the filter equivalent to: [[french]listed[courses][A2]listed[levels]] That was my first move, and then I tried other solutions, including nested lists without finding Stephan's one. It turns that I forgot to remove the regexp support before the end of the beta (I did add the new regexp filter operator which is intended to replace it). I think now we'll have to keep the existing support. It may not be lots of people using the old regexp syntax, since more experienced users like PMario and Evolena were surprised to see it, and less experienced users don't know about it. I think with proper set operators and/or variables which could hold sets, stuff like this could be enhanced. We're halfway there in 5.1.5. Variables can now contain lists, but there's not yet a syntax to retrieve a list from a variable and use it within a filter. I'm looking forward to seeing it implemented (I already tried, but got weird results). Thanks, Alberto -- 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
Hello Felix, I'm playing around with your plugin on my desktop, so expect a couple of posts here making questions and proposals. Regarding linking tiddlers, I saw that you can link tiddlers very easy on the thasgrap editor. Very cool,fast and easy. Why not add that easiness to other feature within the same editor? When I'm editing a graph I want to focus on that graph, so if I add a new node I just expect a popup asking for the name an that's all. But instead of this I have to navigate to a new tiddler and put the name there. Regarding the UI, seems your plugin is totally focalized to a single workflow: having the editor on the sidebar and the tiddlers on the river. My screen is narrow (11) so I prefer to work with your plugin on full screen. Opening the editor plugin is a pain because the problem I explained about adding new nodes. Also the editor looks horrible if you expand the story river. I love your plugin, but this makes the usability very hard to me. I would like to focus on each thing, first editing the map, and then add rich information to the tiddlers. Regards. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] problem with $select widget and computed option values
Hi Tobias The problem is with this line: option value=getValue Transcluded variable attributes like this are not wikified; the attribute gets the raw value of the variable after the textual substitution of parameters and variables. Here's an approach that works around that limitation: \define displayIframe(tiddler) $macrocall $name=static tiddler={{$:/data/core/widgets##$tiddler$}} height=600px scrolling=yes/ \end select a widget: $select tiddler=$:/temp/widget-browser default=action-navigate $list filter='[[$:/data/core/widgets]indexes[]sort[title]]' option value=currentTiddler $text text=currentTiddler/ /option /$list /$select documentation on ~TiddlyWiki.com... $macrocall $name=displayIframe tiddler={{$:/temp/widget-browser}}/ br Best wishes Jeremy On Sat, Nov 22, 2014 at 12:12 PM, Tobias Beer beertob...@gmail.com wrote: Trying to turn the WikiLinks to each widget type into links pointing to the static tiddlers at tiddlywiki.com appears to yield similar problems. http://tb5.tiddlyspot.com/#Iterate%20DataTiddler%20Indexes 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
I find too complicated to link two tiddlers. I second that. The command popup at one tiddler should directly provide the ability to select the target or source tiddler of the edge to link to, i.e. filter all tiddlers, click, done. Best wishes, Tobias. Ah ok now I get what Danielo meant. Yes this should be possible. 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] [TW5] External individual tiddlers via iframes?
An idea with potential use for e.g documentation and much else. (...if it is at all doable) iframes are nothing new, but I just realized it's possible to - almost - make external tiddlers, such as from tw.com, appear to be tiddlers in my own TW: iframe src=http://tiddlywiki.com/static/TiddlyWiki; width=640 height=480/iframe ...or, if the static is omitted, it even works pretty well with an ulr to a live tw thanks to the focusing (i.e scroll down) to the specific tiddler, or the topmost tiddler if many, and the sidebar is squeezed up above it so it's not seen. Eg: iframe src=http://tiddlywiki.com/#TiddlyWiki; width=640 height=480/iframe Note: In HTML 4.01, the width could be defined in pixels or in % of the containing element. In HTML5, the value must be in pixels. (ref. http://www.w3schools.com/tags/att_iframe_width.asp) I notice the text wraps nicely though so there is no horizontal scrollbar, at least for me, so you can exaggerate the width value. Obviously, the shown tiddler/s is not interactive with the surrounding TW - which could actually be used as an advantage: For instance, a site (like) tw.com could iframe and sandbox externally located plugins but still allow edit view for manual copying to ones own tw. People could send a mere link (via email?) with the url of a tw-plugin they've developed or even just found somewhere, and the local site could host a gallery of sandboxed display items. And meta-data could be added locally (..or via the email?) Or documentation tiddlers for that matter. For a site like tw.com there could be a reviewphase where a document is viewable but not yet accepted to the actual site (to have it interact with the local tiddlers) until some criteria is met. Even external meta-data could be appended from yet other urls, i.e yet other people could bring input about the external tiddler. Now, I'm wondering if it is possible to isolate the text/content from such an external tiddler? I presume there's no url but maybe there's something the local tw could do to shave off the surrounding tiddler or to remote-transclude the html element? In this way one can avoid the less pretty double titles that result from the iframing of a tiddler as described above. I figure there should be some advantage that the imported content is not just anything but a tiddler, i.e standardized and in a form we're 100% familiar with. ...alternatively, to create a local tiddler template that does not have a title, or at least doens't show it. I.e so that the iframed tiddler totally fills up an empty tiddler shell. And, who knows, if the remote-transclusion of a specific html-element is possible, then maybe it's possible to evaluate it's content and have it recreated locally. Perhaps a risk with text-box content even if I see value in it. A more innocent, but very valuabe, application would be to do so for the tags. You get the original tags but can edit and add your own to fit the local tw needs. A bit like tiddlyweb, I think. Doable or Pie in the sky? :-) -- 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
Hi Danielo, I'm playing around with your plugin on my desktop, so expect a couple of posts here making questions and proposals. ok, I try to collect them Regarding linking tiddlers, I saw that you can link tiddlers very easy on the thasgrap editor. Very cool,fast and easy. Why not add that easiness to other feature within the same editor? When I'm editing a graph I want to focus on that graph, so if I add a new node I just expect a popup asking for the name an that's all. But instead of this I have to navigate to a new tiddler and put the name there. I thought it would be convenient to open the newly created tiddler in edit mode ready to receive some information. This is how I use the plugin... Otherwise you would have to doubleclick on a tiddler and open it in edit mode after having created it. But maybe your idea is better. Regarding the UI, seems your plugin is totally focalized to a single workflow: having the editor on the sidebar and the tiddlers on the river. My screen is narrow (11) so I prefer to work with your plugin on full screen. Opening the editor plugin is a pain because the problem I explained about adding new nodes. Also the editor looks horrible if you expand the story river. I love your plugin, but this makes the usability very hard to me. I would like to focus on each thing, first editing the map, and then add rich information to the tiddlers. Did I forgot to mention it? Sorry. You just have to set editor=true on a widget to display the editor but the view cannot be changed as it is bound by attribute to a given view. so something like this: $taskgraph mode=graph height=YOUR SIZEpx editor=true view=DANIELOS VIEWNAME/$taskgraph I should also make sure the selectbox doesn't give you the options to change the view as it is simply ignored when a graph is bound to a view.. 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
For every request it would be great if you could file an issue with a small message at github. That way I can organize them -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Taskgraph BETA is out on github and nightly demo is available
I thought it would be convenient to open the newly created tiddler in edit mode ready to receive some information. This is how I use the plugin... Maybe an option? I think the best way is to pass to the widget a parameter like: navigate=false. Did I forgot to mention it? Sorry. You just have to set editor=true on a widget to display the editor but the view cannot be changed as it is bound by attribute to a given view. so something like this: $taskgraph mode=graph height=YOUR SIZEpx editor=true view=DANIELOS VIEWNAME/$taskgraph I should also make sure the selectbox doesn't give you the options to change the view as it is simply ignored when a graph is bound to a view.. I think you forgot to mention that, yes. It's cool, really cool. I think your plugin has a problem with calculating its correct size. If I have the editor on a plugin, and then I expand the view to full screen look what happen: https://lh3.googleusercontent.com/-WQmw1OaVFmg/VHC5AJPS0JI/LmM/VqfKZ68xK1s/s1600/Captura%2Bde%2Bpantalla%2B2014-11-22%2Ba%2Bla%28s%29%2B17.21.56.png Can you see the problem? the graph looks horrible. This is corrected if I edit the tiddler while the river is expanded. Look at the difference: https://lh4.googleusercontent.com/-o7ama_gJO58/VHC5Xg8VQTI/LmU/jM_7oL0vtGM/s1600/Captura%2Bde%2Bpantalla%2B2014-11-22%2Ba%2Bla%28s%29%2B17.26.42.png Sorry for not opening a Github issue for this, but I wanted to show you the pictures. Regards -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [tw5] commenting your wikitext macros?
Hi Mark Some of my macros have become quite complex and difficult to read You can use line breaks to make things a bit easier to read: \define cite(citekeys:) ($list filter=$citekeys$ +[sort[]] +[each[authors]] +[first[]] citeauths $list filter=$citekeys$ +[authors{!!authors}] +[sort[]], $link tiddler=currentTiddler{{!!year}}/$link /$list /$list $list filter=$citekeys$ +[sort[]] +[each[authors]] +[rest[]]; citeauths $list filter=$citekeys$ +[authors{!!authors}] +[sort[]] , $link tiddler=currentTiddler {{!!year}} /$link /$list /$list) \end You can also include comments of the form !-- this is a comment -- The only thing to watch out for is that in a very few situations those line breaks will affect formatting. The line breaks are preserved into the HTML. HTML semantics generally mean that adjacent whitespace is collapsed together, so typically the whitespace generated by the linebreaks is collapsed into adjacent white space. Best wishes Jeremy. On Sat, Nov 22, 2014 at 7:18 AM, Stephan Hradek stephan.hra...@gmail.com wrote: As whitespace helps in commenting but whitespace is meaningfull in wikitext, I would create a seperate tiddler where I reformat and describe the text. So no inline comments in the macro. OTOH - as this is at least double effort - you could try what happens if you insert comments containing linebreaks. like !-- this is a comment --so -- 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
Hola Maybe an option? I think the best way is to pass to the widget a parameter like: navigate=false. Yes an option (but not via attribute, I will create an option tiddler where you have a gui to set options. it will be with ckeckboxes like the dropdown to hide edges) I think you forgot to mention that, yes. It's cool, really cool. Sorry I sometimes forget what I documented/posted and what not... I think your plugin has a problem with calculating its correct size. If I have the editor on a plugin, and then I expand the view to full screen look what happen: https://lh3.googleusercontent.com/-WQmw1OaVFmg/VHC5AJPS0JI/LmM/VqfKZ68xK1s/s1600/Captura%2Bde%2Bpantalla%2B2014-11-22%2Ba%2Bla%28s%29%2B17.21.56.png Can you see the problem? the graph looks horrible. This is corrected if I edit the tiddler while the river is expanded. Look at the difference: https://lh4.googleusercontent.com/-o7ama_gJO58/VHC5Xg8VQTI/LmU/jM_7oL0vtGM/s1600/Captura%2Bde%2Bpantalla%2B2014-11-22%2Ba%2Bla%28s%29%2B17.26.42.png Sorry for not opening a Github issue for this, but I wanted to show you the pictures. I know already. this will be fixed. 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: Table of Contents inside a tiddler
I understand why these requests are framed in terms of implementing sections but I'd really like more insight into the underlying needs. Is the desire for tiddlers with long, hierarchically structured content because they are easier to edit as a single run of text? Or easier to import? Or is it because the single tiddler is easier to read on screen than a sequence of tiddlers? I addressed some of those issues in the post that initiated this chain. Ultimately, in my case, it comes down to being easier to import. Easier to read or easier to edit are secondary considerations. The documents I import and work with in Tiddlywiki can be quite long. Generally I reference them rather than edit them. Generally I must not edit them beyond highlighting a passage. As such, the process of splitting one of these documents into minimal sized tiddlers is laborious and counter-productive since it doesn't create much benefit that I've noticed. The internal Table of Contents gives a quick overview of the document. While being able to jump to a specific section would be useful, I think the simple listing of headers is enough of an improvement for what I do with the tiddlers to be worth the effort. If the jumps can be accomplished easily, then fine. I am no expert but every time I've tried using anchors in the new Tiddlywiki, it has failed spectacularly. The best idea I have on how to accomplish it without anchors would be something like the browser's search function. Select the header, then search through the tiddler until the program comes to the matching string and then move the display so that the found string appears on the string. That is beyond my programming ability and so for the moment, I'm happy with the listing of headers that I have. -- 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: Table of Contents inside a tiddler
Tobias and Danielo, It does look nice but I had one additional thought on this. At the moment, in my version, the background color for the box is hard coded in the CSS. It would be nice if it could automatically use the appropriate color from the selected palette. That seems like it ought to be as simple as knowing the right internal name to use... -- 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: Plugins We Use
Thanks Richard. *Really* nice with reviews - you just made me realize I should get tiddlyclip immediately. And I must check out taglist! My mention of people sharing their plugin lists was more in the context of some kind of automated statistical analysis to identify e.g most popular plugins, clusters of plugins used together, conflicting combinations etc. I think the manual approach is too demanding to get enough info to draw *general* conclusions from. But, hey, my own plugins: My working TW's are still TWC because of exactly the plugins. For instance, I have a zillion forEachTiddler's with very specific setups and thinking about the filters I need to replace these... I'm using the Ostrich strategy so far. In TW5 I mostly test things so far, for instance I converted my main notebook to TW5 and I can see it'll be great once I master TW5. BUT, looking at my TWC's I can tell you which plugins that bring functionality except the already mentioned forEachTiddlerPlugin: TiddlySnip by Zaq Imtiaz - I'm strating with this because of your TiddlyClip mention. In the days of TiddlySnip, I found that very valuable too. TagglyTaggingPlugin by Simon Baird - this coudl probably easily be replaced with a filter in TW5 but Taggly is a neat thing to put in the tiddlertemplate to get various views on tiddlers tagged with the current tiddler and similar. NestedSlidersPlugin - by Eric. It replaced and outperformed the core slider macro (not least syntactically). I'm very fond of sliders, particularly if nestable, because they let you portion out just what the reader wants at that moment. No skipping around on the page with new tiddlers and scrolling etc which distracts the mind from what you were doing. For pure text it also let's you write to different kinds of readers - thos who want/can the shallow information AND those who want elaborations. If I were president I'd make a law forcing every text written from now on to use NestedSlidersPlugin. (Of course I read Dostojevskis Crime and Punishment. Took me about an hour. ;-) BTW, there is the less known http://tw.lewcid.org/#AnnotationsPlugin that has similarities but is more snappy (but much more limited). SaveClose tiddler and CancelClose tiddler. Two small plugins but that I use everyday. Lets you save and close, or cancel and close, in one click. Looking through the TWC plugin list I sense a lot of them have lost their relevance in TW5 which I think shows how superior TW5 is becoming. For instance, to get something similar to the TW5 ToC macro was for a pretty complex task in TWC. :-) On Thursday, November 20, 2014 12:56:15 AM UTC+1, Richard Smith wrote: In response to Mat's suggestion on another thread ( https://groups.google.com/forum/#!topic/tiddlywiki/_rScP9Lscdg) I thought it might be helpful to share the plugins that I am using and what I am using them for and thought maybe you would like to do the same. I am using: 1) $:/plugins/bj/tiddlyclip Makes TW the most useful web-research tool around by letting you clip text and links to images straight into your TW. Works with multiple TW's. You can customise the way that content is imported - eg; the title and tags it gets, the format of the tiddler. You can have multiple actions set up to bring content in in different formats. 2) $:/plugins/tiddlywiki/katex Renders math equations with the khan academy latex thingy. I swapped from using the mathjax plugin for better support. Katex itself is in development but support is very good. Equations from many places on the web render correctly without modification. (I have modified the tiddlyclip template to add $$ ... $$ when I want to clip an equation directly) 3) $:/plugins/tiddlywiki/markdown I am experimenting with importing LaTeX documents and using markdown as an intermediate format. 4) $:/plugins/bj/taglist This lets you re-order a list on a tag by dragging and dropping. I think the way I am using it is quite interesting. I have two tiddlers that render the same list - one of them renders a list of titles using taglist and the other transcludes the text of each tiddler in the list, in the same order. Dragging and dropping to reorder titles in the first list also changes the order of the transcluded tiddlers in the second list. I'm using this to build book sections from individual paragraphs. -- 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
Hi Tobias Any chance you could fill this table with numbers according to spec (=implementation)? 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 variable 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 [variable] for a variable transclusion, and [{title}] for a tiddler transclusion 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? Best wishes Jeremy. http://pv5.tiddlyspot.com ...also referenced here: http://tb5.tiddlyspot.com/#Variables%20vs.%20Parameters 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] New Feature Moratorium
On Saturday, November 22, 2014 3:37:16 AM UTC+1, 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. That sounds easier than github pull requests (if I'm using the term correctly) but there will be a problem with version management i.e an upload overwrites the latest version of the whole wiki potentially overwriting something that had been contributed just recently. Tiddlyspace would probably work better in this respect as each tiddler is saved separately. There could be a policy that you're not allowed to manipulate, or at least not delete, someone elses tiddler but instead e.g append a new tiddler with your updated version. Maybe www.tiddlywiki.org, which actually is on tiddlyspace and already open for edit, could be modified to suit this ( @tobibeer ) However... the greater crux is that documentation is still very demanding, effectively limiting it to the few individuals who'll contribute. And while a few individuals can accomplish great things, I think documentation for TW is a big task. Heck, one of our *super* contributors estimates it will take 3 months of continuous writing to get the most basic questions explained well and he is super qualified on all matters. link https://www.indiegogo.com/projects/inside-tiddlywiki-the-missing-manual. I outlined an idea in the notorious thread (linked to in Jeremys post above) that takes another approach to documentation. The work to set up system that is probably much more limited than the work needed for documentation (which is open ended more or less) - but, of course, few *can* implement it and we can't expect anyone to *actually* implement it. (Personally, I'd gladly help support such a project financially. I believe it has potential to bring temendous value to the community. Anyone interested?) I also started another thread https://groups.google.com/forum/?fromgroups#%21topic/tiddlywiki/K9O5eBkIuW0 with, if technically possible, is yet aother completely differnt take on what could be used for documentation contributions. Another question is of course what would bring the most value to TW. I'm not certain it's the documentation issue, important as that is. Then again, in practice people will (and should) only do what they like in an unpaid project :-) :-) -- 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 reference for using TW5.
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 strikkeglad...@googlemail.com 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout. -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] widget to Goto Ranomized Tiddler
Hi Jed Something that may work for the original question of opening a random tiddler when a button is pressed, and something that I would like to see if possible, is a simple RNG that gets called by a message (like the 'throw the dice' button that can be called by a widget message). Yes, that sounds right to me. It would make a good plugin. Best wishes Jeremy On Thu, Nov 20, 2014 at 9:50 PM, Jed Carty inmyso...@gmail.com wrote: Something that may work for the original question of opening a random tiddler when a button is pressed, and something that I would like to see if possible, is a simple RNG that gets called by a message (like the 'throw the dice' button that can be called by a widget message). That way to implement the 'open a random tiddler' function you initialize the random value into a state tiddler, and then each time you click the button it opens a tiddler based on the current value in the tiddler and updates the value for the next time. Or updates the value and then opens the tiddler, I am not sure how the widget messages are executed so the order may matter. Some interface like $button$action-sendmessage $message='tm-rng' $state=placeToStoreNumber $range=[lowerEnd, upperEnd] $stepsize=someValue/Generate Values/$button could open interesting options for new uses. A parameter that allows you to select the distribution would be interesting, but probably outside the current scope of TW. On Monday, October 6, 2014 5:37:00 PM UTC-6, Philip Coltharp wrote: I envision a widget defined like so.. a list in side a button like so. ( Imagine this was put in a tiddler on http://tiddlywiki.com/) $button to=$list filter=[tag[Widgets]] pick-at-random=1Go To Random Widget Tiddler/$button *OR* $button to=pick-at-random from=$list filter=[tag[Widgets]]Go To Random Widget Tiddler/$button The ideal is to get a button to send a user to a tiddler picked at random from a list. I could do this in Classic Tiddlywiki but I want to learn Tiddlywiki5. How might one do this in TW5 differently than in TWC? -- 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] New Feature Moratorium
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. On Friday, November 21, 2014 5:27:26 AM UTC-7, Jeremy Ruston wrote: Several recent events have conspired to make me suggest that until the end of the year I operate a moratorium on new features for TiddlyWiki5. Instead, I propose to focus on documentation, and presentation of the available editions and plugins. I will of course continue to fix bugs as they are reported wherever it's possible to do so. (In the next few weeks I will also have to pay some attention to TiddlyFox and TiddlyDesktop. In the case of TiddlyFox, imminent Firefox architectural changes will require the architecture of the add-on to be significantly updated). One trigger is obviously the recent thread discussing obstacles to TiddlyWiki's success: https://groups.google.com/d/topic/tiddlywiki/_rScP9Lscdg/discussion A more subtle trigger is my recent experience with implementing the export features for 5.1.5. I started work on those features on around 12 days ago, on November 9th. I committed the first working code on November 10th. Ever since then I've been tied up with fixing up the loose ends: making the strings translatable, making improvements in response to feedback. Most recently, I've been implementing nested popups so that the export button will function when it is invoked through the more menu. The initial implementation was quick and fun, but a lot of the work since has been a slow slog. In my experience that is all pretty typical for a major new UI feature: 2 days to get the basic implementation followed by 5 to 10 days of working through the edge cases and cleaning up. Of course, part of the reason it takes so long is that alongside I'm still working on bug fixes, documentation and the occasional new feature such as the tabbed table of contents. The third trigger starts with the fact that I've been busy over the last few days, and unable to participate in the mailing list threads as much as I'd like. I've still been scanning the messages, and I'm drawn to the conclusion that for many people here, some of the quite basic features of TiddlyWiki are, thanks to the lack of documentation, indistinguishable from voodoo. For example, Danielo's terrific recent post on the variable attribute of the list widget was pretty interesting: another basic feature that hasn't been well enough communicated. So, now that I stand back, I'm not at all sure that the work on the export features was the best use of my time. It's an undeniably important feature in terms of rounding out the interoperability of TiddlyWiki, but it makes little or no difference to new users. My worry is that this will keep happening. There's plenty of voices here calling for new features, and I'm naturally attracted to the intricate problem solving required to implement them. I've a deep motivation to keep smashing through the roadmap of planned features. Hence my proposal for a new feature moratorium. It's a simple way to ensure that my attention stays focussed on the really important things for the next few weeks.
Re: [tw] Re: [TW5] Concatenated Widget Parameters
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 variable 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 [variable] 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. -- 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
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.
[tw] [TW5] concatenating title and textreference into a filter operand
Read below or first take a look at... http://sections.tiddlyspot.com/#FailingChapterToc Starting from tiddlers like... - BookB - BookB / ChapterC - BookB / ChapterC / PageP I am trying to display a list at the bottom of *BookB* showing the subtiddlers based on *BookB* functioning as a prefix. While that's easy to achieve using *[prefixcurrentTiddler]*, I am now trying to remove *BookB / * from *BookB / ChapterC* so as to construct a link that reads *[[ChapterC|**BookB / ChapterC]]* To do that, I introduced *$:/config/ChapterDelimiter* and specifyied * / * as the delimiter to then concatenate the current tiddler as my prefix with it using *$set*, all in all... $list filter=[prefixcurrentTiddlersort[title]]-[currentTiddler] variable=sub $set variable=remove value=currentTiddler {{$:/config/ChapterDelimiter}} $list filter=[subremoveprefixremove] variable=truncated $link to=subtruncated/$linkbr /$set /$list /$list The problem is, I never reach the inner list, i.e. the *remove* variable just won't yield the desired filter. The problem must lie in the variable as it all works if I do it with simple strings... http://sections.tiddlyspot.com/#WorkingChapterToc I also noticed that when I save my delimiter *$:/config/ChapterDelimiter* as * / * and then transclude it via... {{$:/config/ChapterDelimiter}} ...then the leading blank is trimmed! This definitely appears to be a bug. 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] and sections ...revisited (sorry, long post :)
Hi Jeremy, As I am fearing this to become rather lengthy, I am opening this thread to address Jeremy's response at this thread https://groups.google.com/d/msg/tiddlywiki/6zBxrj4nV34/NucvoBSuscYJ with respect to me stating... Actually, I think I'll be satisfied once I managed (to hire a crew to help me) to port SectionLinksPlugin http://www.tiddlytools.com/#SectionLinksPlugin to tw5. ;) Despite any dreaded performance concerns, there are just too many highly useful usecases involved with sections... - section-toc for tiddler *foo*, providing clickable links! (even back to the toc from the heading) - *$link* to section *foo*, from tiddler *bar*, too - *$list* section *foo* of tiddlers tagged *bar* - (edit section *foo*) First of all, allow me to thank you, Jeremy, for taking an inquisitve stance on the topic and for inviting discussion. I know your critical stance towards sections and I am hopeful that you might eventually come to a slightly different opinion, if only once a *SectionPlugin* of a beast sees the light of day. That implies making sections behave exactly like tiddlers. It's a possibility, not a necessity, and certainly not a requirement, although one could make it one. That's problematic because it means that all the behaviours we've built for using and manipulating tiddlers need to be re-engineered to work with sections. In some cases that's extremely tricky. It could indeed be problematic but then there is no need to have sections entirely as addressable and manageable as the tiddlers that supposedly hold them. Of course, it could be complicated if one wanted to address a section that was actually dynamically created, e.g. via $list, as that would imply wikification before being able to do so, e.g. via a parameter that says render:true instead of merely inspecting the basic wikitext. Anyhow, here are some rough sketches for how to implement the above usecases... *1) section toc:* Had I jQuery or the likes, here's what I would try... 1. user puts toc whereever he likes, e.g. the top of the tiddler 2. buildtoc is appended and run from ViewTemplate section with *list-after:body* 3. finds all h1...hx from tiddler 4. sets *id*'s or *rel* attributes at headings so as to have a reference for where to navigate 5. build and render toc 6. use js function to link from *toc.id* to *hx.id* and back using the above attributes, NO *href*! *2) link to section* foo 1. decide on a syntax, e.g. *[[tiddler§§foo]]* 2. display *tiddler*, passing the info to the display method that there's a section to scroll to - after all, there is some scrolling right now, too, so the function is there 3. have the display method find the first mathcing heading element after rendering 4. if found, scroll to *3) list section *foo of filtered tids 1. *filter *tids, e.g. using $list 2. use *regex *to extract section similar to how TWc or matchfilter http://eucaly-tw5.tiddlyspot.com/#%24%3A%2Fplugins%2Feucaly%2Fmatchfilter%2Freadme can do it 3. *wikify* *4) section editing* - should basically be similar to Eric's plugin for TWc, except for the internal functions to be called, of course - that is, if sections are being modeled as wikitext, rather than a JSON dictionary stuffed into a *section* field - might be problematic as *TiddlyWeb* for example limits the length of fields for optimization reasons For example, how would you make a location hash link to a section (eg http://example.com/#my-section-12)? There's no syntax within the location hash to identify the string as being a section name and not a tiddler title. *http://example.com/#[[foo$$bar]]* If there was a tiddler called *foo$$bar*, then we'd go to that, of course. Otherwise we go to section *bar* of tiddler *foo*. But, I would not worry about location hashes too much for now. I would certainly not use actual anchors. The only syntax to identify sections would be specific to tw, so it knows how to interpret *[[foo§§bar]]* Another example, to use the $list widget to list all sections of tiddlers tagged bar would require us to be able to process section names within filters. That implies that sections would need unique IDs - once again, making them meet the definition of a tiddler. I'd say unique ids are not essential or even required, at all. Sections are not tiddlers, but if neither the section nor the tiddler exist, the display handler would simply show the non-existing tiddler as it does right now. Using the first matching heading is just fine, or skipping entirely if not found. Also, I'd want the regex to, by default, match until the next heading of same level ...and, optionally, as TWc does, until any next heading (or end of the body). Basically, TiddlyWiki is a mechanism for manipulating tiddlers. Everything about it is predicated on the idea of a
Re: [tw] Re: Table of Contents inside a tiddler
Hi Jeremy, I'd really like more insight into the underlying needs. Glad you asked. Allow me to try and answer... :) https://groups.google.com/forum/#!topic/tiddlywiki/23PzU2qCsj4 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
Try this: \define remover() $(currentTiddler)$$(delim)$ $set name=delim value={{$:/config/ChapterDelimiter}} $list filter=[prefixcurrentTiddlersort[title]]-[currentTiddler] variable=sub $list filter=[subremoveprefixremover] variable=truncated $link to=subtruncated/$linkbr /$list /$list /$set -- 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 :)
Expanding on... However, using a JSON construct will definitely be an entirely different approach over using what could be called classic sections... Again, perhaps total overkill, but if JSON was the way to go, here's an idea for implementing JSON based sections... !--§§ { sections: { foo: { text: blablabla status: approved }, bar: { text: mumble mumble, tags: [[really?]] [[wow]] modified: ok, that goes too far, but maybe not, after all, why not?!? the adapter could be quite generic } } §§-- Et voilà! The magic of hidden sections. ;-) By all means, compared to classic section handling, that's perhaps a whole different ballpark. But it's probably a lot easier to handle / index / manipulate computationally. You certainly don't want users to edit this stuff in the text editor. So I wouldn't even load it there ...but remember while editing the main body and then provide a section editor for each section, only one instance per tiddler at a time. What would also be thinkable are hidden dictionary sections in usual tiddlers, like so... !--## foo:bar baz:mumble frotz:gronk ##-- Either way, I'd only process one instance each of sections or dictionary JSON per tiddler. After all, there's no need to have more of them, so any matching algorithm would only take care of the first instances. 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] and sections ...revisited (sorry, long post :)
Expanding on... Ok, you can probably scratch those hacky markup proposals. If anything, JSON sections of a tiddler hidden from the main body editor would probably be something more like this... $sections {} /sections and a data section more like... $data foo:bar baz:mumble /data 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?
Hi Mat, For an example see... Reopen Tiddlers On Startup http://tb5.tiddlyspot.com/#Reopen%20Tiddlers%20On%20Startup And the corresponding macro + stylesheet... $:/macros/static http://tb5.tiddlyspot.com/#%24%3A%2Fmacros%2Fstatic $:/styles/static http://tb5.tiddlyspot.com/#%24%3A%2Fstyles%2Fstatic 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: Table of Contents inside a tiddler
Hi Stephan, I did an update and now use the tiddler dropshadow instead. It does look nice but I had one additional thought on this. At the moment, in my version, the background color for the box is hard coded in the CSS. It would be nice if it could automatically use the appropriate color from the selected palette. That seems like it ought to be as simple as knowing the right internal name to use... It would and it seems that I have to decide whether I want that css tiddler to be displayed nicely or whether I am allowed to actually use macros in it... right now I am still inclined to do the former, but in general, if you want to use a color from the palette you... Use the color macro... .myClass{ background:colour page-background; } But then don't assign that tiddler tagged *$:/tags/Stylesheet* a content type of text/css, because TiddlyWiki won't interpret it as wiki markup but plain text insead and you will literally assign the string to your property, which won't work. 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. 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] ListField seems expect distinct values in the list
Hi, Filter operators like list, nth seems expected that all the values in the list are different (like A B C D). If some values are identical in the list field (i.e A B A C) second occurrences are ignored in the list or nth operators. (list ouptut is A B C) ( C is the [nth[3]] element) Is it a bug or an undocumented feature ? Olivier -- 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] problem with $select widget and computed option values
Thanks Jeremy, Here's an approach that works around that limitation: That worked. Will play a little more with using variables and parameters in these situations and demonstrate what works and what doesn't. Best wishes, Tobias. javascript: -- 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: Plugins We Use
I use the five following plugins. The first three are by Danielo. - Context Search - Keyboard Snippets - Inline editable tables This one is by bj - Extendable Calendar And this one by eucaly - Match Filter -- 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?
You're kidding me - WOW And so recently at that! I promise I had no idea about it, I feel silly now! Ok, that looks GREAT. And you did get the very text field only, I have no idea how, I can't tell from looking at the macro http://tb5.tiddlyspot.com/#%24%3A%2Fmacros%2Fstatic but maybe that is not where the inner workings are defined. Now things are getting very interesting. I will try the following, maybe later tonight: Imagine there could be a trusted tree building up from nested iframes. A bit like inclusion on TiddlySpace. A top site owned by person A could have an iframe like that, pointing at a specific tiddler (named T) on a tw owned by someone that A trusts: B. They agree *B* will in this tiddler put in iframes linking to plugins he recommends. This means A delegated this task to his trusted friend. Now, B can do the same thing with a third friend, C, but B sets up this connection, i.e an iframe, inside T (!!!)., perhaps under B's own recommended plugins. C's recommended plugins will then propagate up to T, i.e in A's tw. All parties can obviously delegate to as many as they wish, potentially building up a tree of trust very fast. If this works, it means it should be very easy to build up a complete plugin repository of all existing plugins. Of course one would need ways to eliminate copies. Any spontaneous thoughts before I try this out? Or, rather, try to try this out. I don't even know if iframes can nest, so maybe I'll hit a wall right away. :-) -- 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] Zork-like game, now with an authoring tool (work in progress)
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. 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. 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. 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. 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. 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.
[tw] [TW5] Yet another documentation idea
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.
[tw] Re: [TW5] External individual tiddlers via iframes?
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.
[tw] Re: [TW5] External individual tiddlers via iframes?
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.
[tw] Re: ListField seems expect distinct values in the list
Hmmm That isn't what I expected either If I go to Tiddlywiki.com and put this in a tiddler $list filter=[list[]] /$list and give it a 'list' field 'A B A C' - not only is the second A not rendered, but when the edit is saved, it gets removed from the list altogether. And also... it seems to me like the list filter operator (which I haven't really used before now) doesn't work as expected in another way. If I change my list field to A B C Acknowledgements and then do this; $list filter=[tag[About]] +[list[]] /$list I would expect to get all the tiddlers with the tag 'About' WHICH ARE ALSO in the list, ie; just 'Acknowledgements', but I get the full list from the field. On the other hand if I negate the list operator $list filter=[tag[About]] +[!list[]] /$list I get what I would expect, which is all the tiddlers with the tag 'About' which AREN'T in the list. This is confusing, but at least I've found something I can help to document (once I understand what's going on myself!) 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?
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 dgiff...@crcna.org 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.
Re: [tw] Re: [TW5] Yet another reference for using TW5.
Dear Jed, this is very helpful - thanks Alex On 22 November 2014 at 18:03, Jeremy Ruston jeremy.rus...@gmail.com 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 strikkeglad...@googlemail.com 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+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. -- 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
Lists are (or at least were) nasty as they sometimes behave as sets (no duplicates) sometimes as lists - at least that's ,y experience when I did some plugins using lists. -- 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
Am Sonntag, 23. November 2014 07:02:39 UTC+1 schrieb Richard Smith: If I change my list field to A B C Acknowledgements and then do this; $list filter=[tag[About]] +[list[]] /$list Then you will first get a list of all tiddlers tagged About. In the next step you throw it away by replacing it with the current tiddler's list content. I would expect to get all the tiddlers with the tag 'About' WHICH ARE ALSO in the list, ie; just 'Acknowledgements', but I get the full list from the field. Why did you expect that, when the documentation states: The *list* filter operator replaces the current list with the list contained in the TextReference http://tiddlywiki.com/#TextReference specified in the operand. The default field for the text reference is list . See: http://tiddlywiki.com/#FilterOperator%3A%20list This is confusing, but at least I've found something I can help to document (once I understand what's going on myself!) Try this to get the lists from each of your tiddlers: $list filter=[tag[Aout]] currentTiddler $list filter=[list[]] /$list /$list -- 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.