appypod-rattail/gen/plone25/templates/frontPage.pt

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"
      metal:use-macro="here/main_template/macros/master" i18n:domain="<!applicationName!>">

  <metal:disable fill-slot="top_slot"
                 tal:define="dummy python:request.set('disable_border',1)" />
  <body>
    <div metal:fill-slot="main" tal:define="tool python: context.<!toolInstanceName!>">
      <!pageContent!>
    </div>
  </body>
</html>
Initial import 2009-06-29 07:06:01 -05:00			`<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"`
			`metal:use-macro="here/main_template/macros/master" i18n:domain="<!applicationName!>">`

new.py now can create instances for Plone 2.5.5, Plone 3.0 to Plone 3.3.5. specificWritePermission and specificReadPermission can hold named (string) permissions instead of simple boolean values (which is still allowed). frontPage can call a custom macro. When launching generate.py with -c option, labels prefixed with custom_ are kept. 2010-08-12 04:56:42 -05:00			`<metal:disable fill-slot="top_slot"`
			`tal:define="dummy python:request.set('disable_border',1)" />`
Initial import 2009-06-29 07:06:01 -05:00			`<body>`
new.py now can create instances for Plone 2.5.5, Plone 3.0 to Plone 3.3.5. specificWritePermission and specificReadPermission can hold named (string) permissions instead of simple boolean values (which is still allowed). frontPage can call a custom macro. When launching generate.py with -c option, labels prefixed with custom_ are kept. 2010-08-12 04:56:42 -05:00			`<div metal:fill-slot="main" tal:define="tool python: context.<!toolInstanceName!>">`
			`<!pageContent!>`
Initial import 2009-06-29 07:06:01 -05:00			`</div>`
			`</body>`
			`</html>`