Closed GoogleCodeExporter closed 9 years ago
Hi Eva, thank you for your suggestions. I agree that the persistent search bar
may be very handy - I think that JED has this persistent search bar and JED is
indeed very successful. The problem is that the search bar is only one of four
possible means of finding stuff. Let's assume that the search bar will only
allow searching for text entered, and the SKIP/drawing/Parts search will be
accessible via menu. What if you would like to change some search parameters,
e.g. starts-with, ends-with, find in example sentences - this would
re-duplicate all of the controls in all of the activities. Also, this would
diminish the importance of the search activity as the search functionality is
duplicated everywhere, and I think that the navigability throughout Aedict may
suffer.
So, I think that perhaps the current status is perhaps better. Instead of going
back, you can configure Aedict to prefill Omnisearch box with Last search
string (via Settings / GUI Tuning / Pre-fill Omnisearch), and then just click
the upper-left navigation menu and click first item "Word Search" to quickly
navigate into the search activity, which is now pre-filled with your last
search.
Please let me know if this solution is acceptable for you.
Original comment by martin.v...@gmail.com
on 11 Aug 2014 at 2:29
Perhaps you are right and the word search is somewhat special. Perhaps I will
include a search bar after all, at least to some activities (most notably the
Entry Detail activity).
Original comment by martin.v...@gmail.com
on 4 Sep 2014 at 12:05
Added the search bar to ResultActivity and EntryActivity, let's see how this
idea will work. If this proves useful, I can add this search bar to other
activities as well, based on user requests.
Original comment by martin.v...@gmail.com
on 4 Sep 2014 at 7:22
Oh wow, thank you very much! Looking forward to using it!
Am 05.09.2014 04:22 schrieb <aedict@googlecode.com>:
this idea will work. If this proves useful, I can add this search bar to
other activities as well, based on user requests.
Original comment by 43pup...@gmail.com
on 4 Sep 2014 at 11:47
Original issue reported on code.google.com by
43pup...@gmail.com
on 18 Jul 2014 at 4:01