Hi Mat,
I believe, what we eventually want or need is a csv (multi-)tid serializer
for the core, i.e. another option to export one or more tiddlers and then
the appropriate import handler.
Best wishes,
Tobias.
--
You received this message because you are subscribed to the Google Groups
Thank you Jeremy! It is a present for me. I don't understand why text
field has name "description" and how to export all tiddlers to excel? Now
I use excel macros to convert xlsx to html, but your plugin looks better.
понедельник, 24 октября 2016 г., 1:29:46 UTC+3 пользователь Jeremy Ruston
Steve,
I'll have to have a look later, sounds like you have done the majority of
the required stuff though.
As you say node.js should resolve the continual re-importing issue.
I think in terms of using TW as a report writing system this is great, but
the really sticky point after that is how to
Is there any way to make the """.""" work for transclusions?
I have several tiddlers in wish I would like to includesome fields content;
I currently end up using bullet points as a quick way to make hard line
breaks, but being able to do so automatically would save a whole lot of
trouble.
I do have a tool for CSV here:
https://groups.google.com/d/msg/tiddlywiki/qabE7I41Hos/SnHShTZsBgAJ
Think I've written a more automatic version, but don't have time to sift
through my files at the moment.
Good luck!
Mark
On Sunday, October 23, 2016 at 10:29:49 AM UTC-7, Mark Heptinstall wrote:
Hi Mark,
I made a pull request with a change that will help with the issue:
*allows to specify state qualifier for tag popups*
https://github.com/Jermolene/TiddlyWiki5/pull/2628
However, imho, the solution it implements shouldn't be needed,
for the above mentioned reasons:
*For a given
Hi Mark,
Thanks, though the tags still have the same behavior where clicking one
> causes the tag window to open on all tags of that type in the list. Any
> ideas?
>
The problem here is that all instances of $:/core/ui/TagTemplate use the
same state.
To me, this is how TiddlyWiki should and
Hi Mark,
I agree with PMario, you nailed that just about right.
I would think of fields as a more flexible container for tag-like
structures. In other words, with your custom fields you can have as many
related lists as you want, without cluttering the main tags.
You could then show those
Hi Attila,
I believe you are confusing the documentation for those macros and the
macros themselves. ;-)
Simply start using them as documented on TiddlyWiki.com.
Best wishes,
Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To
On Sunday, October 23, 2016 at 6:00:19 PM UTC+1, stevesuny wrote:
>
> Hi Mark,
>
> I don't believe Eric's #CreateTiddlersFromCSV has been implemented in TW5.
>
> My working solution is to three-step it: (1) Create CSV (2) Convert CSV to
> JSON (best tool:
Hi David,
Just want to be sure you saw that the latest pre-release has a preliminary
bibtex plugin that imports a bib file and puts each reference into a
tiddler; the bibtex id becomes the tiddler name. I'm working on macros to
allow referencing of citations within tiddlers, and generation of a
Mark, you are running into issues involving "state", which I have trouble
with as well.
And, while I'm more-or-less confident the answer is in one of these tiddlers
http://tiddlywiki.com/#StateMechanism:StateMechanism%20%5B%5Bqualify%20Macro%5D%5D%20%5B%5Bqualify%20Macro%20(Examples)%5D%5D
I
Hello all,
I'm in the process of a full redesign of my TW work environment. I've
gotten tired of having a few things in node.js (just learning), having some
in github, and some stuff in dropbox. Sometimes using tiddlydesktop, mostly
using Firefox for writing and Chrome for reading. So, a
On Friday, January 8, 2016 at 10:07:14 PM UTC, Eric Shulman wrote:
>
>
>> I did exactly that for TWClassic:
>http://www.tiddlytools.com/#CreateTiddlersFromCSV
>
> This was implemented as wikitext + HTML and all of the real work is in
> the HTML code, using onclick handlers. You can
On Sunday, October 23, 2016 at 3:27:38 PM UTC+2, Mark Heptinstall wrote:
>
> I would be interested to hear how other users are using tags and fields in
> their TiddlyWiki's?
>
> In my mind they can both achieve the same thing though I'm thinking tags
> are more useful for grouping based on the
I would be interested to hear how other users are using tags and fields in
their TiddlyWiki's?
In my mind they can both achieve the same thing though I'm thinking tags
are more useful for grouping based on the content of a tiddler, whereas
fields are more properties of a tiddler regardless of
Thanks, though the tags still have the same behavior where clicking one
causes the tag window to open on all tags of that type in the list. Any
ideas?
On Sunday, October 23, 2016 at 11:07:01 AM UTC+1, Tobias Beer wrote:
>
> Hi Mark,
>
> Try using actual ULs and LIs:
>
>
> <$list
Hi Tobias & Mat!
Thank you for your help guys.
So, the <> macro is working. Answer: 5.1.13 :-) But this is the
first one, what is working on my Tiddlys. - Thank's Mat.
I try to do a fresh start:
1. I downloaded the tiddler form the homepage. - Getting Started tiddler,
the I used the
@Mark = A neat idea that simply had not occured to me.
@Tobias = An elegant solution.
Thank you both!
On Sunday, October 23, 2016 at 6:07:01 AM UTC-4, Tobias Beer wrote:
>
> Hi Mark,
>
> Try using actual ULs and LIs:
>
>
> <$list filter="[tag[Learning]]">
>
> <$link to={{!!title}}><$view
Hi Mark,
Try using actual ULs and LIs:
<$list filter="[tag[Learning]]">
<$link to={{!!title}}><$view field="title"/>
<$list filter="[all[current]tags[]![Reports]sort[]]"
template="$:/core/ui/TagTemplate">
Best wishes,
Tobias.
--
You received this message because you are subscribed to
I am trying to create a list of links that contain a filtered list of tags
next to them, this is what I have tried so far:
<$list filter="[tag[Reports]]">
* <$link to={{!!title}}><$view field="title"/> <$list
filter="[all[current]tags[]![Reports]sort[]]"
template="$:/core/ui/TagTemplate">
Thanks Tobias!
>
> - When switching from one device to the other (note that most devices
>> stay up even when I'm working on another one), I often need to restart the
>> nodejs server, otherwise it does not seem to be seeing the changes that
>> DropBox pushed to the folder in the mean time;
22 matches
Mail list logo
