Custom Query (18300 matches)
Results (46 - 48 of 18300)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#63 | fixed | unify and rationalize utility namespaces | ||
Description |
As per today's discussion, dojo.xml.domUtil and dojo.xml.htmlUtil need to be moved up to dojo.dom and dojo.xml respectively. Aliasing should be accomplished in the manner described earlier. Other utility namespaces should be considered for consolidation and rationalization. For instance, dojo.alg and dojo.lang may be consolidated into dojo.util. Additionally, graphics and animation namespaces might be normalized. Please comment in this bug to list all of the proposed changes. |
|||
#64 | fixed | build tools need to create per-package rollup files in addition to root package files | ||
Description |
Today, it is onerous and/or penalizing to use dojo via <script /> tags. After discussing the problem in some depth with David, we have decided that the build system needs to be extended/fixed to automatically build "sub-directory rollup" files which is something the package system is already designed for. Additionally, these files should be preceeded by dependency checking code which uses document.write() to add <script /> blocks for including per-module dependencies. The end goal is to allow less-clued developers to include the parts of Dojo that they want in a coarse-grained way using only <script /> tags. |
|||
#65 | fixed | dojo.io.bind should honor method over formNode | ||
Description |
If you pass a method value (i.e. GET, POST) to the object passed to dojo.io.bind it should override the method on the formNode if a formNode is passed. |