[twdev] empty.html should start with "fluid-fixed" layout

Hi folks, I did just create a PR, that sets the default layout of empty.html to: fluid-fixed See: https://github.com/Jermolene/TiddlyWiki5/pull/5492 Please vote +1 if you think it should be merged! have fun! mario -- You received this message because you are subscribed to the Google Groups

[twdev] Re: Custom markup (continued 4)

Hi Folks, We continue at: https://github.com/wikilabs/plugins/discussions/56 have fun! mario -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+uns

[twdev] Re: Custom markup (continued 4)

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 Katex > plugin with the use of Woff files, this plugin is less than 1mb in size. > If a font is about 1 MByte I'd add it to my PC, but in now way I would want to

[twdev] Re: Custom markup (continued 4)

On Tuesday, December 1, 2020 at 6:42:53 PM UTC+1 @TiddlyTweeter wrote: *...* It would be *a very minimal font embedded in TW for JUST markup > glyphs. It would be kilobytes, not megabytes*. To get to the point of > proof-of-concept I need some days yet, but I'm getting close. Its just > trudge

[twdev] Re: Custom markup (continued 4)

On Saturday, November 28, 2020 at 6:44:01 PM UTC+1 codacoder...@outlook.com wrote: *Scoping rules* > What is the scope of \somepragma? Is it possible to globally define them > easily? I feel like I'm missing something obvious here. Wondering if > $:/tags/Macro might do the job - it shouldn't bu

[twdev] Re: Custom markup (continued 4)

ontents !! .. There is a little bit of docs already. > >> *Pragma definitions* >> (@PMario) Like me, you were probably thankful when JavaScript started to >> support arrow functions - the brevity alone lent itself to a boost in >> productivity. Therefore I&#x

[twdev] Re: Custom markup (continued 4)

On Thursday, November 26, 2020 at 11:17:50 AM UTC+1 @TiddlyTweeter wrote: > *BUG? v.0.8.1 -- Block Nesting Broken?* > Try: \\ CUSTOM POETRY \\ -- container - \customize angle=POEM _element="div" _endString="/POEM" _mode=block _classes=".poem-c" \\ -- components --- \\ \customize single=P

[twdev] Re: Custom markup (continued 4)

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 wrote: ... > So perhaps we now need to ask > >- How do we go about a degree of rationalisation >- code pages En

[twdev] Re: Custom markup (continued 4)

Hi, I did a bit more docs for table formatting. So there are the same formatting options as available with standard wikitext. The only problem is, to find good "start" and "end" symbols, to make the wikitext readable. -m -- You received this message because you are subscribed to the Google

[twdev] Re: Custom markup (continued 4)

On Saturday, October 31, 2020 at 9:19:43 AM UTC+1, @TiddlyTweeter wrote: > > PMario wrote: > > Inline nesting seems to have a problem. > > > Right. I noticed that. Hope its solvable! > V0.8.1 should have fixed it. If not please report! -m -- You received this message be

[twdev] Re: Custom markup (continued 4)

On Saturday, October 31, 2020 at 11:05:06 AM UTC+1, @TiddlyTweeter wrote: P.S.: By the way the Pilcrow was originally used inline (often coloured > red) in Medieval manuscripts to indicate a ceasura / hiatus / pause in the > flow of a text. > Vellum / parchment was very expensive so text is as

[twdev] Re: Custom markup (continued 4)

On Saturday, October 31, 2020 at 11:05:06 AM UTC+1, @TiddlyTweeter wrote: The use case I am thinking of is allow me to simplyfy & share with others > an approach to correct manuscripts. > I work often using specialist software to proof edit articles & books for > publishers. > This uses a speci

[twdev] Re: Custom markup (continued 4)

On Saturday, October 31, 2020 at 10:01:42 AM UTC+1, @TiddlyTweeter wrote: Can you please clarify what you mean here! > > Do you mean that are TWO different Unicode glyphs for Underscore being > used? > The default behaviour, should do the exact same thing as the existing __underline__ does. ...

[twdev] Re: Custom markup (continued 4)

On Saturday, October 31, 2020 at 1:44:27 AM UTC+1, TonyM wrote: > This would allow redefinition of mark-up already in a text perhaps even > making it behave like another mark-up language. > and additions like > \customise glyph="-" _element="li" > > - to accept bullets pasted from GitHub > > I w

[twdev] Re: Custom markup (continued 4)

