Simon and Mario - big thanks for clarifications!
The current implementation has no idea about TW-titles. ... We would need > an eg: "title-hint.js" function. > Seems like a most common use case. There's a limited set of titles and easily findable. Could maybe even have all titles in a hash table that is updated on either tiddler save or wiki save. > tag-hint.js, field-hint.js , widget-hint.js > >> > eg: > The existing -closetag AddOn allows us to say eg: <div> .. As soon as you > hit the > letter it will add </div> ... Which is nice. .. > The problem is, that it only works if type is set to "text/html" > Ah. In deed a severe limitation! (...and I fail to understand why it can't be just made to work also in text/vnd.tiddlywiki. I mean, if the user hits the > and Ctrl+space then he wants <this-string repeated again with a / after the <. What does this have to do with tiddler type? ) The problem is: It's complex to guess what the user actually wants to see, > without a specific type definition. ... > Could you give an example of what could be misunderstood? I understand I'm naive about it but doesn't the user 'simply' want to do the usual TW stuff? I.e primarily wikitext and occasionally html and css? These are all covered in text/vnd.tiddlywiki. Also, writing class="foo should show a select list of all classes prefixed >> foo. >> > > This will be extremely complicated and probably slow. TW allows macro > calls in StyleSheet tiddlers. So it's close to impossible. So about 99.7%. > ... or may be 98,7% :)) > Again, I understand I'm naive but... there is clearly some already implemented mechanism that keeps track of, or seeks out, the style classes.... so isn't it "just a matter of" comparing that foo pattern with those? (...and, "Well Mat, if you think it's so simple, then you do it" ...unfortunately it is not simple for me but for other reasons.) > Further, it seems that when I in a Stylesheet type bord (as in "border") >> that *is* recognized as an attribute name because it remains colored red >> until I've typed the last letter in border (and before any eventual space >> character). But I barely see any point with this recognition without >> autocomplete - ? >> > > Yea type: text/CSS ... knows a lot about CSS parameters. .. CTRL-SPACE is > key here. IMO it's already useful, if you don't know the exact parameter > names. It may help a lot with typos. > But so it *does* know that it is the beginning letters of a CSS parameter? ... and then couldn't it just instead list those and let me select the desired one? I also want be able to hover or click on certain keywords and have some >> info text come up. For example, if I click on a macro then perhaps the >> parameter list shows (extracted from some docs or from the macro >> definition) and if I click on a style def attribute then it's possible >> values come up. >> > > So if we come up with a "doc-format" you volunteer to implement the texts > .... right? > Well, the reasonable thing is to use an automated template that e.g extracts the parameter list or some defined field in the docs. As for style def attributes, it seems it is built into the browser inspector so I guess there is a db in every browser. It is all about some pattern recognition and showing a list of stuff pulled >> from either some dictionary or a search in the code. >> > > codemirror docs <http://codemirror.net/doc/manual.html> will have the > info. ... But it's relatively low level developer stuff. But the existing > addOns can be used as examples. .. > Is there little generality in the -hint.js stuff done so far? Or is every -hint.js different? <:-) -- 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/6ee7ebb3-c581-410f-a86b-dd3ebd347b58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
