JIDE表格开发指南：验证、撤销与排序功能解析

需积分: 5 166 浏览量更新于2024-07-09 收藏 2.4MB PDF 举报

"JIDE Grids Developer Guide 是一本关于如何使用 JIDE Grids 库进行 Swing 开发的详细指南。该文档涵盖了 JIDE Grids 的主要功能，包括表格验证、撤销支持、转换处理、单元格编辑器与渲染器、可导航模式、单元格样式、排序功能、过滤功能以及自动筛选表头等高级特性。" 本文档的主要目的是帮助开发者充分利用 JIDE Grids 提供的功能来构建高效、功能丰富的 Swing 应用程序。JIDE Grids 是一个扩展了 Java Swing 中 JTable 组件的库，提供了更强大的表格处理能力。 1. **JIDE Grids 概述** - 包含多个包，这些包提供了各种组件和服务，如表格、树、列表等。 - 类层次结构详细介绍了所有 JIDE 表格的组织结构。 2. **验证支持** - **单元格级验证**：允许对单个单元格的数据进行有效性检查。 - **表格级验证**：在整个表格数据集上执行验证。 - **行级验证**：验证整行数据是否满足特定条件。 - **验证结果**：提供验证失败时的反馈和处理机制。 3. **撤销支持** - **默认可撤销表格模型**和**抽象可撤销表格模型**：实现撤销/重做功能的基础。 - **键盘快捷键**：方便用户通过键盘操作进行撤销和重做。 4. **转换处理增强** - 支持数据在不同格式之间的转换，以适应不同的显示和编辑需求。 5. **单元格编辑器和渲染器** - 可自定义单元格的显示和编辑行为，以满足各种数据类型的呈现和输入。 6. **可导航模式和可导航表格** - 用户可以通过键盘导航表格，提高交互效率。 - **自定义导航键**：允许开发者根据应用需求调整导航键设置。 7. **单元格跨度表格**和**单元格样式表格** - **单元格跨度**：允许单元格跨越多列或多行。 - **单元格样式**：提供多种预设样式，并支持自定义样式和合并样式规则。 8. **排序功能** - **比较器**：实现自定义排序逻辑。 - **可排序表格**和**可排序表格模型**：允许用户对表格数据进行动态排序。 9. **过滤和过滤可变表格模型** - 实现表格数据的动态过滤，帮助用户快速定位所需信息。 - **自动筛选表头**：提供便捷的过滤入口。 10. **表格模型包装器**、**复合表格模型事件**以及**可排序/过滤列表和树** - 这些特性允许开发者更灵活地管理和更新表格数据结构。通过这份指南，开发者可以深入理解 JIDE Grids 的强大功能，并将其有效地应用于实际开发项目中，提升 Swing 应用的用户体验和功能完整性。注意文档中的示例代码和实践指导，将有助于更好地理解和应用这些特性。

map.put(KeyStroke.getKeyStroke("control shift Z"), "redo");

Note that we use "undo" and "redo" as the action names. That's because we already

registered both actions on JideTable's ActionMap. All you need to do is to map the keystroke to

the action on the InputMap.

TransferHandler Enhancement in JideTable

TransferHandler provides the data transfer from and to a Swing component. By default,

JTable provides a TransferHandler that only supports copy. In the other word, you can select a

range of cells and copy the content to the clipboard. But you can't paste the content.

In JideTable, we created JideTableTransferHandler class which can handle both copy and

paste. The copy and paste can be done between a JideTable and Microsoft Excel or any other

applications. Drag and drop works too as it is using the same TransferHandler.

The TransferHandler enhancement works with the undo feature. When you copy and paste

causing the table model change, you can undo the change as long as you are using a

DefaultUndoableTableModel or AbstractUndoableTableModel.

Converter

Before we introduce the next table – ContextSensitiveTable, we have to cover some basic

modules that most tables would need.

As we all know, JTable follows MVC design pattern. The Model is the TableModel. The View

is the JTable. There could be any type of the data in the TableModel. Unless you use custom cell

renderers that can display data in a more fancy way, the default cell renderer only displays

String. It means we need some kinds of conversion that converts from any types of data to

String so that it can be displayed in the table cells. Editing table is the opposite. It needs a

converter that converts from String to any data type. Here comes the ObjectConverter.

Below is the interface of ObjectConverter. All converters implement this interface.

