[tw] Re: [TW5] The $mangletags widget
Hi With the latest version of the $mangletags widget, widgets may be stacked adjacent to one another like this: $mangletags add=one $mangletags add=two $mangletags add=three $button message=tw-mangle-tags param=TestAdd/$button /$mangletags/$mangletags/$mangletags regards On Friday, May 30, 2014 12:40:51 PM UTC+2, Matabele wrote: Hi I have added another widget at: http://gwiz.tiddlyspot.com/ I needed to modify the tags in the template and the $maketid widget overwrites the tags in the template tiddler. Whilst it is possible to do this in some contexts with the $fieldmangler widget, the parameter to the message is used to specify the tag, and according to my stacking mechanism, the title of the target tiddler should be propagated with the parameter to the message. Thus a whole new $mangletags widget and an associated tw-mangle-tags message (to avoid confusions with the widget messages associated with the $fieldmangler widget.) The $mangletags widget can be stacked around a button widget and can do any of the following: -- append a tag to the tags field of the target tiddler -- find and remove a tag from the tags field of the target tiddler (if present) -- find and replace a tag from the tags field of the target tiddler (if present) -- send a different widget message. The unfamiliar attributes are 'add=' and 'find=' -- to add a tag, use only: add=tag-to-add -- to remove a tag, use only: find=tag-to-remove -- to find and replace a tag use: find=tag-to-be-replaced and add=tag-to-substitute Hope this is of use -- there is a demo on the site to show what the widget does. The logic is a little complicated -- hope my code works in all contexts :-) 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: Saving problems, special characters disappearing and corrupting backup saves.
Hi! Thanks for your answers, it gives me hope! First, I'll tell you what I tried yesterday: -I changed the folder in which my wiki was, in order to avoid special characters in the folder path (maybe...) but it didn't work, as expected. -I tried to open the wiki in Google Chrome (which I never use, usually) or in Firefox (but I don't have tiddlyfox), didn't change anything. -I experimented a bit. The best I can do so far is to open the wiki from its folder and save it without any change. If I add something, it bugs. But even if I save it just like that, the special characters die... the file size drops from 1682 Ko to 1530 Ko... which is because it loses all the special characters, I guess. (But it can save properly for anything but the special characters...) I didn't install any securty program, since I'm in the middle of my license. I suspected a malicious program as well, but a total scan didn't reveal anything. I never update IE, because I only use it for the wiki, and the current version I have works fine with it. Concerning my actual version of TW, It's an old classic version. I tried to download the actual classic TW, but I don't like it, because every time I ask it to save, it offers me to download the file, instead of doing a backup file and saving itself automatically. This is enough of a burden to stop me from using it... and I tested it enough to see that it killed the special characters as well when it saves. I will continue to do some research on my sides, starting with TiddlyFox. Thank you for your answers! -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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: Saving problems, special characters disappearing and corrupting backup saves.
Fast feedback: It looks like tiddlyfox did the job. I can save my wiki again, close it and open it to see that the special characters are still there... I'll test it today with bigger tiddlers and changes, and I'll tell you the word of it. Thank you both for your counsels! -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] preventing tiddler-links to break by using ids as reference that translate into titles
Hi
One of the disadvantages of using the 'title' field as the unique ID is,
for example, the impossibility of having more than one tiddler with the
title 'Introduction'. If I wish to use a single TW for several
articles/books, each of which has an introduction -- I am forced to use
titles such as 'Article1 - Introduction' and 'Article2 - Introduction'.
Further, in the finished articles, I must then use labelled links such as
[[Introduction|Article1 - Introduction]], if I want the section to be
titled 'Introduction'.
This makes a strong case for the use of unique uuid's for linking to
tiddlers, with the 'title' field as an alias for the link to the tiddler.
A possible mechanism:
1. a unique ID for the tiddler is created when a new tiddler is first
saved, and
2. an addition is made to a dictionary mapping the new 'title' field to the
ID
3. when a title is edited, a new entry is added to the dictionary (but the
old one remains)
4. the tiddler can now be linked via the ID, the old title or the new title
5. any additional aliases may be added to the dictionary for the same ID
The problem here: that using the alias 'Introduction' will now link to
several ID's -- how do I specify which of the tiddlers with the alias
'Introduction' I wish to target?
My first thought on this is to use two 'anded' aliases to link to a
particular tiddler, when a single alias refers to several tiddler ID's --
[[Introduction Article1]]. Now, this will pick the correct tiddler, and
the displayed title will be whatever the current title of that tiddler --
in this case 'Introduction' -- which is my desired behaviour. The whole
scheme is beginning to look rather like tags!
Have no idea how difficult this would be to implement -- just an opinion
from an end-user point of view.
regards
On Monday, June 2, 2014 6:46:26 PM UTC+2, Jeremy Ruston wrote:
Hi Felix
That's the unavoidable, perennial question referred to above. A simple
formulation is: do we use the title field as the identifier for a tiddler
the title field, or do we use a separate ID field. The two options
can't co-exist, we need to choose one. TiddlyWiki chooses the former on the
basis that is a more human formulation, and that it can trivially emulate
the ID approach. But that is done by using the title field as an ID, not by
introducing a new ID field. The reason is because of the need to enforce
uniqueness: we guarantee the uniqueness of titles, but not of other fields.
Best wishes
Jeremy.
Regards
Felix
On Monday, June 2, 2014 5:02:33 PM UTC+2, Jeremy Ruston wrote:
This question of whether tiddlers should be identified by title or by an
abstract GUID is a perennial one.
My aim is that users should be able to use GUIDs for tiddler titles if
it suits their use case. The missing piece is a way of linking to a tiddler
by it's GUID/title, but having a specified field displayed as the text of
the link. Here's an example of a macro to do that:
\define link(guid)
$tiddler tiddler=$guid$$link$view field=name//$link/$
tiddler
\end
This is a link by guid link qqu99yie1
Of course, it would be more useful if one could arrange for that macro
to be automatically substituted for links.
Best wishes
Jeremy.
On Mon, Jun 2, 2014 at 2:57 PM, Felix Küppers felixk...@hotmail.de
wrote:
Well, I know linking via ids is not readable in edit mode, however in a
non-edit mode, the id translates to a name, so that is ok for me.
As for semantic-alias (i.e. a real second title) vs. ids, I rather
chose ids as their purpose is only to allow exact references. same as in
SQL autoincrement primary keys...
And I rather place them inside a field because I like them to be more
invisible as they have no semantic meaning.
However I took a closer look at you example in your space and it is a
really nice workaround you are using, I mean exploiting the masking-title
of the link as a variable to use it in a local macro.
This way I could do something like
{{ 415241 | id }}
and put the filter in the macro instead of directly writing
{{{ [field:id[]!has[draft.of]first[]] }}}
that will make a nice shortcut...
On Monday, June 2, 2014 3:30:38 PM UTC+2, Stephan Hradek wrote:
I can't see a fundamental difference between my alias approach and
using IDs. Except that ID's tend to be unreadable.
--
You received this message because you are subscribed to the Google
Groups TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send
an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
--
Jeremy Ruston
mailto:jeremy...@gmail.com
--
Jeremy Ruston
mailto:jeremy...@gmail.com javascript:
--
You received this message because you are subscribed to the Google Groups
Re: [tw] Re: [TW5] preventing tiddler-links to break by using ids as reference that translate into titles
Hi Felix That said, I apologize for bothering you with my newbie-opinions or questions, but from my understanding it is possible to have more than one unique-field that identifies a tiddler. Similar to SQL where I can have several unique attributes in a table that each could be used to identify a row. If a new tiddler is created, the system only needs to ensure that the title AND the id is unique. To have two unique tiddler fields in JavaScript would mean using a separate hashmap for each field that we want to enforce uniqueness. It would considerably complicate all the low level operations involving tiddlers. Right now, TW can be fast because the tiddler store is a very thin wrapper around JavaScript's native storage mechanisms. From this point on, it is the decision of the user to reference the tiddler by id or by title. As written above, I have introduced this mechanism in my wiki and it works well. The bit that you don't have is enforcement of the uniqueness of the ID, though. One could imagine adding tools that prompt you if you've got an ID clash, and that wouldn't be ridiculously expensive. But making it a properly enforced constraint is expensive. Providing a build-in alternative to a reference-by-title concept for those who want it would be a nice feature because links wouldn't break. Maybe it's not a common issue but I found a threat on stackexchange where a user had the same problem: http://webapps.stackexchange.com/questions/22850/changing-the-name-of-a-tiddler-in-tiddlywiki-and-retain-the-references-pointing Link breakage is definitely a common problem. As I said at the top, I'm keen to support the ID way of working as an option (using the title field as the ID), but I don't think it's practical to enforce multiple unique fields on the tiddler store. My preferred solution to the breaking links problem is also a solution to wider problems of wikitext authorship: a decent search and replace operation that is syntactically aware; it can reliably find and replace all the references to a tiddler (without being confused by plain text references to the same text). In any case, I fully support your choice to use the title as unique identifier and if TW internals do not allow the introduction of such a parallel-concept then it is totally fine. I think TW is great and offers much flexibility either way! So thank you for your work and your previous answers. Sorry for labouring the response to your points; I just figured it may be useful to lay out some of the reasoning. Best wishes Jeremy Greetings Felix On Monday, June 2, 2014 6:46:26 PM UTC+2, Jeremy Ruston wrote: Hi Felix By the way, is there any reason, why the tiddlers do not get a unique id on creation time as a field value per default? This would support people to create unbreakable references via ids, without the previous effort to give each tiddler a unique id or creating a custom button. That's the unavoidable, perennial question referred to above. A simple formulation is: do we use the title field as the identifier for a tiddler the title field, or do we use a separate ID field. The two options can't co-exist, we need to choose one. TiddlyWiki chooses the former on the basis that is a more human formulation, and that it can trivially emulate the ID approach. But that is done by using the title field as an ID, not by introducing a new ID field. The reason is because of the need to enforce uniqueness: we guarantee the uniqueness of titles, but not of other fields. Best wishes Jeremy. Regards Felix On Monday, June 2, 2014 5:02:33 PM UTC+2, Jeremy Ruston wrote: This question of whether tiddlers should be identified by title or by an abstract GUID is a perennial one. My aim is that users should be able to use GUIDs for tiddler titles if it suits their use case. The missing piece is a way of linking to a tiddler by it's GUID/title, but having a specified field displayed as the text of the link. Here's an example of a macro to do that: \define link(guid) $tiddler tiddler=$guid$$link$view field=name//$link/$tiddl er \end This is a link by guid link qqu99yie1 Of course, it would be more useful if one could arrange for that macro to be automatically substituted for links. Best wishes Jeremy. On Mon, Jun 2, 2014 at 2:57 PM, Felix Küppers felixk...@hotmail.de wrote: Well, I know linking via ids is not readable in edit mode, however in a non-edit mode, the id translates to a name, so that is ok for me. As for semantic-alias (i.e. a real second title) vs. ids, I rather chose ids as their purpose is only to allow exact references. same as in SQL autoincrement primary keys... And I rather place them inside a field because I like them to be more invisible as they have no semantic meaning. However I took a closer look at you example in your space and it is a really nice workaround you are using, I mean exploiting the masking-title of
Re: [tw] TW5 new plugin Preview Search
Hi Danielo
The difference was the upgrade process-- *Node 5.0.8 to node 5.0.12 (I
think all tiddlers are kept)* VS Standalone 5.0.8 to Node 5.0.12 (does it
only import standard tiddlers?)
5.0.12 should be able to import both ordinary and system tiddlers from
5.0.8 wikis. I'd be interested if you could track the problem down a little.
Best wishes
Jeremy
I forgot to mention that maybe this could have an impact on performance or
be too slow when lazy loading tiddlers. But I'm not very sure about this
point.
El lunes, 2 de junio de 2014 14:24:16 UTC+2, Jeremy Ruston escribió:
Hi Danielo
Great stuff, once again I'm very impressed. I notice that
http://braintest.tiddlyspot.com is still running 5.0.8; are your plugins
compatible with 5.0.12?
Best wishes
Jeremy
On Sat, May 31, 2014 at 1:41 AM, Danielo Rodríguez rdan...@gmail.com
wrote:
I'm glad to present a new plugin. It is in beta stage yet, so if you
want to propose something it's possible. If you just want to jump to the
plugin you can find it at : http://braintest.tiddlyspot.com/ and search
for context plugin
This widget looks for a word inside a tiddler and shows the result with
the searched word highlighted with some of its context.
Installation
The easiest way is to just grab the plugin. It contents the basic
tiddlers needed. Just drag and drop the following link into your own wiki:
$:/plugins/danielo/context
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext
Usage
After installing the plugin you will have a new tab in $:/AdvancedSearch
http://braintest.tiddlyspot.com/#%24%3A%2FAdvancedSearch called Context
Search
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext%2FContext%20Search.
If you want this functionality in other places you will have to edit the
desired tiddler yourself adding the *context widget*. For more details
about using the widget see the section below.
Using the widget
The very basic usage of the widget is the following:
$context term=lorem/
Which will render as:
...
the widget is the following:
```
$context term=lorem/
```
Which will render as:
$context term=lorem...
The widgets will search inside the current tiddler by default. Because
that you see the same content twice here. This example is not very useful.
Other more meaningful would be:
$list filter=[search{$:/temp/advancedsearch}sort[title]limit[250]]
{{!!title||$:/core/ui/ListItemTemplate}}
$context term={{$:/temp/advancedsearch}}/
/$list
That will search for tiddlers containing the text specified in
$:/temp/advancedsearch
http://braintest.tiddlyspot.com/#%24%3A%2Ftemp%2Fadvancedsearch and
will display a link to the matching tiddlers plus a preview of the matching
content. Something very similar is used in Context Search
http://braintest.tiddlyspot.com/#Context%20Search. Below you can find
a complete list of parameters and their default values.
parameter description default term The term you want to search
searchTerm An alias for the previous one tiddler The tiddler's name to
look into current tiddler length Number of context characters to show 50
before Number of characters before the matched term to show the value
of the length parameter after Number of characters after the matched
term to show the value of the length parameter maxMatches maximun
number of matched elements to show. Incrementing this can cause several
performance issues 10 element Node element to create. This element will
contain the results of the search. If you want to style it its class is
tw-context pre matchClass The css class to assign to the matched
terms in the results. This is used to highlight the results matched
Customizing the output
There are not many ways to customize the output of this widget. You can
specify *what type of node you want to create* to wrap the results
(div,span...). The default is pre. This container is created with the
class tw-context so you can easily apply styles to it. Something
similar happens to the *highlighted* words. You can specify the name of
the class to assign to it and also you can apply styles to that class.
A very basic example of customization could be:
1. Create a tiddler, for example $:/plugins/danielo/context/css
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext%2Fcss
2. Paste the following text or any css rule you want:
.matched{background-color:yellow}
.tw-context {
border:1px solid blue;
word-break: break-all; word-wrap: break-word;}
3. Tag it with $:/tags/stylesheet
4. Save the tiddler
Live example
You can find a live example at http://braintest.tiddlyspot.com/
--
You received this message because you are subscribed to the Google
Groups TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send
an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit
Re: [tw] Re: TW5: Using TW as a musical scratchpad with BopLand.org services?
Hi TwAfficionados Mohit returned a positive answer yesterday: Mohit: Thanks for the e-mail. I'm okay with someone else building a TiddlyWiki plugin, but I'm not sure that the licenses are compatible. VexTab is free so long as it is not used for commercial purposes and the vexflow.com logo remains visible. If you can annotate your plugins with some text mentioning that this is for non-commercial use only, then I have no problem with it. I'm not sure if it's enough to apply with TW's BSD license - if the plugin is distributed standalone from Github? If Github is used as an official repository for the plugin - and it's not presented as part of an official TW5 package - eg. installed at tiddlywiki.com?? Cheers Måns Mårtensson Den onsdag den 28. maj 2014 18.32.00 UTC+2 skrev Måns: Hi Jeremy You're right, it does present problems if we can't redistribute VexTab under the same BSD license as TiddlyWiki itself. It sounds like it would be worth talking to the author though. Mohit Muthanna (0xFE http://vexflow.com/vextab/) did not answer when I invited him to the Hangout. As you know my first language is far from being English - however I wrote this to Mohit a couple of minutes ago: Hi Mohit Muthanna (0xFE) On the TiddlyWIki mail list/google group we are discussing if we are allowed to create a plugin/redistribute VexTab as a plugin for TiddlyWIki. TiddlyWiki is licensed with BSD. VexFlow is MIT and it should work well with BSD. ... but VexTab however would need some adjustments if we should be able to redistribute it.. Jeremy Ruston, the creator of TiddlyWiki, has shown interest in building a VexTab plugin for TiddlyWiki, live in a Google Hangout - because The API of VexTab is nice and flexible and would be particularly easy to turn into a TW5 widget. I'm a music teacher, a guitarist and a long time TiddlyWiki end user, and I would love to be able to work with musical scores and write chord diagrams directly in my own personal portable wiki which also happens to be a database and a blog like application which is much more versatile than standard word processors like eg. Google Docs or Office Word... Just to name a few. Would you be interested in the making of a plugin for TiddlyWiki? If you are - how do we make it work - regarding the question of license types? Cheers Måns Mårtensson Links: http://tiddlywiki.com https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/nh5vMpPeEvg; Hope it's ok..? Cheers Måns -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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 plugin Preview Search
Very nice work, Danielo! At first it wouldn't work for me, but then I
realized I was only typing in three letters into the search area, and the
context viewing part apparently kicks in on the fourth letter.
Blessings!
On Friday, May 30, 2014 8:41:17 PM UTC-4, Danielo Rodríguez wrote:
I'm glad to present a new plugin. It is in beta stage yet, so if you want
to propose something it's possible. If you just want to jump to the plugin
you can find it at : http://braintest.tiddlyspot.com/ and search for
context plugin
This widget looks for a word inside a tiddler and shows the result with
the searched word highlighted with some of its context.
Installation
The easiest way is to just grab the plugin. It contents the basic tiddlers
needed. Just drag and drop the following link into your own wiki:
$:/plugins/danielo/context
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext
Usage
After installing the plugin you will have a new tab in $:/AdvancedSearch
http://braintest.tiddlyspot.com/#%24%3A%2FAdvancedSearch called Context
Search
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext%2FContext%20Search.
If you want this functionality in other places you will have to edit the
desired tiddler yourself adding the *context widget*. For more details
about using the widget see the section below.
Using the widget
The very basic usage of the widget is the following:
$context term=lorem/
Which will render as:
...
the widget is the following:
```
$context term=lorem/
```
Which will render as:
$context term=lorem...
The widgets will search inside the current tiddler by default. Because
that you see the same content twice here. This example is not very useful.
Other more meaningful would be:
$list filter=[search{$:/temp/advancedsearch}sort[title]limit[250]]
{{!!title||$:/core/ui/ListItemTemplate}}
$context term={{$:/temp/advancedsearch}}/
/$list
That will search for tiddlers containing the text specified in
$:/temp/advancedsearch
http://braintest.tiddlyspot.com/#%24%3A%2Ftemp%2Fadvancedsearch and
will display a link to the matching tiddlers plus a preview of the matching
content. Something very similar is used in Context Search
http://braintest.tiddlyspot.com/#Context%20Search. Below you can find a
complete list of parameters and their default values.
parameterdescriptiondefaulttermThe term you want to searchsearchTermAn
alias for the previous onetiddlerThe tiddler's name to look intocurrent
tiddlerlengthNumber of context characters to show50beforeNumber of
characters before the matched term to showthe value of the length
parameterafterNumber of characters after the matched term to showthe
value of the length parametermaxMatchesmaximun number of matched elements
to show. Incrementing this can cause several performance issues10elementNode
element to create. This element will contain the results of the search. If
you want to style it its class is tw-contextprematchClassThe css class
to assign to the matched terms in the results. This is used to highlight
the resultsmatchedCustomizing the output
There are not many ways to customize the output of this widget. You can
specify *what type of node you want to create* to wrap the results
(div,span...). The default is pre. This container is created with the
class tw-context so you can easily apply styles to it. Something similar
happens to the *highlighted* words. You can specify the name of the class
to assign to it and also you can apply styles to that class.
A very basic example of customization could be:
1. Create a tiddler, for example $:/plugins/danielo/context/css
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext%2Fcss
2. Paste the following text or any css rule you want:
.matched{background-color:yellow}
.tw-context {
border:1px solid blue;
word-break: break-all; word-wrap: break-word;}
3. Tag it with $:/tags/stylesheet
4. Save the tiddler
Live example
You can find a live example at http://braintest.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.
Re: [tw] Re: TW5: Using TW as a musical scratchpad with BopLand.org services?
I'll take a look and see if there is a way to use vexflow on its own. On a first glace it seems that vextab is a compiler that produces scripts for vexflow. BJ On Tuesday, June 3, 2014 12:11:51 PM UTC+2, Måns wrote: Hi TwAfficionados Mohit returned a positive answer yesterday: Mohit: Thanks for the e-mail. I'm okay with someone else building a TiddlyWiki plugin, but I'm not sure that the licenses are compatible. VexTab is free so long as it is not used for commercial purposes and the vexflow.com logo remains visible. If you can annotate your plugins with some text mentioning that this is for non-commercial use only, then I have no problem with it. I'm not sure if it's enough to apply with TW's BSD license - if the plugin is distributed standalone from Github? If Github is used as an official repository for the plugin - and it's not presented as part of an official TW5 package - eg. installed at tiddlywiki.com?? Cheers Måns Mårtensson Den onsdag den 28. maj 2014 18.32.00 UTC+2 skrev Måns: Hi Jeremy You're right, it does present problems if we can't redistribute VexTab under the same BSD license as TiddlyWiki itself. It sounds like it would be worth talking to the author though. Mohit Muthanna (0xFE http://vexflow.com/vextab/) did not answer when I invited him to the Hangout. As you know my first language is far from being English - however I wrote this to Mohit a couple of minutes ago: Hi Mohit Muthanna (0xFE) On the TiddlyWIki mail list/google group we are discussing if we are allowed to create a plugin/redistribute VexTab as a plugin for TiddlyWIki. TiddlyWiki is licensed with BSD. VexFlow is MIT and it should work well with BSD. ... but VexTab however would need some adjustments if we should be able to redistribute it.. Jeremy Ruston, the creator of TiddlyWiki, has shown interest in building a VexTab plugin for TiddlyWiki, live in a Google Hangout - because The API of VexTab is nice and flexible and would be particularly easy to turn into a TW5 widget. I'm a music teacher, a guitarist and a long time TiddlyWiki end user, and I would love to be able to work with musical scores and write chord diagrams directly in my own personal portable wiki which also happens to be a database and a blog like application which is much more versatile than standard word processors like eg. Google Docs or Office Word... Just to name a few. Would you be interested in the making of a plugin for TiddlyWiki? If you are - how do we make it work - regarding the question of license types? Cheers Måns Mårtensson Links: http://tiddlywiki.com https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/nh5vMpPeEvg; Hope it's ok..? Cheers Måns -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] preventing tiddler-links to break by using ids as reference that translate into titles
Am Dienstag, 3. Juni 2014 12:51:04 UTC+2 schrieb Felix Küppers: That is true, I pray to god that the javascript function never creates the same id twice. http://tiddlystuff.tiddlyspot.com/ - UUIDmacro -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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: Using TW as a musical scratchpad with BopLand.org services?
Hi Måns How frustrating. The license for VexTab definitely prevents us from distributing it under the same licensing terms as TW itself. I think that rules out making it any kind of official plugin that is distributed from tiddlywiki.com. I remain very happy to help if anyone else is interested in creating a widget around vextab. Best wishes Jeremy On Tue, Jun 3, 2014 at 12:04 PM, BJ buggy...@gmail.com wrote: I'll take a look and see if there is a way to use vexflow on its own. On a first glace it seems that vextab is a compiler that produces scripts for vexflow. BJ On Tuesday, June 3, 2014 12:11:51 PM UTC+2, Måns wrote: Hi TwAfficionados Mohit returned a positive answer yesterday: Mohit: Thanks for the e-mail. I'm okay with someone else building a TiddlyWiki plugin, but I'm not sure that the licenses are compatible. VexTab is free so long as it is not used for commercial purposes and the vexflow.com logo remains visible. If you can annotate your plugins with some text mentioning that this is for non-commercial use only, then I have no problem with it. I'm not sure if it's enough to apply with TW's BSD license - if the plugin is distributed standalone from Github? If Github is used as an official repository for the plugin - and it's not presented as part of an official TW5 package - eg. installed at tiddlywiki.com?? Cheers Måns Mårtensson Den onsdag den 28. maj 2014 18.32.00 UTC+2 skrev Måns: Hi Jeremy You're right, it does present problems if we can't redistribute VexTab under the same BSD license as TiddlyWiki itself. It sounds like it would be worth talking to the author though. Mohit Muthanna (0xFE http://vexflow.com/vextab/) did not answer when I invited him to the Hangout. As you know my first language is far from being English - however I wrote this to Mohit a couple of minutes ago: Hi Mohit Muthanna (0xFE) On the TiddlyWIki mail list/google group we are discussing if we are allowed to create a plugin/redistribute VexTab as a plugin for TiddlyWIki. TiddlyWiki is licensed with BSD. VexFlow is MIT and it should work well with BSD. ... but VexTab however would need some adjustments if we should be able to redistribute it.. Jeremy Ruston, the creator of TiddlyWiki, has shown interest in building a VexTab plugin for TiddlyWiki, live in a Google Hangout - because The API of VexTab is nice and flexible and would be particularly easy to turn into a TW5 widget. I'm a music teacher, a guitarist and a long time TiddlyWiki end user, and I would love to be able to work with musical scores and write chord diagrams directly in my own personal portable wiki which also happens to be a database and a blog like application which is much more versatile than standard word processors like eg. Google Docs or Office Word... Just to name a few. Would you be interested in the making of a plugin for TiddlyWiki? If you are - how do we make it work - regarding the question of license types? Cheers Måns Mårtensson Links: http://tiddlywiki.com https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/nh5vMpPeEvg; Hope it's ok..? Cheers Måns -- 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 plugin Preview Search
Hi Danielo,
On Monday, June 2, 2014 11:07:43 PM UTC+2, Danielo Rodríguez wrote:
Hi Ton,
Thank you very much. But you were able to search your stuff. The
difference is that now you can do it in a different way.
Yes I could search (and get a list of tiddlers) but with help of the
preview you can *find* things easily ;-)
Glad you liked it. Your guides helped me a lot when I started with TW5
Nice to hear.
Don't forget this is a live development. If you miss something or you have
suggestions just let me know.
I noticed that tags are found as well (but not fields). Found tags result
in a tiddler without preview.
Since tiddlers tagged with a certain tag can be found elsewhere (Sidebar,
tab Tags), may be wise to skip the tag results.
What do you think?
Cheers,
Ton
regards
El lunes, 2 de junio de 2014 21:21:02 UTC+2, Ton Gerner escribió:
Hi Danielo,
Very, very nice plugin.
At last it is possible to find the stuff I entered in my TW5s! ;-)
Thanks a lot.
Cheers,
Ton
On Saturday, May 31, 2014 2:41:17 AM UTC+2, Danielo Rodríguez wrote:
I'm glad to present a new plugin. It is in beta stage yet, so if you
want to propose something it's possible. If you just want to jump to the
plugin you can find it at : http://braintest.tiddlyspot.com/ and search
for context plugin
This widget looks for a word inside a tiddler and shows the result with
the searched word highlighted with some of its context.
Installation
The easiest way is to just grab the plugin. It contents the basic
tiddlers needed. Just drag and drop the following link into your own wiki:
$:/plugins/danielo/context
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext
Usage
After installing the plugin you will have a new tab in $:/AdvancedSearch
http://braintest.tiddlyspot.com/#%24%3A%2FAdvancedSearch called Context
Search
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext%2FContext%20Search.
If you want this functionality in other places you will have to edit the
desired tiddler yourself adding the *context widget*. For more details
about using the widget see the section below.
Using the widget
The very basic usage of the widget is the following:
$context term=lorem/
Which will render as:
...
the widget is the following:
```
$context term=lorem/
```
Which will render as:
$context term=lorem...
The widgets will search inside the current tiddler by default. Because
that you see the same content twice here. This example is not very useful.
Other more meaningful would be:
$list filter=[search{$:/temp/advancedsearch}sort[title]limit[250]]
{{!!title||$:/core/ui/ListItemTemplate}}
$context term={{$:/temp/advancedsearch}}/
/$list
That will search for tiddlers containing the text specified in
$:/temp/advancedsearch
http://braintest.tiddlyspot.com/#%24%3A%2Ftemp%2Fadvancedsearch and
will display a link to the matching tiddlers plus a preview of the matching
content. Something very similar is used in Context Search
http://braintest.tiddlyspot.com/#Context%20Search. Below you can find
a complete list of parameters and their default values.
parameterdescriptiondefaulttermThe term you want to searchsearchTermAn
alias for the previous onetiddlerThe tiddler's name to look intocurrent
tiddlerlengthNumber of context characters to show50beforeNumber of
characters before the matched term to showthe value of the length
parameterafterNumber of characters after the matched term to showthe
value of the length parametermaxMatchesmaximun number of matched
elements to show. Incrementing this can cause several performance issues
10elementNode element to create. This element will contain the results
of the search. If you want to style it its class is tw-contextpre
matchClassThe css class to assign to the matched terms in the results.
This is used to highlight the resultsmatchedCustomizing the output
There are not many ways to customize the output of this widget. You can
specify *what type of node you want to create* to wrap the results
(div,span...). The default is pre. This container is created with the
class tw-context so you can easily apply styles to it. Something
similar happens to the *highlighted* words. You can specify the name of
the class to assign to it and also you can apply styles to that class.
A very basic example of customization could be:
1. Create a tiddler, for example $:/plugins/danielo/context/css
http://braintest.tiddlyspot.com/#%24%3A%2Fplugins%2Fdanielo%2Fcontext%2Fcss
2. Paste the following text or any css rule you want:
.matched{background-color:yellow}
.tw-context {
border:1px solid blue;
word-break: break-all; word-wrap: break-word;}
3. Tag it with $:/tags/stylesheet
4. Save the tiddler
Live example
You can find a live example at http://braintest.tiddlyspot.com/
--
You received this message because you are
Re: [tw] [TW5] syntax [img[imagefile.jpg]] in node.js
Hi Michele I take it that (yet) means there is the plan to support it in the future. Will it be near future? Will the syntax be [img[path/to/local/file]]? Yes, it should be working in the next couple of months. The syntax will definitely use [img[]], and the plan would be to set up the base path so that images can be referenced directly by their tiddler title. Best wishes Jeremy By the way for me also the link syntax a href=file:///home/michele/imagefile.jpgimage/a is not working for me (see https://groups.google.com/d/msg/tiddlywiki/EmJFLV1XAD0/ZL7_W8Jsa18J ) Does it work if you link to a http:// website? Yes, a href=http://...;link/a works on 5.0.12 for me. Best regards, michele -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] Newbie: Line-break question
Hi Andrew If you want to be able to type a literal linebreak then I'd recommend using br; there's no performance difference with including the slash. Both forms will always be supported in TW5 because they are part of the basic HTML tags in wikitext feature. Best wishes Jeremy On Mon, Jun 2, 2014 at 8:18 PM, andrew.j.harrison84 andrew.j.harriso...@gmail.com wrote: Just when you thought this thread was done. Please forgive me if this was previously answered but which functions best with TW5 going forward for line-breaks? br or br/ or something else? I'm wondering if there is any performance differences for each or if anyone knows best practice or what will be the standard? Sent from my Samsung Epic™ 4G Touch Jeremy Ruston jeremy.rus...@gmail.com wrote: I meant to add one key difference between MarkDown and TW5 WikiText; in MarkDown: Note that Markdown formatting syntax is not processed within block-level HTML tags. E.g., you can’t use Markdown-style *emphasis* inside an HTML block. Meanwhile TW5 *does* process wikitext within block-level HTML tags, which I think makes the HTML tag handling much more useful. Best wishes Jeremy On Fri, May 30, 2014 at 8:30 AM, Jeremy Ruston jeremy.rus...@gmail.com wrote: Hi Alex I am in favor of implemented the GFM features, but implementing single line breaks would make it a pain to write HTML in tiddlers. Github does not have this problem since you're not supposed to put HTML in Markdown. Thanks Alex, I did not know that the line break handling isn't part of GFM. HTML has always been part of MarkDown: http://daringfireball.net/projects/markdown/syntax#html Best wishes Jeremy. On Thu, May 29, 2014 at 12:31 PM, Alex V alexverm...@gmail.com wrote: Single line breaks is not part of GFM https://help.github.com/articles/github-flavored-markdown, it is part of the additional features of writing on Github https://help.github.com/articles/writing-on-github. I am in favor of implemented the GFM features, but implementing single line breaks would make it a pain to write HTML in tiddlers. Github does not have this problem since you're not supposed to put HTML in Markdown. On Wednesday, May 28, 2014 12:27:51 PM UTC+2, Jeremy Ruston wrote: TiddlyWiki's paragraph handling is copied from MarkDown, which is becoming a very popular format for online writing. Classic MarkDown treats single line breaks as white space, just like HTML. http://daringfireball.net/projects/markdown/ More recently, GitHub Flavoured MarkDown has gained popularity, which adds (amongst other things) the convention that a single line break produces an HTML br tag: https://help.github.com/articles/github-flavored-markdown The plan is to bring GFM-style linebreak handling to TW5. Best wishes Jeremy. On Wed, May 28, 2014 at 10:14 AM, Kolya kol...@gmail.com wrote: It's a factual standard established by how the majority of online editors work. Another standard is that some people will rather play dumb instead of openly disagreeing. That should sound familiar to you. On Tuesday, 27 May 2014 00:56:28 UTC+2, Stephan Hradek wrote: Am Montag, 26. Mai 2014 16:10:56 UTC+2 schrieb Kolya: There's a standard how webeditors handle linebreaks. Is there? Can you tell me where? I'm really interested. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com. To post to this group, send email to tiddl...@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout. -- Jeremy Ruston mailto:jeremy...@gmail.com -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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
Re: [tw] [TW5] syntax [img[imagefile.jpg]] in node.js
Hi Jeremy, Thank you for the clarification: I look forward to the feature. Best regards, michele On Tue, Jun 3, 2014 at 2:14 PM, Jeremy Ruston jeremy.rus...@gmail.com wrote: Hi Michele I take it that (yet) means there is the plan to support it in the future. Will it be near future? Will the syntax be [img[path/to/local/file]]? Yes, it should be working in the next couple of months. The syntax will definitely use [img[]], and the plan would be to set up the base path so that images can be referenced directly by their tiddler title. Best wishes Jeremy By the way for me also the link syntax a href=file:///home/michele/imagefile.jpgimage/a is not working for me (see https://groups.google.com/d/msg/tiddlywiki/EmJFLV1XAD0/ZL7_W8Jsa18J) Does it work if you link to a http:// website? Yes, a href=http://...;link/a works on 5.0.12 for me. Best regards, michele -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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.
Re: [tw] Re: TW5: Using TW as a musical scratchpad with BopLand.org services?
Who would one go about adding an annotation to the plugin for such a third party license? cheers BJ On Tuesday, June 3, 2014 1:47:18 PM UTC+2, Jeremy Ruston wrote: Hi Måns How frustrating. The license for VexTab definitely prevents us from distributing it under the same licensing terms as TW itself. I think that rules out making it any kind of official plugin that is distributed from tiddlywiki.com. I remain very happy to help if anyone else is interested in creating a widget around vextab. Best wishes Jeremy On Tue, Jun 3, 2014 at 12:04 PM, BJ bugg...@gmail.com javascript: wrote: I'll take a look and see if there is a way to use vexflow on its own. On a first glace it seems that vextab is a compiler that produces scripts for vexflow. BJ On Tuesday, June 3, 2014 12:11:51 PM UTC+2, Måns wrote: Hi TwAfficionados Mohit returned a positive answer yesterday: Mohit: Thanks for the e-mail. I'm okay with someone else building a TiddlyWiki plugin, but I'm not sure that the licenses are compatible. VexTab is free so long as it is not used for commercial purposes and the vexflow.com logo remains visible. If you can annotate your plugins with some text mentioning that this is for non-commercial use only, then I have no problem with it. I'm not sure if it's enough to apply with TW's BSD license - if the plugin is distributed standalone from Github? If Github is used as an official repository for the plugin - and it's not presented as part of an official TW5 package - eg. installed at tiddlywiki.com?? Cheers Måns Mårtensson Den onsdag den 28. maj 2014 18.32.00 UTC+2 skrev Måns: Hi Jeremy You're right, it does present problems if we can't redistribute VexTab under the same BSD license as TiddlyWiki itself. It sounds like it would be worth talking to the author though. Mohit Muthanna (0xFE http://vexflow.com/vextab/) did not answer when I invited him to the Hangout. As you know my first language is far from being English - however I wrote this to Mohit a couple of minutes ago: Hi Mohit Muthanna (0xFE) On the TiddlyWIki mail list/google group we are discussing if we are allowed to create a plugin/redistribute VexTab as a plugin for TiddlyWIki. TiddlyWiki is licensed with BSD. VexFlow is MIT and it should work well with BSD. ... but VexTab however would need some adjustments if we should be able to redistribute it.. Jeremy Ruston, the creator of TiddlyWiki, has shown interest in building a VexTab plugin for TiddlyWiki, live in a Google Hangout - because The API of VexTab is nice and flexible and would be particularly easy to turn into a TW5 widget. I'm a music teacher, a guitarist and a long time TiddlyWiki end user, and I would love to be able to work with musical scores and write chord diagrams directly in my own personal portable wiki which also happens to be a database and a blog like application which is much more versatile than standard word processors like eg. Google Docs or Office Word... Just to name a few. Would you be interested in the making of a plugin for TiddlyWiki? If you are - how do we make it work - regarding the question of license types? Cheers Måns Mårtensson Links: http://tiddlywiki.com https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/nh5vMpPeEvg; Hope it's ok..? Cheers Måns -- Jeremy Ruston mailto:jeremy...@gmail.com 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.
Re: [tw] Re: TW5: Using TW as a musical scratchpad with BopLand.org services?
how would one go about adding an annotation to the plugin for such a third party license? cheers BJ On Tuesday, June 3, 2014 1:47:18 PM UTC+2, Jeremy Ruston wrote: Hi Måns How frustrating. The license for VexTab definitely prevents us from distributing it under the same licensing terms as TW itself. I think that rules out making it any kind of official plugin that is distributed from tiddlywiki.com. I remain very happy to help if anyone else is interested in creating a widget around vextab. Best wishes Jeremy On Tue, Jun 3, 2014 at 12:04 PM, BJ bugg...@gmail.com javascript: wrote: I'll take a look and see if there is a way to use vexflow on its own. On a first glace it seems that vextab is a compiler that produces scripts for vexflow. BJ On Tuesday, June 3, 2014 12:11:51 PM UTC+2, Måns wrote: Hi TwAfficionados Mohit returned a positive answer yesterday: Mohit: Thanks for the e-mail. I'm okay with someone else building a TiddlyWiki plugin, but I'm not sure that the licenses are compatible. VexTab is free so long as it is not used for commercial purposes and the vexflow.com logo remains visible. If you can annotate your plugins with some text mentioning that this is for non-commercial use only, then I have no problem with it. I'm not sure if it's enough to apply with TW's BSD license - if the plugin is distributed standalone from Github? If Github is used as an official repository for the plugin - and it's not presented as part of an official TW5 package - eg. installed at tiddlywiki.com?? Cheers Måns Mårtensson Den onsdag den 28. maj 2014 18.32.00 UTC+2 skrev Måns: Hi Jeremy You're right, it does present problems if we can't redistribute VexTab under the same BSD license as TiddlyWiki itself. It sounds like it would be worth talking to the author though. Mohit Muthanna (0xFE http://vexflow.com/vextab/) did not answer when I invited him to the Hangout. As you know my first language is far from being English - however I wrote this to Mohit a couple of minutes ago: Hi Mohit Muthanna (0xFE) On the TiddlyWIki mail list/google group we are discussing if we are allowed to create a plugin/redistribute VexTab as a plugin for TiddlyWIki. TiddlyWiki is licensed with BSD. VexFlow is MIT and it should work well with BSD. ... but VexTab however would need some adjustments if we should be able to redistribute it.. Jeremy Ruston, the creator of TiddlyWiki, has shown interest in building a VexTab plugin for TiddlyWiki, live in a Google Hangout - because The API of VexTab is nice and flexible and would be particularly easy to turn into a TW5 widget. I'm a music teacher, a guitarist and a long time TiddlyWiki end user, and I would love to be able to work with musical scores and write chord diagrams directly in my own personal portable wiki which also happens to be a database and a blog like application which is much more versatile than standard word processors like eg. Google Docs or Office Word... Just to name a few. Would you be interested in the making of a plugin for TiddlyWiki? If you are - how do we make it work - regarding the question of license types? Cheers Måns Mårtensson Links: http://tiddlywiki.com https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/nh5vMpPeEvg; Hope it's ok..? Cheers Måns -- Jeremy Ruston mailto:jeremy...@gmail.com 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: TiddlyWiki text import in TiddlyWiki format
It works! I changed the extension of the text file from txt to tid, put a title and modifier entry at the top of the file as demonstrated in the link you gave, and then when I imported the files tiddlywiki formatting (such as double brackets around words to specify links) was recognized. Thanks a lot! On Monday, 2 June 2014 09:11:36 UTC-7, Kurt Whittemore wrote: How can I import text files so that they are automatically recognized in the TiddlyWiki format. I know I can drag and drop text files into TiddlyWiki. However, if I have double brackets around a word, the word is not recognized as a link. I can manually change the file type to the TiddlyWiki format, and then the double quotes are recognized as a link. However, how can I set things up so that when I import a collection of text files into TiddlyWiki they are automatically recognized in the TiddlyWiki format? -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] why are these tiddlers created? 1-{-1642131862}
hey everyone, I just upgraded to the newest version, when I imported I noticed a ton of tiddlers in the format above. they all have titles for my tiddlers in them as well. what are these? thanks -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] TiddlyWiki Hangout #48 is about to start
I somehow forgot to post an invitation here, but our regular weekly hangout is kicking off as usual over at: https://plus.google.com/hangouts/_/hoaevent/AP36tYdMMy8ewvJSgkmSIH9QZvWSHNqj_b1eyDFtUYgWC4uqOS0wtQ Best wishes Jeremy -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] The $maketid and $setfield widgets
Thanks for creating widgets to do exactly what I'd been puzzling over! One thing I still can't figure out: Is is possible to create a single button that simultaneously: 1. sets field info AND 2. removes a (specified) tag? Thanks! cmari -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] why are these tiddlers created? 1-{-1642131862}
Hello, I made the same question when I started and people encouraged me to investigate it. I just leaved it apart:-P and I discovered it just some weeks ago. They are state Tiddlers. Any widget that needs a temporary unique place to store information creates that kind of Tiddlers. You can freeley remove them In my opinion it would be better if they are not treated as regular Tiddlers. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] TiddlyWiki Hangout #48 is about to start
Ooooh I missed it. Maybe next week. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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 plugin Preview Search
Hi Ton I noticed that tags are found as well (but not fields). Found tags result in a tiddler without preview. Since tiddlers tagged with a certain tag can be found elsewhere (Sidebar, tab Tags), may be wise to skip the tag results. What do you think?is There are several reasons you can get a result without preview. First let me explain how the widget works. It just searches in a specific tiddler text fields and returns what it finds. If it does find nothing it does not even render the container. I did it that way to maintain it simple and small. The plugin wraps this widget into a search (list widget) , so what you see is the result of both widgets working together. The search operator looks into the text and tags fields while my widget only does it in the first one. That can produce mismatch results. It does not mean any error, it just means that nothing matches the search term in the text field. Other possible cause is that the context widget takes only one search term. It does not split by space like the regular search does. The search term is taken as a whole. This is an intended behavior to maintain a good performance. Anyway there is nothing that stops us to support other scenarios. Other thing that would be easy to implement and maybe can be what average user expects is to show a preview when nothing matches. Maybe the 50 first characters or whatever is specified in the length parameter. Let me know your thoughts -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] The $maketid and $setfield widgets
Knowing that it was possible gave me the fortitude to continue with my
trial-and-error flailing!
I still don't quite understand the pattern for which macro to use first and
when to add which message where, but in case it's helpful for someone else,
here's my working solution to accomplish the following with a single button:
1. set a field
2. set another field
3. add one tag
4. remove another
$setfield set=!!field1 setTo=value1
$setfield set=!!field2 setTo=value2
$mangletags find=oldtag message=tw-set-field
$mangletags add=newtag
$button message=tw-mangle-tagsbutton text here/$button
/$mangletags/$mangletags/$setfield/$setfield
(I haven't included a target because I put this in a tiddler called
MyButton and then use it inside other tiddlers, e.g., {{!!title||MyButton}}
)
This is really helpful - thanks!
cmari
On Tuesday, June 3, 2014 8:42:20 AM UTC-7, Matabele wrote:
Hi cmari
Yes -- using the $setfield and $mangletags widgets available here:
http://gwiz.tiddlyspot.com/
$mangletags find=tag-to-remove
$setfield set=!!field-to-set setTo=value-for-field
message=tw-mangle-tags
$button message=tw-set-field param=target-tiddlerSet/$button
/$setfield/$mangletags
Have a look at the Demos on the site -- the code should give you some
ideas on how to use the widgets. The 'Another Demo', in particular, does
something similar to your needs.
On Tuesday, June 3, 2014 5:26:24 PM UTC+2, cmari wrote:
Thanks for creating widgets to do exactly what I'd been puzzling over!
One thing I still can't figure out: Is is possible to create a single
button that simultaneously:
1. sets field info AND
2. removes a (specified) tag?
Thanks!
cmari
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is there a Widget Guideline ?
Hi Andreas, I am not a developer, just an end-user. Have you see Chris Hunt's guide [1]? According to Jeremy there is a lot of explanation in it. Cheers, Ton [1] http://cjhunt.github.io/ On Tuesday, June 3, 2014 5:16:10 PM UTC+2, Andreas Hahn wrote: Hi, I am more or less new to TW and I may not have a good overview or a good understanding, but there is something I have been wondering about and maybe your answers will help me to deepen my understanding of TW. From what I can tell widgets are a way to enhance WikiText with the goal of displaying content that it would not normally be able to display by default. A good example would be the list widget. Many of these widgets also provide a little bit of functionality that would otherwise not exist. Examples here are the widgets that provide the typical HTML-Form elements like a button, a checkbox/radiobox, textareas, etc.. But I notice that an increasing number of widgets just exist to do a purely functional task which mostly does not involve rendering things or doing something with the child elements of that widget. And most of these are not designed to play exceptionally well together. For example the checkbox widget works on tags, the edit widget on fields. To use them for something else, you usually have to do something extra, like transcluding the field or checking for tags. Also widgets make use of different concepts, the $mangletags widget from Matabele follows his stacking mechanism where high-level functionality is archieved by wrapping AROUND a source element, which propagates the target UP the stack. Other widgets like the core set widgets propagate variables DOWN the stack and are used to provide the necessary parameters for the high-level functionality INSIDE the stack. Some use messages as parameters, others solely rely on their attributes as input. Now my question: Is there a guideline or a core concept which is meant to ensure that widgets work well together ? Are widgets even supposed to work together ? (How will they do this in the future ?) And finally: what was the idea/purpose behind widgets when TW was created ? I would love a short explanation of the more or less theoretical background and concepts of this part of TW. Thanks /Andreas -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is there a Widget Guideline ?
Hi Ton, thank you very much, I found his site previously but I didn't really read it until now, great help, thanks. My question however was a little bit more targeted as to how widget should interact with other widgets in the grand scheme of things, because there is often more than one way of doing it. Take for example the Unix toolchain. All of those tools have a very well defined way of interacting with one another and thats why people like linux terminals, because most of the stuff can be combined pretty easily. /Andreas Am 03.06.2014 19:37, schrieb Ton Gerner: Hi Andreas, I am not a developer, just an end-user. Have you see Chris Hunt's guide [1]? According to Jeremy there is a lot of explanation in it. Cheers, Ton [1] http://cjhunt.github.io/ -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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: Is there a Widget Guideline ?
Hi Andreas, Sorry, I cannot help you further. Guys like Jeremy, Mario, Matabele, ... have to chime in. Cheers, Ton On Tuesday, June 3, 2014 9:07:47 PM UTC+2, Andreas Hahn wrote: Hi Ton, thank you very much, I found his site previously but I didn't really read it until now, great help, thanks. My question however was a little bit more targeted as to how widget should interact with other widgets in the grand scheme of things, because there is often more than one way of doing it. Take for example the Unix toolchain. All of those tools have a very well defined way of interacting with one another and thats why people like linux terminals, because most of the stuff can be combined pretty easily. /Andreas Am 03.06.2014 19:37, schrieb Ton Gerner: Hi Andreas, I am not a developer, just an end-user. Have you see Chris Hunt's guide [1]? According to Jeremy there is a lot of explanation in it. Cheers, Ton [1] http://cjhunt.github.io/ -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] The $maketid and $setfield widgets
Hi cmari
I don't know what you are trying to achieve, but there's also a 'find and
replace' option for the $mangletags widget. Your code using two widgets
will add 'newtag' regardless of whether the tiddler was previously tagged
with 'oldtag' -- with the find and replace option, 'newtag' will be added
only to those tiddlers that were previously tagged 'oldtag'.
The syntax in this case: $mangletags find=oldtag add=newtag
The widgets may be used in any order -- however, the default behaviour in
most cases is to pass on the received message to the next widget in the
stack. it is easier, therefore, to stack widgets of the same type adjacent
to one another -- changing the message only when the widget type changes
(as you have done.) The $maketid widget is the exception, as the
parameter caught by the widget becomes the default for the template
(maintaining compatibility with the standard 'tw-new-tiddler' message) --
and the generated parameter is set to the value of the 'title' attribute.
All of the other widgets pass on the title of the target tiddler as the
parameter to the message by default (unless changed with 'param='), and
pass on the same message by default (unless changed with 'message='.)
Hope this better explains how to use the widgets.
regards
On Tuesday, June 3, 2014 7:33:28 PM UTC+2, cmari wrote:
Knowing that it was possible gave me the fortitude to continue with my
trial-and-error flailing!
I still don't quite understand the pattern for which macro to use first
and when to add which message where, but in case it's helpful for someone
else, here's my working solution to accomplish the following with a single
button:
1. set a field
2. set another field
3. add one tag
4. remove another
$setfield set=!!field1 setTo=value1
$setfield set=!!field2 setTo=value2
$mangletags find=oldtag message=tw-set-field
$mangletags add=newtag
$button message=tw-mangle-tagsbutton text here/$button
/$mangletags/$mangletags/$setfield/$setfield
(I haven't included a target because I put this in a tiddler called
MyButton and then use it inside other tiddlers, e.g., {{!!title||MyButton}}
)
This is really helpful - thanks!
cmari
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Newbie needs help in drafting search code
Super! Works great!
Will take a little work to get everything set up but will really help me in
the long run.
Thanks so much for your help!
R
On Monday, June 2, 2014 4:03:53 PM UTC-4, Danielo Rodríguez wrote:
Yes, it is possible but it would be a bit complex if you are not used to
it.
Each item should be a tiddler.
Take a look at:
http://tiddlywiki.com/#TaskManagementExample:TaskManagementExample
You can have specific list with. Here you will need at least two tags, one
for task and other for task type. Then, you do the master list with just
the tag task.
With your example:
Project A
[x]item 1 tags: task projectA done
[_]item 2 tags: task projectA
[x]item 3 tags: task projectA done
Project B
[_]item 4 tags: task projectB
[x]item 5 tags: task projectB done
[x]item 6 tags: task projectB done
Example for project B list:
$list
filter=[!has[draft.of]tag[task]tag[projectB]!tag[done]sort[title]]
$checkbox tag=done $link to={{!!title}}$view
field=title//$link/$checkbox
/$list
$list filter=[!has[draft.of]tag[task]tag[projectB]
tag[done]sort[title]]
$checkbox tag=done ~~$link to={{!!title}}$view
field=title//$link~~/$checkbox
/$list
Then your just make your master list like:
$list filter=[!has[draft.of]tag[task]!tag[done]sort[title]]
$checkbox tag=done $link to={{!!title}}$view
field=title//$link/$checkbox
/$list
If you have any doubt let me know.
El lunes, 2 de junio de 2014 17:43:01 UTC+2, RickL escribió:
So...is this not possible?
Not enough information?
On Saturday, May 31, 2014 6:38:51 PM UTC-4, RickL wrote:
Not sure about tiddlyspot but will look into it.
Meanwhile, below is an illustration of what I would like.
Project A
[x]item 1
[_]item 2
[x]item 3
Project B
[_]item 4
[x]item 5
[x]item 6
Project C
[x]item 7
[_]item 8
[_]item 9
Formula or code to return the following:
Master Purchase List
[_]item 2
[_]item 4
[_]item 8
[_]item 9
I am using TW 5.0.8 on Chrome; trying to upgrade to the latest 5.0.12
but not having much luck with that either. :)
Is this possible?
On Friday, May 30, 2014 3:55:30 PM UTC-4, Stephan Hradek wrote:
Am Freitag, 30. Mai 2014 16:17:58 UTC+2 schrieb RickL:
I have group of tiddlers for projects, each tagged project.
Each project tiddler contains a list of materials necessary to
complete the project, with a checkbox for each item.
So if you already have that, why not post it on (e.g.) tiddly spot so
that one can play around to help you reach your goal?
I, for example, absolutely hate it, having to set something up which I
*think* is what one described. I prefer to be able to play around with
the real problem to help solve it.
BTW: Is it TWc or TW5?
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email 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: Newbie needs help in drafting search code
You're welcome :-) -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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: Is there a Widget Guideline ?
Hello I think that guide it's a bit outdated or not 100% accurate. It talks about a create function that I didn't see anywhere before. I read it several times and I still not understand the whole TW picture. Maybe it is oriented to more experienced programmers. Regarding the this topic (about widget normalization) I have to admit that the current scenario is a mess. Widgets are small pieces of code that does very specific task and most of them came from different sources. Since there is not an official implementation each one is different. I agree that a standard is needed. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] The $maketid and $setfield widgets
Still a bit confusing to me how the parameter parameter is used. I think I will read the last documentation of your widgets again -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] Updated Classic parser for TW5
I have updated the tw2parser plugin for tw5 v5.0.12 It now supports sections and slices. I have put in a framework for handle the tw2 macro calls and have put in the tabs as well as the slider macro. The code is at https://github.com/buggyj/TiddlyWiki5/tree/tw2parser see the demo: http://twclassic-with-tw5.tiddlyspot.com/ cheers BJ -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: TW5 new plugin Preview Search
Hi Ton I noticed that tags are found as well (but not fields). Found tags result in a tiddler without preview. Since tiddlers tagged with a certain tag can be found elsewhere (Sidebar, tab Tags), may be wise to skip the tag results. What do you think?is There are several reasons you can get a result without preview. First let me explain how the widget works. It just searches in a specific tiddler text fields and returns what it finds. If it does find nothing it does not even render the container. I did it that way to maintain it simple and small. The plugin wraps this widget into a search (list widget) , so what you see is the result of both widgets working together. The search operator looks into the text and tags fields while my widget only does it in the first one. That can produce mismatch results. It does not mean any error, it just means that nothing matches the search term in the text field. Other possible cause is that the context widget takes only one search term. It does not split by space like the regular search does. The search term is taken as a whole. This is an intended behavior to maintain a good performance. Anyway there is nothing that stops us to support other scenarios. Other thing that would be easy to implement and maybe can be what average user expects is to show a preview when nothing matches. Maybe the 50 first characters or whatever is specified in the length parameter. Let me know your thoughts -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] Updated Classic parser for TW5
Hi BJ Superb, very happy to see this. I'd welcome a pull request when you're ready. Best wishes Jeremy On Tue, Jun 3, 2014 at 8:57 PM, BJ buggy...@gmail.com wrote: I have updated the tw2parser plugin for tw5 v5.0.12 It now supports sections and slices. I have put in a framework for handle the tw2 macro calls and have put in the tabs as well as the slider macro. The code is at https://github.com/buggyj/TiddlyWiki5/tree/tw2parser see the demo: http://twclassic-with-tw5.tiddlyspot.com/ cheers BJ -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] The $maketid and $setfield widgets
Hi Danielo Looks like I should write some documentation on how the title of the target tiddler is passed through the stack -- when I've worked it out myself I shall do so :-) In general, the parameter to the received message is understood by the widgets to represent the title of the target tiddler -- the exception is the $maketid widget, which understands the parameter to the 'tw-new-tiddler' message to represent the template (this, to maintain compatibility with the standard message.) Unless the user overrides this default value for the parameter with the 'param=' attribute, the same value will be passed on to the next widget in the stack -- this is the case even if the message is changed with the 'message=' attribute. I think I now have all of the widgets working correctly with this scheme. regards On Tuesday, June 3, 2014 9:51:15 PM UTC+2, Danielo Rodríguez wrote: Still a bit confusing to me how the parameter parameter is used. I think I will read the last documentation of your widgets again -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] Is there a Widget Guideline ?
Hi Andreas Good questions, I'll try to write up some more docs and a longer reply over the next couple of days. Many thanks, Jeremy -- Jeremy Ruston jeremy.rus...@gmail.com On 3 Jun 2014, at 16:16, Andreas Hahn www.gal...@googlemail.com wrote: Hi, I am more or less new to TW and I may not have a good overview or a good understanding, but there is something I have been wondering about and maybe your answers will help me to deepen my understanding of TW. From what I can tell widgets are a way to enhance WikiText with the goal of displaying content that it would not normally be able to display by default. A good example would be the list widget. Many of these widgets also provide a little bit of functionality that would otherwise not exist. Examples here are the widgets that provide the typical HTML-Form elements like a button, a checkbox/radiobox, textareas, etc.. But I notice that an increasing number of widgets just exist to do a purely functional task which mostly does not involve rendering things or doing something with the child elements of that widget. And most of these are not designed to play exceptionally well together. For example the checkbox widget works on tags, the edit widget on fields. To use them for something else, you usually have to do something extra, like transcluding the field or checking for tags. Also widgets make use of different concepts, the $mangletags widget from Matabele follows his stacking mechanism where high-level functionality is archieved by wrapping AROUND a source element, which propagates the target UP the stack. Other widgets like the core set widgets propagate variables DOWN the stack and are used to provide the necessary parameters for the high-level functionality INSIDE the stack. Some use messages as parameters, others solely rely on their attributes as input. Now my question: Is there a guideline or a core concept which is meant to ensure that widgets work well together ? Are widgets even supposed to work together ? (How will they do this in the future ?) And finally: what was the idea/purpose behind widgets when TW was created ? I would love a short explanation of the more or less theoretical background and concepts of this part of TW. Thanks /Andreas -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email 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] The $maketid and $setfield widgets
Thanks for that explanation - very helpful! Thanks also for the reminder
about the find and replace possibility. My solution evolved from one in
which I had figured out how to use setfield to add a tag - so I had that
piece already and was really focusing on shoehorning in tag removal. Now
that I've eliminated an entire $mangletags the whole thing is even more
satisfyingly elegant
cmari
On Tuesday, June 3, 2014 12:14:13 PM UTC-7, Matabele wrote:
Hi cmari
I don't know what you are trying to achieve, but there's also a 'find and
replace' option for the $mangletags widget. Your code using two widgets
will add 'newtag' regardless of whether the tiddler was previously tagged
with 'oldtag' -- with the find and replace option, 'newtag' will be added
only to those tiddlers that were previously tagged 'oldtag'.
The syntax in this case: $mangletags find=oldtag add=newtag
The widgets may be used in any order -- however, the default behaviour in
most cases is to pass on the received message to the next widget in the
stack. it is easier, therefore, to stack widgets of the same type adjacent
to one another -- changing the message only when the widget type changes
(as you have done.) The $maketid widget is the exception, as the
parameter caught by the widget becomes the default for the template
(maintaining compatibility with the standard 'tw-new-tiddler' message) --
and the generated parameter is set to the value of the 'title' attribute.
All of the other widgets pass on the title of the target tiddler as the
parameter to the message by default (unless changed with 'param='), and
pass on the same message by default (unless changed with 'message='.)
Hope this better explains how to use the widgets.
regards
On Tuesday, June 3, 2014 7:33:28 PM UTC+2, cmari wrote:
Knowing that it was possible gave me the fortitude to continue with my
trial-and-error flailing!
I still don't quite understand the pattern for which macro to use first
and when to add which message where, but in case it's helpful for someone
else, here's my working solution to accomplish the following with a single
button:
1. set a field
2. set another field
3. add one tag
4. remove another
$setfield set=!!field1 setTo=value1
$setfield set=!!field2 setTo=value2
$mangletags find=oldtag message=tw-set-field
$mangletags add=newtag
$button message=tw-mangle-tagsbutton text here/$button
/$mangletags/$mangletags/$setfield/$setfield
(I haven't included a target because I put this in a tiddler called
MyButton and then use it inside other tiddlers, e.g., {{!!title||MyButton}}
)
This is really helpful - thanks!
cmari
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
