Releases · PMSI-AlignAlytics/scrollgrid

06 Jan 11:07

0.3.0

fa17ee4

v0.3.0 Latest

Latest

The last release was supposed to be the final one before d3 v4 but there was a significant issue with the library inadvertently storing instance variables in the prototype. It's always been that way but hasn't been an issue in practice because we've only used one Scrollgrid at a time. Unfortunately it was due to a fundamental flaw in the namespacing meaning that this fix required a large refactoring of the codebase, however I think it was important to do this before moving to d3 v4 support.

Assets 4

05 Jan 09:34

johnkiernander

0.2.2

ec9ed05

v0.2.2

This will be the final release before moving to d3 v4.

This includes a new format rule for skipping rows/columns in the form a(n)b where every nth element from a to b will be included. For example the following format rule

{ row: "1:3", column: "1(2)10", ... }

will apply formatting to the first three rows and columns 1, 3, 5, 7 and 9. As with all other format rules, this one can be included in a comma separated list with other rules e.g. "1(3)10,11,20:30". Also as with other format rules, it will only apply to the intersection of a row and column rule, so

 { row: "1(2)10,11:12", column: "1(3)20", ... }

would apply to cells marked X below:

X00X00X00X00X00X00X0
00000000000000000000
X00X00X00X00X00X00X0
00000000000000000000
X00X00X00X00X00X00X0
00000000000000000000
X00X00X00X00X00X00X0
00000000000000000000
X00X00X00X00X00X00X0
00000000000000000000
X00X00X00X00X00X00X0
X00X00X00X00X00X00X0

Finally this release brings significant speed improvements when scrolling the table in Chrome. This is because it uses clip-path CSS for the clipping of text in Chrome, but at time of writing this is not supported in Firefox or IE so the text is clipped with JavaScript. This feature is not tied to the browser, just the compatibility so it will start using it if future versions of the browser support it.

Assets 4

11 Mar 02:09

johnkiernander

0.2.1

8bd906b

v0.2.1

Fixed critical bug with cell rendering and completed missing unit tests

Assets 4

10 Mar 11:58

johnkiernander

0.2.0

919e199

v0.2.0

Changed the getValue methodology to be easier to use.

BREAKING CHANGE for any custom render methods. Instead of having to asynchronously call the getValue method of the datum you now access it directly as d.value. Any custom data adapters will also break, you need to implement them slightly differently - see the examples.

Due to time constraints there are a few tests missing - to be added.

Assets 4