Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The "gsoc2011-RightClickMenu" page has been changed by Dragan Sahpaski. http://wiki.apache.org/tapestry/gsoc2011-RightClickMenu -------------------------------------------------- New page: Proposal Title: '''Right Click Menu component for Apache Tapestry5 java web application framework''' Student Name: Dragan Shahpaski Student E-mail: [email protected] Organization/Project: The Apache Software Foundation / Tapestry 5 Assigned Mentor: '''Proposal Abstract:''' This project will produce a generic and powerfull Right Click Menu (also known as Context Menu) component for Tapestry5. The Right Click Menu component is meant to be highly configurable, can be used along tapestry5 existing components or as standalone component. The component is meant to be integrated within the tapestry5 framework or as a standalone library. '''Detailed Description:''' The first goal (or deliverable) will be providing the Right Click Menu component as a mixin for t5 components. The menu options will contain pairs of labels and t5 links which are ordinary links or event links (able to update a zone for example), that will be configured with some kind of Right Click Menu model interface. The clicks will be processed as t5 events produced for example from an event link. Also it is intended that advanced usage scenarios for enterprise applications are considered like for example having all the options for all the menus in one application in a database and producing them in some generic manner. The second goal is to provide integration with the all mighty t5 grid component, so that we can have right click options in the grid cells and rows with possibly different options for each cell/row. This means that in a grid with 20 cells, 20 javascript instances of the client side component may exist. To avoid bloating the page with many instances of the component possibly not used at all, look at the third goal. The third goal is to provide ajax behavior for the menu's options (label/link pairs) i.e. clicking the component will produce a waiting.. or similar menu that is refreshed with the actual menu contents with ajax update from the server. This can help cases of components with too many menus, like for example loops or grids (see the second goal). The fourth goal is to provide the component as a standalone t5 component if needed (optional and may be discussed with the community). The fifth goal is to examine the possible usage scenarios of the component and make the usage of the component as trivial as possible. '''Additional Information:''' I intend to provide detailed documentation about the component (or mixin), demo examples of most common usage scenarios and maybe one video tutorial. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
