[server-table] (https://github.com/asarosi/serverTable)

Server Table is a table module for angular js. The main aspect of this component is to implement every method (pagination, sorting, filtering, etc.) on the server side, and display the modified data on the client side.

#Install This component has the following dependencies:

• [AngularJS] (https://github.com/angular/angular.js)
• jQuery (bower install jquery)
• [angular-translate] (https://github.com/angular-translate/angular-translate) to make it multilingual
• [ngstorage] (https://github.com/gsklee/ngStorage) if you want filter caching
• [bootstrap] (https://github.com/twbs/bootstrap) for styling

#Bower
bower install server-table

#Usage ![image about the table] (http://i.imgur.com/GWqC09U.png) Include into the HTML

<script src="bower_components/server-table/dist/table.min.js"></script>

Include the model into Angular module

angular.module('app', ['serverTable'])
...

[Example] (https://github.com/asarosi/serverTable/tree/master/example)

#Components sTable should be the wrapper element for every other table component

<div s-table count-url="/count" list-url="/list" s-cache">

sItemsByPage

<div s-items-by-page></div>

sYearFilter

<div s-year-filter start="2000" end="2020"></div>

sMonthFilter

<div s-month-filter></div>

sSearch

<div s-search></div>

sPagination

<td items-by-page="7" s-pagination></td>

sSort should be placed on each table header

<td s-sort="_id"><b>{{'ID' | translate}}</b></td>

sCache should be place on the same element as sTable directive

#Configuration Provider

angular.module('app')
  .config(function(sTableProvider) {
    countUrl: 'item count url',
    listUrl: 'data url',
    sortAscIcon: 'css class name for asc sort icon',
    sortDescIcon: 'css class name for desc sort icon',
    sortNoneIcon: 'css class name for icon when there is no sort',
    paginatorTemplateUrl: 'html template path for paginator',
    itemsByPageTemplateUrl: 'html template path for item by page selector',
    yearFilterTemplateUrl: 'html template path for year filter',
    monthFilterTemplateUrl: 'html template path for month filter',
    searchFieldTemplateUrl: 'html template path for search field'
  }

Component options

Component	Attribute name	Description	Required	Default
sTable	countUrl	item count url for every single table	No	/count
sTable	listUrl	data url for every single table	No	/list
sTable	sCache	define filtere caching	No	-
sPagination	itemsByPage	number of items on every page (sItemsByPage will override it)	No	5
sItemsByPage	itemsByPage	number of items on every page	No	5
sYearFilter	startYear	start year	No	actual year
sYearFilter	endYear	end year	No	actual year

Hint sSort directive always has to have a unique value, which will identify the actual row!

#How it works? The client will call the server side once, a condition has changed. It will send every condition to the server as query parameters. The parameters are the following:

Method	Name	Type	Description
getPageCount, getListFromServer	month	String	Month filter value (from 1 to 12)
getPageCount, getListFromServer	year	String	Year filter value
getPageCount, getListFromServer	searchText	String	Text from the search field
getListFromServer	itemsByPage	String	Number of items by page
getListFromServer	currentPage	String	Current page's number
getListFromServer	sort	Object (as JSON)	Sort object, object will have one attribute, which name will be the value from the s-sort diractive, and the attribute's values can be the following [ascending, descending, none]

#What's next? This is only an alpha build for the component, so there are plenty of work to do. I want to make the filters more dynamical, make a scrollable paginator, which will call the server when while the user scrolling down. Now the table can work wit data comming from the server, but I want to make a fully client based solution too.

#License

The MIT License (MIT)

Copyright (c) 2014-2015 Sahat Yalkabov

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.