1. A Pentana Solutions Presentation
Visage v8.2
04 November 2015

2. New features in 8.2 New features available in v8.2
Responsive Gridsets from containers such as panels, tabs and pages
Pinned table scrolling for displaying tables on responsive devices
Final HTML production now from server rather than from client
Improved support for non IE browsers such as chrome
Server side performance improvements such as reducing reliance on session data variables and allowing a forward loading of select style variables

3. Set from the property editor in designer.
New features in 8.2
Responsive Gridsets on pages
Set from the property editor in designer.
Contains a combination of rows and columns so your grid can fit the layout of your page.
Example of gridsets
2*3 = 2 columns by 3 rows
25/25/50*2 = 3 columns 25%, 25% & 50% by 2 rows

4. New features in 8.2
Example of 3*3 gridset at design time. Shading highlights the different regions of the grid. A frame has been placed in the top 2 regions.

5. New features in 8.2
Example of 3*3 gridset at runtime time (full screen).

6. New features in 8.2
Example of 3*3 gridset at runtime time (reduced screen). Notice how frame5 has now folded under frame4.

7. New features in 8.2
Example of 2*1 gridset at designtime added to each of the frames.

8. New features in 8.2
Content now added to each of the frame gridsets at designtime.

9. New features in 8.2
Runtime (full screen)

10. New features in 8.2
Runtime (foldpoint 1). Content from gridset on right of frame has folded under left.

11. New features in 8.2
Runtime (foldpoint 2). Content from gridset on right of page has folded under left.

12. New features in 8.2 When to use a gridset
Anytime you have content which needs to “push down” is when a gridset should be used.
Eg. If you wish 2 panels to fold under each other then a gridset would be required on the page. If you want just the content of the panels to become responsive then a gridset would just be required inside the panels.

13. New features in 8.2 Percentages
With 8.2 designtime widths are now converted to percentages of the page width at runtime. This will allow elements to grow and shrink dynamically depending on the page size and device used.
Designing pages at application width is recommended.

14. New features in 8.2 Pinned Columns
Allows table to scroll horizontally so full amount of data can be displayed on a smaller device
First column in the table is pinned (full size) and then remainder of columns can be scrolled into view.
A minimum width can be set on each of the columns at design time to determine how much each column is allowed to shrink.

15. New features in 8.2
Table with pinned columns at runtime (full size)

16. New features in 8.2
Table with pinned columns at runtime (shrunk). Notice scrollbar at bottom of table for scrolling.

17. New features in 8.2
Final production of HTML now from database server rather than client
Allows for container in container production
Consistent structure now produced as not reliant on IE browser rendering.
Updates can now happen to pages without having to resave in screen designer. Eg. Modal compiler

18. New features in 8.2 Improved support for non IE browsers
More changes have been made to the core engine to achieve a higher level of compatibility with non IE browsers.
Eg. Events on tables, tab control functions, calendar functionality

19. New features in 8.2 Main Differences between IE and Chrome
Properties (get and set)
Cache (clearing)
ActiveX controls (not supported)

20. New features in 8.2 Property differences
To use object properties in IE you could use the following syntax.
var val = VSC.object.propertyName OR
VSC.object.propertyName = “abc”
To be compatible with all browser the following syntax should be used.
var val = VSC.object.getAttribute(“propertyName”) OR
VSC.object.setAttribute(“propertyName”,”abc”)

21. New features in 8.2
This will be compatible in all browsers (including IE).
Best idea is to avoid using any direct object references or property assignment. Where possible use a VRE function as this will be compatible in all browsers.
If a VRE function doesn’t exist for what you need to do, put a request in for one as otherwise you risk writing code which is specific for only one browser.

22. New features in 8.2 Cache Clearing
In IE a button exists to clear cache. This is achieved via an activeX control which is not available in non IE browsers.
Cache can be cleared manually in other browsers from the history option. Just make sure it is set to “beginning of time”.
For a live site it is recommend that the version number is incremented which each change. This is then appended to each request so it is unique for the installed version, thus not requiring a manual cache clear by the end user.

23. New features in 8.2 ActiveX controls
ActiveX controls are not supported in any browser except IE.
This means extras such as cache clearing, license key generation, writing files to operating system etc will not be available in these browsers.

24. New features in 8.2
Questions?