Community
Participate
Working Groups
We have a bunch of copied code right now across the various pages' "glue" code that initializes the service registry and defines the services. We need to figure out how this should really work.
Sorry Susan, I feel responsible for not cleaning up this mess. I want to target end of next week to sort this stuff out better.
Moving bugs targeting past milestones...
This is a slight tangent, but is something that should be done as part of cleaning up our page load story. From http://dev.eclipse.org/mhonarc/lists/orion-dev/msg00366.html JJB says: >My embedding of coding.html suffers from timing problems. >I wire up to the page on web page "load", but I guess that coding.html >is using 'load' to configure the page. If I get called first I lose. We need to have a page load sequence so that we know we do stuff like: 1 - initialize the registry and services 2 - load the stuff specific to the page 3 - signal that we are done doing all of our work so that an embedding page can know everything is there I'm not sure that #1 even requires the DOM to be loaded. I know there is plenty of garden-variety stuff in #2 that needs the DOM loaded, so we probably do need to define some common event for the end of #2.
*** Bug 334218 has been marked as a duplicate of this bug. ***
We cover the basic first time load case now. For m8 I'd like to use this bug to further formalize the approach.
Fixed. We've moved all the plugin load / service registry initialize code to bootstrap.js and fixed inconsistencies so now all pages will load properly the first time and pick up changes correctly. The bootstrap still needs some work around preferences initialization but that is captured in another bug. -- Mark reviewed and tested this change with me.
