Have two questions.
Make the search filter form non modal.
Allow searching by pressing enter key instead of having to press the Find button.
thanks.
sachin,
Your question seems to be more of a statement, but if you're looking for various options for jqgrid, take a look at:
http://www.trirand.com/jqgrid/jqgrid.html#
New in Version 3.5 > Integrated Search Toolbar
This allows you to interactively search and it respects the Enter key.
However, you lose operators... but I suppose you could modify the code that's given to add something similar back in (or bundle your operator in with the text....ie, user enters "> 400" rather than "400", but this poses security risks)
Related
I want a search bar that will search each time the user enters or deletes a character. The research is done in two columns with an 'OR'.
(EDITED)
I've been able to make my search bar with ajax comunication. But once the user has the search results, the use of the paginator cause an Method Not Allowed on this line of my search function of the controller :
$this->request->allowMethod('ajax');
Although you didn't provide much description in the question, as per the description what you need is the autocomplete functionality.
https://jqueryui.com/autocomplete/ This is the JQ based autocomplete plugin, helped me in a number of project for searching DB when a user enters something in the search box
I have a question about Ultimate Special Offers plugin. Has anybody used it?
The problem is that this plugin sets the table with discounts in a special place where it wants. In my case, it shows up under the "add to cart" button. But I want it to appear above the button. How can I regulate the place where the table shows up?
You have two choices. One is to dig into your theme and move the table yourself. If you right-click the element displaying the table while having your browser console open, you will spot where it is in the HTML that makes up your page. Now click the Add to cart button, and see where it is. Memorize the name of the button, and now look for that in your product.liquid page. Chances are, the plugin itself has some liquid, so you can cut it out of the page, and move it the before the add to cart button in the liquid.
If all that seems like a mountain to climb, just ask the makers of the plugin to do it for you. It is a simple task for them, and should take them a minute to do. If they choose to ignore you, I would call them out as unreliable, and try a different plugin, from a company that will help you with your simple task.
I want to send queries to Wolfram Alpha real fast. I've been using wiki query from search bar for ages, how can I search on WA?
Ultimately I found the solution myself, but it took me some time and I had to devise the solution myself, since all Google searches returned the extension which I wanted to avoid. Here it is.
Right click the address bar and click Edit search engines...
(or open Settings -> Search -> Manage search engines...)
Usually, you can find all recognized search engines you used already listed there, but if not, add this: (*use any keyword of your choice)
The query url: http://www.wolframalpha.com/input/?i=%s
Now it is possible to use wa query from search bar to search on Wolfram Alpha. Note, this method allows you to use any search engine.
This is really handy! I wonder if adding it in Chrome as a search engine is better than using the Wolfram Alpha chrome extension though. That is much easier to search using just combination of "=" followed by space and you can directly type in your search query to the Math engine :)
Wolfram|Alpha (Official)
Instantly query Wolfram|Alpha from any page or tab.
There is more to it, you can type formula and equations directly in your navigation bar using this on any page or tab. Pretty neat!
[Source]: From Wolfram Alpha Official Chrome Extension page
===FEATURES===
✓ Wolfram|Alpha Button – Access the Wolfram|Alpha query box with just one click. You can also right-click the Wolfram|Alpha icon to change extension options.
✓ Omnibox Shortcut – Transform Chrome's omnibox into a Wolfram|Alpha query field by typing an = sign followed by a space.
✓ Context Menu Shortcut – Highlight text to create queries through a context menu (right-click) entry.
Shouting out to StackOverflow community:
I am still learning and appreciating the power of this engine. If you guys have some resources or content apart from Wolfram's official site, please do share!
This will really help me as a beginner in the field and I can use to improve.
What better way to search than the famous Euler's Identity. In Chrome Nav bar
"=" ==> (space) ==> e^(i*pie) ==> (enter)
Or something like:
"=" ==> (space) ==> sqrt(1779)*cube(pi) ==> (enter)
And see the result instantly in Wolfram. Awesome isn't it?
In an existing code base, the call to parse dates depends on the machine's culture. I created a custom resharper search/replace pattern that can spot and fix these calls.
Is there a way quickly find and fix all the hits of this search replace pattern? I'm now doing them one by one and it's going to take forever ...
Isn't the 'Global Fix' at the end of that very blog post you link to exactly what you want?
Global Fix What we’ve just done is a manual local fix,
that is, locate the offending entry and hit Alt+Enter to apply a
QuickFix. We can do this at a global scope by using the
Pattern Catalog tool window.
1. Undo the prefix fix (so as to have several instances) 2.
Open up the Patterns Catalog 3. Select the
recently created Pattern and click on Search now.
This time, instead of the Find Results dialog, we get a Replace dialog
which displays all matching patterns and a Replace
button
4. We can select
the entries we want replacing (by default all checked). Click
Replace We’re done! ReSharper will now
replace all occurrences. So we’ve applied a QuickFix
globally.
I was wondering if it was ever ok not to have a submit button (Ok, Go or Search for example) near a search box in Web pages.
I know that hitting enter is much faster and that it will perform the search.
However, is it an accepted convention for the average non tech savvy user or only for the tech community?
For example, the search box here at stackoverflow doesn't have a submit button, but I don't think anyone is complaining (and I sure don't).
On the other hand, someone suggested using Google as an example: would people notice if the buttons were removed?
I just started reading Don't Make Me Think by Steve Krug and he mentions that every search box should have something that tells me I can click on it to launch the search.
Your thoughts?
Why you should have a button:
Not everyone knows they can hit
enter, so you are leaving some less
savvy people out in the cold.
Some devices like phones and consoles may not have a way to submit without a button. The PC based browser is still dominant but don't assume it is the only way people access your site.
You may not have a button if (both conditions must be satisfied):
Your audience is tech savvy (as on SO)
You provide a visual cue that the search box actually is a search box
By adding text inside it mentioning it should be used to search
By adding an icon inside the box
Generally I would think that hitting enter is a shortcut to submit rather than the primary means.
I think it depends on your target market. If you are StackOverflow it's not too hard too think they know how to use a browser (using a back button on a browser to navigate is a similair design convention) and pressing Enter = submit for search.
However if your target market is say mechanics (no offence to mechanics) that don't use a browser/computer often then look at how Google does it (and they target the broadest scope) - they have a button to submit.
There is a middle ground you could look at, which is have a water mark like StackOverflow which tells users "Click here, type in search values and press enter to search" - or something like that (hopefully shorter) where you actually catering for users of all levels.
Whether or not a button is required depends on the audience. Here are issues to consider:
Technically oriented users may not need a button and will usually not have to think about hitting enter to submit a search request.
Conversely non-technical people may not even know it is possible to hit enter to submit a search request. So no amount of thinking might work for them.
There may be technology limitations that require a button. If you expect your audience to be browsing your form from a platform that does not provide an implicit way to submit a search request then you may need to provide an explicit button.
So essentially you need to know your audiences and determine where the edge cases lie and how critical they are. Using SO as an example, it is directed at technical users so an explicit button probably isn't required. However for a site like google where you need to be accessible to every single user using every possible platform, a clear explicit search button is a must.
"Don't Make Me Think" - so gimme a button.
There will always be someone using the application for the first time; don't make them think either. And your screen shouldn't be so fussy that it is impossible to fit the button in comfortably - that would indicate a different set of problems.
I think for a non-tech person some sort of submit button is needed. Think about people who don't use computers very much. They often click all of the buttons needed instead of hitting enter because they don't realize enter does the same thing. My opinion...if it isn't for tech guys only then it should be as simple as possible.
It depends on your audience. Steve's audience is everybody. Majority of which are so far from IT you'd need a telescope to see them. If your auditory is a single user, you might skip all clues: button (with or w/o names), in-box label.
For my own login window I leave two fields: no labels, no buttons, no javascript to tell you which one is which. But that's not a public project.
A while ago there was an article on Smashing Magazine about this.
There were some alternatives like a looking glass or another icon, but basically there is always a button, or something which represents it.
Having a button makes it clearer that the text field is a search field. Merely having the text field itself indicate this in its contents is unsufficient.