Skip to main content

70-562 ListView and Pager

One of the advantages of the listview over the gridview is the templates and integrates well with css.

Lets say you want to display list items in a inline layout in flow mode with left and top margin of 10px, this defined by a css class.
Now lets create this using a listview so we can have data in it, and still apply the style from the previous css class.

To auto format the xml of the aspx, ctrl+a, ctrl+k, ctrl+f.

To add sorting to the listview, add a button with CommandName set to Sort, CommandArgument set to sort expression.

Add paging if there is too much data, the IPageableItemContainer interface is already implemented by the listview. You can go in the smart tag and click the Configure list view link, and check the box for paging.
If you want to put the pager outside the listview, set the property that allows the pager to point to what it's paging(the ListView control), PageControlID is the name of the attribute.
You can have mutliple pagers, get some of them to display some buttons(previous), the other displaying the others(next), and a numeric pager to show page numbers, and can also show them as link instead of buttons.
You can display page x of y if you startrow indiex and the totalrow index of the container.

It's also possible to use the ChangePage (which has to match the OnPagerCommand attribute in markup) event handler and it's DataPagerCommandEventArgs.

Comments

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.

Javascript: Closure and Lexical Scope

The two are separate topics, I just happen to put them in the same post for now. Closure Closure is the capability to remember it's lexical scope, even when executed outside it's lexical scope. If two inner functions, are within the same scope, they share the same closure.     Lexical scope The lexical scope is the scope in which a variable is declared during the first pass of the javascript compilation, which has two passes, compilation and execution. During the compilation pass, the compiler goes through the code looking for formal declaration, that is, var, function and parameters of function. For each of these formal declarations, the compiler will check the current lexical scope, and add this identifier if it isn't already there. Then at the second pass, execution, the compiler will run the code as we are intuitively use to and once it reaches the the identifiers found earlier, will ask if they are left hand side(RHS), or right hand side (LHS). If th...