From 053267fc5d7a087b315612a43fc493083309f465 Mon Sep 17 00:00:00 2001 From: Miguel de Icaza Date: Mon, 6 Mar 2000 00:56:49 +0000 Subject: Add stuff, revamp stuff svn path=/trunk/; revision=2068 --- doc/white-papers/widgets/e-table.sgml | 70 ++++++++++++++++++++++++++-------- help/white-papers/widgets/e-table.sgml | 70 ++++++++++++++++++++++++++-------- 2 files changed, 110 insertions(+), 30 deletions(-) diff --git a/doc/white-papers/widgets/e-table.sgml b/doc/white-papers/widgets/e-table.sgml index 50e2aa46e5..5ff4faf2ae 100644 --- a/doc/white-papers/widgets/e-table.sgml +++ b/doc/white-papers/widgets/e-table.sgml @@ -5,6 +5,7 @@ ETableSimple"> ETableHeader"> ETableSpecification"> +ETableCol"> ]>
@@ -54,7 +55,7 @@ table. Without any work from the programmer, &ETable; provides rearrangeable columns and editable data. When finished, &ETable; will also provide, again with no programmer intervention, easy interactive - sorting and grouping. + sorting and grouping. @@ -64,19 +65,49 @@ However, once you learn it, &ETable; is not very hard at all to use. + + + &ETable;'s power comes from the fact that it is fully + model/view/controller based. Various models are involved into + the process of rendering the information, and various views are + provided. The programmer has a wide range of options: from the + most finely hand-tuned table to a generic all-encompasing widget + that takes over most of tasks. It is up to the programmer: he + can use the simple to use &ETable; widget that takes care of + everything in a generic way, or he can use the various + components to roll his own tabular display. + + + + &ETable; ships with a standard set of information renderers: + strings, bitmaps, toggle-buttons, check-boxes, and multi-line + strings. But the programmer can write and implement his own + renderer for his information. This means that by default + &ETable; provides the basic display facilities that programmers + required, but they offer the programmer a complete freedom to + incorporate new cell renderers. + + ETableModel - The back end of &ETable; is an &ETableModel;. To use &ETable; - you have to create a subclass of &ETableModel;. However, to save - you the work of defining a new GtkClass, - there is a predefined subclass of &ETableModel; called - &ETableSimple; which simply takes a list of callbacks to perform - the various operations. + The data back end for the &ETable; is an &ETableModel;. The + &ETableModel is an abstract interface that acts as the + information repository for the various &ETable components. + + + To use &ETable; you have to create a subclass of the abstract + &ETableModel; class. However, to save you the work of defining + a new GtkClass every time you use + &ETable, there is a predefined subclass of &ETableModel; called + &ETableSimple; which simply takes a list of function callbacks + to perform the various operations. + + @@ -84,17 +115,26 @@ There are two different meanings to the word "column". The first - is the model column. A model column corresponds to a specific - type of data. This is very much like the usage in a database - table where a column is a field in the database. + is the model column (defined by the &ETableCol: object). A model + column describes how it maps to the column in the &ETableModel; + as well as containing information about its properties (name, + resizability, resize dimensions, and a renderer for this + specific columns). + + + + &ETable; distinguishes between a model column index, and a view + column index. The former reflects the column in which the data + is stored in the &ETableModel; The later represents the actual + location at which the column is being displayed in the screen. - The second type of column is a view column. A view column - corresponds to a visually-displayed column. Each view column - corresponds to a specific model column, though a model column - may have any number of view columns associated with it - (including zero). + Each view column index corresponds to a specific model column, + though a model column may have any number of view columns + associated with it (including zero). For example the same + column might be rendered twice, or the data from one column + could be used to display different bits of information diff --git a/help/white-papers/widgets/e-table.sgml b/help/white-papers/widgets/e-table.sgml index 50e2aa46e5..5ff4faf2ae 100644 --- a/help/white-papers/widgets/e-table.sgml +++ b/help/white-papers/widgets/e-table.sgml @@ -5,6 +5,7 @@ ETableSimple"> ETableHeader"> ETableSpecification"> +ETableCol"> ]>
@@ -54,7 +55,7 @@ table. Without any work from the programmer, &ETable; provides rearrangeable columns and editable data. When finished, &ETable; will also provide, again with no programmer intervention, easy interactive - sorting and grouping. + sorting and grouping. @@ -64,19 +65,49 @@ However, once you learn it, &ETable; is not very hard at all to use. + + + &ETable;'s power comes from the fact that it is fully + model/view/controller based. Various models are involved into + the process of rendering the information, and various views are + provided. The programmer has a wide range of options: from the + most finely hand-tuned table to a generic all-encompasing widget + that takes over most of tasks. It is up to the programmer: he + can use the simple to use &ETable; widget that takes care of + everything in a generic way, or he can use the various + components to roll his own tabular display. + + + + &ETable; ships with a standard set of information renderers: + strings, bitmaps, toggle-buttons, check-boxes, and multi-line + strings. But the programmer can write and implement his own + renderer for his information. This means that by default + &ETable; provides the basic display facilities that programmers + required, but they offer the programmer a complete freedom to + incorporate new cell renderers. + + ETableModel - The back end of &ETable; is an &ETableModel;. To use &ETable; - you have to create a subclass of &ETableModel;. However, to save - you the work of defining a new GtkClass, - there is a predefined subclass of &ETableModel; called - &ETableSimple; which simply takes a list of callbacks to perform - the various operations. + The data back end for the &ETable; is an &ETableModel;. The + &ETableModel is an abstract interface that acts as the + information repository for the various &ETable components. + + + To use &ETable; you have to create a subclass of the abstract + &ETableModel; class. However, to save you the work of defining + a new GtkClass every time you use + &ETable, there is a predefined subclass of &ETableModel; called + &ETableSimple; which simply takes a list of function callbacks + to perform the various operations. + + @@ -84,17 +115,26 @@ There are two different meanings to the word "column". The first - is the model column. A model column corresponds to a specific - type of data. This is very much like the usage in a database - table where a column is a field in the database. + is the model column (defined by the &ETableCol: object). A model + column describes how it maps to the column in the &ETableModel; + as well as containing information about its properties (name, + resizability, resize dimensions, and a renderer for this + specific columns). + + + + &ETable; distinguishes between a model column index, and a view + column index. The former reflects the column in which the data + is stored in the &ETableModel; The later represents the actual + location at which the column is being displayed in the screen. - The second type of column is a view column. A view column - corresponds to a visually-displayed column. Each view column - corresponds to a specific model column, though a model column - may have any number of view columns associated with it - (including zero). + Each view column index corresponds to a specific model column, + though a model column may have any number of view columns + associated with it (including zero). For example the same + column might be rendered twice, or the data from one column + could be used to display different bits of information -- cgit v1.2.3