Syndication::Mapper

Search for usage in LXR

Syndication::Mapper< T > Class Template Referenceabstract

#include <mapper.h>

Inheritance diagram for Syndication::Mapper< T >:

Public Member Functions

virtual ~Mapper ()
 
virtual QSharedPointer< T > map (SpecificDocumentPtr doc) const =0
 

Detailed Description

template<class T>
class Syndication::Mapper< T >

A mapper maps an SpecificDocument to something else.

The type of this "something else" is specified by the template parameter T. In the default implementation it is used with the Feed interface, but it is not limited to that. T can be an arbitrary class.

There are three (advanced and hopefully rare) use cases that require you to implement your own mapper. For more information on the possible uses, see TODO: link docs.

1) Add your own feed parser. In case you need support for another feed format (Okay! News, CDF, completely backward-incompatible Atom 5.0, you name it), you can implement AbstractParser and SpecificDocument for it and provide a Mapper<Feed>

  • class OkayNewsMapper : public Mapper<Feed>
    {
    public:
    virtual FeedPtr map(SpecificDocumentPtr doc) const { ... }
    };
    parserCollection()->registerParser(new OkayNews::Parser, new OkayNewsMapper);
    A mapper maps an SpecificDocument to something else.
    Definition mapper.h:92
    virtual QSharedPointer< T > map(SpecificDocumentPtr doc) const =0
    maps a format-specific document to abstraction of type T.
    ParserCollection< Feed > * parserCollection()
    The default ParserCollection instance parsing a DocumentSource into a Feed object.
    Definition global.cpp:41

2) Implement your own mapper for the Feed abstraction, for an existing parser. E.g. if you think Syndication does map Atom all wrong, you can implement your own Atom mapper and use that instead of the default one.

class MyAtomMapper : public Mapper<Feed>
{
public:
virtual FeedPtr map(SpecificDocumentPtr doc) const { ... }
};
parserCollection()->changeMapper("atom", new MyAtomMapper);

3) Use your own abstraction. In case the Feed interface does not fit your needs, you can use your own interface, let's say "MyFeed". Be aware you have to implement custom mappings for all feed formats then:

class MyFeed
{
public:
QString title() const; // my special title
QList<Article> articles() const; // I name it articles
};
class MyAtomMapper : public Mapper<MyFeed> { ... };
class MyRDFMapper : public Mapper<MyFeed> { ... };
class MyRSS2Mapper : public Mapper<MyFeed> { ... };
ParserCollection<MyFeed>* coll = new ParserCollection<MyFeed>;
coll->registerParser(new Atom::Parser, new MyAtomMapper);
coll->registerParser(new RDF::Parser, new MyRDFMapper);
coll->registerParser(new RSS2::Parser, new MyRSS2Mapper);
Author
Frank Osterfeld

Definition at line 91 of file mapper.h.

Constructor & Destructor Documentation

◆ ~Mapper()

template<class T >
virtual Syndication::Mapper< T >::~Mapper ( )
inlinevirtual

virtual destructor

Definition at line 97 of file mapper.h.

Member Function Documentation

◆ map()

template<class T >
virtual QSharedPointer< T > Syndication::Mapper< T >::map ( SpecificDocumentPtr doc) const
pure virtual

maps a format-specific document to abstraction of type T.

Note
implementations may assume doc to have the type whose mapping they implement and may just statically cast to the subclass without further checking. If you register your own mapper, it's your responsibility to register the mapper only for the format it actually handles.
Parameters
docthe document to map.
Returns
a newly created object implementing the abstraction T.

The documentation for this class was generated from the following file:
This file is part of the KDE documentation.
Documentation copyright © 1996-2024 The KDE developers.
Generated on Fri Dec 6 2024 12:02:22 by doxygen 1.12.0 written by Dimitri van Heesch, © 1997-2006

KDE's Doxygen guidelines are available online.