-
Good points, thanks! There certainly are a lot of issues for FL to consider.
-
Please feel free to write a suggestion or two. I have no problem at all supporting a better proposal (and deleting my suggestion). I'm completely in favor of consistency between the column names, facet names, and field names. I also believe that the breadcrumbs should be consistent with the syntax, whatever that syntax turns out to be. I understand
-
[quote user="SineNomine"]I think that whatever the breadcrumbs show should be functional syntax... which to my mind does not mean that the breadcrumbs need to stay the same as they are now. Type:Systematic-Theology is human-readable syntax.[/quote] Perhaps make a suggestion on the feedback site? I’d like to see something good come out of this!
-
[quote user="MJ. Smith"]I do object to allowing a space after the colon as that is a bad habit to develop[/quote] Perhaps suggest that the breadcrumb’s space after the colon gets removed, since it leads to problems with filtering. (I always saw it as an optional space that shouldn’t be required by the filtering grammar. It’s certainly not a hill I’m
-
I’m sorry, I thought we were talking about using the more readable breadcrumb format in the find box, not the mechanism or behavior of how to copy the breadcrumb to the find box. Does this go back to whether the breadcrumb should show the actual syntax, rather than the more user-friendly syntax?
-
[quote user="MJ. Smith"]I'd go so far as to ask why the average user would assume the filter manual entry line followed the bread crumb model and why they would want to copy what they have in the breadcrumb into it.[/quote] It’s more natural, readable, or understandable? It wouldn’t require the user to learn a different syntax? When we use an assistant
-
[quote user="MJ. Smith"]The actual syntax is what has to be available to the copy function.[/quote] Agreed. Why type the syntax it when it could be copied and pasted. [quote user="MJ. Smith"]The question is whether (a) that slows the user learning of the actual syntax[/quote] FL has given customers the faceted filtering option -- a drastic improvement
-
What Google conventions are you referring to, please? How much overlap exists between filtering syntax and search syntax? Do any types of Logos (non-faceted) searches use breadcrumbs? I believe you mentioned several times how you’d want to see underlying search strings (from context menus?) as I think you had to figure out some particular syntax on
-
I like the sidebar and facets, but I think the breadcrumbs are misleading. They're written in a user-friendly style which differs from the syntax that the find box uses. But if you try to use that string in the Find box, it doesn't do what you'd hope it would. Now imagine if the Find box actually could understand that user-friendly syntax. I think the
-
You can control whether or not a note icon appears by selecting a specific icon to use from the dropdown circled in red.
-
Hmm. type:systematic theology (without any quotes) also returns 82 results type: systematic theology (without any quotes) returns 3 results, not 2 Now I'm totally lost for two more reasons: Why does the absence of quotes change the number of results for type: systematic theology (vs. type: "systematic theology" )? Why does the lack of quotes still produce
-
The space after the colon is throwing it off. type: "systematic theology" (2 results) type:"systematic theology" (82 results) Perhaps someone more knowledgeable can explain the reason to us. [quote user="NB.Mick"]Maybe because of the space character that works as a logical AND? Try the rule type:Systematic-Theology without any spaces.[/quote] Which
-
Same here
-
We know that feedback is being responded to by looking at the planned and in progress changes on the Roadmap (along with the status emails we receive about items we've voted on). Users can also filter to see what's recently done (although that's on a board-by-board basis). That's probably good enough, without FL spending time writing changelog entries
-
I think it’s beneficial to keep feedback changes independent of program changes. It lets us focus on suggestions specific to the feedback site, rather than bug fixes or improvements that had never been suggested or planned in the first place.
-
Graham provided a direct method for adding a link! Here's an option which uses an anchor to link the commentary to the bible reference. Highlight the commentary text to add a note to the commentary. Ensure that a note icon is selected (so that icon will also appear next to the bible text). Add a bible reference anchor to the commentary's highlight.
-
Great! Here’s the link so others can vote: https://feedback.faithlife.com/boards/logos-desktop-app/posts/add-checkbox-to-notes-text
-
[quote user="Rosie Perera"]You can insert/paste this character: ☐[/quote] Yep! Unicode also has checked box characters ( ☑ and ☒).
-
Emoji and symbol fonts will let you insert a character that looks like a checkbox (with or without a check mark), but it won't be interactive. Another possibility is to post a suggestion that checkboxes are added to the Notes editor at Faithlife's Feedback site .
-
Ah, that clears up the mystery, thanks!