[
https://issues.apache.org/jira/browse/TOMAHAWK-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ji Kim updated TOMAHAWK-829:
----------------------------
Status: Open (was: Patch Available)
> Batch of Java codes and JavaScript files for creating Dynamic Tables [such as
> changing between different List, and etceteras]
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-829
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-829
> Project: MyFaces Tomahawk
> Issue Type: New Feature
> Components: New Component
> Environment: In my development I have used mainly JDK 1.4 version.
> Also I have used the following dtd for facesconfig.xml =>
> http://java.sun.com/dtd/web-facesconfig_1_0.dtd.
> Testing has been done on IE 6.0.2800.1106.xpsp1.020828-1920, Firefox 2.0.0.1,
> Opera 8.5, and just for sanity Netscape 8.0.4
> Reporter: Ji Kim
> Attachments: dynamicTable.jpg, FilesToExtractFromRoot.zip,
> noDirectoryPatch.patch
>
>
> In order to run the example :
> Extract FilesToExtractFromRoot.zip at "myfaces checkout" and apply the patch.
> Some of the capable features of the above components that I am
> attempting to integrate are :
> dynamic table
> (1) moving up and down the position within the table via key +
> mouse
> (2) dynamic sorting
> (3) cut, paste, delete, and undelete
> (4) search
> (5) changing the current viewing list with an another
> (6) changing the size of the table [namely # of rows]
> (7) paging capability that is dynamically modified
> (8) and others that I forgot to mention if they exist
> Some of the possible values for the TDs of the dynamic table :
> text, textarea, image, select, span, and etceteras
> In future modifications, I will make sure to improve in sorting by moving
> from merge to quick and improve in other places where I can find efficiency
> in. After one advice from one additional smart person, one thing I will make
> sure to integrate in my free time is to allow refreshing of the data when the
> data binded to is extremely large.
> Meaning after I have made the changes to sorting and the like I will run
> tests to see how much information should be maintained on the client side and
> when a page beyond the maintained data is accessed, the table will refresh to
> retrieve the next set of data with the start page being the previously
> clicked page.
> Thank You!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
