Projects tagged ‘component’, ‘contrib’, and ‘wicket’

A generic Drag&Drop framework for Wicket: operate on any markup element via selectors drag and drop between any Wicket components vertical, horizontal and hierarchical structured markup (i.e. trees) ... [More] drag initiators (a.k.a. handles) common desktop metaphors with 'MOVE', 'COPY' and 'LINK' operations transfer types themeable works in Firefox, Safari, Chrome, IE and Opera See our live examples on http://wicket-dnd.appspot.com/ (beware - very slow!). Theme your DnDAdd a theme to your pages to be used for DnD, e.g. the WindowsTheme: add(CSSPackageResource.getHeaderContribution(new WindowsTheme()));Drag sourceAdd a DragSource behavior to enable a container for drags: container.add(new DragSource(Operation.MOVE) { public void onAfterDrop(AjaxRequestTarget target, Transfer transfer) { // remove transfer data } }.drag("tr"));In this example only a MOVE operation is allowed. Drags are initiated on tags. Drop targetAdd a DropTarget behavior to enable a container for drops: container.add(new DropTarget(Operation.MOVE, Operation.COPY) { public void onDrop(AjaxRequestTarget target, Transfer transfer, Location location) { // add transfer data } }.dropCenter("tr"));In this example MOVE and COPY operations are allowed. Drops are performed on center of tags, the Location holds a reference to the actual component the transfer was dropped on. [Less]

A clean slate development of tree components for Wicket. See our live examples on http://wicket-tree.appspot.com/ Current solutionWe identified the following basic issues concerned with the ... [More] currently available tree components in wicket and wicket-extensions: integration of TreeModel (which is not Swing's highlight) cumbersome change notification using Swing's TreeModelListener no nested markup for trees supported no markup for tabular trees supported markup limitation for node content (height problem) duplicated code for handling table IColumn and tree IColumn complicated code for partial update rendering Proposed redesignThe wicket-tree components try to address these problems: simple interface ITreeProvider similar to IDataProvider: support for multiple roots (and no root at all) get a node's children model factory for each node that's all fully generified no change notification required, always-up-to-date rendering like other repeaters nested markup for NestedTree markup for TableTree arbitrary markup for node content allowed utilizes DataGridView for TableTree: reuse your column implementations reuse toolbars (almost) use pagination use sorting partial updates supported for NestedTree using standard AJAX features To achieve a lightweight solution some features from the original components were rejected: IRenderable optimizations not supported if really useful should be added to DataGridView TableTree would automatically benefit no caching of tree structure in component structure always see up-to-date data caching is better done in ITreeProvider if really needed no selection handling handling state of nodes besides expanse/collapse is irrelevant to a tree implementation better implemented in client code (see examples) no partial updates for TableTree Wicket's AJAX doesn't support inserting/removing elements, these features should be added to Wicket core instead of adding it to a single (tree) component DataTable doesn't support partial updates either [Less]