New Look for Generated Applications

 

As of the May 26th, 2010 update, m-Power has begun to ship with a new look for generated applications. Some of the benefits of this new look are:

  • Improved images, including new Filter & Run buttons, sort images and Work-with Maintenance icons.
  • A comprehensive cascading style sheet that more easily allows for gradient backgrounds.
  • Row-Striping on all Multiple Record Templates to better analyze data.
  • Modern header/footer files to make your Web applications more aesthetically pleasing.
  • All applications now compile with DOCTYPE references, to ensure cross-browser compatibility.

Below we will explain various scenarios to help you understand what will be affected by this release:

Scenario 1: Working with Existing Data Dictionaries

Icons

All Applications in Existing Data Dictionaries will automatically use new icons. This includes new sort arrows and new icons within the Work-with Maintenance template (Add, View, Update, Copy, and Delete).

If you do not want to use these improved icons, the older icons are still available to you.

They can be located in \m-power\proddata\templates\origlook. Simply copy the images you would like to use back into the \m-power\mrcjava\image folder.

Note: This process will need to be done after each m-Power update as installing the update will re-install the new images.

Header, Footer, Stylesheet, and Row-Striping

The Header, Footer, Style Sheet, and Row-Striping will not be implemented for applications in existing data dictionaries. Please see Scenario 3 to learn how to install these features.

Scenario 2: New Look with New Data Dictionary

Icons

All newly created applications will use the updated icons. This includes new sort arrows and new icons within the Work-with Maintenance template (Add, View, Update, Copy, and Delete).

Header, Footer, & Stylesheet

When you create a new Data Dictionary, the new Header, Footer, and Comprehensive CSS are automatically installed in your Data Dictionary.

Note: If you have many other Data Dictionaries in production and wish to use your existing look for consistency within your new Data Dictionary, simply copy the following files from your existing Data Dictionary to your newly created one:

  • mrc_servlet_head.html
  • mrc_servlet_foot.html
  • mrc_servlet_stylesheet_css.html

Row-Striping

Row-Striping will be activated for each Multi-Record template within this Data Dictionary.

To deactivate this feature for the entire Data Dictionary, remove all references from the CSS that begin with “.stripe”.

To deactivate this from a particular application, open the application in m-Painter, open the Source code, and remove the following text: ” class="stripe" “.

Scenario 3: Converting Existing Data Dictionaries to Use New Look

Icons

All existing applications will use the updated icons automatically. This includes new sort arrows and new icons within the Work-with Maintenance template (Add, View, Update, Copy, and Delete).

Header/Footer & Style Sheet

Copy the following files from: \m-power\proddata\templates into: \m-power\mrcjava\WEB-INF\classes\YOUR_DATA_DICTIONARY

  • mrc_servlet_head.html
  • mrc_servlet_foot.html

Next, download a special CSS file designed specifically for your existing data dictionaries/applications. It can be found here. Please download it to the \m-power\mrcjava\WEB-INF\classes\YOUR_DATA_DICTIONARY location on your m-Power server.

Note: Be sure to replace your Data Dictionary’s name in the path, replacing “YOUR_DATA_DICTIONARY”.

Note: Be sure the file saves as a .html extension.

You can then modify the header, footer, and Style Sheet within the interface via Admin –> Edit Data Dictionary Files.

Note: If utilizing security, be sure to copy the updated mrcSignon2.html from \m-power\mrcjava\mrcclasses.

Row-Striping

Implementing Row-Striping requires multiple changes to the HTML. mrc recommends overwriting your HTML on existing applications when possible to easily implement the row-striping effect. If that is not an option (i.e. too much custom Painting to replace), please contact mrc support for the multiple steps required to implement this on existing applications.