server/apps/files_versions/templates/settings.php

<form id="versionssettings">
        <fieldset class="personalblock">
	        <legend><strong><?php echo $l->t('Files Versioning');?></strong></legend>
	        <input type="checkbox" name="versions" id="versions" value="1" <?php if (OCP\Config::getSystemValue('versions', 'true')=='true') echo ' checked="checked"'; ?> /> <label for="versions"><?php echo $l->t('Enable'); ?></label> <br/>
        </fieldset>
</form>
fix label for versioning in admin settings 2012-08-04 16:50:05 +00:00			`<form id="versionssettings">`
Implement a basic versioning configuration. Only a on/off switch for now. I changed my mind about the more complex configuration options. We go with good default for now and don´t expose all the technical options to the users. They can still override in the config file if it´s really really needed and they know what they are doing 2012-04-30 17:18:00 +00:00			`<fieldset class="personalblock">`
add a legend tag. it´s consistent and looks nicer 2012-09-16 15:13:16 +00:00			`<legend><strong><?php echo $l->t('Files Versioning');?></strong></legend>`
			`<input type="checkbox" name="versions" id="versions" value="1" <?php if (OCP\Config::getSystemValue('versions', 'true')=='true') echo ' checked="checked"'; ?> /> <label for="versions"><?php echo $l->t('Enable'); ?></label> <br/>`
Implement a basic versioning configuration. Only a on/off switch for now. I changed my mind about the more complex configuration options. We go with good default for now and don´t expose all the technical options to the users. They can still override in the config file if it´s really really needed and they know what they are doing 2012-04-30 17:18:00 +00:00			`</fieldset>`
			`</form>`