Bug 26009 - Perference page classes loaded too soon
Summary: Perference page classes loaded too soon
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.1 M4   Edit
Assignee: Martin Aeschlimann CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2002-11-11 19:02 EST by Jeff McAffer CLA
Modified: 2002-11-18 13:08 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2002-11-11 19:02:05 EST 
When the JDT UI plugin is started, all of the JDT preference page classes are 
loaded. Apparently this is done to initialize the preferences but the result is 
100's of KB of code that it loaded and likely not needed (the implementaiton of 
the preference page UI) unless the user hits the preference page.
Comment 1 Erich Gamma CLA 2002-11-13 06:23:19 EST 
we should move the static preference initialization methods from the preference 
pages into the Java plugin.

		JavaBasePreferencePage.initDefaults(store);
		AppearancePreferencePage.initDefaults(store);
		ImportOrganizePreferencePage.initDefaults(store);
		ClasspathVariablesPreferencePage.initDefaults(store);
		RefactoringPreferencePage.initDefaults(store);		
		CodeFormatterPreferencePage.initDefaults(store);
		CompilerPreferencePage.initDefaults(store);
		
		PackageExplorerPart.initDefaults(store);
		JavaEditorPreferencePage.initDefaults(store);
	
		TemplatePreferencePage.initDefaults(store);		
		CodeGenerationPreferencePage.initDefaults(store);
		JavadocPreferencePage.initDefaults(store);
		NewJavaProjectPreferencePage.initDefaults(store);
		MembersOrderPreferencePage.initDefaults(store);
Comment 2 Martin Aeschlimann CLA 2002-11-18 13:08:07 EST 
moved all preference constants + initialization code to PreferenceConstants