On Saturday, October 31, 2020 at 1:36:14 AM UTC+1, TonyM wrote: Just for clarification the double underscore (not underscore) is used, does > this not clash with its existing use?, or is this intentional? > As default, it will do the same thing. So it shouldn't be a problem. But I need to fix i

[twdev] Re: Custom markup (continued 4)

Hi folks, I'd like to discuss with you the table syntax as shown in \customize tick=table _element=table _endString="/endTable" _mode=block \customize tick=caption _element=caption \customize tick=! _element=th \customize tick=cell _element=td _classes=".hl" \customize tick _use=cell \customi

[twdev] Re: Custom markup (continued 4)

On Friday, October 30, 2020 at 1:09:16 AM UTC+1, TonyM wrote: Only one issue you may have overlooked, or I missed your answer. Rather > than use pilcrow at the beginning of a line I would only use it at the end, > if you don't see an "end of line only pragma" being possible as discussed > in th

[twdev] Re: Custom markup (continued 4)

Hi Folks, There has been so much feedback lately, that I'm still a bit overwhelmed. .. I need to read and re-read the infos several times. At the moment we have maximum flexibility, except user-glyph-configuration. ... But let us test, what we have atm. ... I'll need to create a lot more aut

[twdev] Re: Custom markup (continued 4)

Hi, Inline nesting seems to have a problem. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discu

[twdev] Re: Custom markup (continued 4)

Hi, V 0.8.0 - 2020-10-29 - There are 4 "inline" like elements - __ underscore__, ﹙ little﹚, ⠒ braille⠶, /° slash°/ - There are 6 "block" like elements - pilcrow: ¶, about: ≈, angle: », degree: °, tick: ´, single: › and it's crazy! The "inline"-like elements do have predefin

[twdev] Re: Custom markup (continued 4)

On Thursday, October 29, 2020 at 1:17:11 AM UTC+1, TonyM wrote: > > 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 editab

[twdev] Re: Custom markup (continued 4)

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="〖" _glyphName="openenc" _endString="〗" _symbol=highlight > _classes=".highlight" _m

[twdev] Re: Custom markup (continued 4)

yphs available that have meaning >>or structure makes me wish to ask if we could allow the user to nominate >>glyphs either single (line/para/blocks) or pairs for inline or block. ie >>customise the customise glyphs. >> >> > Ciao TonyM & PMario > &

[twdev] Re: Custom markup (continued 4)

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 cause a lot more consistency problems, like: ´d ´s some text<-- only works that way because I liked it. With

[twdev] Re: Custom markup (continued 4)

On Wednesday, October 28, 2020 at 1:50:19 AM UTC+1, TonyM wrote: > > 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?

[twdev] Re: Custom markup (continued 4)

On Wednesday, October 28, 2020 at 1:14:30 AM UTC+1, TonyM wrote: > > *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

[twdev] Re: Documentation about plugin dependencies

Hi Matt, If you open the import plugin mode, you can click the expand button. The text that is shown also shows the dependencies, if there are any. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop

[twdev] Re: Custom markup (continued 4)

On Tuesday, October 27, 2020 at 9:33:07 PM UTC+1, TonyM wrote: 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 is able to detect start / end and nested inline definitions.

[twdev] Re: Custom markup (continued 4)

Hi, V 0.7.0 - 2020-10-23 - New Inline functions - _symbol.class.clsss:param:param some text__ - .class and :param work the same way as "block" definitions - Removed underscore from "block" definitions, because it's used by "inline" - Added: \\ pragma comments - It'

[twdev] Re: Custom markup (continued 3)

Hi folks, Please continue discussions here: Custom markup (continued 4) -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving

[twdev] Custom markup (continued 4)

Hi folks, This is the continuation of - Custom markup [1] - Custom markup (continued) - Custom markup (continued 2)

[twdev] Re: Custom markup (continued 3)

On Tuesday, October 27, 2020 at 6:19:56 AM UTC+1, TonyM wrote: ... > ﹙symbol.class:param some text﹚ > > Where if you use ﹙ as the glyph, the end string is "﹚" for inline. The > symbol remains free for other configurations > > A specially formatted quote ﹙q.large some text﹚ in line ﹙ the default

