1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 1997-2010 Oracle and/or its affiliates. All rights reserved.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Other names may be trademarks of their respective owners.
The contents of this file are subject to the terms of either the GNU
General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with the
License. You can obtain a copy of the License at
http://www.netbeans.org/cddl-gplv2.html
or nbbuild/licenses/CDDL-GPL-2-CP. See the License for the
specific language governing permissions and limitations under the
License. When distributing the software, include this License Header
Notice in each file and include the License file at
nbbuild/licenses/CDDL-GPL-2-CP. Oracle designates this
particular file as subject to the "Classpath" exception as provided
by Oracle in the GPL Version 2 section of the License file that
accompanied this code. If applicable, add the following below the
License Header, with the fields enclosed by brackets [] replaced by
your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
The Original Software is NetBeans. The Initial Developer of the Original
Software is Sun Microsystems, Inc. Portions Copyright 1997-2006 Sun
Microsystems, Inc. All Rights Reserved.
If you wish your version of this file to be governed by only the CDDL
or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this distribution
under the [CDDL or GPL Version 2] license." If you do not indicate a
single choice of license, a recipient has the option to distribute
your version of this file under either the CDDL, the GPL Version 2 or
to extend the choice of license to its licensees as provided above.
However, if you add GPL Version 2 code and therefore, elected the GPL
Version 2 license, then the option applies only if the new code is
made subject to such option by the copyright holder.
-->
<?xml-stylesheet type="text/xml" href="../nbbuild/javadoctools/apichanges.xsl"?>
<!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../nbbuild/javadoctools/apichanges.dtd">
<!--
INFO FOR PEOPLE ADDING CHANGES:
Check the DTD (apichanges.dtd) for details on the syntax. You do not
need to regenerate the HTML, as this is part of Javadoc generation; just
change the XML. Rough syntax of a change (several parts optional):
<change>
<api name="compiler"/>
<summary>Some brief description here, can use <b>XHTML</b></summary>
<version major="1" minor="99"/>
<date day="13" month="6" year="2001"/>
<author login="jrhacker"/>
<compatibility addition="yes"/>
<description>
The main description of the change here.
Again can use full <b>XHTML</b> as needed.
</description>
<class package="org.openide.compiler" name="DoWhatIWantCompiler"/>
<issue number="14309"/>
</change>
Also permitted elements: <package>, <branch>. <version> is API spec
version, recommended for all new changes. <compatibility> should say
if things were added/modified/deprecated/etc. and give all information
related to upgrading old code. List affected top-level classes and
link to issue numbers if applicable. See the DTD for more details.
Changes need not be in any particular order, they are sorted in various
ways by the stylesheet anyway.
Dates are assumed to mean "on the trunk". If you *also* make the same
change on a stabilization branch, use the <branch> tag to indicate this
and explain why the change was made on a branch in the <description>.
Please only change this file on the trunk! Rather: you can change it
on branches if you want, but these changes will be ignored; only the
trunk version of this file is important.
Deprecations do not count as incompatible, assuming that code using the
deprecated calls continues to see their documented behavior. But do
specify deprecation="yes" in <compatibility>.
This file is not a replacement for Javadoc: it is intended to list changes,
not describe the complete current behavior, for which ordinary documentation
is the proper place.
-->
<apichanges>
<!-- First, a list of API names you may use: -->
<apidefs>
<apidef name="general">General</apidef>
<!-- etc. -->
</apidefs>
<!-- ACTUAL CHANGES BEGIN HERE: -->
<changes>
<change id="typinghooks-spi-added">
<summary>Typing Hooks SPI added</summary>
<version major="1" minor="31"/>
<date day="5" month="8" year="2010"/>
<author login="vstejskal"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
Typing Hooks SPI allows interception of various key typed events
that are processed in the editor. The SPI is a replacement for
subclassing editor actions such as <code>DefaultKeyTypedAction</code>,
<code>InsertBreakAction</code>, etc.
</description>
<issue number="152655"/>
</change>
<change id="added-line-column-based-dialog-bindings">
<summary>Adding line/column based dialog bindings</summary>
<version major="1" minor="24"/>
<date day="26" month="3" year="2010"/>
<author login="vstejskal"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
Added <code>DialogBinding.bindComponentToFile(FileObject fileObject, int line, int column, int length, JTextComponent component)</code>
and <code>DialogBinding.bindComponentToDocument(Document document, int line, int column, int length, JTextComponent component)</code>.
</description>
<issue number="181523"/>
</change>
<change id="added-toggleNonPrintableCharacters">
<summary>EditorActionNames.toggleNonPrintableCharacters added.</summary>
<version major="1" minor="20"/>
<date day="4" month="3" year="2010"/>
<author login="vstejskal"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
Added EditorActionNames.toggleNonPrintableCharacters action name.
</description>
<issue number="4619"/>
</change>
<change id="added-component-removed-property">
<summary>EditorRegistry.COMPONENT_REMOVED_PROPERTY added.</summary>
<version major="1" minor="13"/>
<date day="1" month="7" year="2009"/>
<author login="dbalek"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>EditorRegistry.COMPONENT_REMOVED_PROPERTY is fired when a component is removed from
component hierarchy.
</description>
</change>
<change id="added-dialogbinding">
<summary>DialogBinding added</summary>
<version major="1" minor="11"/>
<date day="15" month="5" year="2009"/>
<author login="dbalek"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>DialogBinding allows for content of some text component to be virtually placed
to the given offset inside of a file or document. This way, the necessary context is
provided for code completion and similar features to work in any text component.
</description>
<class package="org.netbeans.api.editor" name="DialogBinding"/>
<issue number="163769"/>
</change>
<change id="added-editoractionregistration">
<summary>EditorActionRegistration annotation added</summary>
<version major="1" minor="10"/>
<date day="7" month="4" year="2009"/>
<author login="mmetelka"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
EditorActionRegistration allows to easily register an editor action
into the list of actions of an editor kit. It also allows a lazy
action's class loading (more details in javadoc).
</description>
<class package="org.netbeans.api.editor" name="EditorActionRegistration"/>
<issue number="150875"/>
</change>
<change id="added-codegen-spi">
<summary>Code Generation SPI added</summary>
<version major="1" minor="8"/>
<date day="30" month="4" year="2008"/>
<author login="dbalek"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
The Code Generation SPI consists of two interfaces.
The <code>CodeGenerator</code> implementations registered for
various mime types serve for creating code snippets and inserting
them into documents on the Insert Code editor action invocation.
The <code>CodeGeneratorContextProvider</code> implementations
registered for the mime types could provide the respective
CodeGenerators with an additional context information.
</description>
<issue number="134239"/>
</change>
<change id="added-HighlightAttributeValue">
<summary>HighlightAttributeValue interface added</summary>
<version major="1" minor="5"/>
<date day="13" month="9" year="2007"/>
<author login="vstejskal"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
The <code>HighlightAttributeValue</code> allows specifying highlights
with attributes, which value is lazily evaluated at the time when
the attrbute is used. For example when specifying tooltips.
</description>
<issue number="107107"/>
</change>
<change id="added-EditorRegistry">
<summary>EditorRegistry added</summary>
<version major="1" minor="4"/>
<date day="7" month="6" year="2007"/>
<author login="mmetelka"/>
<compatibility binary="compatible" source="compatible" semantic="compatible" addition="yes"/>
<description>
The <code>EditorRegistry</code> allows to get focused and last focused text component
and list of all registered components and it allows to listen for currently focused
component and changes of documents in it.
</description>
<issue number="103235"/>
</change>
<change id="removed-AttributesUtilities">
<summary>AttributesUtilities removed</summary>
<version major="1" minor="3"/>
<date day="26" month="1" year="2007"/>
<author login="vstejskal"/>
<compatibility binary="incompatible" source="incompatible" semantic="incompatible" deletion="yes"/>
<description>
The <code>AttributesUtilities</code> class has been moved to
<code>editor/settings</code> module.
</description>
</change>
<change id="created">
<summary>editor/lib2 was created.</summary>
<version major="1" minor="0"/>
<date day="1" month="8" year="2006"/>
<author login="mmetelka"/>
<compatibility binary="compatible" source="compatible" semantic="compatible"/>
<description>
The module was created.
</description>
</change>
</changes>
<!-- Now the surrounding HTML text and document structure: -->
<htmlcontents>
<!-- Generated from apichanges.xml -->
<head>
<title>Change History for the Editor Library 2 API</title>
<link rel="stylesheet" href="prose.css" type="text/css"/>
</head>
<body>
<p class="overviewlink"><a href="overview-summary.html">Overview</a></p>
<h1>Introduction</h1>
<p>This document lists changes made to the <a href="overview-summary.html">Editor Library 2 API</a>.</p>
<!-- The actual lists of changes, as summaries and details: -->
<hr/>
<standard-changelists module-code-name="org.netbeans.modules.editor.lib2/1"/>
<hr/><p>@FOOTER@</p>
</body>
</htmlcontents>
</apichanges>
|
