Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLars Vogel2016-09-09 09:40:18 +0000
committerLars Vogel2016-09-19 22:57:45 +0000
commit696cc795317725ee09c4d12d59dba43bee17df40 (patch)
tree7bdf4b692969d0093baa7568d70e554f9fef98bb /org.eclipse.ui.editors
parentde4bc442323d5292a11a22bf5ae9119245be762a (diff)
downloadeclipse.platform.text-696cc795317725ee09c4d12d59dba43bee17df40.tar.gz
eclipse.platform.text-696cc795317725ee09c4d12d59dba43bee17df40.tar.xz
eclipse.platform.text-696cc795317725ee09c4d12d59dba43bee17df40.zip
Bug 501127 - Remove outdated _buildnotes_text_*.html from
org.eclipse.ui.editors Change-Id: I5529f35a09cb97d31d012821c40cf19d378cca40 Signed-off-by: Lars Vogel <Lars.Vogel@vogella.com>
Diffstat (limited to 'org.eclipse.ui.editors')
-rw-r--r--org.eclipse.ui.editors/_buildnotes_text_2_0.html971
-rw-r--r--org.eclipse.ui.editors/_buildnotes_text_2_1.html267
-rw-r--r--org.eclipse.ui.editors/_buildnotes_text_3.2.html132
-rw-r--r--org.eclipse.ui.editors/_buildnotes_text_3.3.html114
-rw-r--r--org.eclipse.ui.editors/_buildnotes_text_3_0.html707
-rw-r--r--org.eclipse.ui.editors/_buildnotes_text_3_1.html231
6 files changed, 0 insertions, 2422 deletions
diff --git a/org.eclipse.ui.editors/_buildnotes_text_2_0.html b/org.eclipse.ui.editors/_buildnotes_text_2_0.html
deleted file mode 100644
index f20e33465..000000000
--- a/org.eclipse.ui.editors/_buildnotes_text_2_0.html
+++ /dev/null
@@ -1,971 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
- <meta name="Author" content="IBM">
- <title>Eclipse Platform Release Notes - Desktop</title>
-</head>
-<body>
-
-<h1>
-Eclipse Platform Build Notes</h1>
-
-<h1>
-Text Editor Support (including JFace Text)</h1>
-
-<p><br>Eclipse SDK Build 20020601
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Introduced the concept of setRedraw(boolean) on text viewers. See ITextViewerExtension.setRedraw(boolean).
-This allows to avoid any UI updating while manipulating the viewer's document.
-While redraw == false, the viewer selection is still available, i.e. setSelectedRange
-and getSelectedRange can be used and always refer to the actual state of
-the viewer's document. However, no selection change event and no view port
-changes are sent out. TextEvent (See ITextListener) has been extented to
-carry the viewer's redraw flag.</li>
-
-<li>
-Introduced the concept of&nbsp; a "sequential rewrite mode" on documents.
-See IDocumentExtension. This informs a document about an upcoming sequence
-of non-overlapping consecutive replace commands. If capable the document
-can use this information to operate on an optimized text store. In JFace
-Text, Document operates on a SequentialRewriteTextStore during this period.</li>
-
-<li>
-Reworked text shifting, line delimiter conversion, and find/replace to
-use the newly introduced concepts.</li>
-
-<li>
-Reworked the reactivation behavior of text hovers.</li>
-
-<li>
-Pushed text hover information computation in a background thread.</li>
-
-<li>
-Reactivated and extended the concept of widget token management. See IWidgetTokenOwner,
-IWidgetTokenKeeper.</li>
-
-<li>
-Extended text operations so that they can externally be enabled/disabled.
-See ITextOperationTargetExtension. Currently, this is only used for content
-assist in the source viewer. All other text operations ignore the enable
-flag.</li>
-
-<li>
-Improved incremental search behavior.</li>
-
-<li>
-Further code cleanup.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-See bugzilla.
-<p>
-<hr WIDTH="100%">
-<br>Eclipse SDK Build 20020517
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-The ruler context menu action are initialized correctly when invoked over
-keyboard shortcut. (Ctrl+W)</li>
-
-<li>
-Added delete line actions ([Esc 0] Ctrl+K with emacs key bindings) to text
-editor</li>
-
-<li>
-Added support for setting/clearing/swapping a mark (emacs style selection)</li>
-
-<li>
-Code Cleanup</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-See bugzilla.
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020514
-<h2>
-Breaking API changes</h2>
-IVerticalRulerInfo.addMouseListener/removeMouseListener have been removed
-again. The vertical ruler now provides a control that shares its listeners
-with its children.
-<p>IDocumentProviderExtension.getStatus(Object element) returns an IStatus
-connected with the given element. The status can be used to relate any
-relevant kind of status information with an element for which a provider
-manages a document.
-<h2>
-Other highlights</h2>
-Introduced a StatusTextEditor. The status text editor checks the status
-flag managed for its input element by the editor' document provider. If
-the status is not-OK, a different control is shown. By default an InfoForm
-is shown. Subclasses can change what is shown or subclass InfoForm.
-<p>StorageDocumentProvider and FileDocumentProvider honor the workbench's
-encoding settings. In addition, encoding support is provided by standard
-text editor. File can be viewed using different encodings. Save always
-uses the workbench's encoding setting. Custom editors can leverage the
-support by including the EncodingActionGroup into their menus. The encoding
-support uses the newly introduced status text editor.
-<p>Text hover timeout when typing has been improved. It's now always 1500ms.
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-See bugzilla.
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<br>&nbsp;
-<p>Eclipse SDK Build 20020508
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-The context menu of the vertical ruler can be opened with Ctrl+W when using
-the default key binding. Accelerator for the emac's key binding is still
-to be defined.</li>
-
-<li>
-Added support for composite vertical ruler. See CompositeVerticalRuler.&nbsp;
-A composite vertical ruler is configured with ruler columns. Two ruler
-columns are provided by default: AnnotationRulerColumn and LineNumberRulerColumn.</li>
-
-<li>
-Performance changes to the reconciling mechanism in JFace Text.</li>
-
-<li>
-Changes in handling read only files: All modifying text actions are disabled
-by default.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#15071 convert line delimiters - one os missing
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20020430
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Introduced the concepts of state dependent actions, i.e. actions which
-change their enabling state depending on whether the editor's input is
-read only or not.</li>
-
-<li>
-Added line delimiter conversion actions for DOS, UNIX and Mac.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020423
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Viewport clipping in the vertical ruler</li>
-
-<li>
-Improved painting of range indicator</li>
-
-<li>
-Fixed problem in position handling in AbstractDocument</li>
-
-<li>
-Improved handling of delete in GapTextStore</li>
-
-<li>
-Changes in partition parsing: Introduced the concept of a partition token
-scanner which can resume scanning in the middle of&nbsp; token range.&nbsp;
-The basic assumption is that partition delimiters don't contain line delimiters.
-Partition token scanners can be built with rules implementing IPredicateRule.
-A predicate rule can start evaluation between their start and end sequence.
-PatternRule has been adapted.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020418
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Added method <i>undelete</i> to Position.</li>
-
-<li>
-AbstractMarkerAnnotationModel better supports heterogenous sets of annotations.</li>
-
-<li>
-DefaultUndoManager causes selection changes when executing undo/redo to
-ensure correct enabling/disabling of selection dependent actions.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020411
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Enabled annotation models for more fine grained change notification</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#13358 incremental find: displays little squares after you press 'delete'
-<br>#13283 Find/Replace: Close button too small
-<br>#13459 Typing tab with selection in middle of line shifts right
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<br>&nbsp;
-<p>Eclipse SDK Build 20020409
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Added support for external contribution of ruler actions. I.e. plugins
-can contribute actions to the context menu of an editor's vertical ruler&nbsp;
-by specifying those actions in their plugin.xml file.</li>
-
-<li>
-In the default key binding Ctrl+ArrowUp and Ctrl+ArrowDown are bound to
-scroll a single line without moving the cursor.</li>
-
-<li>
-AnnotationModel is be used from several threads.</li>
-
-<li>
-TextViewer implements ITextViewerExtensions which supports the stacking
-of VerifyKeyListeners. A listener that is prepended to the list of verify
-key listeners can take over the control over all key strokes not bound
-as menu item accelerators.</li>
-
-<li>
-The scheme according to which an editor calls Workspace.validateEdit has
-been reworked.</li>
-
-<li>
-The editor hooks to the Revert action in the File menu.</li>
-
-<li>
-AbstractTextEditor supports property dependent actions similar to selection
-or content dependent actions.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#11215 Editor task creation actions should use TaskPropertiesDialog
-<br># 9761 Line has to be selected from beginning when using the 'Tab'
-<br>#10806 call validateEdit() again before any further changes
-<br>#11480 READ/WRITE not updated on focus change
-<br>#12901 P2 Find/Replace should keep last selection highlighted
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20020402
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-fixed a problem in the TextViewer's handleDipose method</li>
-
-<li>
-AbstractMarkerAnnotationModel can now deal with a heterogenous set of annotations</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020326
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Enabled key binding support</li>
-
-<li>
-dialog-less incremental search (improvements)</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20020318
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-All find operations can be limited to a scope using the find replace dialog.
-Multi-line selections serve as scope.</li>
-
-<li>
-Emacs-like incremental search (Ctrl-J) is now part of AbstractTextEditor.</li>
-
-<li>
-Preparations for key binding support</li>
-
-<br>&nbsp;</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#2280 Undo does not jump to undone location (1GEK1G5)
-<br>#7381 Search results block hover help for problems
-<br>#7954 Content assist off the edge of the display
-<br>#10141 Shift Left/Right disabled unless selection is "full lines".
-<br>#11047 Index out of bounds on text hover
-<br>#11148 Syntax coloring lost on revert
-<br>#11377 Code assist leaks threads
-<br>#11433 NPE opening editor when some plugins disabled
-<br>&nbsp;
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20020312
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-All editors based on AbstractTextEditor now support <i>Find Next</i> and
-<i>Find
-Previous. </i>Both actions are selection aware, i.e. having a word selected
-when invoking <i>Find Next </i>searches for the next appearance of the
-selected word.</li>
-
-<li>
-A first cut of incremental search is implemented accessible via the Find/Replace
-dialog.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#5191 EC DCR: Add keyboard accelerator for "Find Next"
-<br>#5710 Emacs-like isearch (aka "incremental search")
-<br>#10489 Indention a template results in NPE
-<br>#2698 Opening Default Text Editor not showing right icon in the file
-tab (1GI7GK2)
-<br>#7954 Content assist off the edge of the display
-<br>#9964&nbsp; nor P3 Syntax highlight and comments bug
-<br>#11047&nbsp; nor P2 Index out of bounds on text hover
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20020305
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#8652 ctl-space doesn't wrk for content assist in Java editor when
-<br>#8910 @link-tag in Javadoc display broken
-<br>#9576 Method argument hints not as smart as code assist
-<br>#10315 Syntax highlighting glitch
-<br>#10422 Incorrect syntax highlighting for comments
-<br>#10721 Syntax highlighting lost in Java editor after replace with r
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020212
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Added IContextInformationExtension to support context information positions
-not equal to completion position (related to #4366).</li>
-
-<li>
-Added preference store keys for system default background/foreground colors
-(related to #5811).</li>
-
-<li>
-Reworked handling of read-only resources and state changes of resources.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#2635 Find should remember last string if selection empty (1GHFMYL
-<br>#5380 Error hover doesn't appear
-<br>#7483 NPE during revert in Java editor
-<br>#2575 [JFace Text] BUG - org.eclipse.ui.texteditor inconsistency (1GGLRU6)
-<br>#5969 Find dialog placement needs improvement
-<br>#5811 Pref to set editor background color
-<br>#5819 Code formatter doesn't work well with else if on next line
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020129
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#5819 Code formatter doesn't work well with else if on next line
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020122
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#4324 EC: Find/replace gets stuck in infinite loop (1GLCBZE)
-<br>#3736 DCR: Go to line - would be nice to show valid range (1GEHSDX)
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020115
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#4335 Find/Replace should come up with first history entry (1GEL5NS)
-<br>#4338 Find/change history is never pruned (1GHDUJW)
-<br>#4342 TextViewer.setTopIndex doesn't take horizontal scrollbar into
-account (1GIFYC7)
-<br>#4343 Text hidden inserted by code assist (1GJ9PGK)
-<br>#6701 Code assist: java hint not properly aligned
-<br>#6379 StatusLine 'Writeable' is not readable
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20020108
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#3833 Javadoc hover appears under code assist window (1GF0K3T)
-<br>#4363 Two Java Doc hovers
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20011218
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#1614 Current line in Debugger should start at center of source ed
-<br>#5000 Context menu IDs not fully qualified
-<br>#5959 Text editor: SEVERE - Revert should be undoable
-<br>#6075 NPE while editing in compare view
-<br>#6318 F2 window accessability issues
-<br>#4367 Argument hover doesn't work for nested method call
-<br>#4964 Automatic Code Assist needs to be smarter
-<br>#4966 Automatic Code Assist needs to be smarter #2
-<br>#4967 Automatic Code Assist needs to be smarter #3
-<br>#4968 Automatic Code Assist needs to be smarter #4
-<br>#4969 Automatic Code Assist needs to be smarter #5
-<br>#4999 Automatic Code Assist needs to be smarter #7
-<br>#6589 ctrl+insert, shift+insert incorrectly flips the insert/overw
-<br>#3467 Horizontal scrolling when stepping through errors (1GE6AF1)
-<br>#4041 out of sync error message after copying resources (1GGR6VZ)
-<br>#6699 Save should not flush undo stack
-<br>#4071 Format option loses place in editor (1GHQFU6)
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20011211
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#1614 Current line in Debugger should start at center of source editor
-(1GETH7J)
-<br>#3467 Horizontal scrolling when stepping through errors (1GE6AF1)
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20011206
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-Support for read-only but modifiable resources in editors. For this reason
-AbstractTextEditor now calls validateState if its document provider also
-implement IDocumentProviderExtension. The calls are issued:
-<ul>
-<li>
-when an editor is marked dirty</li>
-
-<li>
-when an editor saves its document to its input</li>
-
-<li>
-when a dirty resource is moved (if allowed)</li>
-</ul>
-Calling validateState may cause changes to the isModifiable and isReadOnly
-properties of the editor's input.
-<br>FileDocumentProvider implements validateState by calling IWorkspace.validateEdit
-on the input file.
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20011204
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-Perparations for supporting the concept of read-only but modifiable resources
-in editors.
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#6203 SEVERE: typing in java editor causes OutOfMemoryError in JDK 1.4
-<br>#6263 Extra closing braces inserted
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 20011127
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-An BasicTextEditorActionContributor now contributes three status fields
-into the window's status line. Each field is dedicated to show information
-of a particular category. The categories are defined in ITextEditorActionConstants.
-A new interface ITextEditorExtension has been introduced. On activation,
-implementing editors of this interface are informed about the status fields
-they can use to publish status information. AbstractTextEditor implements
-ITextEditorExtension. Subclasses of AbstractTextEditor can get access to
-the editor's current status fields using the method getStatusField(String
-category). By default, AbstractTextEditor publishes the following information:
-cursor position, input mode, reade only state of its input. Subclasses
-may change this behavior by overriding updateStatusField(String category)
-or callers of this method.</li>
-
-<li>
-The default text editor uses the feature described above and now provides
-status information.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#4071&nbsp;&nbsp;&nbsp; Format option loses place in editor (1GHQFU6)
-<br>#6168&nbsp;&nbsp;&nbsp; code assist preference (auto complete) does
-not work
-<br>#6087&nbsp;&nbsp;&nbsp; NPE closing content assist from DisplayView
-on exit
-<br>#6013&nbsp;&nbsp;&nbsp; Repeatable Java editor hang in 200111115
-<br>#4947&nbsp;&nbsp;&nbsp; No indication of Insert/Overwrite mode
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20011120
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-Change to AbstractHoverInformationControlManager to reset the hover location
-on a time basis.</li>
-
-<li>
-Added configuration method to ContentAssistant to automatically insert
-a single proposal.</li>
-
-<li>
-Behavioral configuration methods such as enableAutoInsert, enableAutoActivation,
-and setAutoActivationDelay can now be called when after the content assistant
-has been installed.</li>
-
-<li>
-Context information popup recomputes size after style information has been
-applied.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports closed</h2>
-#2569&nbsp;&nbsp;&nbsp; [JFace Text] Content assist list truncated (1GG1W9B)
-<br>#2904&nbsp;&nbsp;&nbsp; [JFace Text] PropagatingFontFieldEditor has
-moved (1GKKL13)
-<br>#1824&nbsp;&nbsp;&nbsp; [JFace Text] 50 reconciling threads for 4 editors
-opened (1GFXMV8)
-<br>&nbsp;
-<p>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 20011101
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-
-<ul>
-<li>
-introduction of setDocumentContent(IDocument, IEditorInput) on StorageDocumentProvider.</li>
-
-<li>
-introduction of IDocumentExtension (see JavaDoc)</li>
-
-<li>
-AbstractDocument implements IDocumentExtension</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-Instances of DefaultInformationControl are wider than necessary.
-<h2>
-Problem reports fixed</h2>
-
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 206
-<h2>
-Breaking API changes</h2>
-Corrected spelling of&nbsp; "anchor" in AbstractInformationControlManager
-and its subclasses.
-<h2>
-Other highlights</h2>
-
-<h2>
-Known deficiencies</h2>
-Instances of DefaultInformationControl are wider than necessary.
-<h2>
-Problem reports fixed</h2>
-<a href="http://dev.eclipse.org/bugs/show_bug.cgi?id=5066">#5066&nbsp;&nbsp;&nbsp;
-Code Assist: Thread created / not removed</a>
-<br><a href="http://dev.eclipse.org/bugs/show_bug.cgi?id=5120">#5120&nbsp;&nbsp;&nbsp;
-Empty popup doc in java editor</a>
-<br><a href="http://dev.eclipse.org/bugs/show_bug.cgi?id=3473">#3473&nbsp;&nbsp;
-mnemonics (1GF25DN)</a>
-<p>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 204
-<h2>
-Breaking API changes</h2>
-
-<h2>
-Other highlights</h2>
-For more information about the following issue please see JavaDoc of the
-classes
-<ul>
-<li>
-Several improvements of the new hover infrastructure, such as customizable
-SWT styles.</li>
-
-<li>
-Improved look of the content assist window.</li>
-
-<li>
-Content assist supports customizable completion characters, i.e. each completion
-proposal can specify which characters trigger its insertion.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-Instances of DefaultInformationControl are wider than necessary.
-<h2>
-Problem reports fixed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>Eclipse SDK Build 203
-<h2>
-Breaking API changes</h2>
-&nbsp; package:&nbsp;&nbsp; org.eclipse.jface.text
-<br>&nbsp; interface:&nbsp;&nbsp; IHoverInfoPresenter
-<br>&nbsp; change:&nbsp;&nbsp; removed interface
-<br>&nbsp; change type: breaking API change for implementers of IHoverInfoPresenter
-<h2>
-Other highlights</h2>
-For more information about the following issue please see JavaDoc of the
-classes
-<ul>
-<li>
-Complete rework of hover popups (previously a package private mechanism
-hidden from clients). There is now the concept of an IInformationControl
-and an IInformationControlCreator. Everywhere where floating windows are
-used to present some kind of information, now IInformationControl is used.
-More precise, the according component is equiped with an IInformationControlCreator
-and creates the IInformationControl instance when needed. So clients can
-set an IInformationControlCreator on a TextViewer and a SourceViewer. They&nbsp;
-use it&nbsp; to create the text hover window and the annotation bar hover
-window respectively. DefaultInformationControl&nbsp; is a StyledText-based
-default implementation of IInformationControl. Clients may implement IInformationControl
-directly and inject their custom information control creator.</li>
-
-<li>
-AbstractInformationControlManager and its subclasses abstractly&nbsp; implement
-the process of providing a SWT control with support for floating information
-windows. This covers layout, positioning, content, and visibility of the
-floating window. They offer a broad customization space such as layout
-strategies, colors, etc.</li>
-
-<li>
-TextViewer hovers, annotation bar hovers, additional info on completion
-proposals in the content assistant, etc. benefit from the new infrastructure.
-UI improvements are especially visible in the layout behavior.</li>
-
-<li>
-Introduced the concept of an information presenter. An information presenter
-shows information on a context derivved subject on request. See IInformationPresenter
-for details as well as SourceViewer and SourceViewerConfiguration for how
-to use it.</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-Instances of DefaultInformationControl are wider than necessary.
-<h2>
-Problem reports fixed</h2>
-
-<p><br>
-<hr WIDTH="100%">
-<p>Eclipse SDK Build 200
-<h2>
-Breaking API changes</h2>
-&nbsp; package:&nbsp;&nbsp; org.eclipse.jface.text
-<br>&nbsp; interface:&nbsp;&nbsp; ITextViewer
-<br>&nbsp; change:&nbsp;&nbsp; added method public void invalidateTextPresentation(
-)
-<br>&nbsp; change type: breaking API change for implementers of ITextViewer
-<p>&nbsp; package:&nbsp;&nbsp; org.eclipse.jface.text
-<br>&nbsp; interface:&nbsp;&nbsp; ITextViewer
-<br>&nbsp; change:&nbsp;&nbsp; added method public void setDefaultPrefixes(String[]
-defaultPrefixes, String contentType)
-<br>&nbsp; change type: breaking API change for implementers of ITextViewer
-<p>&nbsp; package:&nbsp;&nbsp; org.eclipse.jface.text
-<br>&nbsp; interface:&nbsp;&nbsp; ITextViewer
-<br>&nbsp; change:&nbsp;&nbsp; removed method&nbsp; void setDefaultPrefix(String
-defaultPrefix, String contentType)
-<br>&nbsp; change type: breaking API change for implementers of ITextViewer
-<p>&nbsp; package:&nbsp;&nbsp; org.eclipse.jface.text.rules
-<br>&nbsp; class:&nbsp;&nbsp; RuleBasedDamagerRepairer
-<br>&nbsp; change:&nbsp;&nbsp; deprecated constructor&nbsp; public RuleBasedDamagerRepairer(RuleBasedScanner
-scanner, TextAttribute defaultTextAttribute)
-<br>&nbsp; change type: breaking API change for clients of RuleBasedDamagerRepairer
-<h2>
-Other highlights</h2>
-For more information about the following issue please see JavaDoc of the
-classes
-<ul>
-<li>
-IContextInformationValidator implementers may also implement IContextInformationPresenter
-to style context information</li>
-
-<li>
-ITextHover implementers may also implement IHoverInfoPresenter to style
-hover information</li>
-
-<li>
-PropagatingFontFieldEditor has been introduced</li>
-
-<li>
-MonoReconciler has been introduced to support partition independent reconciling</li>
-
-<li>
-Token has been reimplemented, supports setData method now</li>
-
-<li>
-RuleBasedScanner now supports&nbsp; public void setDefaultReturnToken(IToken
-defaultReturnToken). This token is returned if no rule can fire.</li>
-
-<li>
-TextPresentation now supports&nbsp; public static void applyTextPresentation(TextPresentation
-presentation, StyledText text)</li>
-
-<li>
-BasicMarkerUpdater has been marked as final</li>
-
-<li>
-SelectMarkerRulerAction has been introduced</li>
-
-<li>
-WorkbenchChainedTextFontFieldEditor has been introduced</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<h2>
-Problem reports fixed</h2>
-1GJ65EW: ITPSRCEDIT:WINNT - ResourceMarkerAnnotaionModel: unnecessary fireModelChange
-<br>1GIYR3X: ITPSRCEDIT:ALL - NL: word select (double click) in Java comments
-<br>1GGYYWK: ITPJUI:ALL - Dismissing editor with code assist up causes
-lots of Internal Errors
-<br>1GEUOZ9: ITPJUI:ALL - Confusing UI for multiline Bookmarks and Tasks
-<br>1GII2RZ: ITPJUI:WINNT - AssertionFailed Ex. in Java editor
-<br>1GIYQ9K: ITPUI:WINNT - StyledText swallows Shift+TAB
-<br>1GIJZOO: ITPSRCEDIT:ALL - Gotodialog's edit field has no initial focus
-
-</body>
-</html>
diff --git a/org.eclipse.ui.editors/_buildnotes_text_2_1.html b/org.eclipse.ui.editors/_buildnotes_text_2_1.html
deleted file mode 100644
index f4e50d398..000000000
--- a/org.eclipse.ui.editors/_buildnotes_text_2_1.html
+++ /dev/null
@@ -1,267 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
- <meta name="Author" content="IBM">
- <title>Eclipse Platform Release Notes - Desktop</title>
-</head>
-<body>
-
-<h1>
-Eclipse Platform Build Notes</h1>
-
-<h1>
-Platform Text</h1>
-
-<p><br>Eclipse SDK Build 20030205
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-Added new layout anchor option "GLOBAL" to the AbstractInformationControlManager.
-Information controls that are opened using this anchor are placed in the
-middle of the subject control.</li>
-
-<li>
-Changed all internal usages of SWT defined modifiers to the generic modifiers
-MOD?</li>
-
-<li>
-Moved "Go to Line" action into the Navigate menu</li>
-
-<li>
-The default text editor now supports:</li>
-
-<ul>
-<li>
-line numbers</li>
-
-<li>
-cursor line highlighting</li>
-
-<li>
-overview ruler</li>
-
-<li>
-error annotations</li>
-</ul>
-
-<li>
-The overview ruler can now be configured to show an header. The header
-shows the presence of annotations of a certain type.</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-<hr>
-<p>Eclipse SDK Build 20030128
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-Introduced painter infrastructure at text viewer level. The following predefined
-painters are available:</li>
-
-<ul>
-<li>
-AnnotationPainter</li>
-
-<ul>
-<li>
-represents annotations given in the viewer's annotation model as squiggly
-lines in the text widget</li>
-
-<li>
-can be configured along annotation types and colors</li>
-</ul>
-
-<li>
-CursorLinePainter</li>
-
-<ul>
-<li>
-highlights the background of the current line (i.e. the line in which the
-cursor resides)</li>
-
-<li>
-color can be configured</li>
-</ul>
-
-<li>
-MargingPainter</li>
-
-<ul>
-<li>
-draws a vertical line at a certain column</li>
-
-<li>
-color and column can be configured</li>
-</ul>
-
-<li>
-MatchingCharacterPainter</li>
-
-<ul>
-<li>
-highlights the character matching the character close to the current cursor
-position by drawing a bounding box around the character</li>
-
-<li>
-must be configured with a strategy for finding the matching character (ICharacterPairMatcher)</li>
-
-<li>
-color can be configured</li>
-</ul>
-</ul>
-
-<li>
-Painters can dynamically be attached to a source viewer. API is defined
-in&nbsp; the interface ITextViewerExtension2. The TextViewer manages its
-painters using a PaintManager.</li>
-
-<li>
-Introduced the concept of an overview ruler at the source viewer level.
-The API is defined in the interface ISourceViewerExtension.</li>
-
-<li>
-Introduced a helper class SourceViewerDecorationSupport at the text editor
-framework that can be used by editors to manage and configure painters.
-This includes the initialization of painters from preferences and the reaction
-on preference changes.</li>
-
-<li>
-Changed validateEdit behavior for&nbsp; the find/replace case. validateEdit
-is now called directly in front of the first text replace operation.</li>
-
-<li>
-Global action definition ids have been introduced for computing content
-completion proposals and computing content context information.</li>
-
-<li>
-ITextViewerExtension2 now offers API to remove all registered text hovers
-for a given content type</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-<h1>
-
-<hr></h1>
-Eclipse SDK Build 20030107
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-New attribute&nbsp;<span style="font-weight: bold;">symbolicFontName</span>
-has been added to <tt>org.eclipse.ui.editors</tt> extension point. See
-the extension point documentation for more details. If the attribute is
-provided then the text editors use it as primary source for setting the
-text editor font.</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-<hr>
-<h1>
-Eclipse Platform Build Notes</h1>
-
-<h1>
-Platform Text</h1>
-Eclipse SDK Build 20021203
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-Introduced goto to last edit position</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-<hr>
-<p>Eclipse SDK Build 20021008
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-Introduced smart behavior for Home/End key</li>
-
-<li>
-Infrastructure for eating code assist including visual indication of text
-to be replaced</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-<hr>
-<p>Eclipse SDK Build 20021001
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-Applied patch for incremental search to behave more like Emacs</li>
-
-<li>
-Applied patch for delete line to copy to clipboard (Emacs behaviour)</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-<hr>
-<p>Eclipse SDK Build 20020903
-<h2>
-What's new</h2>
-
-<ul>
-<li>
-Adaptable line number ruler width</li>
-
-<li>
-Resizable content assist proposal popup</li>
-
-<li>
-Pre 2.0 build notes have been moved to buildnotes_text_2_0.html</li>
-</ul>
-
-<h2>
-Known deficiencies</h2>
-
-<ul>
-<li>
-Size of content assist proposal popup is not persisted over session boundaries</li>
-
-<li>
-Size of content assist proposal popup is not editor type specific</li>
-</ul>
-
-<h2>
-Problem reports closed</h2>
-
-<blockquote>See bugzilla.</blockquote>
-
-</body>
-</html>
diff --git a/org.eclipse.ui.editors/_buildnotes_text_3.2.html b/org.eclipse.ui.editors/_buildnotes_text_3.2.html
deleted file mode 100644
index 8ce776925..000000000
--- a/org.eclipse.ui.editors/_buildnotes_text_3.2.html
+++ /dev/null
@@ -1,132 +0,0 @@
-<!--
- DO NOT EDIT THIS FILE WITH HTML EDITORS
--->
-
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
- <title>Eclipse Platform Build Notes - Text</title>
-</head>
-
-<body>
-<h1>
-Eclipse Platform Build Notes<br>
-Text</h1>
-To see which bugs have been addressed in one of the builds simply open the <a href="http://bugs.eclipse.org/bugs/query.cgi?short_desc_type=allwordssubstr&amp;product=Platform&amp;component=Text&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;namedcmd=Assigned&amp;newqueryname=&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform-Text bugzilla query page</a>, select status, resolution and the time frame.
-<br>
-<br>
-========== Eclipse Build Input February 7th 2006 ==========<br>
-<pre>
-- added selectionChanged event to ICompletionListener
-- added start/stopListeningForPreferenceChanges to TemplateStore to enable automatic preference store listening
-- bug fixing
-</pre>
-<br>
-<br>
-========== Eclipse Build Input January 17th 2006 ==========<br>
-<pre>
-- deprecated TextViewer::getVisibleLinesInViewport as it won't work with variable line heights
-- bug fixing
-</pre>
-<br>
-<br>
-========== Eclipse Build Input January 10th 2006 ==========<br>
-<pre>
-- Move of the content assist API additions from the various text plug-ins to jdt.ui:
- - reason:
- - the collection-based API of ICompletionProposalComputer has no future in the RCP part of eclipse.
- - it is only currently used in jdt to allow contributions to the Java editor's content assistant
- - removed the unused ContentAssistInvocationContext
- - moved TextContentAssistInvocationContext to jdt.ui
- - moved ICompletionProposalComputer to IJavaCompletionProposalComputer in the jdt.ui plug-in.
- - changed HippieProposalComputer to HippieProposalProcessor, now implementing IContentAssistProcessor instead of ICompletionProposalComputer
-
-- Changes in document setup and creation:
- 1) the extension point 'org.eclipse.core.filebuffers.documentCreation' is now
- deprecated and urges clients to get rid of it along with hints how to do this
- 2) along with 1) 'org.eclipse.core.filebuffers.IDocumentFactory' is deprecated
- 3) the file buffer manager now provides an 'org.eclipse.jface.text.ISynchronizable'
- document. Clients which need a synchronized document can set a lock object.
- Note: To overwrite an existing lock object is considered bad practice and can
- break other clients: if the document already has a lock object set then
- this one should be used by the client.
- 4) a warning is now written to the .log file if a document setup participant
- sets the default partitioner and the extension point documentation has been
- clarified.
- 5) all PartiallySynchronizedDocument implementations can be removed
-
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input December 12th 2005 ==========<br>
-<pre>
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input December 6th 2005 ==========<br>
-<pre>
-- converted code to support the new mutli-font in StyledText widget:
- - getBaseline() ==> getBaseline(int)
- - getLineHeight() ==> getLineHeight(int)
- open issues:
- - waiting for additional StyledText API (https://bugs.eclipse.org/bugs/show_bug.cgi?id=118670)
- - we do not yet handle the case where the line number ruler font is bigger than the biggest line font (https://bugs.eclipse.org/bugs/show_bug.cgi?id=119232)
- - incorrectly painting of projection summary end [..] (https://bugs.eclipse.org/bugs/show_bug.cgi?id=119235)
- - problems with custom image and special sized carets (https://bugs.eclipse.org/bugs/show_bug.cgi?id=118612)
- - StyledText computes the line base too high (https://bugs.eclipse.org/bugs/show_bug.cgi?id=119233)
- - if multi-font is used performance is going down, e.g. when opening or scrolling large files like StyledText
- - [api] Add new API to support memory efficient StyleRange support in StyledText (https://bugs.eclipse.org/bugs/show_bug.cgi?id=119384)
-
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input November 22nd 2005 ==========<br>
-<pre>
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input October 11th 2005 ==========<br>
-<pre>
-- adopted new Eclipse FS (details see https://bugs.eclipse.org/bugs/show_bug.cgi?id=106176)
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input September 13th 2005 ==========<br>
-<pre>
-- pushed down annotation navigation to JFace Text and added annotation
- navigation to all text editors
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input September 6th 2005 ==========<br>
-<pre>
-- pushed down annotation hovering to JFace Text and added text, vertical and
- overview ruler hover support to TextSourceViewerConfiguration which makes this
- available to all clients using this configuration
-- removed object contributions from vertical ruler menu
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input August 30th 2005 ==========<br>
-<pre>
-- hyperlink navigation is now also available if editor does not have focus
-- bug fixing
-</pre>
-<br>
-========== Eclipse Build Input August 16th 2005 ==========<br>
-<pre>
-- Esc on code assist popup no longer closes shell
-- clarified how to translate template file translations
-</pre>
-<br>
-========== Eclipse Build Input August 9th 2005 ==========<br>
-<pre>
-- bug fixing
-</pre>
-<br>
-<br>
-</body>
-</html> \ No newline at end of file
diff --git a/org.eclipse.ui.editors/_buildnotes_text_3.3.html b/org.eclipse.ui.editors/_buildnotes_text_3.3.html
deleted file mode 100644
index c6f8893ae..000000000
--- a/org.eclipse.ui.editors/_buildnotes_text_3.3.html
+++ /dev/null
@@ -1,114 +0,0 @@
-<!--
- DO NOT EDIT THIS FILE WITH HTML EDITORS
--->
-
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
- <title>Eclipse Platform Text Build Notes</title>
-</head>
-
-<body>
-<h1>Eclipse Platform Text Build Notes</h1>
-To see which bugs have been addressed in one of the builds simply open the <a href="http://bugs.eclipse.org/bugs/query.cgi?short_desc_type=allwordssubstr&amp;product=Platform&amp;component=Text&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;namedcmd=Assigned&amp;newqueryname=&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform-Text bugzilla query page</a>, select status, resolution and the time frame.
-<br>
-<br>
-========== Eclipse Build Input November 21th 2006 ==========<br>
-<pre>
-- added spell checking support to text editor
-- editor implementors that want to add spell checking can use the new SpellingCorrectionProcessor and the SpellingReconcileStrategy
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input November 14th 2006 ==========<br>
-<pre>
-- improved annotation painting performance in overview ruler and text area
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input October 10th 2006 ==========<br>
-<pre>
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input September 18th 2006 ==========<br>
-<pre>
-- renamed AbstractRulerColumn to AbstractContributedRulerColumn
-- refactored RulerColumn to no longer extend AbstractContributedRulerColumn and moved it down to JFace Text as AbstractRulerColumn
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input August 29th 2006 ==========<br>
-<pre>
-- bug fixing
-- added default character pair matcher
-- added support to use the FindReplaceAction with shells
-</pre
-<br>
-<br>
-========== Eclipse Build August 8th 2006 (3.3 M1) ==========<br>
-<pre>
-- Implementation of <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=25793">request 25793</a>:
- - Introduced the org.eclipse.ui.workbench.texteditor.rulerColumn extension point. It allows to contribute
- vertical ruler columns to any text editor.
- - Two standard ruler columns used in the Eclipse Text and Java editors have been converted to use
- the new extension point: Line numbers (including quick diff and revision information) and the annotation ruler column.
- - deprecated AbstractDecoratedTextEditor.createChangeRulerColumn()
- While implementing <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=25793">request 25793</a>, we replaced
- the line number and quick diff rulers by one single contribution to the new rulerColumns extension point. Replacing
- createChangeRulerColumn never made any sense, as the a private field in AbstractDecoratedTextEditor got assigned as a
- side effect of calling that method. Replacing the method would have removed the support for quick diff. Implementations
- interested in supplying a custom line number column can still override AbstractDecoratedTextEditor.createLineNumberRulerColumn(), which
- continues to be supported.
- - introduced org.eclipse.jface.text.source.ILineDifferExtension2 that allows to query a line differ for its suspension state
- - introduced predicates to LineNumberChangeRulerColumn that allow clients to test whether it displays line numbers, quick diff information, or revision
- information, or a combination thereof.
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input July 18th 2006 ==========<br>
-<pre>
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input July 4th 2006 ==========<br>
-<pre>
-- bug fixing
-</pre
-<br>
-<br>
-========== Eclipse Build Input June 20th 2006 ==========<br>
-<pre>
-- bug fixing
-- AbstractInformationControlManager#computeInformationControlLocation will no longer use the
- lowest priority anchor in the case that the proposed information control size does not fit
- with any of the anchors. Instead, it uses AbstractInformationControlManager#computeAvailableArea
- to see which anchor offers the largest intersection with the proposed control size. In addition,
- the control size and location are adjusted such that the information control does not overlap
- with the subject area (unless the anchor is ANCHOR_GLOBAL) and does not bleed over the monitor edges.
-</pre>
-<br>
-<br>
-========== Eclipse Build Input June 13th 2006 ==========<br>
-<pre>
-- bug fixing
-- rewrite of GapTextStore which improves random replace operations as less re-allocations
- occur. This allows to deprecate SequentialRewriteTextStore as its performance is not better than
- the new GapTextStore. Users of SequentialRewriteTextStore should simply use GapTextStore instead; consequently,
- the default IDocument implementation (Document) no longer does text store switching
- when a sequential rewrite session starts or ends. Also, the existing constructor of GapTextStore has
- been deprecated.
-</pre>
-<br>
-<br>
-</body>
-</html> \ No newline at end of file
diff --git a/org.eclipse.ui.editors/_buildnotes_text_3_0.html b/org.eclipse.ui.editors/_buildnotes_text_3_0.html
deleted file mode 100644
index a403ed00b..000000000
--- a/org.eclipse.ui.editors/_buildnotes_text_3_0.html
+++ /dev/null
@@ -1,707 +0,0 @@
-<!--
- DO NOT EDIT THIS FILE WITH HTML EDITORS
--->
-
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
- <title>Eclipse Platform Build Notes - Text</title>
-</head>
-
-<body>
-<h1>
-Eclipse Platform Build Notes<br>
-Text</h1>
-To see which bugs have been addressed in one of the builds simply open the <a href="http://bugs.eclipse.org/bugs/query.cgi?short_desc_type=allwordssubstr&amp;product=Platform&amp;component=Text&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;namedcmd=Assigned&amp;newqueryname=&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform-Text bugzilla query page</a>, select status, resolution and the time frame.
-<br>
-<br>
-<br>
-========== Eclipse Build Input May 18th 2004 ==========<br>
-<pre>
-- removed last dependency on compatibility plug-in
-- bug fixing
-
-The infrastructure for collapsing and expanding ranges of lines in editors (referred to as folding)
-is now officially available. The effected plug-ins are org.eclipse.text and org.eclipse.jface.text.
-
-The org.eclipse.text plug-in contains the package org.eclipse.jface.text.projection. This package
-defines the UI independent document infrastructure needed for folding. The center piece is the
-ProjectionDocument. The content of a projection document is a projection of the content of a master
-document. In other words fragments of the master document constitute the segments of the projection
-document. The mapping is enacted by the ProjectionMapping implementing IDocumentInformationMapping.
-After an instance of ProjectionDocument has been created it is initially empty. The content is defined
-by calling addMasterDocumentRange(offsetInMasterDocument, lengthInMasterDocument) and
-removeMasterDocumentRange(offsetInMasterDocument, lengthInMasterDocument). The projection document
-and its master document are causally connected. Thus, any manipulation of the projection document also
-causes master document changes. Any manipulation effecting ranges in the master document that have been
-added to the projection document also cause projection document changes.
-
-The org.eclipse.jface.text plug-in contains the package org.eclipse.jface.text.source.projection.
-This package defines the UI needed for folding based on the projection document infrastructure. The
-center piece is the ProjectionViewer and the ProjectionSupport. A projection support can be installed on
-projection viewer. It controls the existence of a vertical ruler column for collapsing/expanding ranges
-of lines, the hover behavior, and the presentation of collapsed regions in the viewer. The projection viewer
-defines a set of text operations for managing the expansion state of collapsable regions. Collapsable regions
-can be defined by requesting the ProjectionSupport to provide an adapter for ProjectionAnnotationModel.class
-for the viewer it is installed on. The ProjectionAnnotations managed by this projection annotation model
-define the collapsable regions.
-
-ITextViewer defines the concept of a visible region. This concepts is incompatible with folding. Several
-assumptions that were safe to make in the world of visible regions are no longer valid in the presence of folding.
-For example, in order to determine the document line number of the fifth line in the viewer's widget it was
-good enough to determine the start line of the viewer's visible region and to take the fifth line after that.
-When folding is enabled, any number of lines can be between two visible lines. Thus, in order to convert between
-widget and model coordinates, the methods provided by ITextViewerExtension5 should be used.
-
-Editor implementers (based on AbstractTextEditor) who want to support folding have to do the following:
-- override createSourceViewer and return a ProjectionViewer
-- override createPartControl resembling:
-
- public void createPartControl(Composite parent) {
- super.createPartControl(parent);
-
- ProjectionViewer projectionViewer= (ProjectionViewer) getSourceViewer();
-
- fProjectionSupport= new ProjectionSupport(projectionViewer, getAnnotationAccess(), getSharedColors());
- fProjectionSupport.addSummarizableAnnotationType("org.eclipse.ui.workbench.texteditor.error");
- fProjectionSupport.addSummarizableAnnotationType("org.eclipse.ui.workbench.texteditor.warning");
- fProjectionSupport.setHoverControlCreator(new IInformationControlCreator() {
- public IInformationControl createInformationControl(Shell shell) {
- return new CustomSourceInformationControl(shell, IDocument.DEFAULT_CONTENT_TYPE);
- }
- });
- fProjectionSupport.install();
-
- ...
-
- if (isFoldingEnabled())
- projectionViewer.doOperation(ProjectionViewer.TOOGLE);
- }
-
-- extend getAdapter with
-
- public Object getAdapter(Class required) {
- ...
- if (fProjectionSupport != null) {
- Object adapter= fProjectionSupport.getAdapter(getSourceViewer(), required);
- if (adapter != null)
- return adapter;
- }
-
- return super.getAdapter(required);
- }
-
-- provide a way to allow the definition of collpsable regions such as:
-
- ITextEditor editor= getTextEditor();
- ISelection selection= editor.getSelectionProvider().getSelection();
- if (selection instanceof ITextSelection) {
- ITextSelection textSelection= (ITextSelection) selection;
- if (!textSelection.isEmpty()) {
- IAnnotationModel model= (IAnnotationModel) editor.getAdapter(ProjectionAnnotationModel.class);
- if (model != null) {
- int start= textSelection.getStartLine();
- int end= textSelection.getEndLine();
- try {
- IDocument document= editor.getDocumentProvider().getDocument(editor.getEditorInput());
- int offset= document.getLineOffset(start);
- int endOffset= document.getLineOffset(end + 1);
- Position position= new Position(offset, endOffset - offset);
- model.addAnnotation(new ProjectionAnnotation(), position);
- } catch (BadLocationException x) {
- }
- }
- }
- }
-
-</pre>
-========== Eclipse Build Input May 11th 2004 ==========<br>
-<pre>
-- reworked editor preference pages:
- - Annotations and Quick Diff sub-pages are gone: they are now centralized under
- Workbench > Editors
- - added API which allows to configure a client's preference store to use the
- centralized preference pages:
- see: EditorsUI.useAnnotationsPreferencePage(IPreferenceStore)
- see: EditorsUI.useQuickDiffPreferencePage(IPreferenceStore)
- - added ChainedPreferenceStore which allows to chain preference stores
- - the text editor's Appearance sub-page is now the only Text Editor's preference page
-- removed all but one dependencies on compatibility plug-in
-- externalized all strings
-- bug fixing
-</pre>
-========== Eclipse Build Input May 4th 2004 ==========<br>
-<pre>
-- ICompletionProposalExtension3: renamed methods:
- - getCompletionText -> getPrefixCompletionText
- - getCompletionOffset -> getPrefixCompletionOffset
-
-
-Headless annotation model support for text file buffers:
-
-We added headless annotation model support to text file buffers. Each text
-file buffer can now have its own annotation model.
- ITextFileBuffer buffer= FileBuffers.getTextFileBufferManager().getTextFileBuffer(<location>);
- IAnnotationModel model= buffer.getAnnotationModel();
-When the buffer's document is changed, all annotations in the buffer's annotation
-model are accordingly updated.
-
-As annotations (org.eclipse.jface.text.source.Annotation) had dependencies on
-SWT the following changes have been applied. These changes might break existing 3.0 clients.
-The changes in detail:
-- ImageUtilities has been moved from org.eclipse.ui.texteditors to org.eclipse.jface.text.source
-- removed static Annotation.drawImage methods -> use org.eclipse.jface.text.source.ImageUtilities
-- removed setLayer, getLayer, and paint from Annotation -> annotations which want to draw
- themselves should implement IAnnotationPresentation (as has been introduced by Dec. 18th)
-- MarkerAnnotation now directly implements the methods removed from Annotation (setLayer, getLayer, paint)
-- MarkerAnnotation extends SimpleMarkerAnnotation, SimpleMarkerAnnotation just provides
- access to the represented IMarker
-- the following classes have been moved from the plug-in org.eclipse.jface.text to the plug-in
- org.eclipse.text, the package names remain the same
- org.eclipse.jface.text.ISynchronizable
- org.eclipse.jface.text.source.Annotation
- org.eclipse.jface.text.source.AnnotationMap
- org.eclipse.jface.text.source.AnnotationModel
- org.eclipse.jface.text.source.AnnotationModelEvent
- org.eclipse.jface.text.source.IAnnotationMap
- org.eclipse.jface.text.source.IAnnotationModel
- org.eclipse.jface.text.source.IAnnotationModelExtension
- org.eclipse.jface.text.source.IAnnotationModelListener
- org.eclipse.jface.text.source.IAnnotationModelListenerExtension
-
-The following changes were made to add headless annotation model support to filebuffers.
- - added ITextFileBuffer.getAnnotationModel(IPath)
- - added ITextFileBufferManager.createAnnotationModel(IPath)
- - introduced IPersistableAnnotationModel give annotations model a sense of a life cycle
- - added new extension point org.eclipse.core.filebuffers.annotationModelCreation for
- registering factories for file buffer annotation models
- - introduced IAnnotationModelFactory to reify the contract for the extension point
- - changed TextFileDocumentProvider to take the text file buffer annotation models into
- account. This is only the case when a subclass does override
- TextFileDocumentProvider.createAnnotationModel
-
-Theses changes affect the following plug-ins:
- org.eclipse.core.filebuffers
- org.eclipse.jface.text
- org.eclipse.text
- org.eclipse.ui.editors
-
-</pre>
-<br>
-========== Eclipse Build Input April 27th 2004 ==========<br>
-<pre>
-- Added org.eclipse.ui.contentassist.ContentAssistHandler which can
- be used to install and control enablement of the visual cue and the
- key binding for subject control content assistants.
-</pre>
-<br>
-========== Eclipse Build Input April 20th 2004 ==========<br>
-<pre>
-Open / closed partitions:
-From IDocumentPartitionerExtension2:
-This extension introduces the concept of open and closed (or delimited)
-partitions. A delimited partition has a textual token delimiting its start
-and end, while an open partition can fill any space between two delimited
-partitions.
-An open partition of zero length can occur between two delimited partitions,
-thus having the same offset as the following delimited partition. The
-document start and end are considered to be delimiters of open partitions,
-i.e. there may be a zero-length partition between the document start and a
-closed partition starting at offset 0.
-
-The partition information queries on IDocumentPartitionerExtension2 carry a
-boolean argument that specifies whether such open partitions should be returned.
-
------
-
-API changes:
-
-plug-in: org.eclipse.text
-
-- pkg: org.eclipse.jface.text
- - renamed FindReplaceDocumentAdapter.search to FindReplaceDocumentAdapter.find
- - changed FindReplaceDocumentAdapter.findReplace to private
- - merged FindReplaceOperationCode into FindReplaceDocumentAdapter, removed FindReplaceOperationCode
- - deleted deprecated classes whose Javadoc stated that these classes were internal
- - ChildDocument
- - ChildDocumentManager
- - ParentChildMapping
- - CoordinatesTranslator
- - Fragment
- - FragmentUpdater
- - ProjectionDocument
- - ProjectionDocumentManager
- - ProjectionPosition
- - ProjectionPositionUpdater
- - ProjectionTextStore
-
-- pkg: org.eclipse.jface.text.link
- - removed ExclusivePositionUpdater
- - marked InclusivePositionUpdater as internal class using Javadoc
- - renamed LinkedEnvironment to LinkedModeModel
- - renamed methods accordingly
- - renamed LinkedManager to LinkedModeManager
- - renamed ILinkedListener to ILinkedModeListener
- - renamed LinkedUIControl to LinkedModeUI
- - removed LinkedPositionGroup.createPosition methods
- - use LinkedPositionGroup.addPosition instead
-
-- pkg: org.eclipse.jface.text.templates
- - renamed ContextType to TemplateContextType
- - renamed GlobalVariables to GlobalTemplateVariables
- - renamed SimpleVariableResolver to SimpleTemplateVariableResolver
-
-
-----------------------------------------
-
-plug-in org.eclipse.jface.text
-
-- pkg: org.eclipse.jface.text
- - renamed IAnnotationHoverExtension.getInformationControlCreator to IAnnotationHoverExtension.getHoverControlCreator
- - renamed ITextHoverExtension.getInformationControlCreator to ITextHoverExtension.getHoverControlCreator
-
-- pkg: org.eclipse.jface.text.formatter
- - merged IContentFormatterExtension2 into IContentFormatterExtension
- - removed IContentFormatterExtension.getPartitioning
- - changed configuration methods of MultipassContentFormatter: substituted IFormattingStrategy for IFormattingStrategyExtension, added assert statements
- - deprecated ContentFormatter
-
-- pkg: org.eclipse.jface.text.source
- - deleted deprecated classes whose Javadoc stated that these classes were internal
- - OutlinerRulerColumn
- - ProjectionAnnotation
- - ProjectionSourceViewer
-
-- pkg: org.eclipse.jface.text.reconciler
- - deleted DocumentAdapter
- - renamed AnnotationEvent to VerticalRulerEvent
- - renamed VerticalRulerEvent.getAnnotation to VerticalRulerEvent.getSelectedAnnotation
- - renamed VerticalRulerEvent.setAnnotation to VerticalRulerEvent.setSelectedAnnotation
- - CompositeRuler no longer implements IVerticalRulerListener
- - renamed CompositeRuler.annotationSelected to CompositeRuler.fireAnnotationSelected
- - renamed CompositeRuler.annotationDefaultSelected to CompositeRuler.fireAnnotationDefaultSelected
- - renamed CompositeRuler.annotationContextMenuAboutToShow to CompositeRuler.fireAnnotationContextMenuAboutToShow
- - changed constructor of AnnotationExpandHover to accept CompositeRuler rather than IVerticalRulerInfo and IVerticalRulerListener
-
-- pkg: org.eclipse.jface.text.contentassist
- - moved AbstractControlContentAssistSubjectAdapter to package org.eclipse.jface.contentassist
- - moved ComboContentAssistSubjectAdapter to package org.eclipse.jface.contentassist
- - moved ContentAssistant to package org.eclipse.jface.contentassist
- - moved IContentAssistProcessorExtension to package org.eclipse.jface.contentassist
- - renamed IContentAssistProcessorExtension to ISubjectControlContentAssistProcessor.java
- - moved IContentAssistSubject to package org.eclipse.jface.contentassist
- - renamed to IContentAssistSubject IContentAssistSubjectControl
- - moved IContextInformationPresenterExtension to package org.eclipse.jface.contentassist
- - renamed IContextInformationPresenterExtension to ISubjectControlContextInformationPresenter
- - moved IContextInformationValidatorExtension to package org.eclipse.jface.contentassist
- - renamed IContextInformationValidatorExtension to ISubjectControlContextInformationValidator
- - moved TextContentAssistSubjectAdapter to package org.eclipse.jface.contentassist
- - added ISubjectControlContentAssistant to package org.eclipse.jface.contentassist
- - moved IContentAssistantExtension.install(IContentAssistSubjectControl) to ISubjectControlContentAssistant
- - added SubjectControlContentAssistant to package org.eclipse.jface.contentassist
- - added SubjectControlContextInformationValidator to package org.eclipse.jface.contentassist
-
------------------------------------------------
-
-plug-in org.eclipse.ui.workbench.texteditor
-
-- pkg: org.eclipse.ui.texteditor.templates
- - changed EditTemplateDialog to package visible
- - changed TemplateContentProvider to package visible
-
-- org.eclipse.ui.texteditor
- - removed ChainedPreferenceStore (there is a copy in JDT UI)
- - removed PreferencesAdapter (there is copy in JDT UI)
- - deprecated InfoForm
- - renamed SelectMarkerRulerAction2 to SelectAnnotationRulerAction
- - renamed SmartEnterAction to InsertLineAction
-
-- org.eclipse.ui.texteditor.link
- - removed EditorTarget
- - replaced EditorHistoryUpdater with EditorLinkedModeUI
- - clients no longer configure a LinkedModeUI with the EditorHistoryUpdater but instantiate EditorLinedModeUI
-
--------------------------------------------------
-
-plug-in org.eclipse.ui.editors
-
-- pkg: org.eclipse.ui.texteditor
- - moved AnnotationType to package org.eclipse.ui.internal.texteditor
- - moved AnnotationTypeHierarchy to package org.eclipse.ui.internal.texteditor
- - moved DelegatingAnnotationPreference to package org.eclipse.ui.internal.texteditor
- - marked AnnotationPreferenceLookup.getAnnotationPreferenceFragment as internal method using Javadoc
- - renamed ExtendedTextEditor to AbstractDecoratedTextEditor
- - renamed ExtendedTextEditorPreferenceConstants to AbstractDecoratedTextEditorPreferenceConstants
-
-- pkg: org.eclipse.ui.editors.text
- - removed EditorUI.getAnnotationTypeHierarchy
- - moved WorkspaceOperationRunner to package org.eclipse.ui.internal.editors.text
- - moved UISynchronizationContext to package org.eclipse.ui.internal.editors.text
-
-
---------------------------------------------------
-
-plug-in org.eclipse.core.filebuffers
-- extension point org.eclipse.core.filebuffers.documentSetup now supports the attribute 'fileNames'. The union of
- 'fileNames' and 'extensions' is used for setting up a document.
-- extension point org.eclipse.core.filebuffers.documentCreation now supports the attribute 'fileNames'.
- 'fileName' has precedence over any matching criterion of 'extensions' when creating a document.
-
-
-</pre>
-========== Eclipse Build Input March 23rd 2004 ==========<br>
-<pre>
-- Added the <tt>org.eclipse.ui.editors.templates</tt> extension point to the templates infrastructure.
-- Added an example of using the extension point to the <tt>org.eclipse.ui.examples.javaeditor</tt>
- project, see the <tt>Template Editor Example</tt> source folder and the html description for reference.
-</pre>
-========== Eclipse Build Input March 9th 2004 ==========<br>
-<pre>
-- Moved the templates infrastructure to the text, jface.text and ui.workbench.texteditor
- projects, making it API. The template API is still in the flow and might change considerably.
-
- For people that have been using the internal template code, please note:
- - TemplateVariable has been renamed to TemplateVariableResolver
- - TemplatePosition has benn renamed to TemplateVariable
- - there is first support for adding multiple proposals for a variable
-</pre>
-========== Eclipse Build Input March 2nd 2004 ==========<br>
-<pre>
-- Moved the linked position infrastructure to the text, jface.text and ui.workbench.texteditor
- projects, making in API. See package.html in the relevant sections. This is an intermediate step
- in making templates part of the text infrastructure.
-- The content assistant can now be configured to restore the completion proposal
- popup's size. For details see:
- - ContentAssistant.setRestoreCompletionProposalSize(IDialogSettings)
-- Completion proposal popup of the content assistants in Find/Replace dialog
- now remember their size.
-- Several bugs fixed.
-</pre>
-<br>
-========== Eclipse Build Input February 24th 2004 ==========<br>
-<pre>
-- A source viewer can now be unconfigured and afterwards configured again.
-- Information control managers can now be configured to restore the information
- control's location and size. The information control must implement
- IInformationControlExtension3. For details see:
- - AbstractInformationControlManager.setRestoreInformationControlBounds(...)
- - IInformationControlExtension3.getBounds()
-- Several bugs fixed.
-</pre>
-<br>
-========== Eclipse Build Input February 17th 2004 ==========<br>
-<pre>
-- Several bugs fixed.
-</pre>
-<br>
-========== Eclipse Build Input February 10th 2004 ==========<br>
-<pre>
-- ComboContentAssistSubjectAdapter and TextContentAssistSubjectAdapter allow to
- show cue with tooltip.
-- Annotations drawing in text may now be configured. Current drawing styles are boxes, underline,
- squiggly lines, and an i-beam.
- We might introduce an extension point for specifying custom drawing strategies.
-- A roll-over annotation hover has been introduced to cope with many annotations drawn over each
- other in the vertical ruler. Enable for the Java editor using the roll over preference under
- Java->Work in Progress.
-</pre>
-<br>
-========== Eclipse Build Input January 27th 2004 ==========<br>
-<pre>
-- Improved performance when installing contributed actions.
-- The displayed tab width in the text editor can now be configured,
- see Workbench > Editors > Text Editor preferences.
-- Enhanced content assistant to be usable in Text and Combo,
- see ComboContentAssistSubjectAdapter and TextContentAssistSubjectAdapter.
-- The DefaultAnnotation and its usages which was introduced in 3.0 to be
- create non-marker based annotations has been replaced by new API in Annotation.
-</pre>
-<br>
-========== Eclipse Build Input January 20th 2004 ==========<br>
-<pre>
-- Improved annotation painting: adapted painter to fine grained annotation model delta.
-</pre>
-<br>
-========== Eclipse Build Input December 18th 2003 ==========<br>
-<pre>
-This build contains several changes and additions to the annotation mechanism.
-
-1) Annotation Types
-
-There is now the explicit notion of an annotation type. See Annotation.getType() and Annotation.setType().
-The type of an annotation can change over it's lifetime. A new extension point has been added for the declaration
-of annotation types: "org.eclipse.ui.editors.annotationTypes". An annotation type has a name and can be declared
-as being a subtype of another declared annotation type. An annotation type declaration may also use the attributes
-"markerType" and "markerSeverity" in order to specify that markers of a given type and a given severity should be
-represented in text editors as annotations of a particular annotation type. The attributes "markerType" and
-"markerSeverity" in the "org.eclipse.ui.editors.markerAnnotationSpecification" should no longer be used. Marker
-annotation specifications are thus becoming independent from markers and the name thus misleading. However, the
-name is kept in order to ensure backward compatibility.
-
-Instances of subclasses of AbstractMarkerAnnotationModel automatically detect and set the correct annotation
-types for annotations they create from markers. In order to programmatically retrieve the annotation type for
-a given marker or a given pair of markerType and markerSeverity use org.eclipse.ui.texteditor.AnnotationTypeLookup.
-
-Access to the hierarchy of annotation types is provided by AnnotationTypeHierarchy. For a given annotation type
-name you can get an AnnotationType that provides information about the chain of super types and a method to check
-whether an annotation type given as name is a subtype. You can also retrieve the information from
-IAnnotationAccessExtension. DefaultMarkerAnnotationAccess implements this interface.
-
-2) MarkerAnnotationSpecification
-
-The annotation type is the key with which to find the associated marker annotation specification. As annotation
-types can extend other annotation types, there is an implicit relation between marker annotation specifications
-as well. Therefore a marker annotation specification for a given annotation type is completed by the marker
-annotation specifications given for the super types of the given annotation type. Therefore, marker annotation
-specification do not have to be complete as this was required before. Marker annotation specifications are
-reified by AnnotationPreferences. By using org.eclipse.ui.texteditor.AnnotationPreferenceLookup, you can retrieve
-an annotation preference for a given annotation type that transparently performs the completion of the preference
-along the annotation super type chain.
-
-3) Painting annotation
-
-Marker annotation specification has been extended with three addition attributed in order to allow the definition
-of custom appearances of a given annotation type in the vertical ruler. These attributes are: "icon", "symbolicIcon",
-and "annotationImageProvider". The value for "icon" is the path to a file containing the icon image. The value of
-"symbolicIcon" can be one of "error", "warning", "info", "task", "bookmark". The attribute "symbolicIcon" is used
-to tell the platform that annotation should be depicted with the same images that are used by the platform to
-present errors, warnings, infos, tasks, and bookmarks respectively. The value of "annotationImageProvider" is a
-class implementing org.eclipse.ui.texteditor.IAnnotationImageProvider that allows for a full custom annotation
-presentation.
-
-The vertical ruler uses it's associated IAnnotationAccess/IAnnotationAccessExtension to draw annotations.
-The vertical ruler does not call Annotation.paint any longer. In general, Annotations are no longer supposed
-to draw themselves. The "paint" and "getLayer" methods have been deprecated in order to make annotation eventually
-UI independent. DefaultMarkerAnnotationAccess serves as default implementation of IAnnotationAccess/IAnnotationAccessExtension.
-DefaultMarkerAnnotationAccess implements the following strategy for painting annotations: If an annotation implements
-IAnnotationPresentation, IAnnotationPresentation.paint is called. If not, the annotation image provider is looked up
-in the annotation preference. The annotation image provider is only available if specified and if the plug-in defining
-the enclosing marker annotation specification has already been loaded. If there is an annotation image provider, the
-call is forwarded to it. If not, the specified "icon" is looked up. "symbolicIcon" is used as the final fallback. For
-drawing annotations, the annotation presentation layer is relevant. DefaultMarkerAnnotationAccess looks up the presentation
-layer using the following strategy: If the annotation preference specifies a presentation layer, the specified layer is
-used. If there is no layer and the annotation implements IAnnotationPresentation, IAnnotationPresentation.getLayer is used
-otherwise the default presentation layer (which is 0) is returned.
-
-4) Additions to Annotation
-
-Annotations additionally support: a message, a flag to indicate whether the annotation is marked as deleted, a
-flag to indicate whether the annotation is persistent or temporary.
-
-5) Migration
-
-The following annotation types are declared by the org.eclipse.ui.editors plug-in:
-
- &lt;extension point="org.eclipse.ui.editors.annotationTypes"&gt;
- &lt;type
- name="org.eclipse.ui.workbench.texteditor.error"
- markerType="org.eclipse.core.resources.problemmarker"
- markerSeverity="2"&gt;
- &lt;/type&gt;
- &lt;type
- name="org.eclipse.ui.workbench.texteditor.warning"
- markerType="org.eclipse.core.resources.problemmarker"
- markerSeverity="1"&gt;
- &lt;/type&gt;
- &lt;type
- name="org.eclipse.ui.workbench.texteditor.info"
- markerType="org.eclipse.core.resources.problemmarker"
- markerSeverity="0"&gt;
- &lt;/type&gt;
- &lt;type
- name="org.eclipse.ui.workbench.texteditor.task"
- markerType="org.eclipse.core.resources.taskmarker"&gt;
- &lt;/type&gt;
- &lt;type
- name="org.eclipse.ui.workbench.texteditor.bookmark"
- markerType="org.eclipse.core.resources.bookmark"&gt;
- &lt;/type&gt;
- &lt;/extension&gt;
-
-The defined markerAnnotationSpecification extension no longer provide "markerType" and "markerSeverity"
-attributes. They define the "symbolicIcon" attribute with the according value. Thus, MarkerAnnotation.paint
-and MarkerAnnotation.getLayer are not called any longer, i.e. overriding these methods does not have
-any effect.
-</pre>
-<br>
-========== Eclipse Build Input November 11th 2003 ==========<br>
-<pre>
-- Finished annotation background painter
-- Added new concept of ITextPresentationListener which should be used by clients
- to apply a presentation style (e.g. color, bold) to the text. Clients using
- the StyledText.*styleRange* API methods should convert to this new API. A
- ITextPresentationListener can be added and removed from a text viewer (see
- ITextViewerExtension4)
-</pre>
-<br>
-<br>
-
-========== Eclipse Build Input October 28th 2003 ==========<br>
-<pre>
-- Vertical ruler annotations can be disabled via editor's Annotation preference
- page.
-- Added support to set background for annotations
- - annotation background painter <work in progress>
- - key/value attributes to "org.eclipse.ui.workbench.texteditor.markerAnnotationSpecification" extension-point
- - updated annotation preference page to show this attribute
- - enabled this feature for Search annotations
-</pre>
-<br>
-<br>
-========== Eclipse Build Input October 21th 2003 ==========<br>
-<pre>
-- Incremental find has its own editor status line field (findField)
-- IStatusField has been extended (IStatusFieldExtension) with the following concepts:
- - set error text and image
- - set tool tip
- - control visibility
-</pre>
-<br>
-<br>
-========== Eclipse Build Input October 7th 2003 ==========<br>
-<pre>
-- Find/Replace dialog now offers content assist for regular expression search and replace
-- Changes found by Quickdiff are now ordinary annotations. I.e. they can serve as
- navigation target, can be shown in the overview ruler, and in the text. Their presentation
- colors can also be configured.
-- "Open External File" can be found in the Files menu. It opens files which are not workspace files
- with the associated editor or the default text editor if no editor is specified. Text editors support
- external files.
-</pre>
-<br>
-<br>
-========== Eclipse Build Input September 30th 2003 ==========<br>
-<pre>
-- Find/Replace dialog now supports regular expression search and replace
-- Quick Diff annotations can now be displayed on the overview ruler and support Go to Next / Previous
-</pre>
-<br>
-<br>
-========== Eclipse Build Input August 26th 2003 ==========<br>
-<pre>
-- Improved overview ruler:
- - can now handle annotations on same layer
- - added tool tip text to overview ruler header
- - tool tip text for disabled annotation no longer appears
- - click on overview ruler item respects layer
- - clicking on same overview ruler item jumps to next annotation
-- several bugs fixed
-</pre>
-<br>
-<br>
-========== Eclipse Build Input August 19th 2003 ==========<br>
-<pre>
-- added concept of reconcile step: a reconcile step is one of n steps of a
- reconcile strategy that consists of several steps. See the Java Family example
- to see it in action.
-- added concept of translator: a translator translates a given file into another
- language. The translator is also responsible to provide line mapping information
- for the translation and to compute which offset in an original line corresponds
- to a given offset in a target line. See the Java Family example to see it in action.
-- TextEditor extends now ExtendedTextEditor, an additional layer combining features
- used in rich editors, such as the annotation, line number and overview rulers,
- the print margin, current text highlighting, and quick diff.
-- several bugs fixed
-</pre>
-<br>
-<br>
-========== Eclipse Build Input August 12th 2003 ==========<br>
-<pre>
-- the marker annotation specification can now be used to specify if the annotation
- should allow to be a navigation target. For details read the documentation of
- org.eclipse.workbench.texteditor.markerAnnotationSpecification extension point.
-- several bugs fixed
-</pre>
-<br>
-<br>
-========== Eclipse Build Input July 29th 2003 ==========<br>
-<pre>
-- several bugs fixed
-</pre>
-<br>
-<br>
-========== Eclipse Build Input July 22th 2003 ==========<br>
-<pre>
-- several bugs fixed
-</pre>
-<br>
-<br>
-========== Eclipse Build Input July 16th 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-- Improvements and framework changes for the light weight change indication. Change indication
- can now happen in the line number ruler or a dedicated change ruler column.
-</pre>
-<br>
-<br>
-========== Eclipse Build Input July 8th 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-- The TextViewer sends out time-out based selection changed events for
- caret position changes for clients registered as post selection changed listeners.
-- The default text editor supports a light weight change indicator integrated with the line number ruler.
- Can be globally enabled on the Text Editor preference page. Can be enabled/disabled for the current editor
- in the editor's context menu or using the short cut "Ctrl+Shift+Q".
-- Text frameworks have been extended to support light weight diffing.
-</pre>
-<br>
-<br>
-========== Eclipse Build Input June 17th 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-- The TextViewer sends out time-out based selection changed events for caret position changes.
-- added extension interfaces which allow completion proposals to specify their custom
- information control creator
-</pre>
-<br>
-<br>
-========== Eclipse Build Input June 4th 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-- The TextViewer sends out time-out based selection changed events for caret position changes.
-- added extension interfaces which allow text hovers and information providers to specify their custom
- information control creator
-- text editors support three typing modes: Overwrite, Insert, Smart Insert
- - typing modes are toggled by INS in the default key binding
- - each mode is represented with its own caret
- - modes can be disabled per editor, i.e. when toggling insert modes, disabled modes will not be selected
-- status line contribution items can now be associated with an action that is called when double clicking the status item
-</pre>
-<br>
-<br>
-========== Eclipse Build Input May 13th 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-- released new features:
- - Insert new line above the caret line (ui name: "Smart Enter (Inverse)", default key binding: Ctrl+Shift+Enter)
- - Insert new line after the caret line (ui name: "Smart Enter", default key binding: Shift+Enter)
- - Move selected lines upwards (ui name: "Move Lines Up", default key binding: Alt+Arrow_UP)
- - Move selected lines down (ui name: "Move Lines Down", default key binding: Alt+Arrow_Down)
- - Change case of selection to upper case (ui name: "To Upper Case", default key binding: Ctrl+Shift+X)
- - Change case of selection to lower case (ui name: "To Lower Case", default key binding: Ctrl+Shift+Y)
-</pre>
-<br>
-<br>
-========== Eclipse Build Input April 29th 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-</pre>
-<br>
-<br>
-========== Eclipse Build Input April 22nd 2003 ==========<br>
-<!-- Add what's new below and end each line with br tag -->
-<pre>
-- several bugs fixed
-</pre>
-<br>
-<br>
-</body></html> \ No newline at end of file
diff --git a/org.eclipse.ui.editors/_buildnotes_text_3_1.html b/org.eclipse.ui.editors/_buildnotes_text_3_1.html
deleted file mode 100644
index 0b6070f2f..000000000
--- a/org.eclipse.ui.editors/_buildnotes_text_3_1.html
+++ /dev/null
@@ -1,231 +0,0 @@
-<!--
- DO NOT EDIT THIS FILE WITH HTML EDITORS
--->
-
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <meta name="GENERATOR" content="Mozilla/4.76 [en] (Windows NT 5.0; U) [Netscape]">
- <title>Eclipse 3.1 Platform Build Notes - Text</title>
-<link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
-</head>
-
-<body>
-<h1>
-Eclipse 3.1 Platform Build Notes<br>
-Text</h1>
-To see which bugs have been addressed in one of the builds simply open the <a href="http://bugs.eclipse.org/bugs/query.cgi?short_desc_type=allwordssubstr&amp;product=Platform&amp;component=Text&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;namedcmd=Assigned&amp;newqueryname=&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform-Text bugzilla query page</a>, select status, resolution and the time frame.
-<br>
-<br>
-<br>
-========== Eclipse Build Input May 27th 2005 (RC1) ==========<br>
-<pre>
-- added ICompletionProposalExtension4
-- added the auto-insertable property to org.eclipse.jfact.text.templates.Template, adding an additional constructor
- and deprecating an old one. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=81701.
-- bug fixing
-</pre>
-========== Eclipse Build Input May 10th 2005 ==========<br>
-<pre>
-- released new artwork for projection annotations
-- bug fixing
-</pre>
-========== Eclipse Build Input April 26th 2005 ==========<br>
-<pre>
-- added modification stamp to document and document event
-- file buffers are now non-dirty after the document change is undone that caused switch into dirty state
-- bug fixing
-</pre>
-========== Eclipse Build Input April 19th 2005 ==========<br>
-<pre>
-- converted text plug-ins to JARed format
-- bug fixing
-</pre>
-========== Eclipse Build Input April 12th 2005 ==========<br>
-<pre>
-- moved relevant portions from plugin.xml to newly created MANIFEST.MF
-- bug fixing
-</pre>
-========== Eclipse Build Input March 29th 2005 ==========<br>
-<pre>
-- added undo history size to general text editors preference page
-- bug fixing
-</pre>
-========== Eclipse Build Input March 22th 2005 ==========<br>
-<pre>
-- adapted undo manager to new operation support
-- bug fixing
-</pre>
-========== Eclipse Build Input March 1st 2005 ==========<br>
-<pre>
-- added a ctor taking an RGB as parameter to DefaultHyperlinkPresenter
-</pre>
-========== Eclipse Build Input February 8th 2005 ==========<br>
-<pre>
-- added ProjectionAnnotation.getCaptionOffset which allows folding providers
- to specify which line of a folded-away region should be used as the caption
- that remains visible in the document. This change is binary compatible, but
- could break clients that already define such a method.
-- moved the "Change Encoding..." action from "File" > "Conversion" to "Edit"
-- renamed "File" > "Conversion" to "File" > "Convert Line Delimiters To"
-</pre>
-========== Eclipse Build Input February 1st 2005 ==========<br>
-<pre>
-- added FastPartitioner, replacing DefaultPartitioner which is deprecated.
- FastPartitioner has the same interface as DefaultPartitioner, but internally
- caches the partitioning positions set on the document to avoid multiple array
- creations. Current users of DefaultPartitioner are encouraged to migrate to
- FastPartitioner; subclasses of DefaultPartitioner that do not modify the positions
- will work when subclassing FastPartioner as well, those that do will need to call
- clearPositionCache() when positions are modified.
-- encoding change dialog now rejects invalid encodings
-</pre>
-========== Eclipse Build Input January 25th 2005 ==========<br>
-<pre>
-- added Hippie (emacs style) Completion, contributed by Genady Beryozkin. The action (bound to Alt+/ per default)
- scans all open editors for completions to the current prefix and cycles through the completions.
-- bug fixing
-</pre>
-========== Eclipse Build Input January 18th 2005 ==========<br>
-<pre>
-- bug fixing
-</pre>
-========== Eclipse Build Input January 11th 2005 ==========<br>
-<pre>
-- bug fixing
-</pre>
-========== Eclipse Build Input January 4th 2005 ==========<br>
-<pre>
-- Quick Diff:
- - added org.eclipse.jface.text.source.ILineDifferExtension extension interface to ILineDiffer
-
-- Templates:
- - deprecated all setters on org.eclipse.jface.text.templates.Template. Template
- is really a value object and should not be modified any longer.
- - In order to handle the above change, deprecated TemplatePreferencePage.createEditTemplateDialog.
- Subclasses really don't need to display a dialog if they don't want. Editing or adding a template
- can be customized through the new hook method editTemplate method.
-- bug fixing
-</pre>
-========== Eclipse Build Input December 14th 2004 ==========<br>
-<pre>
-- added Spelling API to org.eclipse.ui.workbench.texteditor plug-in:
- - The API is still under construction, provide feedback in
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=77353.
- - New package: org.eclipse.ui.texteditor.spelling
- - New extension-point: org.eclipse.ui.workbench.texteditor.spellingEngine
- - A spelling client can spell-check a document by calling
- SpellingService#check(IDocument document, IRegion[] regions, SpellingContext context, ISpellingProblemCollector collector, IProgressMonitor monitor).
- The supplied SpellingContext allows the spelling engine to determine
- settings specific to this check. Each spelling error is reported to the
- supplied ISpellingProblemCollector as SpellingProblem.
- For example, see org.eclipse.jdt.internal.ui.text.spelling.JavaSpellingReconcileStrategy
- and org.eclipse.jdt.internal.ui.text.spelling.JavaSpellingReconcileStrategy.SpellingProblemCollector.
- - The org.eclipse.ui.editors plug-in provides access to a system-wide instance of
- SpellingService with org.eclipse.ui.editors.text.EditorsUI#getSpellingService()
- and registers a preference page for configuring the SpellingService's and
- the spelling engines' preferences. The SpellingService's preferences are whether
- spelling is enabled and which spelling engine is used. (The spelling preference page
- shows a combo box for chosing the used engine only if more than one engine
- is present.)
- See org.eclipse.ui.texteditor.spelling.SpellingService and
- the General > Editors > All Text Editors > Spelling preference page.
- - A spelling engine implementer must implement ISpellingEngine and extend
- the org.eclipse.ui.workbench.texteditor.spellingEngine extension-point.
- The implementation of ISpellingEngine#check(IDocument document, IRegion[] regions, SpellingContext context, ISpellingProblemCollector collector, IProgressMonitor monitor)
- reports any spelling errors to the given ISpellingProblemCollector as SpellingProblem.
- Note that the engine must not call ISpellingProblemCollector#beginReporting()
- or ISpellingProblemCollector#endReporting() as this is done by the spelling
- infrastructure.
- For example, see org.eclipse.jdt.internal.ui.text.spelling.DefaultSpellingEngine
- and org.eclipse.jdt.internal.ui.text.spelling.JavaSpellingProblem.
- - A spelling engine implementer can implement ISpellingPreferenceBlock and specify
- the implementing class with the extension. A ISpellingPreferenceBlock provides
- a UI for preferences specific to the spelling engine. If the user-supplied preference
- values are not valid, the preference block should notify the IPreferenceStatusMonitor
- it received on ISpellingPreferenceBlock#initialize(IPreferenceStatusMonitor), such
- that the containing preference page can provide corresponding indication to the user.
- For example, see org.eclipse.jdt.internal.ui.preferences.SpellingPreferenceBlock and
- the General > Editors > All Text Editors > Spelling preference page.
- - Extension specification example from the org.eclipse.jdt.ui plug-in's plugin.xml:
- &lt;extension point="org.eclipse.ui.workbench.texteditor.spellingEngine"&gt;
- &lt;engine
- preferencesClass="org.eclipse.jdt.internal.ui.preferences.SpellingPreferenceBlock"
- label="%defaultSpellingEngine.label"
- class="org.eclipse.jdt.internal.ui.text.spelling.DefaultSpellingEngine"
- default="true"
- id="org.eclipse.jdt.internal.ui.text.spelling.DefaultSpellingEngine"&gt;
- &lt;/engine&gt;
- &lt;/extension&gt;
-
-- bug fixing
-</pre>
-========== Eclipse Build Input November 30th 2004 ==========<br>
-<pre>
-- added new hyperlink support to text viewer and editors:
- - new package org.eclipse.jface.text.hyperlink
- - extended ITextEditor with ITextViewerExtension6
- - added shared/global text editor preference to
- - enable/disable hyperlinking (default: enabled)
- - set the hyperlink modifier key (default: MOD1 i.e. Ctrl or Command)
- - set the hyperlink color (default: blue)
- - SourceViewerConfiguration: clients using or subclassing it will now automatically
- get hyperlinking for URLs (using MOD1 modifier).
- - If hyperlinking is not desired then getHyperlinksEnabled(...) can be overwritten
- to return false.
- - To use the shared/global editor hyperlink preference either subclass
- TextSourceViewerConfiguration or duplicate the getHyperlink* methods to your subclass
- of SourceViewerConfiguration.
- Note: your editor's preference store must be a ChainedPreferenceStore, e.g.
- IPreferenceStore generalTextStore= EditorsUI.getPreferenceStore();
- fChainedPreferenceStore= new ChainedPreferenceStore(new IPreferenceStore[] { YourPlugin.getPreferenceStore(), generalTextStore });
- - additional hyperlink targets can be configured by extending SourceViewerConfiguration.getHyperlinkDetectors(...)
- NOTE: In the feature it might (i.e. not sure yet) be possible to provide hyperlinking via
- extension-point(s) and user-configurable it via preferences.
-- preferences:
- - moved many preferences that were available in all editors to a
- shared editor page (see Workbench>Editors>All Text Editors)
- - moved Java editor prefernce page under the Workbench>Editors node
- - this is a temporary position due to the ongoing prefernce page reordering effor
- - removed some preferences:
- - show overview ruler
-
-- bug fixing
-</pre>
-========== Eclipse Build Input November 23th 2004 ==========<br>
-<pre>
-- moved adapter factory registration from plug-in class to extension point
-- bug fixing
-</pre>
-========== Eclipse Build Input September 21 2004 ==========<br>
-<pre>
-- the text editor now retargets the properties action i.e. the command to open
- the properties dialog is enabled when the text editor has focus
-- there's a new Edit > Change Encoding... action which reuses the encoding
- field editor from the properties dialog
-- EncodingActionGroup, IEncodingActionsConstants, IEncodingActionsDefinitionIds and
- IEncodingActionsHelpContextIds are no longer used and have been deprecated
-- bug fixing
-
-LinkedMode:
-- LinkedModeModel: document changes outside of linked positions
- are now tolerated, as well as changes that do not lie completely inside a
- position. Linked mode is still left if any disjointness constraints are violated
- by a change (changes to LinkedModeModel and LinkedPositionGroup)
-- LinkedModeUI now controls the entire exit behavior, so all the exit logic
- is at one point. The UI includes a document listener now and exits the same
- way as LinkedModeModel did before
--> no binary changes, no functional changes for any clients that use LinkedModeUI and LinkedModeModel together.
-</pre>
-<br>
-<br>
-========== Eclipse Build Input July 2004 ==========<br>
-<pre>
-- bug fixing
-</pre>
-<br>
-<br>
-</body>
-</html> \ No newline at end of file

Back to the top