After a quick refactoring of the documentation we are eager to deploy the new version of the documentation. This time refactored from xml into rst so that it can be plain, easy to write on the fly, PR’eable on github, and totally updated with nightly builds. We are glad to present:

You will be ripping the benefits of this new way of doing things for your new PHPSpec projects on 2012.

For the Symfony2 community we are bringing the best of PHPSpec and a new way of doing things on 2012.

Encouragements in all good.

Thanks to Behat (everzet) and Symfony2 community for helping us with the way of doing docs the right way.

Working on a PR today I learned some tricks:

// dbu
git pull --rebase
// lsmith
git remote update
git checkout -b feature/myAssertFix_clean upstream/doctrine_dbal
git merge --no-commit --no-ff feature/myAssertFix
git commit -a -m "commit message explaining your changes"
git push origin feature/myAssertFix_clean
git branch --set-upstream feature/myAssertFix origin/feature/myAssertFix
git push origin feature/myAssertFix_clean

Some explanation of the commands above:

1. makes sure local is aware of all the remote changes
2. creates a new local repository based on the state of the upstream repository
3. moves all the code changes from your old local branch to the new one without committing them
4. commits the changes as one commit in the new local branch
5. pushes your new local branch to your repository on github

Special thanks to dbu and lsmith.

We should also remember our two friends:

git rebase -i SHA1
git merge-base branch1 branch2

The sandbox is now integrating background controllers for ProductBundle and also in the front end i have extended ProductBundle to implement pricing and display products and their price. There is a new twig extension on MonetaryBundle which is capable of exchanging automatically the currency of the product’s price. The template is built using the MopaBootstrapBundle too so it is nice looking and clean.

What is next? Well there seems to be need for a paginator, an image manager, then perhaps a cartbundle although some other components need to be there before we move that far. There is a need for categorization too and that is being achieved by TaxonomyBundle. FulfillmentBundle is also on the cooking as I type this so it is certainly something we could be looking at on the next story.

Thanks for reading and enjoy working with vespolina!

So vespolina ProductBundle gained today a feature section to customize products as we can see:

I guess the next step is to implement or setup nice template and product images to store the to make it more realistic so we can be able to feel the real needs of a component like this. The step after that is the integration with different services within the app so perhaps we will need to make the component even more modular. Refactoring etc coming I supose.

Thanks!

Hours later. I went and worked on getting travis-ci on VespolinaProductBundle and now got it passing at least.

http://travis-ci.org/#!/cordoval/VespolinaProductBundle/builds/319041

Now the store is more functional by itself and things are starting to work more nicely.

Today I was able to use EasyExtends to make use of BaseProduct class by generating a directory structure that would help me implement Product class from Vespolina ProductBundle. The task involved bringing up the mongodb properly installed, with settings on cgi as well as on cli php.ini files to understand the why of EasyExtends.

The command you say?

~ php app/console sonata:easy-extends:generate VespolinaProductBundle --dest=src

The sandbox contains all the additions here showing you the sort of directory structure that was created.

A little encouragement for an url http://store.local/app_dev.php/admin/products/ follows :

I worked also on fixing some of the tests due to the break by refactory. Now that i understand a little bit more about vespolina, I can go back and work more on the tests. Focusing currently on ProductBundle and trying to get something working asap.