Web column view match application column view

[GoogleCodeExporter]

What enhancement are you proposing?
We can configure the screen view to remove columns we don't need to make 
the page fit nicely on the screen.  When we generate the web page we get 
all of he columns.  The page is too wide to fit on the screen.  If teh web 
was genereated from our set configuration within the application many 
columns would be removed and the web page would only have relevant 
information on it and would fit on the screen.

What is the expected output for the proposed enhancement?
See attached file for screen shot of my remote computer.  See my web site 
at http://www.bameyer.com/gary480six.  For me the MHz field is useless so 
I would like to remove it. There is currently no way (at least that I see) 
to configure what fields are in the web view.  It is great on the 
application view by right clicking on the fields and unchecking the 
unwanted fields.

What version of the product are you using?
The latest 0.4.10 Build 156.

Original issue reported on code.google.com by BruceAMe...@gmail.com on 31 Mar 2010 at 4:03

Attachments:

• screen-shot.jpg

[GoogleCodeExporter]

It may not be the easiest or "ideal" solution right now.  But you can copy and 
edit
your copy of the XSLT files found in \HFM.NET\XSLT.  These files control the 
layout
of the HTML pages.  You can move the columns around, remove them, or write a
completely new XSLT file to suit your needs.  You can then tell HFM to use your
edited copies by changing the file locations in Preferences -> Web Visual Styles
(five file locations at the bottom).

I suggest you use copies of the original XSLT files because if you edit the 
files
already in place they will be replaced by the files delivered in the installer
package the next time you upgrade, assuming your using the MSI to install.  If 
you
make copies, your copies can persist and upgrading won't overwrite your changes.

Not saying that I won't come back to this sometime in the future, but I'm going 
to
mark this Issue as Deferred for now as I just implemented the features spoken of
above in v0.4.9 and they are intended to handle this exact situation.

Original comment by harlam357 on 1 Apr 2010 at 7:53

• Changed state: Deferred

[GoogleCodeExporter]

Per my last comment on April 1.

Original comment by harlam357 on 12 May 2010 at 11:38

• Changed state: WontFix

[GoogleCodeExporter]

Original comment by harlam357 on 23 Mar 2012 at 4:32