Skip to Content
author's profile photo
Former Member

the difference between Custom controllers and Component Controller

Thanks to all i have known about it

Message was edited by: jian sun

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Best Answer
    author's profile photo
    Former Member
    Oct 06, 2005 at 12:18 PM

    Hello Jian,

    The difference between the two is nicely explained in the following thread:

    Component and custom controllers

    and here too:

    custom controller vs component controller

    Cheers,

    Dharmi

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Oct 06, 2005 at 12:23 PM

    Hi,

    controller is the Object which has all the logic.

    Now the Component controller is the controller which has all the the logic of the compnent (may be for the corrodination of the objects in the component).

    and custom controller is created by the user. and will be used for specific purpose.

    Regrads

    Divyakumar

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Oct 06, 2005 at 12:33 PM

    Thanks Jian for the points 😊

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Oct 06, 2005 at 12:35 PM

    Hi,

    the most important thing about controllers are their contexts. A context is, simply spoken, a bucket holding some data. The data is organized in context nodes/elements showing a simple parent/child hierachy. UI elements are bound to these contexts, i.e. if you want your UI text field to show a certain (dynamic) string, just bind it to a context element holding that string. There exists kind of a hierarchy of contexts, beginning at the model (which behaves to the outside like a context), then the custom controller (only once per WD component) and at last the view contexts (once per WD view). They can be bound together, transporting a string from the model, through the customer controller, to the view controller to the UI element (you can use of cource less if you like to, but e.g. a model has the advantage of being reusable within many WD components).

    Custom controllers are not bound to any of these levels. They are used to structure the context and source code as the developer likes to, i.e. where WD defines that there exists only one customer controller per component and one per view you can build your own hierarchy of contexts (including source code separation) with customer controllers. IMHO, there is nothing more to them.

    Regards,

    Vedran

    Add comment
    10|10000 characters needed characters exceeded