GUI and Web Frameworks

Solution packages in WSS/MOSS can deploy custom DLLs to GAC or Bin, apply web.config changes, install Features, and include resource files like images. These are the core deployment artifacts managed by the solution framework.

Application pages in SharePoint 2007 are stored in the LAYOUTS directory and are available farm-wide across all sites. They do not run in safe mode - that applies to site pages. Their accessibility spans the entire farm, not limited to a specific site scope.

To enable Create Page and Create Site options in a Team Site, you must activate the Office SharePoint Server Publishing Infrastructure at the site collection level and the Office SharePoint Server Publishing feature at the site level. These publishing features add the necessary content creation capabilities.

SPWebConfigModification is the correct SharePoint API class for programmatically modifying web.config files through the SharePoint object model. It provides safe, tracked modifications without manual file editing.

The number of days to show the 'New!' icon for list items can be changed using the STSADM command line tool with the 'setproperty' operation. This setting is not available through Central Administration UI or individual site collection settings.

SharePoint Designer workflows in SharePoint 2007 could only be associated with a single list or document library, not multiple lists or libraries simultaneously. Each workflow created in SharePoint Designer is bound to one specific list or library.

In SharePoint list definitions, Schema.xml contains the complete list schema including views, fields, forms, and other list elements. To add a new view to a list definition, you modify the Schema.xml file. Onet.xml defines site definitions and contains references to list templates, Feature.xml defines features, and Fldtypes.xml defines custom field types - none of these directly control list views.

In the SharePoint Object Model, SPSite represents a Site Collection and SPWeb represents a site (which can be the top-level site of a collection or a subsite). Therefore Site Collection = SPSite and Sub Site = SPWeb are the correct mappings. The inverse mappings are incorrect.

In SharePoint Publishing, Content Types and Page Layouts have a specific relationship: (A) Every Page Layout must be associated with a Content Type, and (D) Multiple Page Layouts can be created from the same Content Type. Option B is incorrect because a Page Layout can only be associated with one Content Type, and Option C is incorrect because Page Layouts cannot be created without an associated Content Type.

BorderLayout provides predefined constants (NORTH, SOUTH, EAST, WEST, CENTER) that specify where components should be placed within a container using a layout manager. Option A is incorrect because layout managers don't introduce new methods. Option C refers to applets, which are unrelated to layout management. Option D describes font and color attributes, not component positioning.

In SharePoint Object Model, Site Collections are represented by SPSite objects, and Sub Sites (webs) are represented by SPWeb objects. This is the correct mapping. Options B and D reverse these mappings, which is incorrect.

The relationship between Content Types and Page Layouts is: (A) A Content Type must be associated with a Page Layout (you can't create a layout without one), and (D) Multiple Page Layouts can be created using a single Content Type (you can create different layouts for the same content type). Page Layouts cannot be created without a Content Type.

BorderLayout is a layout manager in Java AWT that divides a container into five regions: North, South, East, West, and Center. The static fields (NORTH, SOUTH, EAST, WEST, CENTER) are constants used to specify where components should be added. It simplifies GUI positioning by providing predefined areas.

OLA Watcher provides a Filter button in the interface that allows users to filter displayed tickets based on various criteria. This is the standard UI pattern for filtering in this tool, accessed directly through a labeled button.

The Project Properties Window is where you would see a Categorized view or an Alphabetical View. This is different from the Tool Bar, Tool Box window, and Project explorer which serve different purposes in the IDE.