Hi K,

The h3's are generated by /core/modules/parsers/wikiparser/rules/heading.js 

Let us know how you get on.

Regards,
Richard

On Saturday, October 7, 2017 at 4:38:51 AM UTC+11, K wrote:
>
> Perhaps instead of doing that, if I could find where TW parses and renders 
> the content, I could select all the nodes/arrays and filter them to modify 
> what I want ie. write an if statement inside the parse loop so that it 
> modifies how the h3 tag is rendered. 
>
> Or if I find the render function, I could put the if statement there ie. 
> (if h3) then do this etc.
>
> I just want to scrap the wikitext, tbh the only wikitext I use are the 
> prettylinks -> because ckeditor doesn't do any wonky things to them. 
> Compared to Ckeditor, the speed of editing using wikitext is relatively 
> low, I can do the same amount of work in 30 min in 10 min with html editing.
>
> On Friday, October 6, 2017 at 2:33:06 AM UTC-7, Jed Carty wrote:
>>
>> I agree with BJ, doing this in tiddlywiki is this task that is better 
>> suited to a wikitext than javascript. In my experience using 
>> document.querySelectorAll(..) in a wiki leads to strange edge cases because 
>> everything can be re-rendered individually.
>>
>> Do you have existing html that you are trying to put into tiddlywiki or 
>> are you creating it in tiddlywiki?
>>
>> If you are creating it in tiddlywiki than it would be much simpler to 
>> create a macro for the different tags and put that in places where use them 
>> instead of the tags directly.
>>
>
> @jed If I made a macro for each tag, I'd have to call it potentially 
> hundreds of times....not feasible imo. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/786c11ec-b610-42e8-8e8c-5f402c8bbb37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to