WI regex keys

[Wolfsblvt]

WI keys will now support regexes. (both keys and secondary keys)

• Regex uses javascript syntax, same as Regex extension. Flags are allowed and encouraged
• Key control switched to select2
• input show dropdown of all already chosen keys of this book
• special display of regex keys and regex syntax highlighting

Detailed list of all other changes:

• Custom tokenizer for regex parsing, allowing comma in regex
• Keep mobile-compatibility by switching to textarea
• select2 utility method to pre-fill options
• New inline display mode of select2 multi to save space
• moved select2 styling to its own file
• Cache all keys for the loaded lorebook
• Key selection dropdown shows all keys and how often they are used already

[LenAnderson]

Does select2 allow editing of the keys? Or only delete and re-add?

[Wolfsblvt]

Only delete and re-add.
It's basically the "tagging" feature that they fleshed out.

I could try and implement some kind of edit functionality, but is that worth it?

[LenAnderson]

That's gonna be pain, especially with regex keys.
It's one very poor UX behavior that I really hate about most implementations of these fancy combo boxes. Very few implementations seem to care enough to make it actually usable and not just look pretty.
Even a click to prompt modal would be better than delete and re-add if select2 is built too strongly against editing entries.

Edit: what I'm saying is: yes, definitely worth the effort.

[Wolfsblvt]

select2 is basically an extended dropdown selection box with search and all. So yeah, there is no built-in edit functionality.

I see your point. And it shouldn't be too hard to implement. Left-click an entry opens it in edit-mode where you can edit the text of it again.
I think that's easy enough to implement. A bit work, but possible. I'll add it to my list and work on it soon. Question is - is that request important enough so that this PR should wait before its implemented, or can this be added without it to staging and the imminent next big ST release, before I come around implementing it?

[LenAnderson]

I wouldn't call it a showstopper. ST isn't exactly known for great UX in the first place.
But I know I'm going to hate dealing with WI keys until it's fixed.
Maybe make select2 optional, since the plain textarea is still there for mobile anyways.

[Wolfsblvt]

Request done.

[valden80]

@Wolfsblvt
PLEASE! Make this optional! It's the main thing why I'm switched from the Kobold AI when they start implementig new UI (UI2) to the ST.
IT's ABSOLUTELY horrible UI for anyone who prefer keyboard and want minimal mouse usage. Simple plain text string for keywords is 10 times better experience for me. Please, don't broke something that already works!!!

P.S. I'm proposed about regexp keys long time ago, but if only I know that they will come with this...

[Wolfsblvt]

The "don't make nice UI" people appear. Not unexpected.

The plain textbox still exists for mobile anyway. I can easily make this a toggle.

[valden80]

@Wolfsblvt
Between "nice looking" and "easy to use" - I prefer second. Please, try to test it yourself in something close to real situation (real for user who actively use WI).
For example: just try to enter 5+ WI entries in row with ~10 primary and secondary keys for each. I bet - you will be tired and annoyed with "nice" interface very quickly if you need to switch between keyboard and mouse to add/edit for every keyword...

[Wolfsblvt]

Typing for 10+ world entries is pretty easy, because the input hasn‘t changed at all. You can use Enter instead of comma, that‘s the only difference. Fixing mistakes until you have finished the key by typing Enter/Comma is easy too. Going back to a key with keyboard no. Editing past entries is okay too, but I can see how having to change keys regularly for whatever reason would be kind of annoying.

This PR is on hold. The UI portion will be likely scrapped completely and just the Regex matching stays. We have another big thing planned for which I am really excited.

[Wolfsblvt]

Added an inline switcher of fancy/plaintext input modes. It'll reload the WI window and changes the input types back to the textarea, or the new select control. Saved in user settings.

Also did a few more hotfixes I ran into.

Even though I want to revamp the stuff like I said above, I think actually adding Regex key matching sooner than later makes sense. Would be sad to hold back the actual matching functionality if that one is completely done already.
If you think this is too risky, or I should still scrap the whole new UI control stuff, I can rework it again. I just couldn't bring it over me to just delete everything :/

This PR also makes the existing select2 inputs in WI (world selector at the top, character filter) slimmer and a bit nicer. So yeah.

[Wolfsblvt]

@deffcolony seems like the repo bot is broken. There are no merge conflicts anymore but it didn't remove the tag.
maybe because when I pushed the commits it was still in Draft mode, so the checks didn't ran?

[Cohee1207]

Now all we need is docs for it all.

[Wolfsblvt]

I'll make docs this weekend, for all the new WI stuff.