#5800 closed enhancement (fixed)
Allow segmented builds for memory constrained devices
Reported by: | James Burke | Owned by: | Rawld Gill |
---|---|---|---|
Priority: | low | Milestone: | 1.8 |
Component: | BuildSystem | Version: | 1.0 |
Keywords: | needsreview | Cc: | |
Blocked By: | Blocking: |
Description (last modified by )
Constrained devices like the iphone have hard file size limits for things like caching. The iphone seems to have a 25KB *ungzipped" size limit for keeping things in the cache.
Consider a segmentation option for the build that would:
- Specify limit size on segments
- Make sure segmented layer dojo.require's its other parts.
- Put in markers to know how to split up the layer after we do the shrinksafing, so we know where we can break it apart. The markers should be on a module file basis, since some modules use anonymous functions to use private variables.
Change History (5)
comment:1 Changed 13 years ago by
Description: | modified (diff) |
---|---|
Milestone: | 1.2 → future |
comment:2 Changed 9 years ago by
Keywords: | needsreview added |
---|---|
Priority: | high → low |
is this still something that we need to track in dojo?
comment:3 Changed 9 years ago by
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 9 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
"segmented builds" are now very possible, although deciding the segment partition must be explicit. Since we this ticket specifies no specific additional/still-relevant feature to implement, closing as fixes as of 1.7.
comment:5 Changed 9 years ago by
Milestone: | future → 1.8 |
---|
Bulk update for closed tickets marked as tbd/future. Presumably these should be marked as fixed in 1.8.
Now with the changes related to ticket #7119, it is now possible to more reliably reduce dojo.js into component pieces. So the process is a bit manual (you have to do some builds and see how big the layers get), but you can to something that will fit.
Marking this as "future", to consider doing the auto-partitioning.