
The advantage being I pretty much don't have to write module stuff again, just tweak the file names and class names

Cross-window background code... Ideas/Explanation?
36 posts
• Page 3 of 3 • 1, 2, 3
hmm, am I the only person to be crazy enough to write the module loader code in an external file, and use the JS subscript loader to dynamically load in my actual component implementations?
![]() The advantage being I pretty much don't have to write module stuff again, just tweak the file names and class names ![]() poot.
I've thought about doing this. What I would really like to do is use the javascript loader only when the nsIFactory createInstance is called, so that the files are loaded lazily when the class is created. On a side note, I've started to put together an example of creating javascript xpcom objects in the knowledge base, but it isn't finished yet. My Extensions:
<a href="http://forecastfox.mozdev.org">Forecastfox</a> <a href="http://tipbar.mozdev.org">Tip of the Day</a> <a href="http://urlnav.mozdev.org">Location Navigator</a> <a href="http://finder.mozdev.org">Finder</a> <a href="http://rsszilla.mozdev.org">RSSzilla</a> I'm not sure I understand that... what's the difference between a "function call" and a "method call"?
And how exactly would I get around it in the service code? I'm declaring a function and a function prototype, so I don't actually *have* an object to pass or reference anywhere... Yes, it's great that you're doing it.
I moved the page to http://kb.mozillazine.org/Implementing_ ... JavaScript though - we have decided to switch off the older naming scheme quite a while ago. Daniel_Orner: let's take it to a separate thread, ok? (And please describe the situation again there)
36 posts
Page 3 of 3 • 1, 2, 3
Return to Extension Development Who is onlineUsers browsing this forum: No registered users and 3 guests |
![]() |