Hello,
There is a GWT component named *PagingScrollTable* which is able to
render a table with paging and scrolling features.
The constructor of the class associated with it has the following
signature: *PagingScrollTable(TableModel<RowType>,
TableDefinition<RowType>) *.
To create TableModel, we invoke a REST web service which returns data in
JSON format and then we instance a *IterableTableModel* object whose
constructor has only one parameter, an array list resulted by parsing
the JSON data.
To create TableDefinition, for every column we need a new ColumnModel.
Every row from table is mapped to an object of *User* type. This class
have to be created and his structure is almost the same as the one from
Tapestry.
A priori, we need to know which information will be shown in the table.
For example, *AddressBookEntry* class has a lot of fields. Is it worth
to show all? I'm thinking that every row from table to have a collapse
button and by pushing it we can get more information about a user. Don't
forget that a table with many columns is very ugly.
I attached a patch at the following link:
http://track.sipfoundry.org/secure/attachment/20693/0001-XX-5943-enhance-phonebook-page-in-user-portal.patch
Thanks,
Ernest
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