public interface ObjectConverter {

/**

* Converts from object to String based on current locale.

* @param object object to be converted

* @return the String

abstract String toString(Object object, ConverterContext context);

/**

* If it supports toString method.

* @return true if supports toString

abstract boolean supportToString(Object object, ConverterContext context);

/**

* Converts from String to an object.

* @param string the string

* @return the object converted from string

abstract Object fromString(String string, ConverterContext context);

/**

* If it supports fromString.

* @return true if it supports

abstract boolean supportFromString(String string, ConverterContext context);

}

As an example, assume you are dealing with a Rectangle object, specified as (10, 20, 100,

200). If you represent this Rectangle as the string “10; 20; 100; 200” then 80% of users will

probably understand it as a Rectangle with x equals 10, y equals 20, width equals 100 and height

equals 200. However, what about the other 20% of the people? Well, they might think it is an int

array of four numbers. That’s fine. Users can generally learn by experience: as long as you are

consistent across your application, users will get used to it. What is more important is you use

the converter consistently across your whole application. If you decide to use “;” as the

separator, do not also use “,”.

The situation is slightly more complicated in the case of Color. If we consider the string “0,

100, 200” - if people understand the RGB view of Color then 90% of them will treat as 0 as red,

100 as blue and 200 as green. However, since Color can also be represented in HSL color space

(Hue, Saturation, and Lightness), some people may consider it as hue equal 0, saturation equals

100 and lightness equals 200. Another way to represent the color is to use the HTML color name

such as “#00FFFF”. If your application is an html editor, you probably should use a converter to

convert color to “#00FFFF” instead of “0, 255, 255”. What this means is that, based on your

users’ background, you should consider adding more help information if ambiguity may arise.

We also need to consider internationalization, since the string representation of any object

may be different under different locales.

void registerConverter(Class, ObjectConverter, ConverterContext).

To help users adding their own classes that support ConverterContex, we provide an

interface called ConverterContextSupport (all of our CellEditor and CellRenders implement this

interface).

We didn’t automatically register the existing converters with the ObjectConverterManager.

However, we do provide a method initDefaultConverter() which you can call to register the

default converters (as shown below). In addition to converters, this will register the default

CellEditors and CellRenderers that we have provided. If you wish to make use of this facility then

make sure that you call the initDefaultConverter() method when your application is started.

ObjectConverterManager.initDefaultConverter();

CellEditors and CellRenderers

The usage of CellEditor and CellRenderer is probably one of the most interesting aspects of

the original JTable design.

First, let’s review how JTable handles customization of cell editors and cell renderers.

1. You can set a CellRenderer and CellEditor per column using TableColumn’s

setCellRenderer and setCellEditor methods respectively.

2. You can set a default CellRenderer and CellEditor per data type using

setDefaultRenderer(Class, TableCellRenderer) and setDefaultEditor(Class,

TableCellEditor) respectively.

3. The cell renderer or editor set in the first case has a higher priority than it in the second

one.

From above, you can see a JTable assumes that each column has the same type of value,

and that each data type will use the same type of cell editor. Unfortunately, neither of these

assumptions is true in some cases (such as PropertyTable which we will cover later). Fortunately

enough, JTable does allow us to add extensions to meet our requirements.

In the case of PropertyTable, each row in the value column may have different types of

value, requiring different editors - even when the same underlying data type is being used. In

order to support this requirement we have created two new classes: CellEditorManager and

CellRendererManager, using an approach similar to the ObjectConverterManager.

If we first consider the CellEditorManager, this allows you to register any cell editor with a

given data type, as defined by its class. You can also register a different cell editor to the same

type using different contexts. Different from CellRendererManager, CellEditorManager takes

CellEditorFactory to make sure an unique cell editor is used for each cell editing.

剩余119页未读，继续阅读

fionfrankie

粉丝: 3
资源: 6

JIDE表格开发指南：验证、撤销与排序功能解析

JIDE_Common_Layer_Developer_Guide.pdf

JIDE_Action_Framework_Developer_Guide.pdf

JIDE_Code_Editor_Developer_Guide.pdf

CREATE TABLE TB_CloudIDE_Statistics_info_20230423 Like TB_CloudIDE_Statistics_info

__init__.pyi

maixpy_v0.6.2_73_g1a4f278a5_openmv_kmodel_v4_with_ide_support.bin与kpu有什么关系

__init__.py缺失

__init__.py“找不到引用

pyqt6 在 '__init__.py | __init__.py' 中找不到引用 'QtCharts'

hc32l110_ide_rev1.0.3.zip

最新资源

init.pyi

init.py缺失

init.py“找不到引用

pyqt6 在 'init.py | init.py' 中找不到引用 'QtCharts'