[twdev] Re: Adding client-specific appearance tweaks panel under Control Panel -> Appearance

donmor, Thanks for continuing development on tiddloid. It is a valuable contribution. I was wondering if you are joining us on discourse?. I would like to initiate a private conversation on something that may be of interest and it would be easier over there because we can avoid emails.

[twdev] Re: Tiddloid - A new android editor is to be released

Donmor, Please see if you can get this into a store and charge a few bucks so we can return something for your effort. Even if you leave the apks for the poorer amongst us :) Love your work Tones On Monday, 10 May 2021 at 09:36:36 UTC+10 donmor3000 wrote: > A new version (1.4.0) is coming.

[twdev] Re: Custom markup (continued 4)

TT, Here is a summary of the existing glyphs I established this with this site https://unicode-table.com/en/ Latin-1 Supplement › Acute Accent ´ tick ´ Acute Accent U+00B4 Latin-1 Supplement › Degree Sign ° ° Degree Sign U+00B0 Small Form Variants › Small Left Parenthesis ﹙ ﹙ Small Left

[twdev] Re: Custom markup (continued 4)

nts%2FKaTeX_Math-Italic.woff> tiddler is only 30kb in size. Regards Tones On Wednesday, 9 December 2020 at 23:02:28 UTC+11 PMario wrote: > On Wednesday, December 9, 2020 at 4:58:35 AM UTC+1 TonyM wrote: > > Many of the additional characters for maths is available inside the K

[twdev] Re: Custom markup (continued 4)

sday, 2 December 2020 at 16:28:41 UTC+11 TonyM wrote: > Sorry Wrong link in my reply, part of my development. > > See https://www.unicode.org/Public/UCD/latest/ucd/BidiBrackets.txt for > open and close pairs. > > Tony > > > On Wednesday, 2 December 2020 at 16:26:45 U

[twdev] Re: Peer Review please Cheat sheet

tire UI is built from wikitext. Ultimately, however, it is not my call as > what is supported in the core or not so its not me that you need to > convince. :) > > That said, I do completely agree that we do need some better form of > variable substitution or string templating suppor

[twdev] Re: Peer Review please Cheat sheet

Saq, In effect are you a saying in the latter the reference to the value is the result rather than the value?, I understand the complexities here (I think) however I expect 99% of users - Do not understand this distinction - Think the value is returned, and expects it in filter logic

[twdev] Re: Peer Review please Cheat sheet

t;https://github.com/Jermolene/TiddlyWiki5/issues/5110>, but Saq has an argument that wikify is a poor performer. Regards Tony On Thursday, 3 December 2020 at 12:41:51 UTC+11 codacoder...@outlook.com wrote: > Tony - Looks good on a first pass... I'll need to look at it properly > tomorro

[twdev] Re: Peer Review please Cheat sheet

lt into a filter. Tony Tones On Thursday, 3 December 2020 at 11:46:41 UTC+11 TonyM wrote: > Saq et al, > > Thinking a little further on this issue of "inline concatenation of > various tiddlywiki values", I believe I have just found a quite elegant > solution.

[twdev] Re: Peer Review please Cheat sheet

Saq et al, Thinking a little further on this issue of "inline concatenation of various tiddlywiki values", I believe I have just found a quite elegant solution. Given your complaint about Wikification performance this returns the "evaluated text" Create a tiddler called "&" for concatenate

[twdev] Re: Custom markup (continued 4)

Sorry Wrong link in my reply, part of my development. See https://www.unicode.org/Public/UCD/latest/ucd/BidiBrackets.txt for open and close pairs. Tony On Wednesday, 2 December 2020 at 16:26:45 UTC+11 TonyM wrote: > *TT, et al* > > Yes lets start "* Unicode and Font Support i

[twdev] Re: Custom markup (continued 4)

