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.

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.