Ticket #1663 (new defect)

Opened 22 months ago

Last modified 5 months ago

fix loader.js comments and function names

Reported by: bill Owned by: jburke
Priority: normal Milestone: 1.3
Component: General Version: 0.3
Severity: normal Keywords:
Cc:

Description (last modified by bill) (diff)

As per the recent discussion to call dojo.html a module and dojo.html.common a resource... the comments and function/variable names in loader.js need to be updated. Here's a partial list of suggested updates:

  • rename private functions to have _ in front of them
  • rename loaded_modules --> loaded_resources
  • rename startPackage --> startModule, or roll startPackage() code into dojo.provide(); unclear if a separate function is needed. in any case the comment for the function is confusing because it talks about creating javascript objects, which is more of an implementation detail than a guaranteed api. (contrast w/the comment for dojo.provide)
  • rename findModule -> findResource
  • loadPath - the comment should say it loads resources, or at the least, it shouldn't use the word "modules"
  • modulesLoaded - could be resourcesLoaded? should probably have an underscore
  • signature for addOnLoad/addOnUnload is better written as function(/*Object?*/obj, /*String|Function*/functionName). The first argument is optional and the second is mandatory.

Change History

Changed 22 months ago by bill

  • description modified (diff)

Changed 22 months ago by bill

See also #1544, basically a dup of this (but this bug shouldn't be closed because it has notes on the changes to make).

Changed 12 months ago by jburke

  • milestone changed from 0.9 to 1.0

This should have been done as part of the initial 0.9 code porting, but I missed it. I'm not comfortable making all of the changes this close to a 0.9 RC candidate, so I'm pushing to 1.0. Even though these are API changes they are mostly on things that are considered private. But still, may be too risky to do even then. I'll consult with others after 0.9 gets pushed out.

Changed 10 months ago by jburke

  • milestone changed from 1.0 to 2.0

Pushing this to 2.0, when we might have a chance to cause more disruption to the code.

Changed 5 months ago by alex

  • milestone changed from 2.0 to 1.3

Milestone 2.0 deleted

Note: See TracTickets for help on using tickets.