[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 received this message because you are subscribed to the Google Gro

[twdev] Re: Custom markup (continued 3)

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 > Looks interesting. But you have to test like so: (﹙symbol.class:param some text﹚) or (﹙symbol.class:para

[twdev] Re: Custom markup (continued 3)

On Sunday, October 25, 2020 at 12:59:38 AM UTC+2, TonyM wrote: \customise tick=sig _element="$text" text="Anthony Muscio" > > ´sig > > But inline This is some text written by ´sig the author > > IMO it should be done "the old way" with: \define sig() Mario Pietsch <> But inline This is some t

[twdev] Re: Custom markup (continued 3)

On Sunday, October 25, 2020 at 1:03:50 AM UTC+2, TonyM wrote: On saving https://wikilabs.github.io/editions/custom-markup/ locally and > dropping a plugin on it I get > Which plugin did you "drop". I can't recreate the problem. mario -- You received this message because you are subscribed to

[twdev] Re: Custom markup (continued 3)

On Saturday, October 24, 2020 at 1:35:47 PM UTC+2, @TiddlyTweeter wrote: > > *Final Plea for TWO Inline markers* > I was thinking about that too, because underscore make much more problems as I thought. -m -- You received this message because you are subscribed to the Google Groups "TiddlyW

[twdev] Re: Custom markup (continued 3)

On Saturday, October 24, 2020 at 12:46:49 AM UTC+2, TonyM wrote: > > 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 > g

[twdev] Re: Custom markup (continued 3)

On Friday, October 23, 2020 at 1:06:15 PM UTC+2, PMario wrote: Writing all the above text I was thinking: . . . . > > What about: *_symbol.class.class:param:param some text__ _ some more > text__* > hmmm. It doesn't work out with a "single" start char. Wa

[twdev] Re: Custom markup (continued 3)

On Friday, October 23, 2020 at 1:28:39 PM UTC+2, PMario wrote: *Pragma Comment* > > Could be > > \\ comment comes here till the end of the line > > We are lucky :) > \\ If pragma comments are used here they are faster as used in the define > block. > \\ This comm

[twdev] Re: Custom markup (continued 3)

On Friday, October 23, 2020 at 1:06:15 PM UTC+2, PMario wrote: Writing all the above text I was thinking: . . . . > > What about: *_symbol.class.class:param:param some text__ _ some more > text__* > IF: \customize inline="_" _element="u" ... is a default g

[twdev] Re: Custom markup (continued 3)

On Thursday, October 22, 2020 at 1:53:41 PM UTC+2, @TiddlyTweeter wrote: > > I'm very alive on what PMario is doing. It's very, very useful. > I did some development, but it won't be seen. .. I did use the TW test-framework, to create automated tests. That's sup

[twdev] Re: Basic Question Regarding TW5 Framework

Hi Christopher, You may be interested in this hangout, where 2 D&D and TW enthusiasts present their stuff. https://www.youtube.com/watch?v=Imx-EzCOWGc&list=PLVT_2PPd-1p34gGCQ5qpwC8QdykxVAI3u&index=2 have fun! mario -- You received this message because you are subscribed to the Google Groups

[twdev] Re: Custom markup (continued 3)

On Monday, October 5, 2020 at 11:05:20 AM UTC+2, @TiddlyTweeter wrote: > > For readers on email in my last post prefaced *Regarding examples & > WikiText "interactivity" *I deleted the last paragraph as it was > misleading. > TT > I think it was the one with the space-space-enter, that produce

[twdev] Re: Custom markup (continued 3)

On Monday, October 5, 2020 at 10:03:40 AM UTC+2, @TiddlyTweeter wrote: > > *Regarding a use case using "shorthand"* > > PMario wrote: >> >> >> The point is, I'm completely clueless, why you write "content" with CSS? >> What is the purpo

[twdev] Re: Custom markup (continued 3)

Hi ´aside test asdf is already possible -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on

[twdev] Re: Custom markup (continued 3)

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 follows the special character > > eg > 'aside Content is an aside > > >- That is nominate one of the special character to just automatical

[twdev] Re: Custom markup (continued 3)

On Monday, October 5, 2020 at 2:54:08 PM UTC+2, TonyM wrote: By the way I do nor think we shopuld say > > = > > Since to me the tick degree etc.. is a symbol > > This will be some docs changes only. I would be OK with this. > To me > > = > Would be better and note that name can be a single c

[twdev] Re: Custom markup (continued 3)

On Monday, October 5, 2020 at 11:34:48 AM UTC+2, @TiddlyTweeter wrote: I was suggesting tentatively that there be two ID's for inline markup ... > > degree "°" (entity = °) > > > and another ... (I can help you find one :-) maybe ... > I was thinking about °/ some text and /° ... Since start and

[twdev] Re: Custom markup (continued 3)

Hi foks, I did just upload V0.6.0 which has some INCOMPATIBLE changes. - *New Functionality* - $:/config/custom-markup/pragma/PageTemplate tagged: $:/tags/Macro - content: \importc

[twdev] Re: Custom markup (continued 3)

On Saturday, October 3, 2020 at 10:18:14 AM UTC+2, @TiddlyTweeter wrote: > > Ciao PMario & all > > I been doing a lot of testing of using Custom Markup for layouts and > precision CSS application. It is VERY good. > > A number of issues came up. I will post about

[twdev] Re: Custom markup (continued 3)

On Saturday, October 3, 2020 at 10:56:44 AM UTC+2, @TiddlyTweeter wrote: > > Ciao PMario > > *A CONFESSION -* Using Custom Markup at first was very confusing for me! > As soon as I started to do anything other than simple the layout would > break. > *This is because of Cus

[twdev] Re: Custom markup (continued 3)

On Saturday, October 3, 2020 at 11:56:54 AM UTC+2, @TiddlyTweeter wrote: > > Ciao PMario > > *Is Six ID's Enough? YES.* > > In practical use I think its a good number. > > - Good balance between strict TECHNICAL NEED to make it work (i.e. 2) and > .. > - ... VIS

[twdev] Re: Custom markup (continued 3)

On Sunday, October 4, 2020 at 8:42:31 AM UTC+2, @TiddlyTweeter wrote: Its actually very complex so I've made a simplified single tiddler example > containing the \customize, markup example and style block for you to see. > I hope that will help.The example attached is for using the markup in > B

[twdev] Re: Custom markup (continued 3)

On Sunday, October 4, 2020 at 8:42:31 AM UTC+2, @TiddlyTweeter wrote: > > PMario wrote: >> >> Interesting, but without the actual configuration it's really hard for me >> to see, what it should do. > > .. Can you export your setting and attach a tiddlers.json,

[twdev] Re: Custom markup (continued 3)

On Saturday, October 3, 2020 at 12:57:31 PM UTC+2, @TiddlyTweeter wrote: *Comments on INLINE markup.* > > At the moment I'm writing markup like this ... > > »§ > ›¶ `›¶` Example single line for SA phrase groups. Won't fully work till > custom-inline is finished. ([[TT Notes]]) > »¶ >°O `

[twdev] Re: Custom markup (continued 3)

On Wednesday, September 30, 2020 at 5:10:49 AM UTC+2, TonyM wrote: I have published [RFC] Request for Comment and collaboration - Unique > renamable Tiddlers and children with any name, a total Database? > > Just now, the f

[twdev] Re: Custom markup (continued 3)

I did add a bit more colour to the examples, to visualize the data-flow a bit better. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr

[twdev] Re: Custom markup (continued 3)

Hi, I'm not 100% sure about the parameter names. So they may change. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroup

[twdev] Re: Custom markup (continued 3)

Hi folks, I did just upload V 0.5.3 that contains 3 more very powerful parameters. It lets us do the following: \customize degree=☐ _element="$macrocall" $name="check" _1=tid \define check(src, tid) <$checkbox tiddler=<> tag=done class="db"> <<__src__>> \end °☐:a This is a test °☐:b This

[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)

; they can move the "cryptic" elements into the _params parameter and define a wikitext like so: °this-and-that-should-happen ... For me it's important that both variants work. So when PMario talks about "readability" I want to push it :-) I think what > he means is text

[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 2)

On Friday, September 25, 2020 at 12:42:07 PM UTC+2, @TiddlyTweeter wrote: There are two issues in our context ... > > 1 - does the end user need to see what the author used? My guess is that > they *don't.* > I mean we are doing this to make WRITING easier. But most READERS won't be > writers s

[twdev] Re: Custom markup (continued 2)

Hi folks, We should go on here: Custom markup (continued 3) have fun! -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving email

[twdev] Custom markup (continued 3)

Hi folks, This is the continuation of Custom markup [1] and Custom markup (continued) and Custom markup (continued 2)

[twdev] Re: Custom markup (continued 2)

On Friday, September 25, 2020 at 1:26:12 PM UTC+2, PMario wrote: ... Tony wanted the possibility to add more key=value _params. .. And I think > it should be possible, in the _params section and calling it. eg: > > °☐:a This is a Test > It should be also possible to use the Ballot

[twdev] Re: Custom markup (continued 2)

On Friday, September 25, 2020 at 12:13:08 PM UTC+2, @TiddlyTweeter wrote: Can you PLEASE correct angel to angle. > I knew, that someone would have a problem. But for me this looks like an angel »|« , with some phantasy. I'll think about it, since there may be some "religious" concerns too

[twdev] Re: Custom markup (continued 2)

On Friday, September 25, 2020 at 12:00:22 PM UTC+2, @TiddlyTweeter wrote: > > To clarify my last point about TWO configs, nasty & irritating as the idea > is :-(... > > I think it very LIKELY that PMario's Custom Markup system will be, > eventually, widely used by AUTEURS (originating author geek

[twdev] Re: Custom markup (continued 2)

On Friday, September 25, 2020 at 11:11:56 AM UTC+2, @TiddlyTweeter wrote: Unicode does provide many *paired glyphs*, albeit some are outside the > UTF-16 range. > See, for instance, *some *of them: > https://www.compart.com/en/unicode/mirrored > For javascript, it's not necessary, to use UTF-1

[twdev] Re: Custom markup (continued 2)

On Wednesday, September 23, 2020 at 11:13:10 PM UTC+2, TonyM wrote: > However, without customisations > Count: `<$count filter="[prefix[$:/state]]"/>` works > Count: `<$count filter="[prefix[$:/state]]"` does not > There is a typo: you need to close the first widget element: `<$count filter="[

[twdev] Re: Custom markup (continued 2)

Hi I did update the page and the pluginlibrary 5 minutes ago -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To v

[twdev] Re: Custom markup (continued 2)

On Wednesday, September 23, 2020 at 1:20:52 PM UTC+2, TonyM wrote: > 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 > It needs to be content or template in the body. > A case in point i

[twdev] Re: Custom markup (continued 2)

On Wednesday, September 23, 2020 at 12:22:54 PM UTC+2, TonyM wrote: > Especially the use of src > > Do I understand correctly the _srcName=filter effectively says, assign > the value found in the line, to the parameter filter, in this case that is > in the list? > Right! If _element is a wi

[twdev] Re: Custom markup (continued 2)

On Wednesday, September 23, 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 longer magical to me :) > I see :) -m --

