Page Bottom  The Plain Vanilla Player


the Renderer

You need a "Renderer " to convert your M3M or M1M data structures into various types of nice looking reports (HTML, PDF, Excel, etc.) Again I see this as a set of specialized objects which would each be able to "render" an M1M data structure into one of the desired formats. A detailed analysis of this problem needs to be done, but here are a few remarks:
  1. - it would be good to see if the Renderer could first blindly produce the report in the format in which it is the easiest to produce the report (Excel?)
  2. - then, the specialized objects would convert this report into the requested format (HTML, PDF, …)
There are very good conversion software out there which know how to convert a file format into another file format. Our job would be to select the best converter program in each category.

Here are a number of additional remarks:

to achieve such an ambitious project successfully, an extreme rigor must be adopted at each stage (analysis, development, documentation)

if you were to ask me to help you achieve this project, I would like to use the "simple to more and more complex approach" This means, I would like to concentrate on M1M data structures only at first and within M1Ms, select only a few properties (maybe pvTXT, pvM, pvRT and pvCT) and build the Data Store, the Editor and the Renderer objects necessary to correctly handle these properties (or maybe we could decide the Renderer is really a separate project that can be done a little later). Anyway, I would like these objects to be perfect, i.e. that you do not let me start working on implementing other properties until you consider the work on the first properties and the accompanying documentation to be really perfectly done. Then we can add one more M1M property, and test it until it is considered perfect. Etc. I am used to work on very complex projects like this one and I have learnt over years and years that this is an approach which leads to success.

as is recommended in all modern development systems, there should be a "total" independency of the various project modules (the Data Store, the Editor and the Renderer)

the latter point implies that the M1M data structure be revisited (this does not necessarily mean it should be changed, but maybe) because:

  1. it contains properties which are pure data (pvTXT, pvM, pvRT, pvCT, pvTTL3, etc.)
  2. it contains properties which are related to M3M only (pvDTS, pvVCOM, etc.)
  3. it contains properties which are pure formatting ones (pvFMV)
  4. it contains properties which concerns only the Renderer maybe (the print page headers, footers, etc.)
I have plenty of ideas that could allow to both reduce the number of properties to handle and make it much simpler to implement them.

horizontal line
What's New Page to home page e-mail Page Top