| |
|
| Changed, Enhanced, or Newly Deprecated Features |
Changed, Enhanced, or Newly Deprecated Features |
| |
|
| |
- There is now a 'storage.DMFor(class)' function that returns a configuration |
| |
key for registering or looking up data managers by class. You can use the |
| |
returned key in a binding's 'offerAs' list, or as the target of a 'bindTo()' |
| |
or 'lookupComponent()'. The key is constructed using |
| |
'config.ProviderOf(storage.IDataManager,class)'. |
| |
|
| |
- You can now register utilities that are keyed by the combination of an |
| |
interface and one or more classes, using 'config.ProviderOf(iface,*classes)' |
| |
as a configuration key. Providers are registered under an '(iface,klass)' |
| |
tuple for each specified class, and looked up using the MRO order of the |
| |
class specified for lookup. In other words, searching for a provider will |
| |
find a provider for the requested class, or one of its base classes, with |
| |
precedence given to the more-specific provider. This is primarily intended |
| |
for services like data managers and Specialists. |
| |
|
| - It's now possible to extend .ini file parsing with custom section types, |
- It's now possible to extend .ini file parsing with custom section types, |
| and PEAK defines its own built-in section types using this extension |
and PEAK defines its own built-in section types using this extension |
| mechanism. Custom section types must include at least one space, (e.g. |
mechanism. Custom section types must include at least one space, (e.g. |
| interfaces. |
interfaces. |
| |
|
| - When creating a 'PropertyName()', it's now possible to force conversion of |
- When creating a 'PropertyName()', it's now possible to force conversion of |
| invalid characters to '_', by supplying 'force=True'. This doesn't address |
invalid characters to '_', using the 'PropertyName.fromString()' |
| syntactic issues (like having a non-terminating '*'), or character sets |
constructor. (Note that the input must be a plain-ASCII string.) Unless |
| (non-ASCII characters are still rejected). But it's convenient for things |
you request that wildcards ('?' and '*') be kept, they will also be |
| like filenames or text that might contain spaces. |
converted to '_' characters. This can be convenient for converting things |
| |
like filenames or text that might contain spaces, to property names. |
| |
|
| - It's now possible to declare an attribute as offering a wildcard property; |
- It's now possible to declare an attribute as offering a wildcard property; |
| such lookups now follow the same rules as other wildcard property lookups. |
such lookups now follow the same rules as other wildcard property lookups. |
Diff of /PEAK/CHANGES.txt
Parent Directory
| 
Revision Log