Add more default values

Command/AbstractCommand.php

@@ -604,6 +604,12 @@ EOT;
             'propel.output.dir'         => $kernel->getRootDir().'/propel',
             'propel.php.dir'            => $kernel->getRootDir().'/..',
             'propel.packageObjectModel' => true,
+            'propel.useDateTimeClass'   => true,
+            'propel.dateTimeClass'      => 'DateTime',
+            'propel.defaultTimeFormat'  => '',
+            'propel.defaultDateFormat'  => '',
+            'propel.defaultTimeStampFormat'     => '',
+            'propel.builder.pluralizer.class'   => 'builder.util.StandardEnglishPluralizer',
         ), $properties);
 
         // Adding user defined properties from the configuration

Resources/doc/propel_configuration.markdown

@@ -1,7 +1,12 @@
 Propel Configuration
 ====================
 
-Add a `app/config/propel.ini` file in your project, and copy the following configuration:
+You can add a `app/config/propel.ini` file in your project to specify some
+configuration parameters. See the [Build properties Reference](
+http://www.propelorm.org/reference/buildtime-configuration.html) to get more
+information.
+
+By default the PropelBundle is configured with the default parameters:
 
 ``` ini
 # Enable full use of the DateTime class.
@@ -25,16 +30,8 @@ propel.defaultDateFormat =
 
 # A better Pluralizer
 propel.builder.pluralizer.class = builder.util.StandardEnglishPluralizer
-
-# MySQL config
-# propel.mysql.tableType = InnoDB
-
-# Behaviors come below
 ```
 
-See the [Build properties Reference](http://www.propelorm.org/reference/buildtime-configuration.html) to get more
-information.
-
 
 ## Build properties ##
 
@@ -51,4 +48,21 @@ propel:
 ```
 
 
-[Configure the bundle](configuration.markdown) | [Back to index](index.markdown) | [Write an XML Schema](schema.markdown)
+## Behaviors ##
+
+You can register Propel behaviors using the following syntax:
+
+``` yaml
+# app/config/config.yml
+propel:
+    behaviors:
+        behavior_name: My\Bundle\Behavior\BehaviorClassName
+```
+
+If you rely on third party behaviors, most of them are autoloaded so you don't
+need to register them. But, for your own behaviors, you can either configure the
+autoloader to autoload them, or register them in this section (this is the
+recommended way when you namespace your behaviors).
+
+
+[Configure the bundle](configuration.markdown) | [Back to index](index.markdown) | [Write an XML Schema](schema.markdown)