An abstract base class for data editor page component. A single data editor may contain one or more data views (ViewModel).
All data views must manipulate with the same data set in that editor. For an instance, when a user edit data from one view and switch to another view, the data
shown in the second view must always be identical the same as the first one. An editor may contain a set of actions (ActionModel) which user can perform
on editor's data. For more information about creating your own editor page, please see the documentation below.
Data View
To specify the list of views in an editor, you have to provide a view provider (IDataEditorViewProvider) into editor's constructor. The editor's constructor
will call IDataEditorViewProvider.getViewModels to obtain the list of data views being displayed in this editor. The concept behind data view is that
to provide user the different perspectives on the same data set. For example, if you're going to build a customer data editor page, you may want to provide user a list view
which allows user to easily search a customer by typing into search text box, then, it'll show customer data in tabular form. Therefore, in some sense, you may want to provide
a calendar view displaying customer's birth date to the user --letting he/she to take less efforts on organizing a CRM work plan. For this kind of use, using
data view, instead of building seperate pages, is the best choice to build your application.
An abstract base class for
data editorpage component. A singledata editormay contain one or moredata views (ViewModel). Alldata views must manipulate with the same data set in that editor. For an instance, when a user edit data from one view and switch to another view, the data shown in the second view must always be identical the same as the first one. An editor may contain a set ofactions (ActionModel) which user can perform on editor's data. For more information about creating your own editor page, please see the documentation below.To specify the list of views in an editor, you have to provide a
view provider(IDataEditorViewProvider) into editor's constructor. The editor's constructor will call IDataEditorViewProvider.getViewModels to obtain the list ofdata views being displayed in this editor. The concept behinddata viewis that to provide user the different perspectives on the same data set. For example, if you're going to build a customer data editor page, you may want to provide user alist viewwhich allows user to easily search a customer by typing into search text box, then, it'll show customer data in tabular form. Therefore, in some sense, you may want to provide acalendar viewdisplaying customer's birth date to the user --letting he/she to take less efforts on organizing a CRM work plan. For this kind of use, usingdata view, instead of building seperate pages, is the best choice to build your application.abcdef
shiorin, tee4cute
ViewModel
ActionModel
IDataEditorViewProvider
IDataEditorActionProvider
IDataServiceFactory