On Sunday, April 29, 2018 at 5:20:55 PM UTC+2, Mat wrote:
>
> I note that if I create a new tiddler, named *New Tiddler* and, in
> another tiddler, type [[ I automatically get also the closing brackets
> [[]] (and cursor conveniently placed in between)
>
That's because of the "-closebrackets" addOn. It basically auto-closes (),
[], {}
> but as I begin to type *New* there is no text autocompletion or
> suggestions.
>
The current implementation has no idea about TW-titles. ... We would need
an eg: "title-hint.js" function.
There may be a tag-hint.js, field-hint.js .... and so on.
> Generally put, If I type [[ or <$ or << then I want for all tiddlers /
> widgets / macros to have a list show from which I can select an entry. If
> the string is extended to e.g
>
<$... Oh, that's a widget-hint.js functionality, which nobody wrote yet.
...
> Does this functionality not exist?
>
Yes. .. It doesn't exist.
> What would be required to make it exist?
>
Programmers with some love to detail. ...
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"
So we will need to investigate to enable the possibilities with
text/vnd.tiddlywiki .... Where basically all the addOns could be needed at
the same time.
The problem is: It's complex to guess what the user actually wants to see,
without a specific type definition. ...
Codemirror library knows about a mixed mode, which may be possible to be
used. But as I wrote. The real challenge is to detect which mode should be
active. ... We will need to detect the users intention while they are
typing. ...
> I cannot find any instrux for that "Autocompletion" addon.
>
We did the basics. ... But nobody said, it's finished. ;)
>
> 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% :))
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.
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?
The final goal needs to be, that the TW build system auto-creates the basic
structure. But the "prose text" will be user-made.
> What would it take to enable this type of functionality?
>
A lot of work and spare time.
> 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 will have the info. ... But it's relatively low level
developer stuff. But the existing addOns can be used as examples. ..
have fun!
mario
--
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/7b785826-0cef-46e0-85c1-f6fec4b497a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
