Difference: DpHipePreferences (19 vs. 20)

Revision 202010-06-10 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"

HIPE Preferences

Line: 47 to 47
  Therefore we don't consider system preferences, which are used by developers for introducing some flexibility in the functionality they provide, but users shouldn't be concerned of. The existing properties mechanism may still suffice for them.
Changed:
<
<
The preferences framework is decoupled from the old configuration properties, so that it could be developed while not being dependent on the property roadmap.
>
>
<-- The preferences framework is decoupled from the old configuration properties, so that it could be developed while not being dependent on the property roadmap.-->
  Nevertheless, preferences can reuse properties and even be just a wrapper for them if needed, as explained later. This way, the break is not dramatic, although replacing properties by preferences is encouraged.
Line: 71 to 71
  Preferences lie under a particular category. They are identified by a name called key, which must be unique within that category, but can be reused in other categories.
Deleted:
<
<
-- BrunoMerin - 25 Aug 2009
 The following set of HIPE preferences (mostly based on Eclipse/IDLDE's preferences) has been agreed upon as a starter to populate the HIPE preferences window:


Line: 413 to 410
 
Deleted:
<
<
-- JaimeSaiz - 23 Mar 2009
 
<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl