Re: [nebula-dev] Virtual NatTable

[Edwin Park <esp@xxxxxxxxxx>]

Hi Wim,

Yes - NatTable basically always operates in 'virtual' mode. It doesn't make any assumptions that the entire data set will be in memory and will only ask for the specific data that it needs to render in the UI. All you need to do is provide a data provider that conforms to the following simple interface:

public interface IDataProvider {

	   public Object getDataValue(int columnIndex, int rowIndex);
	   public void setDataValue(int columnIndex, int rowIndex, Object newValue);  // optional
	   public int getColumnCount();
	   public int getRowCount();
	}

It is up to you how you implement lazy loading, batch fetching, cache policies, etc behind the scenes. NatTable doesn't currently provide any special implementations of these as the thought is that this is going to be fairly specific to your particular backend and is relatively straightforward to implement.

Edwin

On Mon, Apr 30, 2012 at 5:43 PM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:

Hi Edwin,

Does the nattable support some form of lazy loading in case the number
of rows will go beyond the available memory.

Regards,

Wim
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev