-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] Load extensions before loading project, then fire APP_READY. #2385
Comments
Comment by dangoor I didn't see anything amiss here. It looks like a nice refactoring. I haven't had a chance to exercise it beyond firing up Brackets and having it run. I'll play around with some more features later on, but it's looking good. |
Comment by njx
|
Comment by njx (oops, meant "it's better to make inline comments in the "Files" tab"--other general comments can just go in Discussion) |
Comment by jasonsanjose Changes pushed. Ready for review |
Comment by dangoor
|
Comment by dangoor Looks good to me, and I just tested out a number of features and everything is working fine. I'll merge. |
Comment by njx Removing "for release note" label from this old pull request. |
Comment by njx Hmm. Apparently I can't remove the label, even from the summary view. Oh well. |
Issue by jasonsanjose
Wednesday Jan 09, 2013 at 22:35 GMT
Originally opened as adobe/brackets#2501
Fix for #1951
Change app initialization to load extensions first, then load the project and initialize the working set before firing the
APP_READY
event. Many thanks to@
DennisKehrig.While cleaning up the startup process, I opportunistically cleaned up a lot of startup code by deferring some initialization out of the module init (implicit and/or explicit) and into
APP_READY
andHTML_READY
handlers as appropriate.Unit, performance and extension tests are passing.
jasonsanjose included the following code: https://github.com/adobe/brackets/pull/2501/commits
The text was updated successfully, but these errors were encountered: