Files
acceptance-tests
data
debian
docs
external
Newtonsoft.Json
api-doc-tools
external
mdoc
monodoc
Assembly
Mono.Documentation
Mono.Utilities
Monodoc
caches
generators
providers
storage
HelpSource.cs
HelpSource_Legacy.cs
Node.cs
Node_Legacy.cs
Provider.cs
RootTree.cs
RootTree_Legacy.cs
SearchableDocument.cs
SearchableIndex.cs
Tree.cs
TypeUtils.cs
cache.cs
generator.cs
index.cs
settings.cs
settings_Legacy.cs
storage.cs
Monodoc.Ecma
Properties
Resources
Test
Makefile
jay.sh
monodoc.csproj
monodoc.dll.config
.gitignore
.gitmodules
Makefile
README.md
apidoctools.sln
api-snapshot
aspnetwebstack
binary-reference-assemblies
bockbuild
boringssl
cecil
cecil-legacy
corefx
corert
ikdasm
ikvm
linker
nuget-buildtasks
nunit-lite
roslyn-binaries
rx
xunit-binaries
ikvm-native
libgc
llvm
m4
man
mcs
mk
mono
msvc
po
runtime
samples
scripts
support
tools
COPYING.LIB
LICENSE
Makefile.am
Makefile.in
NEWS
README.md
acinclude.m4
aclocal.m4
autogen.sh
code_of_conduct.md
compile
config.guess
config.h.in
config.rpath
config.sub
configure.REMOVED.git-id
configure.ac.REMOVED.git-id
depcomp
install-sh
ltmain.sh.REMOVED.git-id
missing
mkinstalldirs
mono-uninstalled.pc.in
test-driver
winconfig.h
linux-packaging-mono/external/api-doc-tools/monodoc/Monodoc/generator.cs
Xamarin Public Jenkins (auto-signing) 536cd135cc Imported Upstream version 5.4.0.167
Former-commit-id: 5624ac747d633e885131e8349322922b6a59baaa
2017-08-21 15:34:15 +00:00

32 lines
948 B
C#

using System;
using System.Collections.Generic;
namespace Monodoc
{
// All type of documents that a generator may find as input
public enum DocumentType {
EcmaXml, // Our main monodoc format
EcmaSpecXml,
Man,
AddinXml,
MonoBook, // This is mostly XHTML already, just need a tiny bit of processing
Html,
TocXml, // Used by help source displaying some kind of toc of the content they host
PlainText,
ErrorXml
}
/* This interface defines a set of transformation engine
* that convert multiple documentation source to a single output format
*/
public interface IDocGenerator<TOutput>
{
/* This method is responsible for finding out the documentation type
* for the given ID and use the right engine internally
* The id can be accompanied by a context dictionary giving away extra
* informtion to the renderer
*/
TOutput Generate (HelpSource hs, string internalId, Dictionary<string, string> context);
}
}