[TIMOB-9348] MobileWeb: Rearchitect how annotations are stored internally
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-06-15T13:22:03.000+0000 |
|---|
| Affected Version/s | Release 2.0.1 |
|---|
| Fix Version/s | Release 2.1.0, Sprint 2012-12 MW |
|---|
| Components | MobileWeb |
|---|
| Labels | n/a |
|---|
| Reporter | Chris Barber |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2012-06-02T16:16:38.000+0000 |
|---|
| Updated | 2017-03-03T23:29:55.000+0000 |
|---|
Description
Annotations are currently stored in an array. If an annotation is removed, the array element is nulled, but not removed. If you add and remove annotations a lot, the array becomes too big. Plus the annotations array is gettable with all those nulls. Adding a hash to lookup annotations by title and splicing annotations out of the array should solve the problem
Attachments
| File | Date | Size |
|---|
| app.js | 2012-06-15T13:04:26.000+0000 | 3011 |
Pull request: https://github.com/appcelerator/titanium_mobile/pull/2409
Closing ticket as MobileWeb is no longer supported.