Once we are changing the command searching, (btw I also really like the plugin-starting-name idea), would it be to much resource-cost for the search to work somewhat like google instant search?
Well actually we dont need so much, it would just be helpful that if the user doesnt start the searching with the accurate plugin name, he gets the command shown anyway. So if he searches for "pane", he will obtain a list of commands that include the word pane. This way, when he knows he wants to change the pane but doesnt know the command, just by writing that and tab, he will have all the options. Since there are not hundreds of commands, I think that will be enough, but if we had much more, it would also be helpful to be able to find them in the following way: *User writtes:* "men edi"+tab *Command results:* activate-edit-menu Because the searches used non-full words, and in random order. We could even, if the user gives several words, and there are no results, just search word by word and offer the matches. That will always be more informative than a blank answer, and maybe points the user in the right direction of the comand search. Going one step further, with this search strategy we could do two more things: - Include the "deactivated plugins" commands also, and if the user tries to execute one, leo will tell him: "Plugin not active, follow this hyperlink to activate the node". This way the user knows what leo can do, and even when he searchs for another thing, he will still be learning more possibilities leo has, a few at a time. - Give longer names to commands, more descriptive. This would help users that dont know the commands to find them out easier. Cheers guys. On Wednesday, August 14, 2013 9:25:42 PM UTC+2, Jacob Peck wrote: > > Rev 5904 adds the following two commands as a part of the printing.py > plugin: > > print-selected-node-body-html > --- > Opens up the print dialog to print the body of the selected node as a > rendered HTML (i.e., rich text) document. > > print-preview-selected-node-body-html > --- > Opens up the print preview dialog to preview the body of the selected > node as a rendered HTML (i.e., rich text) document. > > These commands work nicely with Terry's recent work on the rich-text.py > plugin, allowing users to print a close approximation of the final > results of rich-text nodes. > > -->Jake > -- You received this message because you are subscribed to the Google Groups "leo-editor" 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