[twdev] Re: Custom markup (continued 2)

On Wednesday, September 23, 2020 at 10:49:18 AM UTC+2, TonyM wrote: 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 tic

[twdev] Re: Custom markup (continued 2)

On Wednesday, September 23, 2020 at 8:46:08 AM UTC+2, TonyM wrote: 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. Yo

[twdev] Re: Custom markup (continued 2)

On Tuesday, September 22, 2020 at 8:46:25 PM UTC+2, Mat wrote: > > So, if the CSS is defined elsewhere, do I understand it right that the > user has to insert the following bit in every tiddler that he wants to make > such styled notes in? > See the \importcustom pragma https://wikilabs.github.

[twdev] Re: Custom markup (continued 2)

Hi, If you have some text from the book, ASIDE would be an option too. https://wikilabs.github.io/editions/custom-markup/#test-aside-without-pragma:test-aside-without-pragma%20test-aside-clearfix So your comments can be the aside element. -mario -- You received this message because you are

[twdev] Re: Custom markup (continued 2)

On Tuesday, September 22, 2020 at 2:20:08 PM UTC+2, PMario wrote: »note ´page [[book]] 1-5 > your comment! > -- > You can define a stamp of the above text to be quicker. Just some thoughts. -mario -- You received this message because you are subscribed to the Goog

