Skip to Content
author's profile photo Former Member
Former Member

Communication between interface view and specific view


I would like to know if it is possible to pass the parameters received by an inbound plug in the Interface view to a specific view.

For example, I have two components A and B. View in component A has an outbound plug and a link to the inbound plug of the interface view of B. Currently, the default view of B appear when the plug is fired. I may pass parameters from the view A to the interface view of B, but I did not figure out how to communicate those parameters directly to the default view.

Of course, I can use the Component Controller to get/set the information in the context, but I wonder if there is a better way to do this?

Finally, is it possible to link an outbound plug of an interface view to an inbound plug of a specific view (in the same component).

Thanks in advance,


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jun 01, 2004 at 01:05 PM

    Ok, I just found a way to propagate parameters received through the inbound plug of an interface view.

    I fire an event (with parameters) from the component controller and one of my view is registered to handle this event. I can now propagate the parameters in a way that seems clean to me.

    Since the view is created before the code of the interface view is executed, this works.

    Is it the good way to do this?

    I would also like to know if it is possible to create (initialize) a view without using declarative plug?



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Barthelemy,

      as you've already noticed, views or more precisely View controllers are different to handle, since they are not directly accessible as all other controller types.

      So, you've the following possibilities to transport data from another controller A to a View controller V:

      1. Via context mapping from V to A.

      2. Via direct programmatic access of the context of A by V.

      3. Via Eventhandlers (including parameters) of V registered at A.

      4. Via declaration of methods in A, which return the required data and are called by V.

      5. Via Inbound Plugs of V linked to Outbound plugs of A, if A is another View or InterfaceView controller.

      There's no general answer what is better or worse. This depends on current application scenario and, well, what you like most. I prefer 1. and 3. (4. in case of communication between View controllers).

      And yes, there are ways to create and navigate views manually, but they are not supported by the API, only for internal use.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.