TYPO3 Core

EditDocumentController contents powerful features that could be also used in other places.
At the moment, a lot of parameters are provided by url, assigned as class properties an used along the methods.
What I would like to achieve here is to split it at least in 2 different classes:

• the controller one, which gets the parameters from url, and prepare the render part of the module like the titles between each field record
• the second class, not sure here if the naming is Service or Provider which returns the "valuable" part of the controller: the render of records and each selected fields, saving form url and or javascript needed

Why do this?
Main use case here appears in front of me suddenly. I've been playing to rendering inputs, youtube videos or other thins directly on Page, for the page and also for the Preview of a content element or in Page. This split provide us the opportunity of creating, for example, a <f:be.document table="tt_content" id="1" columnsOnly="title,doktype" />

This could be used later to get something like this: