This project is open to everyone to join, cause it works better if people improves it as they try it out and as they learn new things. So more people will contribute to this and more useful it will be for all Yii users.

Note: since many users asked to join but then didn't contributed in any way, I urge you to first download the source from svn and start working on it locally (read-only access is open to everyone) and then, when you will have something to commit, go on and require to join. Thanks.

There are some few things that are required in order to join, but don't be afraid of them; if you have any question feel free to ask in the dedicated forum thread.

How to join: Send me a Personal Message on the Yii Framework forum, with your google account email address specifying which new/improved examples you already have developed that you want to commit.

Requisites to join:

• joining this project means that you want to contribute with some new examples or that you want improve the existing ones, so, before making a join request, make sure you already have something to commit, thanks
• good knowledge of the MVC design pattern
• basic Yii knowledge: know how the Yii template system works and knowledge of how Yii works in general
• sufficient knowledge of the topic you want to cover in your demo
• know how to use svn (see bellow)
• read the docs in the project wiki

Guidelines for contributors:

• use tabs to indent (not spaces)
• possibily use the netbeans ide, but this is not a must ;)
• start having a look to the breadcrumbs, zii yui dialog and ajax request demos (look also at the code of the views)
• put breadcrumbs in your demo page

Getting started: SVN You may have already tried the playground app from the live demo or by downloading it but the best way to try it out is to grab the code from svn. If you are not familiar with svn here are some tips..

When you use svn, concept to know are mostly these 4:

• checkout
• update
• commit
• export

when you checkout you download the source tree to your pc. from that poin on you will likely only need to do updates. When you change some files you'll have to commit them in order to send your changes up to svn repository.

When you want to work on a clean local copy, not to be used with svn, or if you want to release a downloadable package, you then have to export your tree. This will create a copy of your sources that doesn't have the .svn hidden folders inside it (that folders contains svn information).

Before you start making changes to the source that it is under svn you should always perform an update: if you edit a file that, in the meantime, has been edited and committed by someone else you'll get a conflict. In that case you'll have to merge the files using a diff tool and then mark it as resolved.. (the first times it could be a pain ;))

As last thing: if you delete a file that you committed don't first delete it from your filesystem but always use the delete function of svn. (if you just download a file from svn and then commit you can get some conflicts, while if you update it after you deleted it from you fs the file should reappear). At the same way new files created in your filesystem are not (usually, but netbeans does it) automatically added to the svn tree.. so you should perform an "add" action..

important: don't commit folders that are generated inside the assets/ folder. Put that folders on the ignore list using the ignore command.

Some useful links:

• Tortoise svn video tutorial (see this first/anyway if you are new with svn!)
• http://netbeans.org/kb/docs/ide/subversion.html
• http://www.solitarygeek.com/java/subversion-and-netbeans-a-quick-start-guide/
• http://wiki.netbeans.org/FaqSubversionSSH
• http://tortoisesvn.net/
• http://tortoisesvn.net/docs/release/TortoiseSVN_en/index.html
• http://zoneit.free.fr/esvn/
• http://www.rapidsvn.org/
• http://blog.taragana.com/index.php/archive/5-minutes-guide-to-subversion/