Mohammad,
So what about yammer is not free and the content is open and exportable. I am
not even asked about this except once.
That can not be the explanation in my view.
Tony
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe
Tony,
I understood people like a free and open host like google forum.
-Mohammad
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I have not used Bob yet, but I see it has the same tiddlers-as-files support
that TiddlyServer does. Theres nothing stopping you from "expanding" a plugin
tiddler (make non-shadow copies of all the shadow tiddlers) in vanilla
tiddlywiki.
Back up your data!
Apparently, the easiest way to
Example Yammer Integration
Post Yammer messages with new GitHub commits
Make sure everyone knows what's going on with development, even if they're
not checking GitHub, by setting up this automation to post about it. Every
new commit on GitHub will trigger this Zap, posting a new message on
Mohammad,
You tell me the answer to your Question. I built Yammer
at https://www.yammer.com/tiddlywiki/
But even with 25+ people joining only a few even tried to have a
conversation, with this tool.
We do not even have the community involvement to discuss its pros and cons
I suggested it is
Folks,
I believe I have argued it in the past, but I would like to offer my
opinion that you should not use prefixes on tags to represent what they
mean.
Apart from anything you are breaking database normalisation rules by
making an attribute of an object be part of the key to the object,
Thank you so much for all you do and for the reply - it's nice to know!!
For anyone else having problems - my workaround:
I use tmux inside the docker container to start two instances of the nodejs
server using the same wiki folder (obviously) but having two ports - one
with the 'anon' and
Mark,
Love it.
If as I hope Bimlas's Kin operator becomes part of the core, you could use
the kin operator to find the parents of this "backlinks" field, or for that
matter any other kin relationship. The field should be a title list
allowing multiple references such that if transcluded in
Olegh,
That looks good and it should be practical in many cases?
Tony
On Thursday, December 13, 2018 at 2:24:32 AM UTC+11, oleghbond wrote:
>
> Having based on the core macros:
>
> <>
>
> I redesigned macros for setting (anchoring), showing (referencing) and
> listing artifacts:
>
> <>
> <>
>
Idea #665
Modify excision so that when the new tiddler is made, it has a "backlinks"
field pointing to the tiddler from which it was excised. Modify the search
routine to add the backlinks field to the output list. Possibly each time
an excision occurs, add to the backlinks field, so all
Olegh,
See the tabbed internal
TOC,
https://tiddlywiki.com/#Example%20Table%20of%20Contents%3A%20Tabbed%20Internal
defined here $:/core/macros/toc
The above provides some background to marks helpful example
outlier
https://groups.google.com/forum/#!msg/tiddlywiki/ol_3zvGPbk8/-EdORwtrBAAJ
Folks,
Speculation
Would it be posible to export a fully wikified tiddlywiki to a file, a bit like
an index file, then use search in that file to identify the target tiddlers
with rendered content? Is the static html version like this?
Now somehow intergrate this with the original wiki so
Hi Mark
> Running it all the time would be resource-intensive, for sure.
>
> But what about a tool that renders all the tiddlers ON DEMAND with a title
> like $:/rendered/ with a tag "rendered" and the original title in the
> caption field. Before the tools runs, it would delete existing items
Running it all the time would be resource-intensive, for sure.
But what about a tool that renders all the tiddlers ON DEMAND with a title
like $:/rendered/ with a tag "rendered" and the original title in
the caption field. Before the tools runs, it would delete existing items
tagged as
> I'm wondering whether an option could be added to the search operator
> allowing to search a "wikified" version of the text (or the field) of a
> tiddler.
It's an interesting idea, and I'm sure worth some experimentation but there is
a substantial performance issue in having to wikify all
Hi Tony, Mohammad & Ton,
sorry for my late answer...
I think, I mean a different thing.
I *don't* have a "normal" static table like
|head1|head2|head3|
|cell1|cell2|cell3|
*But I generated a table with the formula plugin
(https://evanbalster.com/tiddlywiki/formulas.html
Tony,
I'd be interested to have a look at your modified TOC approach.
It is also my understanding that AUTOREF has to be based on passing all the
tiddlers involved according to the TOC order. But instead of revealing the
tiddler titles (as TOC does) AUTOREF has to build indexes of artifacts
Hi S.S
Look at
https://kookma.github.io/Reveal-Gradually/
See how wizard and steps work!
To see a smooth navigation set animation duration in control panel to zero.
BTW, I want to thank you for your great efforts on beginner guide!
- Mohammad
On Sunday, December 16, 2018 at 7:42:56 PM
@TiddlyTweeter wrote:
>
> Ciao Riz
>
> Some time ago you made for me a neat system (later refined by Mark S.)
> which auto-adds tags based on save on IN-LINE words.
>
> The specific use-case was I post to #Twitter. Any in-line #hastagged word
> would get auto added as a tag to a Tiddler on save.
Hi,
I'm wondering whether an option could be added to the search operator
allowing to search a "wikified" version of the text (or the field) of a
tiddler.
The change in the code could be in the search function that lives in
wiki.js. The field that is to be searched could be wikified before the
Hi Donald
Thanks, I’m afraid this turns out to be a bug introduced late in v5.1.18:
https://github.com/Jermolene/TiddlyWiki5/issues/3647
I’ll include a fix as part of v5.1.19 shortly,
Best wishes
Jeremy
> On 16 Dec 2018, at 11:39, Donald Coates wrote:
>
> Hello all and thank you for all
Hi Simon,
thanks a lot, what enormous speed...and it works perfect.
It is interesting that now to close the modal with the tm-close-tiddler
with the same click, this commant has to be outside:
<$button>
<$navigator story="$:/StoryList" history="$:/HistoryList">
<$action-navigate
Ha! You're right of course. I did not notice! The scrolling out of the ToC
tiddler threw me. Thank you.
I wonder how a beginner will deal with that. Will it confuse them too? I
don't know.
I also notice now that EVERY link clicked in tiddlers in theToC's view
pane - opens within the view
Hi Jan, Jeremy recently mentioned that this worked before, without adding
anything...
but at the moment, you'd need to add a navigator widget pointing to the
story and history:
<$navigator story="$:/StoryList" history="$:/HistoryList">
<$button>
<$action-navigate
Hello,
I made a modal with a button which is using the widget message
tm-edit-tiddler.
<$button>
<$action-navigate $to={{$:/temp/patternname}}/>
<$action-sendmessage $message="tm-edit-tiddler"
$param={{$:/temp/patternname}}/>
<$action-sendmessage $message="tm-close-tiddler"/>
selber machen
Coming back again :o)
I believe we've both been mislead by the scrolling behavior of the story
river
try closing all tiddlers but the one containing the ToC - I think your
links work well!
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To
Hi, coming back to this - I've realized it's much easier!
The toc-tabbed-internal-nav macro catches navigation messages so that links
are opened within the ToC
I changed your Next-link to a button:
<$button class="tc-btn-invisible tc-tiddlylink"actions="""<$action-navigate
$to="Some of the
Hi S.S.
> Some weeks back, I began working on a tutorial for tiddlywiki.com's
> documentation to show beginners how to make a Table of Contents. To do this
> effectively, I realized quite a few other concepts and info need to be
> presented at a beginners' level.
>
> I have this feeling that
Some weeks back, I began working on a tutorial for tiddlywiki.com's
documentation to show beginner's how to make a Table of Contents. To do
this effectively, I realized quite a few other concepts and info need to be
presented at a beginner's level.
I have this feeling that an effective way
Caro Bimlas
You recent work on "kin" is very interesting for how to emerge local, wiki
specific workable TAXONOMIES.
In the root space of taggery history was I think a false debate between
"flat" taggery (the main system used now on web) and "world-order"
hierarchy taxonomy... dating back to
Ciao Riz
Some time ago you made for me a neat system (later refined by Mark S.)
which auto-adds tags based on save on IN-LINE words.
The specific use-case was I post to #Twitter. Any in-line #hastagged word
would get auto added as a tag to a Tiddler on save. Very neat. For those I
never need
> I like the way this discussion is shaping up. May be a plugin could be
> written to ignore a set of characters like "@", "#" etc appearing in the
> begining of tag pill, so that user can use them safely to denote different
> branches of their organization system.
>
> sincerely
> Riz
>
It
The save plugin as a folder feature is still pretty experimental. I
probably shouldn't have actually released it yet. I made that feature when
I was planning on doing more work on it but then decided to take a break
from the development instead and since I came back I have been focusing on
Hi Jed
I'm a lurker that's just surfacing now. I've recently started using the
Bob plugin, which I really like - it seems like it will make a lot of
things more convenient, and some others possible. Thank you for your hard
work on this and your willingness to share it.
I have several wikis,
Hello all and thank you for all your hard work!
I am running tiddlywiki 5.1.18 on node inside docker. when I start the
server with
tiddlywiki myserver --listen host=0.0.0.0 port=9067 "readers=(anon)" writers
=joe username=joe password=joe
I am taken to the appropriate page without the ability
S. S. wrote:
>
> So RANDOMLY - without putting much thought into what symbol to prefix the
> tags ...
>
> Keywords? How about starting those with : *#my-keyword*
> Category? How about : *@my-category*
> Topic? How about: *!topic*
> Keeping track of excised data?: *^Parent-Tiddler-Name*
>
36 matches
Mail list logo