3 UTC+11 @TiddlyTweeter wrote: > Ciao TonyM & PMario > > TonyM wrote: > >> Here is my initial draft Glyphs 5.1.23-prerelease — Identifying >> reliable Unicode Glyphs on TiddlyWiki Build Date (anthonymuscio.github.io) >> <https://anthonymuscio.github.io/PreRel

[twdev] Re: Peer Review please Cheat sheet

!color}}"""> > style=<> > > > Me: > > Check this in > devtools > > Not sure which you might prefer... > > > On Thursday, October 1, 2020 at 8:13:01 PM UTC-5 TonyM wrote: > >> Folks, >> >> This working tiddler is published here; &

[twdev] Re: Custom markup (continued 4)

ite, just a practical one. Search and play. You have swallowed the "red pill <https://en.wikipedia.org/wiki/Red_pill_and_blue_pill>". More the discovery of infinite scope than unpleasant truths. TonyM -- You received this message because you are subscribed to the Google Groups &quo

[twdev] Re: Custom markup (continued 4)

21:22 UTC+11 @TiddlyTweeter wrote: > Ciao TonyM > > TonyM wrote: > >> The thing I find frustrating is fonts seem not to document the "code >> pages" they include. There must be Unicode rich ones available for linux >> and apple and other devices as there is for

Re: [twdev] date of build-time on prerelease-website?

Jeremy, When I look at the pre-release I always check recent, or the release notes but it is not consistent in indicating recent changes. Displaying the build would at least guide us a little. Eg make the subtitle <> <$text text={{{ [{$:/build}split[ at ]last[]] }}}/> Tones On Friday, 27

[twdev] Re: Custom markup (continued 4)

26 November 2020 at 21:52:56 UTC+11 @TiddlyTweeter wrote: > *Font-ish Thoughts ... * > > Ciao TonyM & PMario > > TonyM wrote: > >> What I did discover is the following >> <https://keyboard.cool/db/enclosed-alphanumeric-supplement/regional-indicator-symbol-letter-a>

[twdev] Re: Custom markup (continued 4)

wishes > TT > On Monday, 23 November 2020 at 14:27:12 UTC+1 PMario wrote: > >> Sorry for the late reply. ... I Wasn't aware, that I can only see, if >> something is going on, if I change the group :/ >> >> On Wednesday, November 18, 2020 at 11:48:23 PM UTC+1 TonyM w

[twdev] Re: Custom markup (continued 4)

I Wasn't aware, that I can only see, if > something is going on, if I change the group :/ > > On Wednesday, November 18, 2020 at 11:48:23 PM UTC+1 TonyM wrote: > ... > >> So perhaps we now need to ask >> >>- How do we go about a degree of ratio

[twdev] Re: Custom markup (continued 4)

to ask - How do we go about a degree of rationalisation - code pages English + Extended Symbols and utilities eg mathematical alphanumeric's - font recommendations - Multi-Platform support TT What do you perceive should be included?. Regards TonyM On Wednesday, 18 November 202

[twdev] Re: Custom markup (continued 4)

there needs to be quite a lot of checking. > > Best wishes > TT > > > On Wednesday, 11 November 2020 23:38:34 UTC+1, TonyM wrote: >> >> Further to this generic element solution; >> >> Eg; >> ⮰td terminates end of line >> ⭭tr terminates with /tr >

[twdev] Re: Custom markup (continued 4)

Further to this generic element solution; Eg; ⮰td terminates end of line ⭭tr terminates with /tr Only valid at the beginning of line it should be rare that a clash would occur. Tony On Thursday, 12 November 2020 09:18:24 UTC+11, TonyM wrote: > > Mario, > > I think I raised thi

[twdev] Re: Custom markup (continued 4)

' and ° Regards Tones On Saturday, 7 November 2020 09:39:43 UTC+11, TonyM wrote: > > Mario, > > That's why I favour customised 'tr and /tr but then you have to be > familiar with html tables. > > Regards > Tony > > On Friday, 6 November 2020 21:13:23 UTC+11, PMario wrote: &g

[twdev] Re: Custom markup (continued 4)

Mario, That's why I favour customised 'tr and /tr but then you have to be familiar with html tables. Regards Tony On Friday, 6 November 2020 21:13:23 UTC+11, PMario wrote: > > Hi, > > I did a bit more docs for table formatting. So there are the same > formatting options as available with

[twdev] Re: Custom markup (continued 4)

Replacing the old nested sliders plugin from TWC In this Discussion <https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/VJKh0H8N7eo> a request mat be satisfied with custom wikitext. Remember +++ content +++ content2 === === Tony On Tuesday, 3 November 2020 16:26:18 UTC+11,

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

Corey Perhaps such a library of tools could be helpful, but a lot can already be done by building a tiddler in which what you see is what you get, open it in a new window and print to pdf. Especially if you include page breaks in the display. I like foxit reader as even the free version

[twdev] Re: Custom markup (continued 4)

Gentlemen, I just discovered on Windows 10, Win+; opens a character dialogue in which I can find »° and others. This means there is a simple though not too quick way to access many of the glyphs we use. However I have being building tools in tiddlywiki for access to other Unicode character

[twdev] Re: Custom markup (continued 4)

documenting if the symbols are chosen well. Tony On Sunday, 1 November 2020 11:44:36 UTC+11, TonyM wrote: > > TT, > > I did read your history, it's Quite interesting. And to some extent I > defer to you, but in my return quote I pointed out the "modern" use of > Pilcrow. &

[twdev] Re: Custom markup (continued 4)

pre-release https://tiddlywiki.com/prerelease/#Filter%20Expression Equivalent named prefix Regards Tony On Sunday, 1 November 2020 03:57:52 UTC+11, @TiddlyTweeter wrote: > > TonyM wrote: >> >> ¶ >> I would not bother with the use of pilcrow unless it was part of an end

[twdev] Re: Custom markup (continued 4)

Do note I found these alternate small braces that may be better. ﹙₍ ₎﹚ Regards Tony On Saturday, 31 October 2020 12:01:43 UTC+11, TonyM wrote: > > Mario, > > I would be keen to see these additional inline glyphs made available. They > look like a fusion of [ ] and ( ) > &

[twdev] Re: Custom markup (continued 4)

Mario, I would be keen to see these additional inline glyphs made available. They look like a fusion of [ ] and ( ) It would be ideal for mark-up that involves links or buttons and where the content is considered a title. *A line with〖 This inline 〗and more - They also look good when no

[twdev] Re: Custom markup (continued 4)

Question, If other glyphs and characters could be selected could we actually redefine existing mark-up with customise? \customise glyph="*" parameters *This would then take on the new definition here? I raise this because this us what the current double underscore is effectively doing. An

[twdev] Re: Custom markup (continued 4)

Mario, Just for clarification the double underscore (not underscore) is used, does this not clash with its existing use?, or is this intentional? It is available on most keyboards. Regards Tony On Saturday, 31 October 2020 00:55:25 UTC+11, PMario wrote: > > Hi folks, > > I'd like to discuss

[twdev] Re: Custom markup (continued 4)

Mario, I think it would be useful to include such "compound customisations" with the plugin or at lest on the plugins website. Although perhaps it could be an optional item that requires tagging. Having used html tables within wikitext for so long, I find it easier to follow a html table

[twdev] Re: Custom markup (continued 4)

l my tests generate. I not you have many of my prior examples in test tiddlers, thanks its a helpful reference. Tony On Friday, 30 October 2020 15:44:29 UTC+11, PMario wrote: > > On Friday, October 30, 2020 at 1:09:16 AM UTC+1, TonyM wrote: > > Only one issue you may have overlooked, or

[twdev] Re: Custom markup (continued 4)

Mario, What you have done is fantastic. I will focus on V 0.8.0 - 2020-10-29 From a testing and features arising point of view. I am Happy to stabilise with the current solution as a first release if you want. My only urgency to raise the custom Glyphs is that your are aware of it as a

[twdev] Re: Custom markup (continued 4)

Mario, Sorry about the overwhelming. I will try and simplify >> *The attached local view template demonstrates the use of additional code >> in a specific tiddler. * >> >>- *In this case of you add the field local-viewtemplate to any >>tiddler in the edit view and a new editable field

[twdev] Re: Custom markup (continued 4)

:20 UTC+11, PMario wrote: > > On Thursday, October 29, 2020 at 1:05:53 AM UTC+1, TonyM wrote: > > Just a thought, if the customise definition was to accept both glyph and >> symbol as parameters this may be an easier approach. >> \customise _glyph="〖" _glyphNam

[twdev] Re: Custom markup (continued 4)

Gentlemen, The attached local view template demonstrates the use of additional code in a specific tiddler. - In this case of you add the field local-viewtemplate to any tiddler in the edit view and a new editable field appears. This will be applied through the view template. -

[twdev] Re: Custom markup (continued 4)

to a mime type also permits providing the character set. Regards Tony On Thursday, 29 October 2020 01:53:12 UTC+11, PMario wrote: > > On Wednesday, October 28, 2020 at 1:50:44 PM UTC+1, @TiddlyTweeter wrote: >> >> *Regarding User Possibility To Set Markup Glyphs?* >> >> T

[twdev] Re: Custom markup (continued 4)

utomation or formatting can be done to automate this feature. Tony On Thursday, 29 October 2020 01:53:12 UTC+11, PMario wrote: > > On Wednesday, October 28, 2020 at 1:50:44 PM UTC+1, @TiddlyTweeter wrote: >> >> *Regarding User Possibility To Set Markup Glyphs?* >> >>

[twdev] Re: Custom markup (continued 4)

It must be late for you - good night Tony On Wednesday, 28 October 2020 12:21:02 UTC+11, PMario wrote: > > Hi Tony, > > Very good questions. ... all of them. > > As I do read the requests, I think we shouldn't make a difference between > \customize and \customize inline But this could

[twdev] Re: Custom markup (continued 4)

Minor additional note > > *A random Idea* > >- I used to use a character combination to annotate lines on personal >hand written notes, I have found unicode versions, they always live at the >end of a line > - ? a question (A question) Special forms of these also exist. >

[twdev] Re: Custom markup (continued 4)

Mario, > _endString will be _not_ configurable. > I agree with this but ask if if it makes sense to be auto-terminated with \n or \n\n am I wrong to think *Typically inline does end at a line or paragraph break?* So if we use the glyphs I suggested ⁽ this is inline⁾ this inline ⁽.coda at

[twdev] Re: Custom markup (continued 4)

To clarify, The following is about the use of underscore or another glyph to handle "inline custom wiki text." > I am not sure why you say new inline functions then you say no inline >> customise functions. >> Do you mean inline works with underscore, you just can not customise it? >> > > It

[twdev] Re: Custom markup (continued 4)

Mario, *A few observations.* Again please don't be overwhelmed just consider these ideas please. Nor do these ideas imply it demands your work, although in some cases that is most likely. The key issue I am grappling with is the systemisation of glyphs, symbols and the scope of customises

[twdev] Re: Custom markup (continued 3)

: > > On Monday, October 26, 2020 at 2:21:44 AM UTC+1, TonyM wrote: > > The best resource I have found now is https://www.unicode.org/charts/ >> > > I use this one, it names them nicely: > https://www.compart.com/en/unicode/category > > -m > > > -- You receiv

[twdev] Re: Custom markup (continued 4)

Mario Thanks for the update today. I will review in the next few hours. In responce to your last reply, to me the small brackets, do not look like they are surrounded by spaces in tiddlywiki. I will look at the 4 possibilities above, my current personal preference is d, b, a, c; but I want to

[twdev] Re: Custom markup (continued 3)

Mario, On Tuesday, 27 October 2020 00:26:49 UTC+11, PMario wrote: > > On Monday, October 26, 2020 at 2:21:44 AM UTC+1, TonyM wrote: > > so we could use ﹙ to mark inline ﹚ then continue >> >> compare with (﹙ ﹚) so we could use (﹙ to mark inline ﹚) then continue >>

[twdev] Re: Custom markup (continued 3)

See also Unicode discovery additional alphabets and tiddlywiki, and a keyboard Question <https://groups.google.com/forum/?oldui=1#!topic/tiddlywiki/OElkElXfG7Y> Tony On Monday, 26 October 2020 12:21:44 UTC+11, TonyM wrote: > > Folks, > > Just sharing some Unicode explor

[twdev] Re: Custom markup (continued 3)

Folks, Just sharing some Unicode exploration The best resource I have found now is https://www.unicode.org/charts/ Fullwidth brackets FF5F ｟ FULLWIDTH LEFT WHITE PARENTHESIS • the most commonly occurring glyph variant looks like doubled parentheses → 2E28 ⸨ left double parenthesis ≈ 2985 ⦅

[twdev] Re: Custom markup (continued 3)

cro. Sure let us explain the use case and when a more common existing method is best, in fact that will help people understand customise better. Regards Tony On Monday, 26 October 2020 05:28:11 UTC+11, PMario wrote: > > On Sunday, October 25, 2020 at 12:59:38 AM UTC+2, TonyM wrote: > &g

[twdev] Re: Custom markup (continued 3)

Mario, On saving https://wikilabs.github.io/editions/custom-markup/ locally and dropping a plugin on it I get Internal JavaScript Error Well, this is embarrassing. It is recommended that you restart TiddlyWiki by refreshing your browser Uncaught TypeError: Cannot read property 'configTickText'

[twdev] Re: Custom markup (continued 3)

Folks, In relation to inline use with custom pragmas we have being focusing on applying styles etc to some text delineated with open and close. Keep in mind that with the wealth of things customise can do for us we may just want to use it for shortcuts \customise tick=sig _element="$text"

[twdev] Re: Custom markup (continued 3)

ution. > > IF you have time to explore this it could be useful. For ... > > 1 - MY needs; > > 2 - WIDER demonstration of the utility of macros UNDER Custom Markup. > > I think it is point (2) that has most gravitas. > > Best wishes > TT > > On Friday, 23

[twdev] Re: Custom markup (continued 3)

Edited in Forum On Saturday, 24 October 2020 17:22:26 UTC+11, TonyM wrote: > > My Response [edited] > > On Saturday, 24 October 2020 13:46:22 UTC+11, PMario wrote: >> >> On Saturday, October 24, 2020 at 12:46:49 AM UTC+2, TonyM wrote: >>> >>> M

[twdev] Re: Custom markup (continued 3)

On Saturday, 24 October 2020 13:46:22 UTC+11, PMario wrote: > > On Saturday, October 24, 2020 at 12:46:49 AM UTC+2, TonyM wrote: >> >> Mario, >> Inline syntax defaults to a SPAN. The inline wikitext syntax doesn't >> care about linebreaks. >> > > So

[twdev] Re: Custom markup (continued 3)

Mario, So ⠪.class:param Braille 246 and Braille 2345⠞ may be an option. > > I understand open and close needs to be asymmetric to see which is which. But the solution such as /glyph content glyph/ - inline or glyph content /glyphline - para or block Still retains a degree of symmetry and is

[twdev] Re: Custom markup (continued 3)

> > Me ... > >> A SERIOUS use case would be HOW to invoke dynamic style change via inline >>> buttons. >>> >> > TonyM ... > >> Can you give an example? > > > A simple one would be to able to dynamically change "block style" for >

[twdev] Re: Custom markup (continued 3)

to extract them from text programaticaly. Regards Tony > > Best, TT > > > > On Thursday, 22 October 2020 11:51:11 UTC+2, TonyM wrote: >> >> Bump, >> >> I too needed a break from this all expansive and innovative rush. But we >> should try and move it

[twdev] Re: Custom markup (continued 3)

Bump, I too needed a break from this all expansive and innovative rush. But we should try and move it to at least a beta releases before our memories fade. Please advise if there is something I can do. Tony -- You received this message because you are subscribed to the Google Groups

[twdev] Re: Basic Question Regarding TW5 Framework

, October 20, 2020 at 4:04:16 PM UTC-6 TonyM wrote: > >> Christopher, >> >> Dungeon Master notes is possibly one of the most common specific uses of >> TiddlyWiki >> >> Look for T5 TiddlyWiki 5 in discord this is where a lot of gamers reside. >&g

[twdev] Re: Basic Question Regarding TW5 Framework

ch as "Spare Bedroom", even though they > would have different paths for linking purposes. > > The text editor from TiddlyWiki mostly serves my purposes for a text > editor perfectly, though there's a fair amount of customization that I'd > actually like to cut down on, for th

[twdev] Re: Basic Question Regarding TW5 Framework

t;> https://softwareas.com/tiddlywiki-internals-1-of-3-architectural-concepts/ >> >> https://softwareas.com/tiddlywiki-internals-2-of-3-list-of-javascript-files/ >> >> https://softwareas.com/tiddlywiki-internals-3-of-3-key-javascript-classes-and-files/ >> h

[twdev] Question: Illegal tiddler titles as namespace for features

Folks, There is a warning not to use curly braces or square brackets in the tiddler titles eg {text} There is also a warning for [ ] square barckets. eg [prefix[prefix[]] such as a filter. I understand this and would notmake use of these as a rule. However you can actually create tiddlers

[twdev] Re: Question: Set cursor in editmode to fieldname?

Sorry, Reposted in main forum On Monday, 19 October 2020 10:56:39 UTC+11, TonyM wrote: > > Folks, > > I have a button that creates a new field then uses the message > <$action-sendmessage $message="tm-edit-tiddler" $param="tiddlername"/> > To open the

[twdev] Question: Set cursor in editmode to fieldname?

Folks, I have a button that creates a new field then uses the message <$action-sendmessage $message="tm-edit-tiddler" $param="tiddlername"/> To open the tiddler for edit. Is it possible somehow to get the cursor to appear in the new field? Why? This would simplify providing a value to the field

[twdev] Re: How can I install an unofficial Saver?

Ryan, Always consider an unofficial saver as a candidate for an official saver if you can expand and democratise tiddlywiki, Regards Tones On Tuesday, 22 September 2020 09:14:27 UTC+10, Ryan Kramer wrote: > > Thank you Mario, that looks like what I want to do. (Assuming that once I > build

[twdev] Re: Basic Question Regarding TW5 Framework

Christopher, Others can give a more technical origins story, but to me TiddlyWiki is the framework. It is a platform in its own right and relies on broad standards of HTML and Javascript. When incorporating Javascript you need to be aware of the way tiddlywiki works because its efficient

[twdev] Re: Custom markup (continued 3)

Folks, I simply can't get over the power this adds to tiddlywiki. - Even just to use a symbol for a known or arbitrary html element name is immensely powerful. - Having a symbol and name simply replace a specific implementation of a widget and pre-set attributes - This

[twdev] Re: Custom markup (continued 3)

to define such customise parameters at all. Regards Tony On Tuesday, 6 October 2020 02:58:47 UTC+11, PMario wrote: > > On Monday, October 5, 2020 at 2:54:08 PM UTC+2, TonyM wrote: > > This makes me ask if one of out special characters could simply default to >> the element that f

[twdev] Re: Custom markup (continued 3)

Mario, I have returned to research after a short break, and realise it is not as intuitive when you come back to, it but I am getting there. As a starter I am reviewing first simple elements only eg; \customise tick=kbd _element=kbd _mode='inline' \customise tick=div _element=div \customise

[twdev] Re: Custom markup (continued 3)

Sorry, To be a little clearer on my previous question answer You may use answers to display all answers at once; Otherwise 'q1 Question 1 'a1 answer 1 etc... Tony On Monday, 5 October 2020 23:54:08 UTC+11, TonyM wrote: > > Mario, > > I have returned to research after a short break,

[twdev] Re: Custom markup (continued 3)

Mario, Thanks for the progress and listening. Today is a public holiday and I am spending time with my partner, so may not feedback today. This project certainly has "energised me" both for its outcomes and what I perceive to be other key improvements we need in TiddlyWiki. It has also led to

[twdev] Re: Peer Review please Cheat sheet

Folks, This working tiddler is published here; https://anthonymuscio.github.io/#Standard%20Nomenclature Regards Tony On Thursday, 1 October 2020 12:17:43 UTC+10, TonyM wrote: > > Folks, > > I have being building a "CheatSheet" that I would appreciate expert review

[twdev] Peer Review please Cheat sheet

Folks, I have being building a "CheatSheet" that I would appreciate expert review if possible. Please respond with references to the number of each item. You can see it is built on Tobias and Eric's work to name a few. It tries and make simple, some particularly tricky issues that new and

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

Joshua, Thanks so much for building on this comprehensive solution. I have not yet made use of it much yet, but it is very important to tiddlywiki, because it opens many integration possibilities. I stumbled on https://en.wikipedia.org/wiki/WordNet and https://wordnet.princeton.edu/ which I

[twdev] Re: Custom markup (continued 3)

Mario, Yes Very interesting. Please keep this possibility alive, I agree the checklist plugin is great, and its very low complexity in wikitext one of its key advantages however I do like the ability to have a minimalist output or read only view of those we can build in custom wiki text

[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

[twdev] Re: Custom markup (continued 3)

Folks, I continue researching the possibilities for these reasons - It is seriously exciting - To work with Mario and others (What a pleasure) - To discover the possibilities - To test the limits, and perhaps uncover minor tweaks that add great value - Lastly to solve long

[twdev] Re: Custom markup (continued 3)

TT, 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 more others view the results can be as brief as you want. - If

[twdev] Re: Custom markup (continued 2)

Mario, I don't think very specific id's are a problem if the result is of substantial utility. I have a larger concern about the symbols which have a wider applicability, because I think they need to be given a default purpose, kind of defacto standard for each of them, to encourage some

[twdev] Re: Custom markup (continued 2)

TT, > But, as I work with it myself I sometimes struggle with the PERMUTATIONS > possible. > This is so often the case in tiddlywiki, the customisations and possibilities are virtually infinite in many directions. This is just another few dimensions of control. > My main wondering is WHO

[twdev] Re: Custom markup (continued 2)

Mario, Is it not your bed time? > > There is a typo: you need to close the first widget element: `<$count > filter="[prefix[$:/state]]">` > > Not really. The string is like the _endString parameter for > the standard TW parser. So it doesn't need to be created. > My mistake again. However

[twdev] Re: Custom markup (continued 2)

Mario, Yes I was erroneously using the 4.1 version while testing 5.1 (my Bad) Every widget that is used "self closing" like <$count /> there should be > _no_ problem. They should all work. _And with the _srcName you have *one > parameter*, that can be defined in the "user line".. > > However,

[twdev] Re: Custom markup (continued 2)

Mario, I think you suggested this before, but our use of widgets is limited by those who do not honour the close part of <$wiggetname params>content rule A case in point is the <$count widget, as it can only be closed with /> not Going forward - Perhaps we should raise this as a fix,

[twdev] Re: Custom markup (continued 2)

, 2020 at 10:49:18 AM UTC+2, TonyM wrote: > > \customize tick=children _element="$list" filter="[parent]" >> >> >> And the last one children has set me of on a one and many to many >> relationship solution >> * now that what TocP is no lo

[twdev] Re: Custom markup (continued 2)

Mario and Folks, This example not only shows that the customise pragma can be used to store a canned filter for reuse, but also shows how the first in a nested list can be concealed behind a helpful name like system-shadows \customize tick=system-shadows _element="$list" filter=

[twdev] Re: Custom markup (continued 2)

Folks, A little experimental fun; This method uses the vars widget to pre-define a set of variables for use inside the custom markup. As in this examples we have all out standard address details using well known names. You choose which to use and how to arrange them. Of course the variable

[twdev] Re: Custom markup (continued 2)

ly not smooth enough for live > note taking.) > > OK, just a report from IRL. > > <:-) > On Tuesday, September 22, 2020 at 1:31:33 AM UTC+2 TonyM wrote: > >> TT, >> >> I understand your concern, its correct to raise it. I think you need a >> ex

[twdev] Re: Custom markup (continued 2)

TT, I understand your concern, its correct to raise it. I think you need a explanation from me who is pushing this capacity, is warranted. - What I am doing is pushing the solution to its logical conclusions, not to necessarily expand the features (although that is good), but explore

[twdev] Re: Custom markup (continued 2)

Mario, The need for an endString, although may be valid in other use cases is a good way to recognise when a multi-line block or inline text is in use, rather than the line based approach. Many of the current wiki text is line based. It seems to me that making use of a method like

[twdev] Re: Custom markup (continued 2)

\whitespace trim <$set name=todo-tiddler value="""$:/todo/$(currentTiddler)$/$content$"""> <$set name=content value="""$content$"""> <$tiddler tiddler=<> > <$button tooltip="This is marked as a todo item,

[twdev] Re: Custom markup (continued 2)

day laziness, but it could also be a lack of clarity either in the solution or in the documentation. *Would it be possible for you to write a short clarifying summary of the differences between these 4 items above please?* - *It seems to me this is a key area of the documentation* Thank in advanc

[twdev] Re: Custom markup (continued 2)

aces that text in a data tiddler with next nth key - Turn text into a tag - to copy line to keyboard - Allowing footnotes to be created - many more Tony On Friday, 18 September 2020 at 22:33:33 UTC+10 PMario wrote: > On Friday, September 18, 2020 at 2:18:47 PM UTC+2,

[twdev] Re: Custom markup (continued 2)

I need to clock Off, almost midnight here, Great work, The revolution is Brewing :) Tony On Friday, 18 September 2020 at 23:44:48 UTC+10 TonyM wrote: > > Mario, > > >> The Usage string is: ° » ´ › - -- --- >> > > Lol > > Actually finally we have a way

[twdev] Re: Custom markup (continued 2)

Mario, > The Usage string is: ° » ´ › - -- --- > Lol Actually finally we have a way to obfuscate! for good I mean, like hard to find strings. Or user or password details? Regards Tony -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.

[twdev] Re: Custom markup (continued 2)

nformal standards. Tony On Friday, 18 September 2020 at 22:05:44 UTC+10 TonyM wrote: > All, > > In the below it demonstrates how convention allows the Capital to be used, > eg Big X refers to Close all > >- Close all works, but not copy to clipboard? >- Again th

[twdev] Re: Custom markup (continued 2)

All, In the below it demonstrates how convention allows the Capital to be used, eg Big X refers to Close all - Close all works, but not copy to clipboard? - Again this shows how rather than write a macro you can use _element="$widget" to simply code a shortcut for a button - I

[twdev] Re: Custom markup (continued 2)

Mario, I think this could be an independent solution. ANd alias may be away to go, but I am thinking more with a view to core one day, perhaps that's where a simplified alias should go as well? Regards Tony On Friday, 18 September 2020 at 20:55:56 UTC+10 PMario wrote: > I'll give it an

  1   2   3   4   5   6   7   8   >