[twdev] Re: Custom markup (continued 2)

Hi Mat, I think it can be done in a similar way to the html DETAILS element. I'd go with something similar to this: BUT the section should be in a separate CSS tiddler \customize angel="note" _element="div" _params=".note.notop.cbox.cbox-primary.hard-linebreaks" open _mode=block _endStrin

[twdev] Re: Custom markup (continued 2)

On Tuesday, September 22, 2020 at 12:04:52 PM UTC+2, Mat wrote: > > I'm unfortunately swamped with work, thus my absence here. Sorry for that. no problem. I have to go through several books and in doing so I take out notes and > quotes. I want to refer to these snips by the page they can be fou

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 7:42:38 PM UTC+2, @TiddlyTweeter wrote: BUT are we seeing a version of Advanced Yoga (bloke was able to twist his > leg behind his head)? > Probably yes. ... > My concern is it will confuse adding macros. Let's see. > With TW5 Jeremy invented the widgets. W

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

Hi Ryan, How do you build your TW? With node? You can set your environment variables see: https://tiddlywiki.com/#Environment%20Variables%20on%20Node.js to your plugin library. If you build a new TW the plugin will be included. Have a closer look at this discussion: https://groups.google.c

[twdev] Re: Custom markup (continued 2)

@Tony, If you drag & drop import the WikiLabs Plugin Configuration tiddler into your wiki, you can update with the default TW plugin update workflow. -mario -- You received t

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 6:13:28 PM UTC+2, @TiddlyTweeter wrote: > > The checklist example TonyM gave I don't think adds anything that does not > exist already. > > As PMario implied before, the Grossinger plugin IS using markup > intelligently to deliver live.

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 6:06:56 PM UTC+2, @TiddlyTweeter wrote: > > The more I hear about "macros" in this the worse I feel. > Why? ... It works now, which is a big win. > I don't care if the device lets you skip over the moon. I DO care that > mortals can understand it. OR totally av

