A note to new Developers » History » Version 3
Rick Glunt, 02/08/2010 09:20 AM
h1. A note to new Developers
Once you have been included in the development team you can then select an open task/bug/whatever from our developer portal. When you have selected something you would like to work on you will need to assign yourself to that item. If you do not have access yet one of the development leaders can do that for you.
Once you have code that is ready to commit to SVN please contact one of the development leaders. We will evaluate your code and commit it. After this you will be granted commit rights to the SVN directly. I am sure all of you can understand the need for us to have a look at your first commit offer.
Guides how to start:
* Please start with the developer guide https://dev.virtuemart.net/cb/wiki/4161.
* After that please read the forum threads marked with [DECISION] so you know what is already discussed.
* Take a look at the tracker http://184.108.40.206:3000/projects/virtuemart/issues. If you don't have already access to it, please alert Milbo in skype bhangla.
* When you find a task the suits to you, just write a message and you may start with it at once.
Rick wrote a system so that we can rewrite VirtueMart to MVC step by step or better said by view. Please read this to enable your new written view.
There are 2 columns in the vm_admin_menu table; a view column and a task column. Just add the view name to this table and the admin menu will create the link using that view name. It is coded the admin menu helper in such a way so that if the view name and/or task is present in the table it will create the link based on that. If it is not present it will create the link in the manner it was done in VirtueMart.
So as you complete moving sections of code to MVC, make the necessary changes to the vm_admin_menu table to use the new view.
Remember to update the sql files in install and migration.
An important goal is to go Joomla native. So try to use the Joomla native methods as best as possible. Use j! debugger, language, db and so on.
You can find a best practices guide using the following link:
This will help us develop pages that work and act consistantly.