Jobeet for Doctrine
After the initial release of Jobeet, the response was excellent! People are very happy with the Christmas surprise. The only thing some people were not happy about is that it was in Propel instead of Doctrine.
Jon and I worked very hard during the last few days to find a solution. We have updated the symfony documentation process to allow us to have an easy to maintain copy of all documentation for both Propel and Doctrine.
The new symfony website has now been deployed and you can start reading the Jobeet tutorial for Doctrine. Be warned that the Jobeet Subversion repository is still for Propel only.
I hope you all enjoy learning symfony 1.2 with the Jobeet tutorial. Good luck with the leap from Propel to Doctrine :)
For translators: We have added some special notations to support both Propel and Doctrine in one file:
- A Propel specific section must be enclosed in
<propel> / </propel>tags (
<doctrine>has to be used for Doctrine). Each tag must be on its own line and start at the beginning of a line
sfPropeloccurrences are replaced with
sfDoctrinewhen the Doctrine tutorial is generated
##ORM##string is automatically replaced with Propel or Doctrine depending on the context
- Also, when a tutorial is independent of the ORM or if you have provided the needed , the file must end with
Have a look at day 3 for an example.
Help the Symfony project!
As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
Keep going, please :-)
lots of tks !!!