Unity Scopes API
|
Renaming of various API elements for consistency and clarity:
PreviewWidget::add_attribute() -> PreviewWidget::add_attribute_value() PreviewWidget::attributes() -> PreviewWidget::attribute_values() PreviewWidget::add_component() -> PreviewWidget::add_attribute_mapping() PreviewWidget::components() -> PreviewWidget::attribute_mappings()
ActivationListener -> ActivationListenerBase ActivationListenerBase::activation_response() -> ActivationListenerBase::activated()
PreviewListener -> PreviewListenerBase
SearchListener -> SearchListenerBase
PreviewQuery -> PreviewQueryBase
SearchQuery -> SearchQueryBase
ActivationBase -> ActivationQueryBase
ReplyBase -> Reply
RegistryBase -> Registry
Query -> CannedQuery CannedQuery::scope_name() -> CannedQuery::scope_id()
ScopeMetadata::scope_name() -> CannedQuery::scope_id()
Scope::create_query() -> Scope::search()
ScopeBase::create_query() -> ScopeBase::search()
SearchQuery::create_subquery() -> SearchQuery::subsearch()
Variant::Type: changed ordinal values of enumerators
The scoperegistry allows extra scopes to be added on the command line now:
$ scoperegistry some/path/Runtime.ini some/other/path/Fred.ini Joe.ini
This loads Fred and Joe scopes in addition to any scopes picked up via the normal configuration. If Fred or Joe appear in configuration as well as on the command line, the config file on the command line takes precedence. The .so for additional scopes is expected to be in the same directory as the corresponding .ini file.