Starting CiviCRM 2.0 development ...

The last few weeks of a release is always quite frustrating. The team is itching to get started with new development and get on with the next version. However, users are testing the beta release and filing new issues and bugs, few tweaks need to be done etc. So overall, things are in a neither here nor there status. However, once we mark a release as stable, we move most of the development team onto the new release and things get more exciting. CiviCRM v2.0 is a big release for us internally. The current feature list for v2.0 is here. I think it will have very few bells and whistles, but will have a much improved schema and a more extensible core. Drupal has shown us the benefits of building an extensible system. I think we still have a few more revisions to go before we get there, but we are headed in the right direction. Here are some of the things that are exciting about v2.0 (IMO)

• Flattening the schema (in a few core places) and making it significantly more efficient that the current schema. We have learned a fair amount in the past two years and these new changes should help us scale quite nicely. The changes in Contact/Location and Custom Data should make search much faster.
• Ability to use interfaces, reflection and other PHP5 features. We plan on using some of these features to define interfaces for all our components
• Ability to use views, triggers and stored procedures in MySQL5. We will also start using the Foreign Key Constraint functionality of InnoDB (ON DELETE CASCADE / SET NULL). This should simplify the DELETE code in quite a few places.
• Using more AJAX and building cool widgets with Dojo Toolkit 0.9. We plan to make all large forms dynamically loaded and hence much faster

I suspect there are way more changes than we can comfortably fit into a release and a few will be pushed back to the 2.1 release. There is always a struggle between doing a release periodically (every 3-4 months) vs taking a long time for a release (hence more code, more bugs etc). I think a "release early, release often" mentality is good for the development team and the community.

Comments

Can u explain us the reason for using Dojo toolkit?
I think Jquery is faster than Dojo.
Why Jquery?
* (for Drupal users)
-> need to install another module,
-> site will be slower because with every page both jquery and dojo will be loaded.
* Jquery has very big plugins collection.
* Development of Jquery is faster than Dojo.

---
Sharique uddin Ahmed Farooqui

Web Developer
http://it.managefolio.com

of our reasoning.

Experiences with ajax and dojo

Bottom line, we made a decision in the same timeframe and chose a different package. So far, we are quite happy with our choice