Tony - Looks good on a first pass... I'll need to look at it properly
tomorrow (it's late here).
On Wednesday, December 2, 2020 at 6:59:28 PM UTC-6 TonyM wrote:
> And using codaCodas examples prior;
>
> <$wikify name=style-value text="""color: {{!!color}}""">
> style=<>
>
>
> Check this in
!!field}}`>my span
On Wednesday, December 2, 2020 at 11:03:34 AM UTC-6 coda coder wrote:
> Yep, it is interesting. I do try to avoid wikify until I prove it's the
> only way. In essence, even though the goal is simply stated,
> transclusion-filters (to me) seem to cloud the simp
Yep, it is interesting. I do try to avoid wikify until I prove it's the
only way. In essence, even though the goal is simply stated,
transclusion-filters (to me) seem to cloud the simplicity - leaving a lot
of syntax noise behind. Wikify seems to read simpler, because it's "broken
down" I gues
On Wednesday, December 2, 2020 at 12:40:17 AM UTC-6 saq wrote:
> FYI, the solution using join[] (or addsuffix[]) is *substantially*
> faster...
addsuffix - duh! - Jeez... thanks for the face-palm, Saq!
There's only so long I can stare at something (sometimes, anyway).
--
You received this m
Yes. But following along with your thinking was kinda slow. I had to reread
a few times to "get" what you were saying. It was probably me - too tired
at the time.
On Tuesday, December 1, 2020 at 11:11:15 PM UTC-6 TonyM wrote:
> CodaCoda,
>
> Yes I understand that, but I will review the cheat sh
Agreed. But syntax noise is... well, noisy :/
On Wednesday, December 2, 2020 at 12:40:17 AM UTC-6 saq.i...@gmail.com
wrote:
> FYI, the solution using join[] (or addsuffix[]) is *substantially* faster
> than using wikify to assign widget attributes.
>
> You:
>
> <$wikify name=style-value text="
Hi Tony
Bold effort!
I spotted something in there that I do quite often, but I do it a little
differently:
You:
<$wikify name=style-value text="""color: {{!!color}}""">
style=<>
Me:
Check this in
devtools
Not sure which you might prefer...
On Thursday, October 1, 2020 at 8:13:01 PM
https://wikilabs.github.io/editions/custom-markup/#Global%20Pragma%20Definitions
Perfect. Thanks, Mario.
On Sunday, November 29, 2020 at 7:55:01 AM UTC-6 PMario wrote:
> On Saturday, November 28, 2020 at 6:44:01 PM UTC+1
> codacoder...@outlook.com wrote:
>
> *Scoping rules*
>> What is the scope
On Saturday, November 28, 2020 at 11:44:01 AM UTC-6 coda coder wrote:
>
> Joshua - your guidance and background on unicode codepoints and the
> potential disconnect with font support is second to none. Excellent
> diligence!
>
> Face-palm - JOSIAH. Blame post-thanksgiving
Wow - I mean just WOW! I just spent I-don't-know-how-long reading all
this stuff - yes, ALL four threads (I managed to resist hunting down any
off shoots to the main forum but if there's anything over there I SHOULD
read, please let me know!)
Joshua - your guidance and background on unicode c
Hi Cd.K
I hope you'll take Jeremy's word for it - he's telling you the same as I
told you (same link too). Browsers have been collapsing white-space for
over 25 years - even before there was any CSS.
You space-space idea seems like you're trying to "fudge" a little bit of
markdown into HTML. L
On Thursday, September 19, 2019 at 3:44:02 PM UTC-5, Alan Aldrich wrote:
>
>
> Hopefully I am explaining this clearly.
>
Well, I'm following it ;)
> What this means to me is we will likely need a customized solution.
>
I think so. In js, you could rebuild the datalist "live" as the input
On Wednesday, September 18, 2019 at 10:11:10 PM UTC-5, Alan Aldrich wrote:
>
> I don't know if there are exceptions to this rule for elements like
> datalist, but there should be.
>
They should have used --id or similar. (data-id would tread on author
territory so that's no good).
> Re-usin
tence of ids
> in the content. As I pointed out, I am merely saving content from the web,
> which already has ids and id based navigation.
>
> On 19 September 2019 8:14:08 AM coda coder > wrote:
>
>> Hi Riz
>>
>> You should probably read my response he
Hi Riz
You should probably read my response here before you spend any more time
with this:
https://groups.google.com/d/msg/tiddlywikidev/C2JWmchpyaw/czI86aDvAAAJ
But understand, no one will *stop* you creating ids... if they are
replicated via transclusion, DOM APIs will return a node collecti
On Wednesday, September 18, 2019 at 4:58:27 PM UTC-5, Alan Aldrich wrote:
>
> coda coder,
> Yes the *id* attribute is required for the datalist element to work. It
> must match the *list* attribute of the input element generated by the
> EditText Widget. I am requesting we modi
Would be nice but...
The options list can't be styled (or can it?)
A datalist and associated input element are associated via the id
attribute. You can very easily "break the rules" by having more than one
element with the same id. Think: transclude your tiddler {{DataList Feature
in Edit-Text
> The design of TW5 tries to use the minimum number of primitives needed to
support the required complexity.
Jem Gem.
#justsayin
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from i
You might take a look in here...
https://tiddlywiki.com/dev/
On Sunday, December 9, 2018 at 7:12:06 AM UTC-6, joearms wrote:
>
> I'd like an overview of how wikitext ends up as HTML
>
> 1) macros are expanded
>
>
> ?) html is output
>
> or is it
>
> 1) wikitext is parsed
>
>
> etc.
>
>
Looks interesting. How is that meant to be used?
On Monday, February 19, 2018 at 1:39:46 PM UTC-6, Simon Huber wrote:
>
>
>
>> Kudos. Nice bit of tech-sloothing, Simon.
>>
>>
>> Thanks :)
>
> I guess something like this then could wrap it in a sidebar?
> https://gist.github.com/Noitidart/8728393
Kudos. Nice bit of tech-sloothing, Simon.
On Monday, February 19, 2018 at 12:44:00 PM UTC-6, Simon Huber wrote:
>
>
>
>
>
> *The settings that appear to make it work faster when tab is in
> background, for chrome/chromium and firefox:firefox (58) (goto about:config
> [do it at your own risk])*
On Monday, February 19, 2018 at 11:34:42 AM UTC-6, Simon Huber wrote:
>
> Another issue is that its operation slows down a lot when one changes
> browser tab to other pages (and that's what this should be good for)
>
> does anybody know a why and a how for that?
>
The new window belongs to the
On Monday, February 19, 2018 at 9:52:35 AM UTC-6, Simon Huber wrote:
>
>
> np. And again, a regular textfile bookmarklet is generally better (for the
>> OP solution). File/SaveAs is good enough (sans images). And it doesn't
>> *need* to be in the sidebar, either... create two, one of each.
>>
On Monday, February 19, 2018 at 9:26:13 AM UTC-6, Andreas Hahn wrote:
>
> That's pretty cool.
>
>
Yep, I like it a lot, though not necessarily for TWs. The problem there is
that dropped images surface at the dropzone widget, not at the tiddler.
With a regular "textfile" bookmarklet, the imag
On Monday, February 19, 2018 at 9:19:06 AM UTC-6, Simon Huber wrote:
>
> hm... how do you do that with local files?
>
>
This one is a bit prettier too...
data:text/html;charset=utf-8,%20Textfilebody,
.vw-iframe{margin:0;border:none;height:100%;width:100%;}
Or node/Tiddlyserver...
data:text/h
Hi Simon,
Before you commit to the notes testpilot as a starting point, throw this
into a bookmark URL field:
data:text/html;charset=utf-8, Textfile
Open it up and play. You can even paste images.
I did have one that saved full html but I can't find it right now.
Either way, this saves LOC
On Tuesday, February 6, 2018 at 8:24:17 PM UTC-6, TonyM wrote:
>
> Folks,
>
> Recent exploration of this suggests if we could rename fields yet retain
> their value, and handle prefixes much could be achived
>
> eg The "menu tiddler"
> http://127.0.0.1:8088/Local-Instances/Development/MyMenus.h
Is there some reason ## can't used again? And how about strict "[[...]]"
and '[[...]]' for arrays?
{
a: {
b: {
c: {
x: 5,
y: "six",
z: "[[7, "eight"]
}
}
}
}
-> "a##b##c##x", 'a##b##c##z"[[0]]"' etc.
--
You received this message because you a
+1
On Friday, January 19, 2018 at 11:55:55 AM UTC-6, Evan Balster wrote:
>
> *a warning mechanism would still be immensely useful with a fraction of
> this functionality*.
>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe
If that's you just testing, that's fine. Otherwise you (the middle man)
are stealing a click from me (user) targeting YT itself -- in my view,
naughty ;)
On Tuesday, January 16, 2018 at 9:42:01 AM UTC-6, Simon Huber wrote:
>
> Ah but... trying to go fullscreen on the yt video fails -- the video
Ah but... trying to go fullscreen on the yt video fails -- the video
disappears.
On Tuesday, January 16, 2018 at 9:31:42 AM UTC-6, coda coder wrote:
>
> Tried FF on Win10 too. Same.
>
> However (brace yourself) it works on FF 59.0a1, Win7
>
> Can't try Win10 (don't
Tried FF on Win10 too. Same.
However (brace yourself) it works on FF 59.0a1, Win7
Can't try Win10 (don't have FF 59).
On Tuesday, January 16, 2018 at 9:26:05 AM UTC-6, coda coder wrote:
>
> No, sorry. Same as before.
>
> On Tuesday, January 16, 2018 at 8:09:11 AM UT
No, sorry. Same as before.
On Tuesday, January 16, 2018 at 8:09:11 AM UTC-6, Simon Huber wrote:
>
> thanks @coda coder,
>
> that's bad news, I really want this :D
>
> I changed something I should have done earlier, if you want to give it
> another try
>
> I
Simon,
I'm assuming your class addition to the body element should be toggling as
I toggle F11? If so, it's not working here. Your class "tw5-burning-tree"
once applied, is never removed. Your console message always says "not
fullscreen" regardless of the actual state. Also, your class is ne
On Monday, January 15, 2018 at 11:22:31 AM UTC-6, Evan Balster wrote:
>
> Hey, Coda —
>
> Yeah, I'm lazy and write unterminated widgets quite often.
>
>
> General warning about the timer plugin: I'm still working out the
> design. In particular, it's possible for a "time=X" timer to be set aft
On Sunday, January 14, 2018 at 11:25:17 PM UTC-6, Evan Balster wrote:
>
> Hey, all —
>
> Show-and-tell time!
>
>
It's probably benign, Evan, but there's an unterminated $tiddlerWidget in
Pomodoro Timer.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDe
Totally agree with Mat - it was a very interesting discussion.
Evan, Eric, Mario: crystal clear, Jeremy: mostly poor -- damn shame. Tried
to post a message to that effect but the chat window seemed to be disabled.
The most frustrating part for me was when the discussion was centering
(cycling?
On Tuesday, December 26, 2017 at 11:23:36 AM UTC-6, Evan Balster wrote:
>
> Explaining the use-case is pretty simple: Most users of TiddlyWiki are
> looking at markup and start off thinking linearly rather than in terms of
> widget trees. Requiring them to grok the internal architecture puts
Just some "first-read" feedback ...
On Monday, December 25, 2017 at 1:56:28 PM UTC-6, Evan Balster wrote:
>
> Hello, all —
>
> In the other thread Jeremy mentioned his interest in implementing "lateral
> variables" in TiddlyWiki. These would be variables that can be set
> somewhere in wikitext
39 matches
Mail list logo
