Projects tagged ‘web’ and ‘wicket’

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]

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.

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

Based on Wicket and JCR, it is the ONLY Wicket-based CMS framework available today. BRIX was built on the idea of "Power versus Complexity", providing for ease of use while at the same time allowing ... [More] designers the highest degree of freedom in developing a rich user experience. [Less]

VC Aperture provides you with a thorough view of your version control repository. It lets you look both wide and deep into your source code.

Apache Wicket integration for Soundmanager Javascript Sound API

gidooCMS is a kind of framework for CMS systems based on Apache Wicket. You have the basic features of an CMS, but you add you own functionality by extending Java-classes. E.g. you will write the code ... [More] for creating a menu by yourself directly in Java. Currently we use Apache Jackrabbit as persistance engine. Some of the important features: * rights management using sections (like Servlet contexts) * version history * backup (import and export) * XML validation of new pages * simple preview functionality * extend the GUI of the CMS * a lot of small things that make life easier ;-) [Less]

this is a project hosted in google app engine

Réalisation d'une interface web avec wicket dans le but de mettre en valeur cette outil.

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]