lumiera_/src/proc/mobject/session/scope-query.hpp
Ichthyostega e902757a14 (DRAFT) refactor the way how to retrieve the syntactic query representation
there can't be a callback from the base ctor;
instead the subclass must pass a QueryText definition
2012-12-29 00:31:24 +01:00

220 lines
6.6 KiB
C++

/*
SCOPE-QUERY.hpp - query to discover the contents of a container-like part of the model
Copyright (C) Lumiera.org
2009, Hermann Vosseler <Ichthyostega@web.de>
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of
the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
/** @file scope-query.hpp
** Specific queries to explore contents of a scope within the high-level model.
** This is an application of the QueryResolver facility, and used heavily to
** provide the various search and exploration functions on the session API.
** It is implemented by accessing a SessionService, which resolves the
** queries by iteration on the PlacementIndex behind the scenes.
**
** @see query-focus.hpp
** @see query-resolver.hpp
** @see scope-query-test.cpp
** @see placement-index-query-test.cpp
** @see PlacementIndexQueryResolver
**
*/
#ifndef PROC_MOBJECT_SESSION_SCOPE_QUERY_H
#define PROC_MOBJECT_SESSION_SCOPE_QUERY_H
#include "proc/mobject/placement.hpp"
#include "common/query/query-resolver.hpp"
#include <tr1/functional>
namespace proc {
namespace mobject {
namespace session {
using std::tr1::bind;
using std::tr1::function;
using std::tr1::placeholders::_1;
using lumiera::Goal;
using lumiera::Query;
/**
* ABC to build Queries for placement-attached objects.
* The Placements obtained from such a query are typed to the
* specific MObject type given as template parameter. To ensure
* this, an additional ContentFilter is applied on the yielded
* results; this filter function is constructed by a virtual
* call when actually issuing the query.
*/
template<class MO>
class DiscoveryQuery
: public Query<Placement<MO> >
{
typedef Query<Placement<MO> > _Query;
public:
typedef typename _Query::iterator iterator;
typedef function<bool(PlacementMO const&)> ContentFilter;
ContentFilter
contentFilter () const
{
return buildContentFilter();
}
protected:
/** yield additional filter to be applied to the result set. */
virtual ContentFilter buildContentFilter() const =0;
DiscoveryQuery ()
: _Query (_Query::defineQueryTypeID (Goal::DISCOVERY)
, lib::QueryText("TODO")) /////////////////////////////////////////////TODO: generate syntactic representation
{ }
private:
/// Assignment explicitly disallowed (but copy ctor is ok)
DiscoveryQuery const& operator=(DiscoveryQuery const&);
};
enum ScopeQueryKind
{ CONTENTS = 0 ///< discover any contained objects depth-first
, CHILDREN ///< discover the immediate children
, PARENTS ///< discover the enclosing scopes
, PATH ///< discover the path to root
};
/**
* Query a scope to discover it's contents or location.
* This is a special kind of query, wired up such as to enumerate
* the contents or parents of a scope, filtered by a subtype-check.
* For the actual resolution of the elements to discover, this query
* relies on an index like facility (usually Session's PlacementIndex),
* which is abstracted as a QueryResolver, but actually is expected to
* cooperate especially with this Query subclass to retrieve the scope
* to be enumerated and the definition of the actual filter predicate.
* Currently (11/09), there is a special, hard-wired Query-kind-ID
* \c Goal::DISCOVERY to distinguish this special kind of a Query.
*
* Contrary to the usual handling of a generic query, a ScopeQuery
* object holds it's own discovery iterator and thus is completely
* self contained. The query is issued automatically on construction,
* thus the embedded iterator immediately points at the first result.
* Moreover, since any Lumiera Forward Iterator is \c bool checkable,
* a ScopeQuery not yielding any results will evaluate to \c false
* immediately after construction, allowing convenient inline checks.
* The query can be re-issued by the function operator, and the
* embedded result iterator can of course be copied to a bare
* iterator instance, e.g. for passing it on (ScopeQuery
* itself is intended to be used polymorphically and
* thus defined to be not assignable)
*/
template<class MO>
class ScopeQuery
: public DiscoveryQuery<MO>
{
typedef DiscoveryQuery<MO> _Parent;
typedef Query<Placement<MO> > _Query;
PlacementMO::ID startPoint_;
ScopeQueryKind to_discover_;
public:
typedef typename _Parent::iterator iterator;
typedef typename _Parent::ContentFilter ContentFilter;
ScopeQuery (PlacementMO const& scope,
ScopeQueryKind direction)
: startPoint_(scope)
, to_discover_(direction)
{ }
PlacementMO::ID const&
searchScope () const
{
return startPoint_;
}
ScopeQueryKind
searchDirection () const
{
return to_discover_;
}
private:
/** the default implementation of the content filtering
* builds on the downcast-function available on each
* Placement instance. By parametrising this function
* with our template parameter MO, we pick out only
* those elements of the scope being subclasses of MO
*/
ContentFilter
buildContentFilter() const
{
return bind (&PlacementMO::isCompatible<MO>, _1 );
}
};
template<class MO>
struct ContentsQuery
: ScopeQuery<MO>
{
ContentsQuery (PlacementMO const& scope)
: ScopeQuery<MO> (scope, CONTENTS)
{ }
};
template<class MO>
struct PathQuery
: ScopeQuery<MO>
{
PathQuery (PlacementMO const& scope)
: ScopeQuery<MO> (scope, PARENTS)
{ }
};
}}} // namespace proc::mobject::session
#endif