Page: adaptive gridview page

[touseefbsb]

we can have a page option with adaptive gridview( as in uwp community toolkit ) and/or Listview with slideable listview items ( also in uwp community toolkit) and both of these controls can have a sticky header ( within uwp community toolkit ) or shy header ( when in creators update or further, shy header example is present in windows dev UI sample app ).
Datatemplate and structure of each griview or listview item can be of typical use with couple of basic properties which can be easily edited obviously afterwards by the developer as in MVVM pattren would be perfect for this scenario.

[crutkas]

One issue per request, this is two requests.

[mrlacey]

Different header options make this even more than two requests.

For reference: http://docs.uwpcommunitytoolkit.com/en/master/controls/AdaptiveGridView/

Also note that the ListView in the Fall Creators Update adds native support for swipeable list items too.

[touseefbsb]

then only gridview page with header would be enough for this one request. Thanks

[crutkas]

GridView vs Adaptaptive gridview, why not just reference the UWP toolkit one via a comment. If someone wants to do the upgrade, the could. While powerful, it should be an easy swap

[mrlacey]

Is the current Grid page sufficient or is there the need for a toolkit/adaptive version as well?
Or would documentation on how to use something else be enough?

[crutkas]

is the new photo grid page more inline? I really think that we are splitting hairs here for swapping out controls. i stand behind we comment the template that you can swap it out with others else we'll have hundreds of permutations.

[touseefbsb]

@crutkas @mrlacey I have some more feature recommendations, regarding this gridviewpage, or extensions in adaptivegridview if you will.

1. Search bar : a top search bar attached to the control which can be enabled/disabled with a bollean property. this search bar auto filters the items on basis of the filterDescriptor provided ( filter descriptor can be defined by the developer, tht which string,time,int property to match with which condition i.e : Contains, startswith, endswith e.t.c. and which operator to use [AND/OR] in case of multiple property filter provided.)

2. Grouping : another optional feature to enable grouping on basis of a string property of the items. and this grouping will obviously include the semantic zoom feature as well.

3. Incremental Loading: I know this is already in the community toolkit. But it can be part of the control with another boolean property to enable it.

4. Sorting : sorting with 1 or more properties.

5. List/GridSwitcher : there can be a toggle button on the top of the control which can toggle the control to view as a listview ( each item expanded fully ) or to a gridview ( normal grid like behaviour )

These are some of the most common scenarios which are required by developers and there are many ways to do it, but this can get very complicated to align them with best practices. We can discuss which features are doable or should be done, or should a seperate dedicated new type of page should be created for all these features? or maybe should I post it in community toolkit repo instead?

Please note that many of these features are inspired from Telerik UWP Grid Control but that is rather just a row by row control to show the data, but I was wondering if some of those key features can be implemented in a traditional collectionView which is native to uwp and has the brilliant UI we all know and love, which works great with fluent design obviously by default and users can add animations etc into it if they want. This can be a very powerful control/page yet looking very good to the eye as well.

[mrlacey]

@touseefbsb a lot of what you're mentioning seems more related to #520 where we have split out the ideas behind a more complex list page.

also, where are the two quotes from?

[mrlacey]

I'm open to having a separate grid page option (for the Community Toolkit version) but we need to be clear on how it's different to the Telerik one and the different advantages of each.

[touseefbsb]

@mrlacey

yeah sure let me elaborate how it can be different from telerik one.

Telerik control disadvantages for uwp platform.

1. No Fluent Design
2. No responsiveness because of multiple columns.
3. Restricted to a column based data only ( cannot show data like a traditional gridview)
4. column headers are not needed in all scenarios.

Basically what I am trying to explain here is that telerik grid control is limited to 1 specific scenario which is to represent and deal with column based data with mostly, strings, datetime, int and all mathemetical properties and taking their sum, avg etc. which is good with database like apps and apps which need to deal with that sort of data only.

Meanwhile if we want to show a list of items with any sort of custom functionality and custom data template working with images, videos, buttons, commandbars, semantic zoom, grouping, and whole lot of fancy uwp stuff which traditional listview/gridview offer, also they offer fluent design and on the road map of UI that should be prefered.

telerik UI has bundle of features which are mostly not used unless ( as i said before ) you have an admin dasboard app and you need to work with database stuff.

So I am proposing a powerful control which is based on traditional uwp gridview/listview ( or AdaptiveGridView would be even better ). and then add those uwp extension features to it by default, which are already present in the platform but user has to do a lot of work to enable them, like sorting, switching between grid./list mode,, semantic zoom and grouping. this will be 1 advantage, and then I want to take only some features inspired from telerik grid, which can be used in almost 90 percent of the uwps apps which have a list of elements in any form, and those features are like searching ( filtering as we type ) accross 1 or more properties, as told by the developer.

I can show you guyx images or other references or examples of such use cases, on web and on other mobile apps well where this use case is very very common.

**Summary **:

this new control = uwp adaptive gridview + uwp features to extend the listview/gridview + some extra new features which can be seen in almost every app