This is really amazing. I'm just starting to learn development for TW and I always though: "hey, TW could be a very nice tool for coding: look at this fine hypertext structure, no need of this linear mess!". And this can actually bring a new age of coding (for TW) -- I mean, when TW becomes ready to be the _main_ tool for coding.
Not much to say about the highlightning -- it is great, although in the cmEdit mode it's poorer than in the view mode (especially for CSS). Actually, I haven't understood the thing about those tags and fields in a)-d). Do you mean that you want to figure how to declare in which mode the highlightning should be used (XML, CSS, JS or Python)? I think it can be set on user to decide (just make some settings so that one can choose which tag/field defines each mode). As for the mixed mode, aside elaborate templates (like in TiddlyTools) it seems that usually the only need for mixed mode which happens in TW is CSS + JS in the same plugin tiddler, isn't it? Some side notes: * if it is possible to read the core code of TW highlighted within TW it adds more perspective for development (I mean, this would introduce more explorability of the core, although cooked TW is less readable than separate .js files) * it seems that there are some other things to overcome so that TW become a really good tool for development (including a "cooking" engine within TW), but anyway this is a great step forward * I have no idea why Python is here? Do you intend to use TW as a development tool for Python? Thanks for working on this, looking forward for the separate plugin version. Yakov. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
