Search functionality #239
Replies: 14 comments 7 replies
-
I think concept (1) would be really nice, since it would allow people who
are using commercial apps to have the same functionality in AsTeRICS-grid
and thus, facilitate the use with a feature they are used to have.
As a first start, I believe concept (1) would be valuable.
Something like an icon "search" or a "search bar" that opens a keyboard
and then, the user can type the word and retrieve all the grids where this
word is located.
This icon or search bar could be part of the global grid so that it is
available in all grids.
Professionals who are working with multiple AAC devices and grids with
different organizations would benefit from searching and finding the words
quickly to either model or communicate.
Em ter., 14 de fev. de 2023 às 05:30, Benjamin Klaus <
***@***.***> escreveu:
… Quote by @tiekoide <https://github.com/tiekoide>:
I have a question about the possibility to search for elements in grids (
#77 <#77>). Therapists
started using and asked if this was possible, since it facilitates
navigating the system.
Yes, it's a good idea, but I'm not sure how it's best to implement.
Do you think users should be able to search for words on their own, or is
it something only professionals will use? I've just looked at a commercial
AAC app and there they only have a search bar at the top, which I think
cannot easily be used by the user, unless he/she is able to type on a
normal hardware keyboard. So I see two general concepts:
1. Separate search fuctionality somewhere, within an own view/menu
entry/modal. Only usable by typing a word using a standard keyboard.
2. Integrated search functionality within grids. Users would be able
to input a search term on a keyboard grid and then get some search results
also represented within a grid (similar as YouTube search now). Pro: users
can use it, Con: it's only available if the keyboard and search
functionality is built up manually within the grid/existing in the
configuration.
I think in a first step it would be easier to implement concept (1). But I
would be interested about your opinion and thoughts how this search
functionality ideally should work and look like.
—
Reply to this email directly, view it on GitHub
<#239>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3GQUAYSJ3O53UMWKNXYBDTWXM7CRANCNFSM6AAAAAAU3IAFRM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Tie Koide
Professora Associada
Departamento de Bioquímica e Imunologia | Department of Biochemistry and
Immunology
Faculdade de Medicina de Ribeirão Preto | Medical School of Ribeirão Preto
Universidade de São Paulo - Brasil
***@***.***
***@***.***
http://labisismi.fmrp.usp.br
|
Beta Was this translation helpful? Give feedback.
-
OK, then I think it would be most logical to add a new button "Search" at the top of the normal grid view like here: It would open a modal (popup) where a search term could be entered and the results are shown within the modal. Do you think we also need the path from the start grid to the word or only the grids where the word is located? |
Beta Was this translation helpful? Give feedback.
-
In my opinion, this search button should be after the "trash", a
"magnifying glass" as part of the "main bar" of the global grid, so that it
is available when the system is being used in full screen mode, which is
probably the most used form.
The "search" function would be available not to "construct" the tables but
to find the elements while using the system. (so probably I did not
correctly understand concepts 1 and 2..., sorry : the search would be
available to the user...)
I think only the grids where the element is located would be enough as
search results.
This would facilitate the "real time use" of the system, less is more...
Too much information about the path could confuse the rapid use of the
communicator (in my opinion).
And if the search is too recurrent, maybe it is a sign for the user to
put/add the element somewhere else they are easier to find...
Em qui., 16 de fev. de 2023 às 10:22, Benjamin Klaus <
***@***.***> escreveu:
… OK, then I think it would be most logical to add a new button "Search" at
the top of the normal grid view like here:
[image: image]
<https://user-images.githubusercontent.com/2537025/219361035-23a8967e-8642-46cd-837a-9ebd77212e3a.png>
It would open a modal (popup) where a search term could be entered and the
results are shown within the modal. Do you think we also need the path from
the start grid to the word or only the grids where the word is located?
Maybe it would also make sense to implement a "guide" which shows the path
to the element by highlighting the elements that are necessary to select?!
—
Reply to this email directly, view it on GitHub
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3GQUAYUP6RBVZLM7HS7XZTWXYS2JANCNFSM6AAAAAAU3IAFRM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Tie Koide
Professora Associada
Departamento de Bioquímica e Imunologia | Department of Biochemistry and
Immunology
Faculdade de Medicina de Ribeirão Preto | Medical School of Ribeirão Preto
Universidade de São Paulo - Brasil
***@***.***
***@***.***
http://labisismi.fmrp.usp.br
|
Beta Was this translation helpful? Give feedback.
-
OK, but I think we should have both: the search button in the top menu bar as in my screenshot and maybe additionally the possibility to open the search modal by selecting an element within the global grid. If it's only in the global grid, the search wouldn't be accessible for custom global grids. |
Beta Was this translation helpful? Give feedback.
-
For the time being try this: You can click on elements in the PDF and if there is a link you will be taken to the inked grid. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, I am a new user of this fantastic project and I have some limitations. |
Beta Was this translation helpful? Give feedback.
-
Hi @AlphaJet64 and thanks for your comment!
For this we already have this similar issue: #75
We already have this issue: #1 |
Beta Was this translation helpful? Give feedback.
-
@klues .Thank you for your reply, I had not seen the different conversations. |
Beta Was this translation helpful? Give feedback.
-
Regarding looping in WebRadio: Regarding the date/time info element, I've added a comment here: #75 If you have additional ideas or comments, please either add new disscussion topics or new issues - because here we are in a Thread about "Search functionality". |
Beta Was this translation helpful? Give feedback.
-
Please test first version of the search functionality at https://grid.asterics.eu/latest/ Now there's a search button at the top right in normal grid view: (just saw that the button label still needs to be translated) The search modal looks like this: Please tell me your feedback. Any features missing? Should search also be available within the edit view? |
Beta Was this translation helpful? Give feedback.
-
Bravo,
It works really well. I like that it starts looking given only 2
characters, and that you can see both the path, as well as being able to
link directly to the element.
Thanks so much for this,
Jim Luther
…On Tue, Nov 28, 2023 at 10:45 AM Benjamin Klaus ***@***.***> wrote:
Please test first version of the search functionality at
https://grid.asterics.eu/latest/
Now there's a search button at the top right in normal grid view:
grafik.png (view on web)
<https://github.com/asterics/AsTeRICS-Grid/assets/2537025/ba149f70-e8af-4948-8c13-48906d9bae0b>
(just saw that the button label still needs to be translated)
The search modal looks like this:
grafik.png (view on web)
<https://github.com/asterics/AsTeRICS-Grid/assets/2537025/0e51d120-6fdb-4e8d-8c40-43b971930da0>
Please tell me your feedback. Any features missing? Should search also be
available within the edit view?
—
Reply to this email directly, view it on GitHub
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF4D6ZQFU5TA4OUIZZK5QCLYGYBI5AVCNFSM6AAAAAAU3IAFROVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMOJTHA4TC>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Great that you like it. |
Beta Was this translation helpful? Give feedback.
-
The keyboard shortcut would be a great idea. I would use it when I
construct/modify grid sets.
jl
…On Wed, Nov 29, 2023 at 9:42 AM Benjamin Klaus ***@***.***> wrote:
Great that you like it.
I think about making it globally available with keyboard shortcut Ctrl + F,
so that it's also shown in "Manage grids" or in edit view when pressing Ctrl
+ F. What do you think?! Or is it enough to be only accessible in the
main view?
—
Reply to this email directly, view it on GitHub
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF4D6ZVZDI3VVHECW4TQRW3YG5CU3AVCNFSM6AAAAAAU3IAFROVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TOMBVGY4DQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
all further info/discussions here: #77 |
Beta Was this translation helpful? Give feedback.
-
Quote by @tiekoide:
Yes, it's a good idea, but I'm not sure how it's best to implement.
Do you think users should be able to search for words on their own, or is it something only professionals will use? I've just looked at a commercial AAC app and there they only have a search bar at the top, which I think cannot easily be used by the user, unless he/she is able to type on a normal hardware keyboard. So I see two general concepts:
I think in a first step it would be easier to implement concept (1). But I would be interested about your opinion and thoughts how this search functionality ideally should work and look like.
Beta Was this translation helpful? Give feedback.
All reactions