3.0 Release

[orneryd]

Major architectural overhaul

We have come up with a better architecture design for the grid and will be working here int he near future to bring you all the grid you and angularjs deserves.

More to come.

[marklagendijk]

Sounds great!
How can I contribute? I have quite some experience with Angular, and would be willing to help.

For my current project I have written a 'DataSource' class which helps you to bind data coming from a JayData EntitySet to an ngGrid. It takes care of paging, filtering etc. I think it would be a good idea to include these kind of helpers (other people could write one for BreezeJS etc) in the ngGrid project itself.

I also have some ideas about how to make sure that you have full control over everything that happens in the Grid. Such as:

• Make all default (key) events cancel-able. It is great that the Grid has good defaults, but sometimes you just want to do things differently.
• Make sure that all options etc work two ways. For example, currently changing the 'selectedItems' does not (de)select items in the grid.

[roblarsen]

Starting to look at the declarative markup for a version 3.0. Please take a look and share your thoughts.

https://github.com/angular-ui/ng-grid/blob/3.0/Brainstorm.md

[matthughes]

I personally find directive attributes very unreadable. I'd much rather have them as element names and avoid the divitis.

<ui-grid>
  <ui-grid-header>
    <!-- auto-generate column headers if no content supplied? -->
  </ui-grid-header>

  <!-- ui-grid-repeat auto-generates columns, ui-repeat-virtual handles the actual virtual repeater functionality? -->
  <ui-grid-repeat  ui-repeat-virtual="d in data">
    <!-- auto-generate columns if no content supplied? -->
  </ui-grid-repeat>

  <!-- or perhaps this?? (from ProLoser) -->
  <ng-repeat="item in $virtualized" ui-virtualize="items">
  <!--
    ui-virtualize virtualizes a list of items and hands it to the built-in repeater, if the repeater is performant enough
  -->
</ui-grid>

[c0bra]

@matthughes that's personal preference. The directives can be restrict: 'EA' and you can use whichever method you want.

[smithscripts]

Being able to toggle edit mode without having to switch templates and rebuild the entire grid. Is this going to be part of 3.0?

[jonricaurte]

@robsmithers It shouldn't do that right now. Can you make a plunker?

[jonricaurte]

The reason for not using divs would be to not have to use jquery for accessing elements. Right now angular's element.find() only supports tag names:

http://docs.angularjs.org/api/angular.element

[smithscripts]

@jonricaurte Your right, it does not do that right now, I'm suggesting that as a feature. You shouldn't have to replace the grid template and rebuild to go from read-only mode to edit mode.

[Drahakar]

If it's possible, It would be nice if ngGrid provided with more functions / features / documentation for unit testing. I am using ngGrid in a project and I feel it's really hard to test functions that interact with ngGrid.

Thank you

[c0bra]

TDD is a major focus for us moving forward. If you can describe the
interactions you want to test that would be great.
On Dec 11, 2013 8:43 PM, "Drahakar" notifications@github.com wrote:

If it's possible, It would be nice if ngGrid provided with more functions
/ features / documentation for unit testing. I am using ngGrid in a project
and I feel it's really hard to test functions that interact with ngGrid.

Thank you

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/727#issuecomment-30385117
.

[Drahakar]

@c0bra ideally, everything the grids allows should be "emulable" in unit test. More precisely, here are some test cases that I can think of :

• Emulate a row selection (suppose I'd like to see some calculation go on when a row is selected)
• Emulate a cell edit (same reasons)
• Be able to validate that all/some (of) the rows were selected/unselected
• (any other grid interactions with the controller)

Also, if a controller is using some of the grid functions (like selecting a row), I need to declare a ng-element that contains a ngGrid and compile this element to get the grid functions into my scope (otherwise the grids method are not "added" into the scope). Would there be a way to remove the need for that?

Maybe there is already a way to do all of these, but I find it really hard to get documentation on how to unit test my interactions with the grid (without writing e2e tests). It would make my daily life easier if I could get more features / documentation to unit test controllers that uses the grid.

Thank you.