Interface View Controller

[Former Member]

Hi Experts,

Can anyone explain me what is the purpose Interface View Controller?

And the difference between Interface Controller and Interface View Controller?

Regards,

Imtiyaz

[Former Member]

hi

pls refer to the explanation by Chandran Subramanian in the thread

link:[;

regards,

amit

[Former Member]

Hi,

Please check this:

http://help.sap.com/saphelp_nw04/Helpdata/EN/04/43f00d8f027746a1e23267f22e8c71/content.htm

Regards,

Nagaraju

[Former Member]

Hi ,

Interface view controller - This is nothing but the represnetation of you window.You can implement any features you requirs with a web dynpro window on this.For example you need to navigate from one window to the other using plugs (just like you would have done fron one view to the other) you define plugs on interface view.

Interface controller- If one component controller is added into another as used component then interface controller has a role.Only methods and context in the interface contoller can be accessed by the external controller that has defined a usage type.

Regards,

Ashok

[Former Member]

Hi,

Interface controller

Used to control access from other components.

Is created automatically when a component is created.

Exists as long as its component is embedded in another

component.

This controller contains data, methods, and events that can be used by other Web Dynpro components.

A componentu2019s interface controller can be used by the embedding component for mappings, eventing, etc.

Interface for external users of a component: data transfer,

eventing.

Interface Controller

One Web Dynpro Component may declare the use of another Web Dynpro Component to form a u201CParent-Childu201D usage relationship. In such cases, the only point of interaction between the parent and child components is the functionality found in the childu2019s interface controller.

View controller

Each view consists of the layout part and exactly one view controller. This controller cares for view-specific flow logic, like checking user input and handling user actions. The instantiation of a view controller is delayed until the first method of the controller is called. The lifetime of a view controller can be controlled by the views properties. If framework controlled is selected, the view instance will be deleted with the component. If when visible is selected, the view instance is deleted as soon as the view no longer belongs to the view assembly.

Regards,

Sunaina Reddy T

[former_member192434]

Hi

InterfaceConterlloer - To transfer/ expose the data (through context) and to exposte the methods to another WDComponent.

The context of a view differs from the contexts of other controllers by its restricted visibility. Nodes and attributes that you create within a view context can only be used there, whereas the context elements of other controllers can be used for the cross-view data transport through binding to several other contexts. Data can even be transported across components using the interface controller

View Controllers are visual building block of a Web Dynpro component and are designed to handle all

aspects of data display and user interaction. Only view controllers have a visual interface. In order for a

view to be seen on the screen, it must be embedded into a Window

Thanks

[Former Member]

Hi,

The interface view Controller of a WebDynpro window is used to link a Window with a Web Dynpro application that can be called by the user.

The interface controller is used to share the context and methods to be accessed from other DC's when the component is exposed as a public part.

Hope this helps you..

Regards,

Saleem