new look Architecture & Concepts

1. newlook Architecture & Concepts • In this presentation… • About newlook’s architecture. • Basic newlook configuration and startup information. • newlook concepts Overrides and Screen IDs.

2. newlook Architecture & Concepts • Architecture • Dynamic architecture • newlook Design Repository • newlook Recognition Engine • Configuration • Settings • Connections • Rules • Concepts • Overrides • Screen ID • Identify • Designer

3. Architecture • Dynamic Architecture • newlook operates within a dynamic "real-time" environment where System i screen conversions occur "on-the-fly". The dynamic graphical interface is generated instantly based on the execution time state of the host application and custom newlook rules. • This just-in-time process allows you to generate web or desktop based applications much faster than batch based alternatives.

4. Architecture • How does newlook work? • newlook analyzes the green screen image (emulator) generated by your System i application – not the underling code. newlook then applies a series of changes or overrides to generate the newlook UI. • No access or modification to source code is required. newlook will work with any System i application – even if you don’t have access to the source. • You can use newlook’s development tools to add to, or change the default settings.

5. Architecture • Recognition Engine • newlook’s recognition engine uses pattern matching components to analyze the 5250 System i data stream. • The recognition engine classifies each System i screen element into a particular category based on settings defined by IBMs CUA design guidelines, and customized changes created using newlook. • If your application differs markedly from IBMs CUA design guidelines, you will need to use newlook’s development tools to create a series of changes or overrides to assist recognition. • CUA guidelines: http://publib.boulder.ibm.com/pubs/html/as400/online/v4r4eng.htm • Design Repository • newlook’s design repository (.sid file) along with the .ini file store all custom changes applied to the newlook UI.

6. newlook Configuration newlook UI nl.exe .ini Shared.sid System i screen User.sid

7. newlook Configuration - Starting newlook • nl.exe • Double-click the nl.exe to start newlook. • nl.exe references the .ini and .sid files • nl.exe, .sid and .ini are the 3 main ingredients used in generating the newlook UI. • .ini and .sid apply custom changes to newlook. • Command line arguments • INI File specification -i<FileName> • E.g. –iacme\acme.ini • Connection (-c<ConnectionName>) • E.g. –cAcme • Start macro (-r<MacroName>) • E.g. -rAcmeWelcome • Display mode etc. (-vr : allows GUI view only) **Windows client: specified in the properties of a shortcut pointing to nl.exe **Web client: specified in html file

8. newlook Configuration - Starting newlook • .ini File • Used to establish environment. • Require one per user. • Stores newlook settings. newlook UI .ini Shared.sid System i screen User.sid

9. newlook Configuration - Settings • Global environment settings • Used on startup to establish newlook UI preferences. • Settings are used to customize the look and feel of the newlook generated interface. You can customize anything from basic font and color display through to the appearance of the menu. Options include: • General • Display • Keyboard • Commands • Preferences • Settings are stored in the .ini file • Repositories • References the Shared.sid • References the User.sid

10. newlook Configuration - Settings • General tab • Use the Generaltab to specify: • The file location for your repository file, including both the shared and user sid files. • A common username and password that can be used for all connections. • Display • Appearance: • Customize look and feel of your application. 28 categories in all. • Background: • Customize background graphic or color etc. • Menus: • Customize menu look and feel, e.g. numbers or bullets etc.

11. newlook Configuration - Settings • Keyboard • Customize keyboard shortcuts. • Command • Specify command history recall options. • Preferences • Splash screen on/off. • Confirmation dialogs on/off. • Etc.

12. newlook Configuration - iSeries Connections • Connection settings • Used in accessing your System i application. • Connection settings determine how newlook initiates display, printer and file transfer connections between newlook and your System i application. The connection settings specify: • General • Name • Connection type (single or group) • TCP/IP address • Internet address, e.g. 192.168.1.2 • Session type, e.g. display or printer etc. • Printer settings • Host Print Transform vs SCS. • Connections are stored in the Shared or User.sid file

13. newlook Configuration - iSeries Connections • FTP • Anonymous sign in • Passive firewall • Security settings • Anonymous sign in • Passive firewall • Regional settings • Language & Currency options • Signon settings • Specify username & password • Connections are stored in the Shared or User.sid file

14. newlook Configuration - Starting newlook • Sid files • Sid files store all newlook metadata. All information is stored in a "ready-to-execute" state and is located on the server or the client. Information stored in the sid file, includes: filters, macros, variables, button commands, and screen overrides. The two types of sid files available are: • Shared repository (.sid) • Global settings • Connections • Rules • Overrides • Macros • User Repository (.sid) • Personalized settings • Connections • Macros Shared.sid User.sid

15. newlook Configuration - Starting newlook • Global rules • newlook Rules are automatically applied to individual System i screens upon establishing a connection. • Rules are primarily filter based mechanisms designed to provide system-wide changes to the newlook generated interface. Rules are also used to configure smartclient users' access rights plus specification of shared and local sid files. Configurable Options include: • General rules • Policies • Categories • Filters • Subfiles • Check Fields • Borders • Combo Fields • Rules are stored in the Shared.sid file

16. newlook Concepts • Overrides • Overrides refer to dynamic changes applied to newlook's automatically generated interface (GUI). Interface changes or overrides are made using Identify and Designer. • Overrides are applied instantly to System i screens on establishing a connection. • Overrides are most commonly required for: • IBM CUA non-compliant applications. • Application extending, e.g. new forms and buttons. • Specialized customization, e.g. screen-specific backgrounds, logos or pictures. • Screen ID • Important newlook concept. Used to designate which screens to apply which Identify and Designer based overrides. • Identify • Overrides used to assist recognition of 5250 data stream. • Designer • Overrides used to customize look and feel of generated newlook UI. • Overrides are stored in the shared.sid file.

17. newlook Concepts • Screen ID • The screen ID is a special category used to identify one or more host application screens. Note: The screen ID is very important to the refacing process – we’ll cover more information on this in the next presentation. • Key to recognition • Any character • Any attribute byte • Do not use transient data, e.g. date/time. • Applied using Identify

18. newlook Concepts • Identify overrides • 5250 recognition • Category overrides • Visual clues

19. newlook Concepts • Designer overrides • GUI modification • Visual development tool • Layering • Develop in lowest resolution • Object orientated • Event driven

20. newlook Concepts • Macros • A set of one or more actions that perform a particular action, e.g. open a new form or window. Macros are used to automate common tasks. • newlook’s programming language • centric has support for scripting in VBScript and JScript • Actions • Parameters • Labels • Conditions • A condition is a logical expression. A macro may follow different paths depending on whether the condition is True or False. • Macros are stored in the shared or user.sid file.

21. Summary • newlook operates within a dynamic environment. • newlook analyzes the System i “green screen” image, not the underlying source code prior to generating the newlook UI. • newlook stores all customized changes or overrides in the .ini or .sid files. The sid file is also known as the Design Repository. • On startup, newlook references information from the .ini. and .sid files. These files contain a combination default settings based on IBMs CUA design guidelines and custom changes created using newlook development tools. • Changes made using Identify, Designer and the Macro Editor are called overrides, and dynamically change the look and feel of the generated newlook UI.

22. Workshop 2 newlook 8 Training