Thanks to the wonderful people from Joomla! who took us under their Google Summer of Code umbrella and personal commitment from Wes Morgan, of Environment America (who will be mentoring on CiviCRM’s behalf), we’re very, very happy to announce that we have two student projects funded by Google this year!
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.
18 avril 2008
par lobo sujet CiviCRM, Drupal, Joomla
Drupal 6 introduced a new menu system. CiviCRM had modeled its menu system after drupal 4.x which meant we needed to upgrade the menu code significantly to upgrade CiviCRM to Drupal 6. We took the opportunity to learn and understand more from drupal's new system and also simplify the interface between CiviCRM and Drupal with regard to the menu hook.
The CiviCRM menu system has been based on the Drupal menu system, so all credit for the below goes to chx and the Drupal folks (all blame should be assigned to us). We have simplified and extended it a bit to meet our needs. Similar to Drupal menu system, the CiviCRM menu data now resides in the database. civicrm_menu stores all the information for a menu item.
14 avril 2008
par Dave Greenbergsujet
Brian Shaughnessy is working on some layout improvements for a client - which may potentially result in some core code contributions. He posted this question on the forums today:
I notice there's some inconsistencies regarding how some of the forms are laid out. Specifically, I'm running into forms that use a mix of table/tr/td tags with dl/dt/dd tags to layout the form labels and fields. This makes it more difficult to have consistency laying out the page using css, because those tags are structured differently.
My personal preference is to use table tags exclusively. Because of the built-in structure of dl/dt/dd tags, I find them hard to layout on a consistent and growable/shrinkable manner. I know that in a strict-css-world we shouldn't use table tags for layout, but for a long list of form labels and fields, many of which have option contingencies, tables seem like the most logical way to handle layout.
Since this is an issue we've struggled with, and because we're looking at changes to some key screens and forms to improve usability - I'm posting my response here as a blog. Hopefully we'll grab a few more eyeballs and get some useful input from folks with expertise in this area...
9 avril 2008
par shot sujet CiviCRMWe’re currently planning on various improvements to the duplicate contact finding (and merging) engine for CiviCRM 2.1. Among others, we plan to have a more responsive mechanism by caching the dedupe search results in a more effective way, add the ability to restrict deduping to a certain group, as well as move at least parts of the dedupe out of PHP and into MySQL (now that we require MySQL 5 anyway).
9 avril 2008
par lobo sujet CiviCRMSome members of the core CiviCRM team are getting together for a design and code sprint towards 2.1 in Nelson NZ from April 24th - May 8th. As part of improving CiviCRM, we'd love to get together with some CiviCRM users and learn a bit about how we can improve and make CiviCRM more effective.
9 avril 2008
par lobo sujet CiviCRMThis event is cancelled. The training group is going for drinks and dinner in CBD. Send me email if you'd like to join
As most of you are aware, we are doing a CiviCRM developer training in Melbourne. We are keen to do a meetup with CiviCRM users in Melbourne on April 21st at 6:00 pm on the second day of the training.
7 avril 2008
par kurundsujet Continuing the database cleanup that we started with v2.0, we are planning to drop some of the unused fields from civicrm_address table.
CiviCRM v2.0 ERD
List of fields that will be dropped.
1. street_number 2. street_number_suffix 3. street_number_predirectional 4. street_name 5. street_type 6. street_number_postdirectional 7. street_unit 8. supplemental_address_3
7 avril 2008
par shot sujet CiviCRMTo side-step the issue of users switching our demo installation to non-English languages and as a proof-of-concept for a possible future CiviCRM feature, we’ve implemented a ‘dynamic’ language switching – after logging in, check the demo’s dashboard (i.e., the ‘CiviCRM Home’ page) and look for the ‘Choose Language’ box in the top right.
5 avril 2008
par deepak.srivastavasujet There are many screens in CiviCRM where the options in one drop-down affect what you see in a second or third drop-down menu. For example, when you do an Import or Export, and select Email - you then get a second drop-down to select a location (Home, Work, etc.). The widget which we use for this is PEAR's Hierarchical Select.
4 avril 2008
par lobo sujet CiviCRMUPDATE: We have discontinued our use of UserVoice as of 12/11/2008
We've been trying to figure out a good structured and fair way of getting user input. We were pointed to UserVoice.com by Greg Heller at NTEN. UserVoice seems a fairly simple Web 2.0 site which does exactly that. Hopefully it has a decent search / sort / categoization system to handle an expanding list of features.
