Projects tagged ‘component’ and ‘wicket’


Jump to tag:

Projects tagged ‘component’ and ‘wicket’

Filtered by Project Tags component wicket

Refine results Project Tags java (6) web (6) apache (5) framework (4) development (3) mvc (3) contrib (2) xhtml (2) j2ee (2) components (2) ajax (2) html (2)

[8 total ]

85 Users
   

With proper mark-up/logic separation, a POJO data model, and a refreshing lack of XML, Apache Wicket makes developing web-apps simple and enjoyable again. Swap the boilerplate, complex debugging and ... [More] brittle code for powerful, reusable components written with plain Java and HTML. [Less]
Created over 3 years ago.

37 Users
   

Tapestry is an open-source framework for creating dynamic, robust, highly scalable web applications in Java. Tapestry complements and builds upon the standard Java Servlet API, and so it works in any servlet container or application server.
Created over 3 years ago.

31 Users
   

Umbrella project for integrations of Wicket and other projects such as Jasper Reports, Hibernate, Freemarker. Also a home for small community contributions.
Created over 3 years ago.

0 Users

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]
Created 4 months ago.

0 Users

Wicket SkunkworksExperimental Wicket Extensions The Official Domain of this project is: http://wicketskunkworks.org Wikipedia has the following to say about a Skunkworks Project: A ... [More] '''skunkworks project''' is one typically developed by a small and loosely structured group of people who research and develop a project primarily for the sake of innovation. The term typically refers to technology projects, and originated with Skunk Works, an official alias for the Lockheed Martin Advanced Development Programs (formerly Lockheed Advanced Development Projects). A skunkworks project often operates with a high degree of autonomy and unhampered by bureaucracy, tasked with working on advanced or secret projects. These projects are often undertaken in secret with the understanding that if the development is successful then the product will be designed later according to the usual process. Quick DocumentationAdding Wicket Skunkworks to your Maven build [Less]
Created 8 months ago.

0 Users

Code from the regular London Wicket User Group meet-ups. Apache Wicket is an open source Java web component framework. The London Wicket User Group meets up approximately every two months for a set ... [More] of informal talks and general chatter. Details and sign-up for the next event.There's often code behind the talks, and this site hosts that code in a Subversion repository. Here you'll find various components, snippets and applications. We try to keep this code up-to-date with the latest library and Wicket versions. For slides and the original code (downloadable as ZIPs), please see the download page. We'll move the code into subversion soon. Components available: Generic bean editor component. Generic drag-and-drop AJAX list editor component. Dynamic AJAX image cropping component. Gallery application (uses the list editor and image cropper). Some of the projects depend on others (most depend on the "common" project), so you will need to build and install SNAPSHOTs of these dependencies into your local Maven 2 repository for these to be found. If you are having difficulty, ask on the Google Group for this project. [Less]
Created about 1 year ago.

0 Users

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]
Created 4 months ago.

0 Users

WARNING: This is PRE-ALPHA code, use at your own risk !!
Created 2 months ago.