Volatility 1.4 doesn't allow new renders to be written for all plugins easily

[GoogleCodeExporter]

Hiya guys,

This is just a placeholder bug to put information pertaining to the rendering 
engine problem.

At the moment all plugins specify a render_text function which accepts a data 
object (can be anything) from it's own calculate function, and a file 
descriptor.  It then prints out the important text to the file descriptor.  
Status/progress information can be printed/written to stdout.

It would be nice to have the ability to write a whole new output format (such 
as XML or SQL) that applies to all plugins, including those that already exist. 
 To do this, some kind of common standard will be needed.

Scudette's taken a first crack at this, which has lived mostly in the 
experimental branch.  It is backwards compatible (so that existing 1.4 plugins 
will still output to text if necessary) and works by defining a UI object, 
which different rendering engines can then work with.

I'm attaching a patch that applies to r392 of the Volatility-1.4_rc1 branch 
just so that we've got a copy locally.  You can also find this at 
https://gist.github.com/54ed859a20d9d01c489d complete with syntax highlighting.

Original issue reported on code.google.com by mike.auty@gmail.com on 22 Aug 2010 at 2:26

Attachments:

• volatility-render-ui.patch

[GoogleCodeExporter]

This patch has been applied to a fresh experimental branch (the old one was 
removed, but will still be available in subversion for those curious).  Any 
additional work on the renderer will go on there, although other experimental 
bits and pieces may be worked on in there too.

Original comment by mike.auty@gmail.com on 2 Sep 2010 at 4:35

[GoogleCodeExporter]

This is no longer a project goal so closing. Renderers and UI presentation can 
be written as users of the framework.

Original comment by scude...@gmail.com on 25 Mar 2012 at 11:21

• Changed state: WontFix