Command palette plugin v1.0 , powerful context search bar, search under filter, etc

Peter · July 21, 2024, 5:26am

I added a small stylesheet tiddler which gets the command palette to match my color scheme a bit better. Hopefully this is a good spot for you to start:

.aa-Panel {
  background: <<colour modal-background>>;
}

.aa-Item {
  color: <<colour foreground>>;
}

.aa-SourceHeader {
  color: <<colour foreground>>;
}

.aa-Input {
  border-color: <<colour tiddler-link-foreground>>;
}

.aa-Label {
  background: <<colour modal-background>>;
}

linonetwo · August 11, 2024, 5:29pm

Posting here won’t help other much. Make PR in Github is the best choise.

linonetwo · August 11, 2024, 5:31pm

Latest v1.7.0 have history search list. See if it cause bug on filter search.

In next version this plugin will split into tw-command-patette and autocomplete plugin. So I can embed a pure autocomplete input on my new layout.

baiguai · August 28, 2024, 6:03pm

I’m SO glad this plugin is being actively updated etc!
I’ve been using the original and LOVE it.
I better grab this modernized version.
Thank you!

BurningTreeC · September 21, 2024, 1:27pm

Hi @linonetwo !

I have tried your command palette with TiddlyFlex and there are some minor issues I’d like to fix with your help.

With the command palette closed the dropzones of the different story views in the different columns don’t work. Does your CSS have something to do with that or do you change some widgets?
If I find a Tiddler with the command palette and hit Enter on Chromium browsers it doesn’t scroll to that tiddler. That’s a sign that and additional scroll gets triggered somewhere within the command palette. On Firefox this works well because FF doesn’t stop scrolling if there’s a second scroll. But Chromium does, it simply stops scrolling… or do you use a storyview in your command palette?
The “untagged” Button in the sidebar under More > Tags is really big … that’s a minor issue but we can fix it

Thank you for your time!
Simon

linonetwo · September 23, 2024, 4:37pm

How to test this, I tried open&close command palette, and drag tiddler from tw5-com to the wiki, and it still show the $:/import.

I’m simply sending this message in my widget, do you handle this standard message?

github.com

tiddly-gittly/tw-command-palette/blob/341bf5a47a3b5f7d155576f71f207c845fbe0c06/src/autocomplete/widgets/widget.ts#L135-L143

    
      
          if (!state.context.noNavigate) {
            // let layout handle the layout change before navigation https://github.com/Jermolene/TiddlyWiki5/discussions/8123
            // $tw.wiki.setText('$:/layout', 'text', undefined, '', { suppressTimestamp: true });
            this.dispatchEvent({
              type: 'tm-navigate',
              navigateTo: itemUrl,
              navigateFromNode: this,
            });
          }

I see it works on FF but not Edge. What should I do?

Fixed, it is caused by my custom lingo macro. And I will remove this lingo macro after feat: i18n framework based on extracting translations from plugin's /languages/ to /language/ by linonetwo · Pull Request #8435 · TiddlyWiki/TiddlyWiki5 · GitHub

linonetwo · October 27, 2024, 11:11am

Command palette is now a simple wrapper around <$auto-complete-search /> widget plugin. And providing some initial setup and configs.
When using CPL to install command palette, it will auto install this auto-complete-box plugin as dependency too.

So other plugins can use this widget to build search box for their own UI. So your plugin works for people don’t want to install command palette.

baiguai · November 5, 2024, 6:28am

I love this plugin so much. The save feature allows me to work mostly mouse free.

Is there a way to search field values?
It doesn’t appear to do that, so I’ve been required to fire up the advanced search and click the fields tab etc.

Thank you!

linonetwo · November 6, 2024, 7:36am

I think it is configuable in control panel. You can search configs for command palette by search $command palette (and it is on the bottom or search result)

You can config this so it always works, I already put what I need as the default value:

or you can use filter, like search for [search:someFieldName[xxxx]]