Web Apps: Closeable Announcements/Info/Tooltip boxes - java

I want to understand how to implement an announcement/info box system that displays
a box for the user with information.
The user can do nothing or close the box, but then it will never be seen again.
E.g. Facebook home page. Box asking for Translators.
if you leave it then its always there.
But if you close it, it never appears again.
Does this mean that a Boolean value needs to be used and checked
for announcement/info boxes?
I'm looking for a pseudo way with database tables to do this?

This info goes into a portal page personalization attributes table for that user.
Each portlet will have Display set to True or False for each user.

Related

Create a hyperlink that will expire after one click

I am creating an hyperlink that will be send to user mail(gmail in my case). I want to expire the link after user once clicked in it(I don't want the user to click more than once).Once user clicked on the link it will trigger subsequent mail to manager. Here I also want similar functionality.
Note: link has some encrypted data too.It should remain intact.
I solved the issue.Instead of relying on session.I am using last update value in DB to check the life of hyperlink.

How to stop the user to enter the data in outside the fields in the J2ME application?

I have J2ME application, contains lot of forms and lists.
I have the following problem in that application.
Whenever I enter the details of the form and press down button, the cursor is coming to the space available in between the fields and footer of the form, After that if I press the middle button it is allowing the user to type data.
please help me,how to stop the user to enter data in outside of the fields ?
U might have added some field inside it. j2me doesnt allows editing on the form . please provide the code so that we can help u

How textbox identifies type of data and autocompletes it

I was wondering that the textbox itself identifies its type and when clicked inside textbox it gives the suggestion for that. For a instance i am creating a textbox for mobile no and when click inside the textbox it correctly detects it. Can anyone explain me how it was coded. It was browser feature or HTML feature?
Here is the Image explanation
This features of modern browsers is called auto-fill option, where the browser recognizes that you have performed a specific search before and suggests information that you have typed before. For sweepers, auto-fill saves a ton of time. When Roboform doesn't fill out a form for me, I usually only have to double-click in the text field and select the data I want from the drop-down list of options. This is particularly useful for daily sweepstakes that require codes.

Check there is one checked checkbox before display confirm dialog Wicket

I intended to give user a chance to confirm their action by adding JavascriptEventConfirmation as the example from this tutorial :
https://cwiki.apache.org/WICKET/getting-user-confirmation.html
However, I want to be able to check first if there is at least one checkbox (out of mulitple) is being checked before displaying the confirmation dialog.
How can I achieve this?
Note that the confirmation is implemented via a simple javascript snippet that is added to the button tag's onclick attribute.
To add the verification, just change the generated snippet to fit your needs.

Best way to implement refusing a value change by the user in Swing?

I have a JCheckBox that should not be checked by the user when a certain other field is empty.
So now I want to have an error popup and then reset the checkbox (I've considered disabling the checkbox, but the connection to the other field is non-obvious, and a tooltip text IMO not visible enough).
What's the correct way to do that in Swing? Through a PropertyVetoException? Where do I throw it and where do I catch it? My first (probably ugly) idea would be to add a ChangeListener that itself shows the popup and resets the value.
Edit: The question is about Nikki (screenshot below), an app I am developing which geotags images and exports them to Google Earth's KMZ format. The checkbox is used to select the images to include in the export. But this requires the images to be gotagged first (which in turn requires either a timestamp, or manual assignment). I don't think this requirement can be made obvious through the UI layout.
(source: brazzy.de)
I would simply disable the check box and add a message explaining why the option is not available. A nice way to show the message is to display a mini exclamation mark next to the check box and put the message in a tooltip.
Poping up an exception often feels wrong because users don't read error messages. For most users an error message popup means that the application did something wrong, in your case it's the normal behavior.
Edit if you insist on letting the check box enabled, another way to show the user that some info is missing would be to flash the missing data. Eg. if latitude and longitude are missing and the user clicks on export, set a red background onto these fields for a just a second. This will clearly show the user what's missing.
In this screen, don't you want to put the mouse over the red circle to understand what's going on?
validation http://www.vogella.de/articles/EclipseDataBinding/images/validation10.gif
I don't think the Export JCheckBox should be disabled at all. Instead, the Export JButton itself should examine the current export list and display any anomalous entries in a way that allows navigation to a chosen photograph. If all entries are correct, Export would proceed as usual.
Addendum: It think you are right to keep the interface as non-modal as possible. My model for this would be unsaved files when exiting an editor or uncommitted changes when closing a project in an IDE.
If that's a status line at the bottom of the window, you might indicate the number of photographs currently selected for export, adding a count if any still need geocoding.
The field should simply be allowed to disable the checkbox. If the coupling is unintuitive then the GUI layout may have to be reconsidered.
EDIT: I ran it from your page, and I believe the issue here is that you actually have a third and fourth step in addition to select folder, select images. The third step is validate image, and fourth is select images for export. I think your problem is that this is not clearly conveyed in the current layout, and that reflects in your question.
I would suggest that you create a separate column containing the checkbox for each image, and that THAT checkbox is disabled until the image passes validation (step 3). Perhaps with an explanatory text in the column about why the image hasn't passed yet.

Categories