Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

[f2d102]: index.html Maximize Restore History

Download this file

index.html    56 lines (54 with data), 2.6 kB

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
<html>
<title>DirtyGutter plugin</title>
<body>
<h1>The DirtyGutter plugin</h1>
Written by Shlomy Reinstein, August 2009.
<h2>Table of Contents</h2>
<ol>
<li><a href="#description">Description</a>
<li><a href="#feedback">Feedback</a>
</ol>
<a name="description">
<h2>Description</h2>
</a>
The DirtyGutter plugin marks dirty lines (lines modified since last save) in the
Gutter area. The dirty line information is provided by a so-called "Dirty line
provider". There are two built-in dirty line providers:
<ul>
<li>Simple: This provider keeps track of content changes in the buffer, and
marks all types of changes (added content, removed content, modified
content) the same way, using colored markers.<br>
The Simple provider tries to keep overall resource consumption to a minimum
(memory, I/O, CPU).<br>
The provider supports undo/redo by maintaining its own undo information.
By default, the plugin is activated on jEdit startup, so tracking the buffer
content changes is sufficient for maintaining the undo information, but if
the plugin is installed or manually enabled using the Plugin Manager, this
provider uses a complex algorithm to build its initial undo-support information,
which includes performing all available undo and redo operations (eventually
restoring the buffer state to the plugin activation time).
<li>Diff: This provider keeps track of content changes in the buffer, and runs
a 'diff' algorithm between the saved file and the buffer contents whenever a
multi-line content change occurs. The 'diff' algorithm used is the same one used
by JDiffPlugin, which was "inherited" from GNU diff. Single-line content changes
are recorded internally by the provider and marked according to the type of
change - where each type has its own (configurable) marker color. The 'diff'
algorithm also marks the changes in different colors, but only for inserted /
removed lines, not for content inserted or removed within a line, which are
always considered as "changed". Hence, after running a 'diff', any other type
of marker in modified lines will be replaced with a "changed" marker.
</ul>
<br>
In addition, the plugin provides a service for other plugins (e.g. SCM plugins)
to contribute dirty line providers, e.g.:<br>
<code>
&nbsp;&nbsp;&lt;SERVICE CLASS="lcm.DirtyLineProvider" NAME="Simple"&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;new lcm.providers.simple.SimpleDirtyLineProvider();<br>
&nbsp;&nbsp;&lt;/SERVICE&gt;<br>
</code>
<a name="feedback">
<h2>Feedback</h2>
</a>
Any feedback would be most welcome. Please send your feedback to the jedit-users or jedit-devel mailing list.
</body>
</html>