Opened 13 years ago

Closed 10 years ago

#7685 closed defect (invalid)

Suggestions for improving build system usability

Reported by: James Burke Owned by: Rawld Gill
Priority: low Milestone: 2.0
Component: BuildSystem Version: 1.2beta
Keywords: Cc: Rawld Gill
Blocked By: Blocking:


A ticket to hold suggestions to consider for Dojo 2.0 for the build system, to make it easier to understand and to avoid errors. These changes will likely need to be considered as part of Dojo 2.0, since the changes may not be 1.x compatible.

Started from this forum thread:

To start:

1) Try to normalize paths so profiles do not have a mix of ../.. and ../ paths. Maybe solve this by having the layer name be a resourceName and not a file path. We need resourceNames anyway, because otherwise the i18n bundle loading for the layer will not work. So switching to a "dot" name ("") instead of specifying "../foo/bar.js" would be good. For "dojo.js" the name would be just "dojo".

Then it could automatically put in a dojo.provide call for the layer if there was not already one that matches, and we avoid the need for either "name" or "resourceName" extra layer property. Need to decide which one is clearer to use.

Other things can be added to this ticket as we think of them.

Change History (4)

comment:1 Changed 11 years ago by bill

Can we close this now, since the AMD loader is in place?

comment:2 Changed 10 years ago by ben hockey

Cc: Rawld Gill added
Priority: highlow
Status: newpending

I agree with closing this.

If there's no further comments the ticket will automatically close in 14 days.

comment:3 Changed 10 years ago by bill

Owner: changed from James Burke to Rawld Gill

Bulk update to assign BuildSystem? tickets to Rawld. Many of these are probably already fixed in 1.7.

comment:4 Changed 10 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.