[twdev] Re: Custom markup (continued 2)

Hi Latest version is now at: https://wikilabs.github.io/editions/custom-markup/ V0.5.1 @ Tony your "macro" call works now. And there is a new _srcName parameter. Mario -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from th

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 10:54:48 AM UTC+2, @TiddlyTweeter wrote: ... > I also read the detail on discussion of using it for macros. I'm slightly > nervous about that. > The GAINS on HTML insertion and CSS styling are very substantial. I would > not want handling macros to confuse the b

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 6:05:06 AM UTC+2, TonyM wrote: *The macro(s) just for completeness* > \define done-check(tiddlername) > \whitespace trim > <$set name=tiddlername value="""$tiddlername$""" > emptyValue=<> > > <$list filter="[!done[yes]!done[cancel]]"> > <$button tooltip="click to

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 6:05:06 AM UTC+2, TonyM wrote: I expect it is too late in the rendering process; but it seems common sense > (does not mean it is) that some pragma could read as such; > °☐ "This is a todo line" > This will work with *V0.5.1*! There was a bug in my praser _and_

[twdev] Re: Custom markup (continued 2)

Hi Tony, I did find a bug, that made it impossible to use \customize _element="$xxx" properly. ... There was a problem with the parameter parsing. It will be fixed with the next version. I did also have a look, which widgets can be customized. .. It seems all of them should work. But I'm no

[twdev] Re: Custom markup (continued 2)

On Monday, September 21, 2020 at 10:54:48 AM UTC+2, @TiddlyTweeter wrote: I had an example Use Case to show but things changed so much in your tool > I'm revising it. Hopefully I have time soon. > Yea, It was alpha as we started. It is beta now. So I think we settled on the naming conventions.

[twdev] Re: Custom markup (continued 2)

On Sunday, September 20, 2020 at 6:02:43 AM UTC+2, TonyM wrote: > > Mario, Et al. > > More review and research into the extensibility on top of Version 0.4.1 > > I just did this in a tiddler > \customize degree="button" _element="$button" mode="block" > \customize tick="kbd" _element="kbd" > >

[twdev] Re: Custom markup (continued 2)

On Sunday, September 20, 2020 at 1:12:12 AM UTC+2, TonyM wrote: This idea is very powerful from a user perspective, but I have no idea how > achievable technically, please give it some thought. > >- If feasible it only needs the development of one new customise >feature reference the co

[twdev] Re: Custom markup (continued 2)

On Friday, September 18, 2020 at 2:18:47 PM UTC+2, TonyM wrote: > > In the new Google Groups I can edit an existing post :( again > *Additional Content* > > 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 c

[twdev] Re: Custom markup (continued 2)

It would be used mainly for documentation purposes -m On Friday, September 18, 2020 at 2:27:27 PM UTC+2, PMario wrote: > > That's a nice example. > > But what I wanted is a "partial" copy-to-clipboard, which isn't possible > atm. The <$button> body is

[twdev] Re: Custom markup (continued 2)

That's a nice example. But what I wanted is a "partial" copy-to-clipboard, which isn't possible atm. The <$button> body is used to create the button-text instead of defining the text, that should be copied. So the widget I'm imagining is more like this <$clipboard buttonText="copy to clipboa

[twdev] Re: Custom markup (continued 2)

Hi, I think the following works well out of the box for me. ».hl several lines of paragraph text with single line breaks where onyl 1 indicator is needed just a thought. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe fro

  1   2   3   4   5   6   7   8   9   10   >