I have an application in which i am trying to create autocompletion of jTextField and jTable from database values as we do in address bar of browsers. I tried many ways,but i couldnt complete it. Do any one know how to do this in a simple way, the links and notes which i had got was quite confusing for me. I am using java and MySQl in netbeans.Hoping a reply soon..
Thank you
You can give JIDE JIDE Common Layer at http://www.jidesoft.com/products/oss.htm a try. It is free and open source. There are two features you might be interested in. Both are in JIDE Common Layer. One is AutoCompletion feature which can auto-complete based on a known list while you are typing (no drop down). The other is IntelliHint feature which will show a list of matching choices in a drop down while you are typing. Since you mention something like address bar of a browser, I would recommend IntelliHint. Hope it helps.
Related
In the SCRUM planning screen there is a "Details View" on the left.
How do I configure this to show only the things I am interested in, and hide those I am not. Also there are things I am occasionally interested in that I would like to shuffle to the bottom (like attachments).
Is there a bluffers guide to Jira configuration? The atlassian help pages are... not helping me...
Edit:
Sorry I was not clear enough.
I want to hide things like Fix Versions and Dates and re-order things like People to be lower on the list of things. Not alter what tickets I see.
In order to see what you are interested in, you can create quick filters in the following manner:
Click on Board -> Configure.
Go to "Quick Filters"
Configure and add a new filter
What ways are used to show a user help the first time they use a page - to showcase certain features they might not realize are there.
For instance, say a search form is introduced that has a hidden "advanced search" option:
I would think most people would see the chevron and click it, but..you never know. I know that I could add a cookie to say "Hey - this user has seen it" or create a table in the database.
The problem I see with adding a cookie, is if the user deletes cookies and logs back in - they will have to always dismiss the alert/error/whatever. Unless after a period of time, I go in and manually delete it (which then new users wouldn't see the alert.)
Alternatively, adding a table to the database seems too much for such a simple task. It's what I'm leaning towards, but I hate it...there has to be a better way.
Are there any other ways to show a one time alert for certain pages?
Edit - I used a pretty trivial example on purpose.
I guess both your options are right. The cookie option is bit better cause it will be lighter on the server, again in case you have many users then the database options will be not great.
You may also lookup the new HTML5 feature of storing data on client side. Its a better local storage method.
It goes like localStorage.uid="1234" or something like clickcount.. Refer the html5 docs its a great feature as well.
Heres the link..
http://www.w3schools.com/html/html5_webstorage.asp
have fun..
I'm trying to extend the behaviour of ttk::combobox to make it behave like the Google search box in my browser - i.e. I'd like it to drop down automatically and limit the entries in the listbox to those which match the string that I've typed in so far. Ultimately, I'd like to select the part of the string that's been autocompleted so that the next character the user types will cause it to be deleted and re-start the matching process.
I found the page on the Tcler's wiki, but that appears to select the entry with the letter just typed, which isn't what I want. (Consider a user selecting from a list of US States. When they type A, I want the selection to be limited to Alabama, Alaska, Arizona and Arkansas; when they then type an L, the list should be limited to Alabama and Alaska. The code on the wiki would select Alabama when the user types A, then Louisiana when they type L.)
I tried defining a few bindings on the ttk::combobox, but gave that up - to be honest, I can't remember why - and have tried to extend the behaviour of a ttk::entry to cover it.
After borrowing liberally from ttk/combobox.tcl I've managed to post a listbox and to limit the entries in the listbox, but am having big problems now that I've added bindings to make the up and down arrows alter the selection. To be precise, the selected item is moved happily, but some of the time when the entry widget loses focus, the whole application hangs up and my tclsh soaks up all the CPU.
I'm developing using ActiveTcl 8.6 on both Windows and Linux and the code seems to behave the same on both platforms, although I haven't tried on Linux since I first saw it not hanging in Windows. I'd be very happy to share my code, but since the demo script runs to about 450 lines, I wouldn't read it myself if someone else posted that much.
Can anyone help by asking the right question to set off a lightbulb for me? The problem feels like a timing problem, but I've no idea where to start trying to track it down.
Many thanks.
Edit I've been racking my brain, and I think the reason I abandonned the attempt to extend ttk::combobx was because there were already a large number of bindings in place, and some did things that I didn't want. The current effort uses a validatecommand on the entry widget and Key-Up, Key-Down, FocusIn and FocusOut bindings.
Current code is on pastebin here.
Well, that was embarrassing!
I took another look at the code on the wiki and discovered that it did the thing I most wanted. It doesn't post the listbox, but it does autocomplete, and if you attempt to navigate the (unposted) listbox, by pressing Key-Up or Key-Down, it starts off with the appropriate item highlighted.
That's quite enough for what I need; if I decide I really must have the listbox posted, I can see about that at the time. (Given my bad experience trying to roll my own, however, I suspect that I'll just live with this.)
Many thanks for the forebearance and suggestions.
I'm implementing a help system for a desktop app (Win32) and am looking for how to go about designing it.
What kind of structure should a help system have, what's actually helpful for the user?
e.g. Should the help system be a big list of FAQ's (office 2010 help seems to be like this)? or should it be a Feature list documenting and describing what everything does (This is probably only helpful if the user is not sure how a feature they already know about works)
What kind of knowledge should I expect the end-user to have? It's probably slightly demeaning to write into the help file that File -> Open Project Closes the current project (if present) and Opens an existing project.
What I'm looking for here is some guidence, a set of features any good help system should have and a method of organising the topics in a way that users can find them.
"Open project" can also be a good place to put a reference to the definition of a project, and other more general descriptions and procedures relating to opening of projects.
In general CHM help is accessed either via context sensitive help (which is the typical for the file->open case) and via the general table of contents, fulltext search and indexes. Most recent apps seem to only create one help page per container (a dialogue, or pullodwn menu), where they list all the items on that screen (e.g. by annotated screenshot) and not a lemma for each item (checkbox, menu entry) in the GUI. Less clutter and navigation, and many points only need a fairly short description
Besides context sensitive help, one can also browse the help via the help system.
A CHM is pretty much a bit like an e-book, with a table of contents (TOC), index and optionally support for fulltext search.
The index and fulltext search are ways for the user to search for content.
The main difference is that the index is more under your control, and the fulltext search is largely automatic when enabled.
The TOC is a treeview of nodes that act like the TOC in a book, and should fixate the general structure of the "ebook". FAQs are typically an appendix in this TOC.
Besides this, there is a default "entry" page, which is like the homepage of a website. It should navigate users to the most commonly searched topics.
Be careful by comparing to Microsoft products. They sometimes use systems that are not available for end-users/developers yet.
Good help uses all these elements.
There are broadly two styles of help: reference-based (i.e. what does this checkbox mean?) and task-based (how do I achieve XYZ?).
You're probably best off creating a task-based tutorial first, backed up by a FAQ if necessary.
Terminology: What do you call this type of web gui feature?
I'm trying to research on a gui interaction where the user chooses an option, and the next set of options are loaded based on the previous.
I'm calling it cascading, but that doesn't seem to be right.
Example below:
User chooses company A
company A services load
user chooses service 1
serivce 1 loads, with only options company A wants
...cycle continues...
Silly question probably, but I am tired of getting all these search results that have nothing to do with what I'm after. Thanks in advance for any guidance.
If it matters, I'm thinking of using jquery for this, with C#/asp.net backend. Chose not to include those in the topic tags as I didn't think the language would change the terminology.
I think you're right with cascading if I understand you properly, ASP.Net/AJAX example here:
http://www.asp.net/ajax/ajaxcontroltoolkit/Samples/CascadingDropDown/CascadingDropDown.aspx