Everyone is continuing to produce an incredible amount of content for the book, plus rework and update areas that were showing some age. The new set of chapters for developers and people who want to extend CiviCRM is really fantastic. Everyone who has been wanting to extend CiviCRM, but didn't know where to start should be able to dive in. Everyone is increasing their knowledge of CiviCRM, getting ideas for new features and improving existing features.
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
Today's localisation sprint started with a presentation from Piotr on how multilingual installations works in CiviCRM.
Multilingual is when you want to have not only a localised interface, but many co-existing languages. So for example the labels of custom fields may need to be in English or Spanish if the organisation has a bilingual website. In general, most labels can be translated using multilingual, but not the data itself. The main except to this is the contact name, so that it can be entered in multiple alphabets.
The following notes were gathered from the CiviCon session on what the community would like to see in CiviCRM 4.0:
* Goals * No new features * Framework switch * Not as major a rewrite as it looks * Don't want to change many of the private APIs * Want to switch away from pear * Test unit coverage * Better API hooks * What users would like to see * Continuous Integration * Hudson - as you submit code runs through suite of unit tests to see what's broken * Better decoupling * Drupal Forms API
It's 5 to midnight and we're just wrapping up. Mr Kurund says that I can't go to bed until I've written this post, so...
Participating in the second book sprint is just as fascinating as it was the first time around, but the dynamic is definitely different. Having a book in place already makes a big difference - there's no panicking that we'll end up with the sections half finished, and it is easier to cover components when a lot of the design decisions have already been made. Having already written sections on the components is especially helpful when covering new components.
Well, it's been done, we chose the translation platform: Transifex. We're fully aware that we did not actually choose a platform that fully supports the ideal situation, but such a platform does not exists. This is more the choice of a promising back-end which we hope we can eventually develop into the ideal situation.
The interesting part in the discussion was finding a balance between the technical and functional interests.
That's right, you probably noticed there are two sprints going on here in Tahoe. You can read the report from the book sprint in Jack blog post, now it's time you found out what's the second sprint about.
It's 11pm in beautiful Truckee, CA, and the CiviCRM Book Sprint crew of twelve dedicated souls is still hard at work after a 10am start. We've come from across the US and around the globe to help update and improve the existing book, making it more useful for CiviCRM users, developers, implementers, and administrators.
This Thursday, the first ever CiviCon took place. After five years of constant development of the CiviCRM project, we felt it was definitely time to have an in-person gathering of CiviCRM community members, talk about past, plan the future and enjoy being together. It was really a great day.
We had another super awesome day at DrupalCon SF 2010 today. Was great to watch and hear Cricket from Jane Goodall Institude proclaim: "I love CiviCRM!" to the audience :) To keep the momentum going, we've scheduled two BoF sessions for today. Please check the BoF notice board for the rooms.
Originally posted at TwoMiceAndAStrawberry.com.
I recently had to modify CiviCRM to support a specific use case for a client. In this project I needed to allow the user to enter anything in the Individual Prefix field, rather than choosing from a list of options. The client in this case was very sensitive about presenting the individual's honorific precisely as the individual wants, so that "Dr.," "Rev. Dr.," and "Most Rt. Rev. Dr." should all be possible, along with anything else the user might want to enter.
