[twdev] Re: Custom markup (continued 3)

TT et al, Word of the day? "Nomenclature " The easiest way I could describe it is "*Private Shorthand Supporting > Public Messaging*". > > One advantage we have both by design and by circumstance is TiddlyWiki produces its results via f

[twdev] [TW5 Plugin] JsonMangler v2.2.3 Released!

This release ads two new filter operators: "comparefield[]" and "compareindex[]" operators that function as "compare[]" on a specific field or index. The first prefix is now the field or index name. See the help documentation in the example wiki. Requires TiddlyWiki v5.1.23-pre I now have a ne

[twdev] Re: Writing Forms (not HTML forms, ways of writing)

Right. The very freedom has slashed the throat of slow evolution. Visual design potentials got over DIVORCED from meaning. So we have exciting visuals, for what? I do think its interesting to look back to perfectly viable systems where the pen had to handle both content AND form simultaneously

[twdev] Re: Writing Forms (not HTML forms, ways of writing)

Hi, That's a very interesting topic. Printing books has been developed and improved since about 500 years. .. HTML and the internet was able to "destroy" it in 20 years. .. In the last may be 10 years the standardizing groups try to implement elements from "printed media" into "web media" We g

[twdev] Re: Writing Forms (not HTML forms, ways of writing)

Hi, It's still possible to create a ::first-letter in CSS. See: https://developer.mozilla.org/en-US/docs/Web/CSS/::first-letter Especially the variant h2 + p::first-letter {} is very interesting. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev"

[twdev] Re: Custom markup (continued 3)

PMario and all I been thinking about all this. Especially markup symbols. Looking back at Gruber 2004. At that time you were stuck visually on glyphs between a rock & a hard place. We are no longer so constrained. MY POINT? Let us ensure we are VISUALLY free on markup symbols, not get stuck

[twdev] Re: Exclude files from build

Yes, but that did not work either unfortunately. Guess I will have to stick with moving .fslckout in and out of that directory... On Friday, September 25, 2020 at 5:24:39 PM UTC saq.i...@gmail.com wrote: > Have you tried setting a *directories* entry in the tiddlywiki.files > file, with a *file

[twdev] Writing Forms (not HTML forms, ways of writing)

Lot of the time here we deal in housekeeping -- developing necessary code work to be able to write what we want as we want it. Yet we seem bad at exposing what it is for. End products. I am very interested in writing forms. Modernist writing style for instance (already 100+ years old); playing

[twdev] Re: Custom markup (continued 3)

On Saturday, September 26, 2020 at 1:33:40 PM UTC+2, @TiddlyTweeter wrote: Quick point. In my USE CASE I'm interested in using CSS classes AS the > "code" / shorthand (actual end-user text is inserted via CSS *::before *) > . The user would see NO comprehensible text at all if they opened a Tidd

[twdev] Re: Custom markup (continued 3)

On Saturday, September 26, 2020 at 3:28:40 AM UTC+2, TonyM wrote: 2. Setting and using evaluated variables > \customize tick=ghost _element="$set" name=ghost > filter="""[all[current]addprefix[$:/ghost/]]""" _endString="/ghost" > > ´ghost <> > > And <> the value is here > > <$set name=new-var val

[twdev] Re: Custom markup (continued 3)

PMario & Friends The implications of The Tool are freeing, whilst also complex and diverse. IN PARTICULAR the easier use of CSS could lead to what PMario identified as a potential TOWER OF BABEL. In my own case I recognize the need for a decent way of thinking CSS class naming through (there w

[twdev] Re: Custom markup (continued 3)

TonyM (& PMario) TonyM wrote: > > Readability in programming languages has often simply come from a body of > work. You can write code in short or long ways. I imagin you choose > depending on the audience. For example your own shortcuts where at *most > *others > view the results can be as br