Thank you. I am much relieved. I would not have looked forward to having
every file in my git repository touched, and to have all of the tiddlers'
text bodies crammed into one line.
On Saturday, July 24, 2021 at 4:36:50 PM UTC-4 saq.i...@gmail.com wrote:
> Hi Flibbles,
>
> No significant
Hi Flibbles,
No significant changes to saving no node.js. Currently tiddlers of type
text/vnd.tiddlywiki are saved as .tid, files unless they have mutliline
fields in which case those tiddlers are saved as .json files. This will
remain the same with the addendum that a tiddler with field names
Hey all,
Question: Is this going to impact the way NodeJS servers saves tiddlers to
file? Will they no longer be .tid files, and maybe be .json files instead?
-Flibbles
On Friday, July 23, 2021 at 9:53:46 PM UTC-4 TW Tones wrote:
> Springer,
>
> From a design perspective for column headings I
Springer,
>From a design perspective for column headings I would stick to a standard
fields such as column-heading with the value"" on a tiddler called
"tennis", or as the case may be a sport tiddler.
Already dynamic tables support alternate column names in a standard
field/value and there
Hi,
There was no offence intended in my last post. Your tests are good and you
already discovered a problem, that would have caused a severe problem in
production, if you hadn't found it. ... So -- well done!
What I wanted to say is that we need to test all kind of filter operators,
that can
Mario,
Thanks for the bracket fix! (I should have caught that, but was getting
bleary-eyed.)
When you say, "you mainly test with tiddler titles, and not fields. Even if
you have strange field names...," I'm not sure what you mean. I have
focused mostly on having strange field names that
Hi,
Nice tests, but you mainly test with tiddler titles, and not fields. Even
if you have strange field names in your tiddlers.
https://springerspandrel.github.io/tw/new-json-tw-experiment.html#Show%20related%20field-table%20(ViewTemplate)
.. The filter is probably broken, because the number
Springer,
I totally agree, we need to prepare for any ungainly titles and fieldnames.
I suppose my point is to not to abuse this and restate the value of keeping
a limited set of naming rules when developing macros and plugins. Basically
proposing the use of Okams razor. The rules are meant to
Jeremy and all,
I've played around with the updated prerelease file, starting by importing
all the tiddlers from the "broken" version. So far, saves on github are
going fine.
Only one (!) major glitch. If you name a field with a double-angle-bracket
expression (Who would do such a thing?!),
> On 21 Jul 2021, at 21:11, Saq Imtiaz wrote:
>
> I believe this check for field names is the cause:
>
> https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606
>
>
Tones and Mario,
For public-facing projects, being able to name tiddlers with natural
language expressions (including spaces) has been essential, and it seems
much of the expanded power of fields in 5.2.0 will come from scanning for
matches between field names and tiddler titles.
(Emojis and
Mario,
I am glad someone concurs. For me with my de facto standards and the new
freedom, if a field name looks like a tiddler title it possibly is.
Do you think many ancient and / or unsupported plugins will break?,. if
they use fields even extensively the issue will only be if they are used
On Thursday, July 22, 2021 at 3:24:54 AM UTC+2 TW Tones wrote:
> However am I the only one who still intends to keep field names to a
> defacto naming standard such as i-am-afield no caps or spaces? so It is
> easy for me to tell field names apart from text and titles!
>
No -- you are not.
I am glad you are onto this bug, spaces in fieldnames,
However am I the only one who still intends to keep field names to a
defacto naming standard such as i-am-afield no caps or spaces? so It is
easy for me to tell field names apart from text and titles!
Of course I look forward to naming
I believe this check for field names is the cause:
https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606
On Wednesday, July 21, 2021 at 9:34:54 PM UTC+2 Saq Imtiaz wrote:
> @Jeremy regarding this bug, I think it is related to having a space
>
@Jeremy regarding this bug, I think it is related to having a space
character in a field name.
At https://tiddlywiki.com/prerelease/empty.html
Create a new tiddler called "test" with a field name "my field" with a
value of "hello".
Save and open the resultant file.
You get a blank white
Since I need to be away for a while, and in case it's helpful, here's a
link to the entire json segment (copied from "inspect" tool from crash
window):
https://www.dropbox.com/s/8h1nb4z3npl6odj/json-store-from-crash.json?dl=0
Oddly, I can drag this whole json file onto the official
No red screen! Just "poof" no tiddlywiki interface.
But here's one clue: I tried exporting a json set of tiddlers from the
non-crash "early" version (which you can load at url above), and THAT json
export file, when re-imported, yields an error that suggests the dynamic
table's json entry
I don't have the opportunity to debug this at the moment but I believe this
is the commit responsible:
https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265
Seems like the boot process just
Jeremy and all: I "broke" the pre-release this morning, recklessly pushing
the limits with field-names (saving on github).
Alas, it's not easy for me to reconstruct what the last straw was. I don't
know how to restore (to the most recent non-broken version) with github, so
as to retrace the
20 matches
Mail list logo
