The contextValue can be used to uniquely identify a row. Just use a oncontextmenu on the row which is generated by ice:panelGroup when used along with the attributes contextValue and menuPopup. This is of course not a very intuitive way of working, so I was wondering if there's a way to tie the row selection to the right mouse button, or perhaps to tie the context menu to the left mouse button - either works, so long as the user just has to click once. This means users need to first left-click the table entry they want to edit, then right-click to see the menu. As the user enters text into the component it provides a pop-up list of possible matching values that the user may select from.
#Icefaces rowselector manual#
This component provides an input text component enhanced with auto-complete functionality. The new IceFaces 1.6 aims to allow for manual row selection on tables (from the release notes: 'ice:rowSelector can be configured for manual row selection mode'). The auto-complete component is actually the ice:selectInputText component.
#Icefaces rowselector how to#
We've implemented this context menu using the contextMenu component ( ) and it works fine, with one issue: right-clicking does not trigger the rowSelectionListener. How to Use the ICEfaces Auto-Complete Component. We would like to replace the two buttons with a single context menu, where the user can right-click a row and select their desired option. When either one is clicked, it triggers two listeners: a RowSelectionListener which updates the model with the ID of the selected row, and a second listener depending on the button that uses this ID to retrieve the selected form, creates a copy, and redirects the user to the relevant edit page. In the current system, the final column of each row has two buttons, one for each variant of duplicate. Technically, the close() method is available for any window, but window.close() is ignored by most browsers if window is not created with window.open(). To check if a window is closed: win.closed. To select a form, the user has a search page that returns a sortable table of search results. So the connection between the windows is bidirectional: the main window and the popup have a reference to each other. There are two variations in these duplicates: one an identical copy, one with some information redacted. Im having some problems with Icefaces 1.82 (we cannot use any later version than this.) and a datatable with a rowselector. Part of this application allows the user to select a form, create a duplicate, and then edit and save this duplicate under a different name.
I am working with an application built on IceFaces. We are planning an enhanced POC application for release 1.2 to demonstrate the capabilities of a J4Fry enhanced standard JSF application to convince you that the use of mass-component frameworks like Trinidad, Tobago or IceFaces will not become the main stream for JSF development.
0 kommentar(er)
