Delayed reaction, I stepped away from this and came back to it. Works
awesome. Thank you Mark!
On Thursday, November 21, 2019 at 8:40:46 AM UTC-6, Mark S. wrote:
>
> <$vars now=<> lb="[[" pipe="|" rb="]]">
> {{{ [[sources]addprefixaddsuffixaddsuffixaddsuffix] }}}
>
>
> On Thursday, November 21,
Hello ,
I have a data-tiddler called posologies in the form of :
formulaOne : thisProduct : 3, thatProduct : 12, anotherProduct : 6
formulaTwo : thisProduct : 8, aProduct : 4, strangeProduct : 3,
smallProduct : 3
formulaThree : anotherProduct : 9, thisProduct : 6
...
it references posologies
Hi TiddlyWiki-Community
I am new here and eager to learn.
*Goal*: For my private wiki (knowledge base) I want to manage my still open
questions spread all over serveral different tiddlers.
To mark something as an open question, I defined a macro like this
\define open-question(text:"none")
springer:
> If someone asks "How much trouble is it to go through and put brackets
>> around all the key terms after you paste?" that person is probably not
>> working in front of a live audience (where that audience is not there to
>> get TiddlyWiki lessons).
>>
>
Mark S. wrote:
>
On Monday, January 6, 2020 at 3:40:25 AM UTC-8, Rolf Sonderegger wrote:
>
> I am new here and eager to learn.
>
Welcome!
> *Goal*: For my private wiki (knowledge base) I want to manage my still
> open questions spread all over serveral different tiddlers.
> To mark something as an open
>
> *Goal*: For my private wiki (knowledge base) I want to manage my still
>> open questions spread all over serveral different tiddlers.
>>
>> As you've discovered, the backlinks[] filter doesn't work the way you
> want.
>
> But, as you stated, your goal is to find tiddlers that are *using*
Wouldn't this greatly increase overhead? In TW, each tiddler has it's own
collection of fields, and those fields may be used independently of any
other tiddler.
So "mylist" in one tiddler might be a standard title list field, but in
another tiddler it might be a CSV list of work contacts
Hello Associates,
Any available local consultants for LEAD Salesforce Developer . I have an
excellent project with my client in Boston, MA.
*Please send your resume to **fah...@mirthconsulting.net*
* for the below positions.*
Job Title: LEAD Salesforce Developer
Location:
Hi Bimlas
> I think that besides being able to read these settings, they should be
> adjustable. For example, if I want to use a custom macro instead of
> "<>", which can open all tiddlers, I simply replace the template in the
> "tags" field definition with a macro I want.
It sounds like
*Another experimental commander-ii is up*
Commander 2.0.1 beta
Selective and non-selective operations
https://github.com/kookma/TW-Commander/tree/commande-ii
1. Go to https://github.com/kookma/TW-Commander/tree/commande-ii
2. Clone or download to your computer
3. Open the
OK, all. I have mentioned that in the classroom my students see lots of
TiddlyWiki; I freely navigate links, on the big screen, to pull up relevant
bits during discussion.
But I'm also a kind of database nerd. In my office I work out of FileMaker.
FileMaker is the "back end" of what I do in
Sean,
Evans solution https://evanbalster.com/tiddlywiki/formulas.html has the
full set of functions to use sophisticated spreadsheet calculations.
However when using a range you need to consider how your data is organised.
I currently print sophisticated tables via open in new window (Although
Hi bimlas,
Regarding your example:
> For example, if I want to use a custom macro instead of "<>", which
> can open all tiddlers, I simply replace the template in the "tags" field
> definition with a macro I want.
>
I once made a plugin to get my own template working with tags ... took me 8
Folks,
I believe it is in a case like this, where we are trying to push a little
more sophistication into tiddlywiki where the use of Google Groups starts
to show its limitations.
Perhaps some kind of online hangout where we can present and review each
others approaches and increase
Mark et al,
Field definitions field-types and macros can provision sophisticated by
easy to use field without any core change or the use of Javascript. We
already have all the tools available in tiddlywiki, I am building my own
solution but a community developed defacto standard would have
MarkS,
I understand what you mean and you are right that the same field may
contain completely different data.
*Having to* include all that meta data for every tiddler would bloat TW
> even more, which already has ~100 bytes of overhead per tiddler.
I imagine the template is *optional*: for
You have a good understanding of the different approaches. One thing to
note is that native-Tiddlywiki syntax can only understand "flat" (1 level
deep) JSON structure.
Being able to proccess large-data-sets from other data-management
structures i one of the reasons I made the "JsonMangler"
Hi Joshua, thanks for your reply. The JsonMangler sounds impressive!
I suspect that (at least for now) flat table (vanilla) functionality is
fine, since I still do all my relational database work in FileMaker.
What I would really benefit from is some kind of walkthrough of a very
basic JSON
For email readers: post edited
Is there any way to distinguish between user field and system field?
Assume you have several tiddlers tagged with x and have fields
- system fields like: title, tags, type, text, ...
- user fields like: myfield, yourfield, ... [those created by user NOT
Is there any way to distinguish between user field and system field?
Assume you have a tiddler called tidA
- system fields like: title, tags, type, text, ...
- user fields like: myfield, yourfield, ... [those created by user NOT
Tiddlywiki
And then
<$list
Hi Josiah,
I am starting to implement your proposed configuration!
Please lets me know more details!
- mg is implemented
- m OR g has been implemented
Do we need the first match?
Any other flags useful here?
I also try to make the interface simple! Newbies should be able to perform
21 matches
Mail list logo
