You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Greg Woolsey (JIRA)" <de...@tapestry.apache.org> on 2007/04/26 21:16:15 UTC
[jira] Created: (TAPESTRY-1430) Add searchIds parameter to Shell
component (passthrough to djConfig)
Add searchIds parameter to Shell component (passthrough to djConfig)
--------------------------------------------------------------------
Key: TAPESTRY-1430
URL: https://issues.apache.org/jira/browse/TAPESTRY-1430
Project: Tapestry
Issue Type: Improvement
Components: Core Components, Framework, JavaScript, tapestry-core, Web, XHR/dhtml/Ajax
Affects Versions: 4.1.1
Reporter: Greg Woolsey
Fix For: 4.1.2
The djConfig parameter "searchIds" provides a way to have Dojo automatically parse a known set of page widgets without enabling full automatic parsing (slow for performance reasons).
When an application has a component defined around the Shell component to provide common functionality (navigation, etc) and look-and-feel consistency across pages in an application, it would be nice to be able to specify a fixed list of client IDs for Dojo to parse for widgets rather than needing to instantiate them individually via JavaScript in the component.
For example, I just tested a page where our menu widgets (a TreeV3 and related controllers and selectors) are all defined inside a wrapper DIV with an ID of "menuControls". Adding this DIV ID to djConfig.searchIds allowed the menu to be parsed from the markup without needing to traverse the entire page or manually configure all the widgets involved in a tree via JavaScript.
This is especially useful when a hybrid tree instantiation fails because of a bug in Dojo - creating a TreeV3 widget via JavaScript from an existing DOM node with child nodes specifying tree node dojoType values fails because the tree widget domNode hasn't been appended to the document yet at the time the child nodes try to register.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1430) Add searchIds parameter to Shell
component (passthrough to djConfig)
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1430:
------------------------------------
Fix Version/s: (was: 4.1.2)
4.1.3
> Add searchIds parameter to Shell component (passthrough to djConfig)
> --------------------------------------------------------------------
>
> Key: TAPESTRY-1430
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1430
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components, Framework, JavaScript, tapestry-core, Web, XHR/dhtml/Ajax
> Affects Versions: 4.1.1
> Reporter: Greg Woolsey
> Fix For: 4.1.3
>
>
> The djConfig parameter "searchIds" provides a way to have Dojo automatically parse a known set of page widgets without enabling full automatic parsing (slow for performance reasons).
> When an application has a component defined around the Shell component to provide common functionality (navigation, etc) and look-and-feel consistency across pages in an application, it would be nice to be able to specify a fixed list of client IDs for Dojo to parse for widgets rather than needing to instantiate them individually via JavaScript in the component.
> For example, I just tested a page where our menu widgets (a TreeV3 and related controllers and selectors) are all defined inside a wrapper DIV with an ID of "menuControls". Adding this DIV ID to djConfig.searchIds allowed the menu to be parsed from the markup without needing to traverse the entire page or manually configure all the widgets involved in a tree via JavaScript.
> This is especially useful when a hybrid tree instantiation fails because of a bug in Dojo - creating a TreeV3 widget via JavaScript from an existing DOM node with child nodes specifying tree node dojoType values fails because the tree widget domNode hasn't been appended to the document yet at the time the child nodes try to register.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-1430) Add searchIds parameter to Shell
component (passthrough to djConfig)
Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou resolved TAPESTRY-1430.
---------------------------------------
Resolution: Fixed
> Add searchIds parameter to Shell component (passthrough to djConfig)
> --------------------------------------------------------------------
>
> Key: TAPESTRY-1430
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1430
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components, Framework, JavaScript, tapestry-core, Web, XHR/dhtml/Ajax
> Affects Versions: 4.1.1
> Reporter: Greg Woolsey
> Assignee: Andreas Andreou
> Fix For: 4.1.4
>
>
> The djConfig parameter "searchIds" provides a way to have Dojo automatically parse a known set of page widgets without enabling full automatic parsing (slow for performance reasons).
> When an application has a component defined around the Shell component to provide common functionality (navigation, etc) and look-and-feel consistency across pages in an application, it would be nice to be able to specify a fixed list of client IDs for Dojo to parse for widgets rather than needing to instantiate them individually via JavaScript in the component.
> For example, I just tested a page where our menu widgets (a TreeV3 and related controllers and selectors) are all defined inside a wrapper DIV with an ID of "menuControls". Adding this DIV ID to djConfig.searchIds allowed the menu to be parsed from the markup without needing to traverse the entire page or manually configure all the widgets involved in a tree via JavaScript.
> This is especially useful when a hybrid tree instantiation fails because of a bug in Dojo - creating a TreeV3 widget via JavaScript from an existing DOM node with child nodes specifying tree node dojoType values fails because the tree widget domNode hasn't been appended to the document yet at the time the child nodes try to register.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1430) Add searchIds parameter to Shell
component (passthrough to djConfig)
Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou reassigned TAPESTRY-1430:
-----------------------------------------
Assignee: Andreas Andreou
> Add searchIds parameter to Shell component (passthrough to djConfig)
> --------------------------------------------------------------------
>
> Key: TAPESTRY-1430
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1430
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components, Framework, JavaScript, tapestry-core, Web, XHR/dhtml/Ajax
> Affects Versions: 4.1.1
> Reporter: Greg Woolsey
> Assignee: Andreas Andreou
> Fix For: 4.1.4
>
>
> The djConfig parameter "searchIds" provides a way to have Dojo automatically parse a known set of page widgets without enabling full automatic parsing (slow for performance reasons).
> When an application has a component defined around the Shell component to provide common functionality (navigation, etc) and look-and-feel consistency across pages in an application, it would be nice to be able to specify a fixed list of client IDs for Dojo to parse for widgets rather than needing to instantiate them individually via JavaScript in the component.
> For example, I just tested a page where our menu widgets (a TreeV3 and related controllers and selectors) are all defined inside a wrapper DIV with an ID of "menuControls". Adding this DIV ID to djConfig.searchIds allowed the menu to be parsed from the markup without needing to traverse the entire page or manually configure all the widgets involved in a tree via JavaScript.
> This is especially useful when a hybrid tree instantiation fails because of a bug in Dojo - creating a TreeV3 widget via JavaScript from an existing DOM node with child nodes specifying tree node dojoType values fails because the tree widget domNode hasn't been appended to the document yet at the time the child nodes try to register.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1430) Add searchIds parameter to Shell
component (passthrough to djConfig)
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1430:
------------------------------------
Fix Version/s: (was: 4.1.3)
4.1.4
> Add searchIds parameter to Shell component (passthrough to djConfig)
> --------------------------------------------------------------------
>
> Key: TAPESTRY-1430
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1430
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components, Framework, JavaScript, tapestry-core, Web, XHR/dhtml/Ajax
> Affects Versions: 4.1.1
> Reporter: Greg Woolsey
> Fix For: 4.1.4
>
>
> The djConfig parameter "searchIds" provides a way to have Dojo automatically parse a known set of page widgets without enabling full automatic parsing (slow for performance reasons).
> When an application has a component defined around the Shell component to provide common functionality (navigation, etc) and look-and-feel consistency across pages in an application, it would be nice to be able to specify a fixed list of client IDs for Dojo to parse for widgets rather than needing to instantiate them individually via JavaScript in the component.
> For example, I just tested a page where our menu widgets (a TreeV3 and related controllers and selectors) are all defined inside a wrapper DIV with an ID of "menuControls". Adding this DIV ID to djConfig.searchIds allowed the menu to be parsed from the markup without needing to traverse the entire page or manually configure all the widgets involved in a tree via JavaScript.
> This is especially useful when a hybrid tree instantiation fails because of a bug in Dojo - creating a TreeV3 widget via JavaScript from an existing DOM node with child nodes specifying tree node dojoType values fails because the tree widget domNode hasn't been appended to the document yet at the time the child nodes try to register.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org