On Jun 19, 2009, at 3:11 AM, Jeremy Cowles wrote: > I saw a ticket in Trac talking about a conversion from custom PHP to > using Drupal CMS. Is there any activity on this front?
As far as I've heard, there's been a little bit of progress on that proposal, but nothing significant has been done. I had offered to be a resource for the conversion (since I'm deeply involved in the Drupal community, and also did some work with integrating BOINC with Condor back when I worked for UW-Madison), but David and I never managed to discuss it further. > If not, has Django (Python) been considered? I've never used Django, so I don't have a strong opinion about that, but I wanted to clear up some things about Drupal... > + Enables unification of the data access layer between scripts and > Web apps > (Django ORM). Drupal has a data access layer that can be shared by scripts and web apps. > + Django is modular, so the BOINC app could be literally plugged > into any > existing Django app Drupal is modular. It's known for its plugable, modular architecture. > + Django generates a nice admin interface for basic CRUD data > functionality As does Drupal. > + Authentication, etc, built in As does Drupal. Seems like the main (only?) pro that Django has over Drupal is that it's written in python instead of PHP. It's been so long since I looked at the actual source tree for BOINC that I have no idea how much python code already exists there. I can certainly understand a desire to rely on fewer languages, but the BOINC community should consider if that's a sufficient reason to go with Django. Cheers, -Derek _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
