I have a decent grasp of running erl_tidy itself and use many similar Eclipse features on a day to day basis in Java Development. I think I can make this work.

I left out the Compare Editor part, but I will investigate it.

Shouldn't erl_tidy be a save action? Like in JDT.

We can add that later, the important thing is that we can run it somehow.

Can you add a ticket for "erl_tidy be a save action", Jakob?

Child association with ticket #496 was added

I will be refactoring this feature to use erl_tidy:forms instead as Vlad has suggested. The resource of an ErlangEditor in Eclipse may not be backed on a local file or on a file at all. This makes the current implementation brittle. The current implementation also has issues with edited or out of sync files on Windows. Hopefully running the resource edits within Eclipse should resolve both of these weaknesses in the current implementation.

Vlad's suggestion is to use the ErlIDE scanner and feed the syntax token representation to erl_parse to get the abstract forms which erl_tidy:forms can use:

One could have an editor open on a resource that is
not a file. The operation should call erl_tidy:module and use the
parsed representation of whatever is in the editor. The model we use
doesn't parse the whole file, but you can retrieve the scanned tokens
(erlide_scanner_server:getTokens), feed them to erl_parse:parse and
the result to erl_tidy:forms. The name used for the module in Erlang
is
                       scannerName = ErlangToolkit.createScannerModuleName(module);

Made a number of runs at using erlide_scanner_server:getTokens/1 as a source of data for erl_tidy:module/1 without luck. I cannot seem to convert the output of erlide_scanner_server:getTokens/1 into a format acceptable to erl_parse:parse_forms/1. It looks fine on visual inspection but erl_parse:parse_forms/1 always returns something like:
{error,{"%%%-------------------------------------------------------------------",erl_parse,["syntax error before: ","comment"]}}

It looks like erl_tidy solves this problem by somehow ignoring comments, but its not clear to me. I will try again in a couple of days. I am unable to work on this tomorrow evening unfortunately.

I hope you're aware of the different token formats: erlide uses a records #token{} (defined in erlide_scanner.hrl), and syntax_tools uses the tuple format. A lot of functions in erl_syntax will have to be rewritten.
There are also a lot of things missing in syntax_tools, it seems to be one of those applications that are included in OTP, but never really used or supported...

Did you use erlide_scan:filter_comments and filter_ws and possibly even filter1?

Related association with ticket #508 was added

moved to 'planned work' -- has to be reactivated when we have a pretty-printer (#508)

Updating tickets (#491, #496)

This is done, but we can't include it because it reformats the code (and erl_pretty results are pretty ugly :-)

Updating tickets (#114, #373, #386, #431, #473, #502, #532, #325, #529, #553, #176, #177, #291, #323, #401, #409, #434, #491, #496, #503, #520, #560, #567, #569, #475, #550)

Updating tickets (#130, #223, #235, #276, #325, #438, #580, #53, #58, #116, #117, #121, #164, #170, #211, #234, #238, #239, #244, #252, #255, #328, #374, #377, #378, #392, #394, #407, #410, #447, #459, #491, #496, #508, #524, #545, #576, #590, #205, #240, #493, #495, #514, #515, #517, #557, #589, #62, #99, #118, #359, #437, #445, #498, #499)

Updating tickets (#106, #113, #129, #130, #182, #223, #235, #276, #325, #438, #483, #529, #580, #40, #42, #43, #44, #46, #53, #58, #61, #69, #76, #80, #84, #89, #115, #116, #117, #119, #121, #123, #152, #164, #166, #168, #169, #170, #176, #188, #199, #208, #211, #216, #231, #234, #237, #238, #239, #244, #249, #252, #255, #264, #291, #294, #313, #314, #317, #321, #323, #326, #328, #336, #366, #374, #377, #378, #380, #392, #394, #398, #407, #410, #430, #440, #447, #459, #463, #465, #477, #478, #485, #491, #494, #496, #508, #511, #524, #530, #545, #560, #565, #569, #570, #576, #584, #590, #594, #596, #620, #621, #100, #160, #205, #240, #265, #436, #439, #452, #475, #493, #495, #506, #514, #515, #517, #536, #548, #557, #589, #600, #62, #99, #118, #132, #145, #210, #359, #387, #419, #433, #437, #445, #488, #498, #499)

I have included this in 'pu', but the commands are disabled. This is so that i don't have to keep rebasing the branch.