Textile Markup Language(textile-lang.com)

    @Section[name=quickstart]{@Title{Quickstart}
    
    @P{ The official documentation is very sparse, but as a quickstart here is what you need to do: }
    
    @List{
        @Item{Create a fullscreen window to render into}
        @Item{Initialize the library with @FuncRef{S3DTK_InitLib}.}
        @Item{Create a renderer with @FuncRef{S3DTK_CreateRenderer}.}
        @Item{Create an IDirectDraw instance - DirectDraw is mainly used to manage video memory.}
        @Item{Setup exclusive and fullscreen cooperative level and set the video mode to 640x480x16bpp or whatever.}
        @Item{Obtain the base of the framebuffer (see below) to use for calculating surface offsets.}
        @Item{Create a primary surface with a secondary buffer attached to it to act as a swap chain.}
        @Item{Create two @TypeRef{TS3DTK_SURFACE} variables to hold info about the surfaces. S3D actually needs very little info about a surface: its size, pixel/texel format and the offset in video memory from the framebuffer. This bit is the trickiest one.}
        @Item{Optionally create a 16bit surface to hold a z buffer - again you need to do this via DirectDraw and @TypeRef{TS3DTK_SURFACE}.}
    }
    
    @P{ And that is about it. Beyond that it is mainly setting state and drawing triangles. In terms of memory management, S3D relies on DirectDraw to do the video memory allocation/etc so in general the process is allocating a DirectDraw surface and filling a @TypeRef{TS3DTK_SURFACE} variable with info about it. The S3D API itself does not actually know about DirectDraw, it is only used indirectly to obtain the memory offsets and to perform surface flipping. In theory it might be possible to allocate a big surface and chop it to smaller pieces with multiple @TypeRef{TS3DTK_SURFACE}s. }