NetBeans API リスト - NetBeans 日本普及化支援

NetBeans API リスト

Version 4.0

2004年12月9日

（現在翻訳作業中です2005.2.24）

このドキュメントは NetBeans 4.0のためにリリースされた NetBeans API のリストを提供するものです。
Each API comes with a short description of what it can be used for, and a table describing different types of interfaces (see What is an API? to understand why we list DTDs, file formats, etc.) and with a stability category (see API life-cycle for a list of possible API stability categories and their meaning). The aim is to provide as detailed a definition of NetBeans module external interfaces as possible and give other developers a chance to decide whether they want to depend on a particular API or not.

このドキュメントはNetBeans 4.0で安定状態にあるAPIのみをリストアップしています。
もしあなたが NetBeans が提供するすべての API のリストを探しているなら、開発バージョンのドキュメントを見てください。

Some of these APIs are part of the NetBeans Platform (for example lookup, loaders, utilities, nodes, explorer, window systems, multiview, etc.), some of them are specific to NetBeans IDE (projects, javacore, diff, etc.) and some are not included in the release at all and are just provided for download (usually via autoupdate).
Basically when building an application based on NetBeans one is free to choose the set of modules and their APIs to satisfy one's needs.
基本的にNetBeansをベースとしたアプリケーションを作成しようとする場合、モジュールのセットとこれらのAPIを必要に応じて自由に組み合わせることが出来ます。

追加情報

• Index of all NetBeans API classes すべての NetBeans API クラスのインデックス
• How to use certain NetBeans APIs ある特定の NetBeans API を使う方法

---

内容

• Actions - Actions provides system of support and utility classes for 'actions' usage in NetBeans.
• ant/project - Provides the basic infrastructure by which Ant-based projects can be created, read and write configuration parameters and properties from/to disk, satisfy common queries and interfaces, etc.
• Debugger Core API - The debuggercore/api module (Debugger Core API) allows to install different debugger implementation to one IDE.
• Debugger Core UI API - The debuggercore module (Debugger Core UI) contains shared UI components for all debugger implementations, and defines some SPI for sharing of them.
• Debugger JPDA API - The debuggerjpda/api (Debugger JPDA API) defines API for NetBeans Java Debugger.
• Deployment Descriptor API - The project is based on the requirement to access the web module deployment descriptor for other Netbeans modules in a simple and servlet spec.
• Dialogs API - The DialogsAPI allows creating a user notification, a dialog's description and also permits it to be displayed.
• Diff - The diff module provides the ability to visualize differencies between source files.
• Editor - The EditorAPI is used for accessing editor-related functionality from within the IDE for use by other modules and the core IDE itself.
• Execution - The IDE uses a small interface to describe the execution of Java-based classes together with arguments.
• Explorer API - The ExplorerAPI is build around Explorer - solely a user-interface device: it has no particular knowledge of the structure of the IDE.
• Filesystems - The Filesystems API provides a common API to access files in a uniform manner.
• Input/Output System - The Input/Output API is a small API module (openide-io.jar) which contains InputOutput and related interfaces used in driving the Output Window.
• java/api - Models basic aspects of the metadata surrounding Java source files, such as the classpath.
• java/platform - Many Java-based project types need to be able to configure the version and location of Java to be used when building and running the project.
• java/project - Provides support infrastructure for projects working with the Java language.
• JavaCore - Java Language Model API Implementation - The Java Language API is good for providing a uniform way of accessing/modifying Java metadata from the IDE modules.
• JavaHelp API - The JavaHelp integration API wraps the standard JavaHelp extension library.
• Java Language Model API - The Java Language API is good for providing a uniform way of accessing/modifying Java metadata from the IDE modules.
• java-srcmodel - This module defines JavaHierarchyAPI which allows to inspect Java classes and possibly manipulate with portions of a .java source.
• Loaders - In summary, the LoadersAPI is responsible for scanning files in a directory on disk, weeding out irrelevant files of no interest to the IDE, and grouping the rest into logical chunks, or just determining what type of data each represents.
• Lookup - The Lookup is a central part of communication between different parts of a modularized component system.
• Modules - The Modules API lies at the core of NetBeans and describes how plug-in modules are added and managed.
• NetBeans Metadata Repository - See answer to the use-cases question.
• Nodes - Nodes API serves as the main aparatus for visualisation of objects in NetBeans.
• projects/libraries - Permits libraries to be defined, customized, and stored by the user for reuse in multiple projects.
• projects/projectapi - Provides a generic infrastructure for modelling projects.
• projects/projectuiapi - The module supplies the APIs for the basic, generic UI infrastructure for projects: list of opened projects, main project, basic project-sensitive actions, template wizards, etc.
• projects/queries - General kinds of queries between modules.
• PropertySheet API - The property sheet is a generic user interface component and infrastructure for displaying and editing properties of objects.
• Settings - Settings are persistent objects with a set of properties, that should be available via lookup.
• Utilities - JRE concept wrappersm, improved UI building classes and Usefull methods that are harder to write correctly in separate modules are provided in this Utilities API.
• VCS Core API - The VCS Core module provides basic structure and libraries on which support modules for various version control systems can be based.
• View Model - The debuggercore/ViewModel module (View Model) allows to share one TreeTableView among different modules.
• Window System - Window System API is used to display and control application GUI: Main window, frames, components.