GUI and Web Frameworks

In Silverlight and WPF, a Storyboard is a specialized class used to control animations using a timeline, specifying property targeting details for child animations. It is not a generic GUI control, video player, or an AJAX utility.

MVVM (Model-View-ViewModel) is the most appropriate design pattern for Silverlight development. It separates the UI (View) from business logic (Model) using a ViewModel that leverages Silverlight's data binding and command infrastructure. MVC and MVP are less suited to Silverlight's data-binding-centric architecture.

Silverlight applications support multiple service types: traditional ASMX Web Services, WCF (Windows Communication Foundation) Services for advanced SOA scenarios, and WCF RIA Services specifically designed for Silverlight business applications. All three are valid approaches depending on requirements.

Silverlight's key advantage is being cross-platform - it runs on Windows, Mac, and was available for Linux (Moonlight) through a browser plugin, enabling consistent experiences across operating systems. While development is relatively easy and memory usage is reasonable, cross-platform reach is the primary differentiator.

The Unity Application Block is a lightweight, extensible dependency injection (DI) container that supports constructor, property, and method call injection. It helps manage object lifecycles and dependencies, promoting loose coupling and testability. It does not directly manage memory or increase performance - those are side effects of good architecture.

In the Java AWT (Abstract Window Toolkit) hierarchy, the Applet class directly extends Panel. The full inheritance chain is: Object -> Component -> Container -> Panel -> Applet. Panel is the immediate superclass, not Frame, Window, or the abstract AWT class itself.

In Android, users add widgets to their Home screen by touching and holding an empty area on the Home screen or an app icon, which opens the widget selector menu. Home button and sliding do not trigger the widget picker.

Android widgets include bounding boxes (for touch/interaction areas), frames (structural containers), and graphical controls (buttons, text fields, etc.). A menu is typically a separate UI component, not considered a widget itself.

Implementing a custom widget requires a Java/Kotlin file to define behavior, an XML metadata definition file to specify widget properties, and an XML layout file to define the user interface. HTML is not used for standard Android widgets.

AppWidgetProvider, AppWidgetProviderInfo, and AppWidgetManager are the essential Android classes used to define, configure, and manage App Widgets. AppWidgetDialer is a made-up class name and not part of the Android framework.

App Widgets are mini-application views that can be embedded in other applications, most commonly the Home screen. They provide users with quick, glanceable updates and basic control over application features directly from the launcher interface, bypassing the need to launch the main activity.

In Apache Wicket, each component is responsible for handling its own events through listeners and event handlers. This is a core principle of Wicket's component-based architecture where components encapsulate both state and behavior. True is the correct answer.

Apache Wicket's main features include its component-based architecture where you build pages from reusable components, separation of pure Java code and pure HTML templates (no special tags needed), and automatic state management across requests. Option B is incorrect because not all framework classes are interface-based - Wicket uses concrete classes extensively for practical implementation.