silverstripe-reports/templates/Includes/ReportAdmin_Content.ss

<div class="cms-content center $BaseCSSClasses" data-layout-type="border">

	<div class="cms-content-header north">
		<h2><% _t('REPORTS','Reports') %></h2>
	</div>

	$Tools

	<div class="cms-content-fields center ui-widget-content">
		$EditForm
	</div>
	
</div>
MINOR Using HTML5 data attributes for denoting layout in templates 2012-02-16 17:36:45 +01:00			`<div class="cms-content center $BaseCSSClasses" data-layout-type="border">`
MINOR Changed ReportAdmin to new ReportAdmin_Content template, viewing available reports as unordered list instead of a tree (they can't be nested anyway) 2011-04-19 08:44:23 +02:00
			`<div class="cms-content-header north">`
			`<h2><% _t('REPORTS','Reports') %></h2>`
			`</div>`

ENHANCEMENT Using new "tools" panel architecture to render CMS templates, which e.g. allows CMSPageEditController to reload the form without the tree in the side-by-side display variation, and hence avoids slowing down the loading and saving process 2012-02-14 21:52:55 +01:00			`$Tools`
MINOR Changed ReportAdmin to new ReportAdmin_Content template, viewing available reports as unordered list instead of a tree (they can't be nested anyway) 2011-04-19 08:44:23 +02:00
MINOR Clearer CSS classes in CMS controller templates, added $BaseCSSClasses to content templates in order to support partial template loads through ajax (instead of relying on stale CSS classes on the <body> tag) 2011-07-05 11:31:33 +02:00			`<div class="cms-content-fields center ui-widget-content">`
MINOR Changed ReportAdmin to new ReportAdmin_Content template, viewing available reports as unordered list instead of a tree (they can't be nested anyway) 2011-04-19 08:44:23 +02:00			`$EditForm`
			`</div>`

			`</div>`