Bug 26272 Add _$ to list of prefixes for field getter/setter creation [code manipulation]
A common convention is to use _ for instance variables and _$ for static instance variables. Although _ will be stripped by default, it would be useful if _$ was also in the list. Of course, this is settable for individual users (which I've already done) but since it is not an uncommon coding convention (and won't harm anyone in general if present) then I would vote for it to be added to the getter/setter generation prefixes.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java
*/
	public static final String BROWSING_LINK_VIEW_TO_EDITOR= "org.eclipse.jdt.ui.browsing.linktoeditor"; 
	/**
	 * A named preference that controls the layout of the Java Browsing views vertically. Boolean value.
	 * <p>
	 * Value is of type <code>Boolean</code>. If <code>true<code> the views are stacked vertical.
	 * If <code>false</code> they are stacked horizontal.
	 * </p>
	 */
	public static final String BROWSING_STACK_VERTICALLY= "org.eclipse.jdt.ui.browsing.stackVertically"; 
	
	
	/**
	 * A named preference that controls if templates are formatted when applied.
	 * <p>
	 * Value is of type <code>Boolean</code>.
	 * </p>
	 *
	 * @since 2.1
	 */	
	public static final String TEMPLATES_USE_CODEFORMATTER= "org.eclipse.jdt.ui.template.format"; 
	
	
	public static void initializeDefaultValues(IPreferenceStore store) {
		store.setDefault(PreferenceConstants.EDITOR_SHOW_HOVER, true);
		store.setDefault(PreferenceConstants.EDITOR_SHOW_SEGMENTS, false);
		
		store.setDefault(PreferenceConstants.LINK_PACKAGES_TO_EDITOR, true);
		store.setDefault(PreferenceConstants.LINK_TYPEHIERARCHY_TO_EDITOR, false);
		store.setDefault(PreferenceConstants.LINK_BROWSING_VIEW_TO_EDITOR, true);