Yeah, that's kind of my point. I understand why standard inline javascript is not something that can be part of the core, or anything so fundamental to the way tiddlywiki works. That's why I'm wondering if it would be possible to sanitize it, removing any DOM related stuff or anything that might pose a security problem, but allow things like string and array manipulation and basic logic. I've found the wikitext and widget syntax within TW5 to be a lot more difficult to learn than Javascript. If I'm not alone in that, being able to do some of the lifting with a skill that is more widely applicable might help with uptake with new users.
Best wishes, Adam On Tuesday, January 15, 2019 at 7:13:05 PM UTC, @TiddlyTweeter wrote: > > My two cents as a person who understands quite a lot of what JS does but > has little comprehension of how it does what it does. Nor much interest in > it for its own sake. > > All I'd say is its probably a good idea to know what you are doing before > enabling it without restriction (which you can do). > > As far as I grasp it, TW JS has a specific model of the "DOM" that is > different from a lot of JS? So its coding needs follow a specific approach? > > On the other hand, if you budding into JS and like that kind of thing, why > not? > > Just thoughts > Josiah > > > -- 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/30434d59-020c-4d7a-9c49-07999c6f9b80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
