Package net.walend.grid

Grids are Collections built on multidimensional arrays.

See:
Description

Interface Summary

Address	This class is a set of coordinates to address a cell in a Grid.
Grid	Grid is a Collection implanted in a multidimensional array.
Grid2D	Grid2D is a simple two-dimensional Grid, indexed by (i,j).
MutableGrid	MutableGrid adds methods to change Grids.
MutableGrid2D	Grid2D is a simple two-dimensional Grid, indexed by (i,j).

Class Summary

AbstractArrayGrid2D	Grid2D is a simple two-dimensional Grid.
AbstractMapGrid2D	Grid2D is a simple two-dimensional Grid built atop a Map.
Address2D	This class is a set of coordinates to address a cell in a Grid.
ArrayGrid2D	Grid2D is a simple two-dimensional Grid.
Dimension	This is a member of an enum of Dimensions
Grid2D.Dimensions2D
MapGrid2D	Grid2D is a simple two-dimensional Grid.
MutableArrayGrid2D	MutableGrid2D is a simple two-dimensional Grid that you can put and take.
MutableMapGrid2D	MutableGrid2D is a simple two-dimensional Grid that you can put and take.

Exception Summary

BadDimensionException
GridException
ObjectNotOnGridException
OffGridException

Package net.walend.grid Description

Grids are Collections built on multidimensional arrays. The most sane way to access objects within grids is by using their coordiantes or Addresses. Collection methods tend not to be very efficient.

If a Grid will have mostly only one Object at any given Address, use a HashGrid. Otherwise, use an ArrayGrid.

I currently supply Grid2D and ArrayGrid2D. HashGrid2D will come later.

Addresses and Dimensions provide abstractions for handling any grids which may or may not be useful for machine learning.

I use Grid2D as the basis for Boards, and as the guts of matrix-backed CEDigraphs and UEDigraphs. I'm not yet on a vector to build Grid3D, but will do it some day.