Thanks again. I did check the supplied snippet and was struck by the similarity - standards,eh :-) Anyway, I've got the three tiddlers setup as you suggest - I assume the fact that the error comes from Lexer.js means that the function has at least been found.
I'll play around with a few things, but I do appreciate your assistance. I'm an ESL teacher: my students probably feel about English the way I feel about TW -powerful, but a bit tricky! On Tuesday, 3 July 2012 10:10:19 UTC+10, PMario wrote: > > On Jul 3, 12:30 am, tejjyid <andrew.x.w...@gmail.com> wrote: > > http://code.google.com/p/jspos/ > > > > The "string.match is not a function" message comes out of the Lexer. > > > > What I've done is put the POSTagger & Lexer functions, as well as the > > "database" variables, > > into the systemConfig-tagged tiddler (is its name important, and if > > so, in what way?). Then I'm implemeting the "body" code snippet as > > inline Javascript. > > systemConfig tagged tiddlers are ordered by name and started in that > order by the TW core. So aa.js has higher priority than bb.js. > > Did you have a look into sample.html with a text editor? > it's quite similar to my general description. > > <script type="text/javascript" src="lexer.js"></script> > <script type="text/javascript" src="lexicon.js_"></script> > <script type="text/javascript" src="POSTagger.js"></script> > > If you name your tiddlers Lexer.js, Lexicon.js_ and POSTagger.js they > will be started in the right order. Uppercase has higher priority than > lowercase. > > I'll have a closer look but not now :) > -m > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/eiJ8wrcH-8sJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
