This page (revision-11) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 6 KB JMyers to previous
10 26-Nov-2021 10:22 6 KB JMyers to previous | to last
9 26-Nov-2021 10:22 6 KB JMyers to previous | to last
8 26-Nov-2021 10:22 6 KB JMyers to previous | to last
7 26-Nov-2021 10:22 6 KB JMyers to previous | to last
6 26-Nov-2021 10:22 6 KB JMyers to previous | to last
5 26-Nov-2021 10:22 6 KB JMyers to previous | to last
4 26-Nov-2021 10:22 6 KB JMyers to previous | to last
3 26-Nov-2021 10:22 6 KB JMyers to previous | to last
2 26-Nov-2021 10:22 6 KB JMyers to previous | to last
1 26-Nov-2021 10:22 6 KB JMyers to last

Page References

Incoming links Outgoing links
SELF SERVICE 2.0
SELF SERVICE 2.0

Version management

Difference between version and

At line 25 changed one line
The former Self-Service layout was “liquid” as it would stretch or contract to fit the dimensions of the browser window. Various browser-sizes and screen resolutions often cause issues in such layouts including unwanted wrapping of web objects or over-expanded text-areas. \\
The former Self-Service layout was “liquid”, meaning it would stretch or contract to fit the dimensions of the browser window. Various browser sizes and screen resolutions often cause issues in such layouts including the unwanted wrapping of web objects or over-expanded text areas. \\
At line 28 removed one line
800x600 1024x768 1280x1024 \\
At line 30 changed 2 lines
Browser Compatibility and following Web Standards actually go hand-in-hand. In order to be compatible with Mozilla FireFox 2, all HTML, CSS and JavaScript had to conform to current Web Standards. \\
The process of ensuring browser compatibility also involved making the layout completely frameless and replacing all HTML TABLE elements with DIV and SPAN elements. In addition, all HTML is completely styled using CSS ensuring a clear separation between style and content. \\
Browser compatibility and following Web Standards actually go hand-in-hand. In order to be compatible with Mozilla FireFox 2, all HTML, CSS and JavaScript had to conform to current Web Standards. \\
The process of ensuring browser compatibility also involved making the layout completely frameless and replacing all HTML TABLE elements with DIV and SPAN elements. In addition, all HTML is completely styled using CSS to ensure a clear separation between style and content. \\
At line 33 changed one line
Mozilla FireFox Microsoft Internet Explorer
!!Remove the FRAME but Keeping the Functionality
It is also worth mentioning that although we didn’t want to work with Frame elements we wanted to keep the Frame functionality as it is very convenient to keep the application header static. \\
The content area sizes and re-sizes itself dynamically relative to the height of the browser window to ensure that the full height of the browser window is utilized. This is best illustrated by viewing the layout in the three different resolutions in the previous section. In all 3 images, we see the content area dynamically sized relative to the browser window and never see the vertical scroll bar for the browser window, which allows the user to scroll through a form or splash menu but always keep the application header in view.
At line 35 removed 4 lines
!!Ditching the FRAME but keeping the functionality
It is also worth mentioning that although we didn’t want to work with FRAME elements we wanted to keep the FRAME functionality as it is very convenient to keep the application header static. \\
The content area sizes and re-sizes itself dynamically relative to the height of the browser window to ensure that the full height of the browser window is utilized. This is best illustrated by viewing the layout in the 3 different resolutions in the previous section. In all 3 images, we see the content area dynamically sized relative to the browser window and never see the vertical scroll bar for the browser window, which allows the user to scroll through a form or splash menu but always keep the application header in view.
This page (revision-11) was last changed on 26-Nov-2021 10:22 by JMyersTop