Good thoughts Matt.<div><br></div><div>Jim, perhaps one of the bigger frustrations I come across is while trying to change the look and feel. I'd like to see CiviCRM adopt the same PHPtemplate theme system that Drupal uses. Look at <a href="http://www.jewishideas.org/contribute">www.jewishideas.org/contribute</a> and it's easy to see which parts of the form are exposed by Drupal and which by CiviCRM.</div>
<div><br></div><div>And if it were to adopt Drupal's module system too, we could see all kinds of added functionality between releases. I could go on.</div>
<div><br></div><div>The biggest boon, as Matt said, is that by adopting the same parts as Drupal, you're bringing in an army of developers and implementors.</div><div><br></div><div>--D<br clear="all">--<br>D202 - People-Centric Websites<br>
646.536.7502 || Office<br><a href="http://www.davidnotik.com" target="_blank">www.davidnotik.com</a><br>
<br><br><div class="gmail_quote">On Wed, May 5, 2010 at 2:23 PM, Matt Chapman <span dir="ltr"><<a href="mailto:matt@ninjitsuweb.com" target="_blank">matt@ninjitsuweb.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Wed, May 5, 2010 at 11:01 AM, Jim Taylor <<a href="mailto:jim@rootyhollow.com" target="_blank">jim@rootyhollow.com</a>> wrote:<br>
> I'm -1 on the re-creation of a CRM in Drupal as it's a whole lot of work and<br>
> all you ar doing is re-reating the wheel imho. Unless you have a large team<br>
> behind it I don't see the point.<br>
<br>
</div>The point would be:<br>
<br>
1.) Migrating to a single, unified framework instead of the<br>
hodge-podge of disparate libraries that make-up CiviCRM now<br>
<br>
2.) and therefore, vastly increasing the pool of capable developers,<br>
and every competent Drupal 7 developer would then also be a competent<br>
CiviCRM developer without significant additional effort.<br>
<br>
3.) and, increased consistency of UI and user experience when moving<br>
between Drupal and CiviCRM interfaces.<br>
<br>
I agree that a team of several people is needed, and I think the<br>
Drupal community could provide that team as volunteers. The ubercart<br>
project would stand as a reasonably good model of how this could be<br>
done.<br>
<br>
This is less like recreating the wheel and more about replacing the<br>
engine in the car with better parts.<br>
<div><br>
<br>
All the Best,<br>
<br>
Matt Chapman<br>
Ninjitsu Web Development<br>
<br>
--<br>
The contents of this message should be assumed to be Confidential, and<br>
may not be disclosed without permission of the sender.<br>
<br>
<br>
<br>
<br>
</div><div><div></div><div>> David,<br>
> I would be curious to hear what ese you see need in view integration, as of<br>
> 2.2 you should be able to access almost all the CiviCRM field in views (feel<br>
> free to answer that off list or file a ticket with CiviCRM).<br>
> We talked about CCK among a couple developers at CiviCon and really couldn't<br>
> come up with a pressing use case except for replacing the profiles<br>
> integration with Fields API integration for the user entity, in Drupal 7.<br>
> So use Fields API to display the CiviCRM profiles that are exposed during<br>
> user registration.<br>
> What what seemed more important to work on was greater<br>
> Rules/Workflow/Actions integration to create workflows in CiviCRM. This<br>
> should be a huge help in customizing CiviCRM's behaviors and default<br>
> workflows.<br>
> I'm -1 on the re-creation of a CRM in Drupal as it's a whole lot of work and<br>
> all you ar doing is re-reating the wheel imho. Unless you have a large team<br>
> behind it I don't see the point.<br>
><br>
><br>
> On Wed, May 5, 2010 at 1:48 PM, David Notik <<a href="mailto:dave@d202.org" target="_blank">dave@d202.org</a>> wrote:<br>
>><br>
>> Hi.<br>
>> On Wed, May 5, 2010 at 1:24 PM, Matt Chapman <<a href="mailto:matt@ninjitsuweb.com" target="_blank">matt@ninjitsuweb.com</a>> wrote:<br>
>>><br>
>>> Is there anybody<br>
>>> around who's got the management skills to help redirect the momentum<br>
>>> among CiviCRM new-comers into a project to re-create CiviCRM<br>
>>> functionality using Drupal 7 as the framework?<br>
>><br>
>> Music to my ears. I don't have the resources to lead that effort, but +1<br>
>> for the need. It's really to bad we can't work with CCK and Views for most<br>
>> all CiviCRM functionality.<br>
>> I agree with your assessment about demand. CiviCRM is arguably much<br>
>> harder to work with than Drupal -- yet it does some powerful things,<br>
>> integrates with Drupal, and remains in demand largely because of those<br>
>> points. For CiviCRM/Drupal integration that goes beyond tying users to<br>
>> contact records and exposing contribution pages and event registrations in<br>
>> the CMS, you can and should command a higher rate than Drupal most of the<br>
>> time. Anyway, my shop charges one rate regardless.<br>
>> Just did a bit of work on one Drupal/CiviCRM project of ours --<br>
>> <a href="http://www.jewishideas.org" target="_blank">www.jewishideas.org</a> -- including replaced the fundraising campaign"goal<br>
>> widget' with some custom stuff.<br>
>> Best,<br>
>> --D<br>
>> --<br>
>> D202 - People-Centric Websites<br>
>> 646.536.7502 || Office<br>
>> <a href="http://www.davidnotik.com" target="_blank">www.davidnotik.com</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> consulting mailing list<br>
>> <a href="mailto:consulting@drupal.org" target="_blank">consulting@drupal.org</a><br>
>> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> consulting mailing list<br>
> <a href="mailto:consulting@drupal.org" target="_blank">consulting@drupal.org</a><br>
> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
><br>
><br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org" target="_blank">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br></div>