ppttemplate

type Layout struct {
	TitleX, TitleY, TitleW, TitleH float64 // custom marshal; see below
	BodyX, BodyY, BodyW, BodyH     float64
}

type PageRole struct {
	// Index is the 1-based slide number in the master_file this role refers to.
	// e.g. content role on slide 3 of a 4-page cover/toc/content/closing template.
	Index int `json:"index"`
	// FillRegion gives the normalized 0-100 area (on the 960x540 canvas) where
	// new content text should be placed when this page is used. For "content"
	// pages that get duplicated + filled, this is where body text lands (relative
	// to the page). Omit for pages used as-is (cover/closing with fixed text).
	FillRegion *Layout `json:"fill_region,omitempty"`
}

type Template struct {
	// ID is the template's unique id. Defaults to the JSON filename stem.
	ID string `json:"id"`
	// Name is the human label shown in the settings dropdown.
	Name string `json:"name"`
	// MasterFile is an optional .pptx the deck opens from (inherits its cover,
	// theme, fonts). Empty = use a WPS default blank deck. Absolute path.
	MasterFile string `json:"master_file,omitempty"`
	// Theme holds colors/fonts applied to added text. All optional.
	Theme Theme `json:"theme,omitempty"`
	// Layouts maps a layout name (cover/content/section/...) to coordinates for
	// its elements. The CUA uses these directly instead of perceiving each slide.
	Layouts map[string]Layout `json:"layouts,omitempty"`
	// DefaultLayout is used when a slide doesn't specify one (e.g. body slides).
	DefaultLayout string `json:"default_layout,omitempty"`
	// PageRoles describes what each slide in the master_file IS, so the renderer
	// can use them correctly: duplicate the "content" page as a background for
	// new body slides, keep the "cover"/"toc"/"closing" pages as-is or fill their
	// designated regions. Keys are roles (cover/toc/content/closing/...), values
	// carry the 1-based slide index in the master + the content-fill region for
	// that role (normalized 0-100, like Layouts). When set, renders build body
	// slides by COPYING the content page (preserving its background) rather than
	// appending blank slides — the correct way to use a designed template.
	PageRoles map[string]PageRole `json:"page_roles,omitempty"`
}

type Theme struct {
	PrimaryColor    string `json:"primary_color,omitempty"` // "RRGGBB" hex, no #
	AccentColor     string `json:"accent_color,omitempty"`
	BackgroundColor string `json:"background_color,omitempty"`
	FontTitle       string `json:"font_title,omitempty"` // e.g. "微软雅黑"
	FontBody        string `json:"font_body,omitempty"`
	FontSizeTitle   int    `json:"font_size_title,omitempty"`
	FontSizeBody    int    `json:"font_size_body,omitempty"`
}

type View struct {
	ID   string `json:"id"`
	Name string `json:"name"`
}