|| || || || || || || ||

---

Impala::Core::Database::PathCreator Class Reference

This (utility) class provides an abstraction over the RawDataSet in order to make it easier to get paths. More...

#include <PathCreator.h>

Inheritance diagram for Impala::Core::Database::PathCreator:

[legend]Collaboration diagram for Impala::Core::Database::PathCreator:

[legend]List of all members.

Public Member Functions
virtual String	GetFilePathSimilarityData (String filename, bool toWrite=false, bool silent=false)=0
virtual String	GetFilePathFeatureData (bool toWrite=false, bool silent=false)=0
virtual RawDataSet *	GetDataSet ()=0
virtual int	GetFolderOrVideoId ()=0
Util::Database *	GetDatabase ()
PathCreator *	SetModel (String s)
PathCreator *	SetFeature (String s)
PathCreator *	SetConceptSet (String s)
void	SetWalkType (String walkType)
String	GetWalkType ()
Protected Attributes
String	mConceptSet
String	mModel
String	mFeature
String	mWalkType
Private Attributes
	ILOG_VAR_DEC

---

Detailed Description

This (utility) class provides an abstraction over the RawDataSet in order to make it easier to get paths.

RawDataSet::GetFilePathSimilarityData() for example has an overload for videosets and one for imagesets. (candidate for refactoring?) The goal of this class is to give one entity all information to get the paths so that this knowledge doesn't need to spread throughout impala. This also simplifies the agrument list of some functions as they don't need 4 or 5 arguments to build a path.

question: is it bad to put pure virtual functions in a not-abstract class?

Definition at line 25 of file PathCreator.h.

---

The documentation for this class was generated from the following file:

• Core/Database/PathCreator.h

---