Tapestry
  1. Tapestry
  2. TAPESTRY-1060

dojo config "parseWidgets: false" prevent tree widget.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.1
    • Component/s: JavaScript
    • Labels:
      None

      Description

      I find the Shell delegate produce the text:
      djConfig =

      { isDebug: true, debugContainerId:'debug', baseRelativePath:"http://localhost:8080/assets/static/dojo/", preventBackButtonFix: false, parseWidgets: false }

      ;

      the parseWidgets:false will prevent all widgets.
      I want to implement a tree widget.the config is wrong.

      I think can add a parameter parseWidgets in the AjaxShellDelegate.

        Activity

        Hide
        Jesse Kuhnert added a comment -

        Added new parseWidgets parameter to @Shell component.

        Show
        Jesse Kuhnert added a comment - Added new parseWidgets parameter to @Shell component.
        Hide
        Jun Tsai added a comment -

        yes.I use
        dojo.widget.createWidget("TreeLoadingController", $

        {id}prop, node);
        or
        tapestry.widget.synchronizeWidgetState("${id}

        ", "TreeLoadingController", $

        {id}

        prop);

        Show
        Jun Tsai added a comment - yes.I use dojo.widget.createWidget("TreeLoadingController", $ {id}prop, node); or tapestry.widget.synchronizeWidgetState("${id} ", "TreeLoadingController", $ {id} prop);
        Hide
        Jesse Kuhnert added a comment -

        The parseWidgets parameter isn't "wrong" in this sense, but I don't have a problem letting people shoot themselves in the foot if they want to. I'll update this to make it configurable.

        Really what you want to do is call dojo.widget.createWidget(node). This will parse the widget dynamically for a specific node, which is much faster than letting it traverse your entire DOM tree looking for nodes with dojoType attributes.

        Show
        Jesse Kuhnert added a comment - The parseWidgets parameter isn't "wrong" in this sense, but I don't have a problem letting people shoot themselves in the foot if they want to. I'll update this to make it configurable. Really what you want to do is call dojo.widget.createWidget(node). This will parse the widget dynamically for a specific node, which is much faster than letting it traverse your entire DOM tree looking for nodes with dojoType attributes.

          People

          • Assignee:
            Jesse Kuhnert
            Reporter:
            Jun Tsai
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development