In my exposure to software architecture (not extensive), I've seen nothing like whatTW5 seems to me to be, a fully interactive browser based application, featuring a user facing domain-specific language (WikiText), and a module/plugin system for extensibility, all self-contained in a single HTML file. I wonder about how much of it is designed and implemented. To start, though, I'm curious as to how the app manages to load the strings (are they stored as strings?) representing modules into itself? I'd love to understand this on every level; abstract, are there design patterns concerned with this, general programming nations, *et cetera*; down to the concrete, is eval() used, what files/lines in the git repo are responsible for turning module text into executable JS? Hope this makes sense. Thanks.
-- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/2ae8a3bb-e5e6-47f0-aa8e-156d4f766e73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
