GUI and Web Frameworks

window.open() is the correct method to open a new browser window. Option A uses window.new (doesn't exist), while C and D use 'new' incorrectly (new.open() and new.window() are not valid JavaScript).

Web Intelligence XI R3 introduced the ability to directly edit SQL queries, giving users more control over data retrieval. Interactive editing capabilities were also added to improve the user experience. Option B is incorrect because dimension merging is possible. Option D is false as .wqy documents are not supported in XI R3.

WinFX (Win-FX) was the codename for the .NET Framework 3.0 APIs, which included WPF, WCF, and Workflow Foundation. WWF later became Windows Workflow Foundation, WWP was not a Microsoft codename, and Silverlight was a separate web application framework.

In HTML forms, attributes like enable, form, name, type, and value are called properties that define element characteristics and behavior. They are not events (triggered actions), methods (functions), or elements themselves.

onBlur, onClick, and onFocus are JavaScript event handlers that trigger code when specific user interactions occur. These are events, not elements, properties, or methods.

JSF follows the Model-View-Controller architecture where the Model represents application data and business logic, the View is the presentation layer (JSF pages with UI components), and the Controller is the FacesServlet that manages request processing and lifecycle.

Netscape Navigator 2.0 beta was the first browser to support JavaScript in 1995. Microsoft Internet Explorer came later. Opera and HotJava were not the first to support JavaScript.

JavaScript 1.1 (in Netscape Navigator 3.0) was the first version to support the Image object, enabling image swapping and roll-overs. Version 1.0 had limited capabilities. The more advanced features came in later versions.

Flow, Grid, and Border are all standard base layout types used in portal systems for positioning portlets within a page. Flow layouts arrange components sequentially, Grid layouts use row/column positioning, and Border layouts place components in regions like north/south/east/west/center.

In portal architecture, 'books' control the navigation menus. Books contain pages and portlets, and their hierarchical structure defines the menu/navigation tree. Options A, B, and D are incorrect - pages display content, portlets are service components, and desktops are top-level containers, not menu controllers.

In Pega Portal architecture, pages are the containers that display portlets. A book contains pages, and a portal contains books. The desktop is the top-level container for the entire portal structure.

The desktop is the foundational container in Pega Portal architecture and must be created first. It serves as the top-level parent for all other portal elements - portals, books, pages, and portlets are added to it hierarchically.

Localization requires adapting an application for different regions and languages. Presenting UI in different languages (A), handling different currencies (B), and defining alternate business calendars (C) are all standard localization steps. Since all listed steps ARE involved in localization, there is no step among A-C that is NOT involved - making 'None of the above' correct.

Customizing the skeleton or structure of a portal requires JSP (JavaServer Pages) resources. JSP files define the HTML markup, layout, and structural elements that form the portal's framework. JavaScript handles client-side behavior, CSS manages styling, and XML is for configuration. The skeleton is the structural markup layer, which JSP provides.

Customizing the skin or visual appearance of a portal requires CSS (Cascading Style Sheets) resources. CSS controls colors, fonts, spacing, and all visual styling aspects. JavaScript handles interactivity, JSP manages structure, and XML handles configuration. Skin refers specifically to the visual presentation layer.