SummerOfCode/2013/newMemoryPage/week3: Difference between revisions
| Line 5: | Line 5: | ||
The moment that became clear, I knew that it had to be a bug -- there was just no other explanation. And so the report was duly [http://bugzilla.mozilla.org/show_bug.cgi?id=893193 filed], and the other developers seem to agree -- this behavior is not by design. The SDK should not impose the strict mod on any and all embedded content in the target HTML file. | The moment that became clear, I knew that it had to be a bug -- there was just no other explanation. And so the report was duly [http://bugzilla.mozilla.org/show_bug.cgi?id=893193 filed], and the other developers seem to agree -- this behavior is not by design. The SDK should not impose the strict mod on any and all embedded content in the target HTML file. | ||
Although this | Although this behavior got me to explore the amazing power of the contentScript and contectScriptFile functionality of the SDK, so thumbs up for that! It turned out to be really useful, and resulted in the addon structure being very well sorted, and readable. I have managed to reduce the main script to the essential chrome calls, and the rest has been transferred to a module that solely interacts with D3. Very neat! | ||
Revision as of 22:32, 4 August 2013
End of Week 3: Report
Although the calender disagrees, I seem to feel that an eternity has passed since I first started trying to get D3 to work inside the SDK. I just could not get away from the fact that the library itself was showing errors when compiled with the SDK. It is a dark day when you need to edit a whole library to get it to run, when it works like a charm for so many others. Although I did spend a few hours trying to edit the library, I quickly decided that this could not be the answer. So I delved deeper, and found that the problem lay with the Jetpack SDK itself -- the code embedded within an HTML file was being subjected to the 'strict' mode of JavaScript.
The moment that became clear, I knew that it had to be a bug -- there was just no other explanation. And so the report was duly filed, and the other developers seem to agree -- this behavior is not by design. The SDK should not impose the strict mod on any and all embedded content in the target HTML file.
Although this behavior got me to explore the amazing power of the contentScript and contectScriptFile functionality of the SDK, so thumbs up for that! It turned out to be really useful, and resulted in the addon structure being very well sorted, and readable. I have managed to reduce the main script to the essential chrome calls, and the rest has been transferred to a module that solely interacts with D3. Very neat!