Custom Field Types follow the Symfony 2 extension mechanism: bundles. We can get started with a bundle us= ing the built-in Symfony 2 bundle generator.
From the eZ Platform root, run the following:
php app/console generate:bundle=20
First, we are asked for the namespace. As the vendor, we will use EzSyst= ems as the root namespace. This must of course be changed to whatever ident= ifies you as a vendor (your name, company name, etc). We then choose a pref= erably unique name for the Field Type itself, and make the name end with Bu= ndle. Here we=E2=80=99ve chosen TweetFieldTypeBundle.
Bundle namespace: EzSystems/TweetFieldTypeBundle<enter>=20
We must next input the bundle=E2=80=99s name. Nothing exotic here: we co= ncatenate the vendor=E2=80=99s namespace and the bundle=E2=80=99s namespace= , which is the default. Just hit Enter:
Bundle name [EzSystemsTweetFieldTypeBundle]:<enter>=20
We are then asked for the target directory. We will begin within the vendor at some point. Again, this is the default, and we=
just hit Enter.
Target directory [/home/bertrand/www/ezpublish5/src]:<enter>==20
We must then specify which format the configuration must be generated as= . We will use yml, since it is what we use in eZ Platform itself. Of course= , any other format could be used.
Configuration format (yml, xml, php, or annotation): yml<enter&= gt;=20
The generator will then offer to create the whole directory structure fo= r us. Since our bundle isn=E2=80=99t really a standard Symfony full stack b= undle, we decline.
Do you want to generate the whole directory structure [no]? no<= enter>=20
We then get a summary of what will be generated:
You are going to generate a "EzSystems\TweetFieldTypeBundle\EzSyst= emsTweetFieldTypeBundle" bundle in "/home/bertrand/www/ezpublish5/src/" using the "yml" format. Do you confirm generation [yes]?<enter>=20
After generation, the wizard will offer to update the kernel with our bu= ndle (answer "yes"), and to update the app=E2=80=99s routing with our bundl= e=E2=80=99s route file (answer "no").
Generating the bundle code: OK Checking that the bundle is autoloaded: OK Confirm automatic update of your Kernel [yes]? <enter> Enabling the bundle inside the Kernel: OK Confirm automatic update of the Routing [yes]? no <enter>=20
Our bundle should now be generated. Navigate to src/EzSystems/EzSy=
stemsTweetBundle and you should see the following structure:
$ ls -l src/EzSystems/TweetFieldTypeBundle Controller DependencyInjection EzSystemsTweetFieldTypeBundle.php Resources Tests=20
Feel free to delete the Controller folder, since we won=E2=80=99t use it= in this tutorial. It could have been useful, had our Field Type required a= n interface of its own.