I believe what's needed for boinc is a bridging framework to allow boinc web code to operate in tandem with other CMS's. The current problem is the web code is heavy to maintain. It would be nice to see a combined effort where everyone worked to try to build a bridge between drupal and boinc. But in reality if boinc web code can be properly bridged with any of the popular CMS's, or several of them, then the main goal has been achieved.
Both drupal and django are excellent and i think if either of you have the expertise to write the code to bridge these with boinc, that would be a great start. Take the initiative and start writing the code. Personally i have become very familiar with Joomla and i might see in the coming weeks if i can write a bridging code to integrate Joomla with boinc web code. Its only because i know the Joomla software and i'm not fimilar with the others Yet! People are going to do their own thing anyway. At the end of the day, if there is one bridge available that works really well with boinc web code, this just makes life easier for the computer scientist to do his work and not have to think about the web code. Several projects have tried various methods of blending boinc web code with a CMS. http://drugdiscoveryathome.com/ with iFrames http://www.climateprediction.net/ almost zero integration with the web code. http://mothershipathome.org/ not sure here? http://www.renderfarm.fi/ reasonable integration. http://docking.cis.udel.edu/ quite seamless, possibly the best so far! Whatever you decide to do, its pointless if its not available to currently running projects. But it also needs to be something that will work with a fresh install of both boinc web code and the chosen CMS. John. On Mon, Jun 22, 2009 at 6:23 AM, Jeremy Cowles <[email protected]>wrote: > > > > + 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. > > > > I was referring to the existing BOINC Python scripts. Currently there is a > C++ data access layer, a home-brew ORM for Python and then another data > access layer in PHP for the web. > > Using Django would provide a common layer for both scripts and web apps and > eliminate the duplicate code. I don't think Drupal could do that without > some serious duct tape. > > > > > + 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. > > > > Agreed. I wasn't trying to imply anything negative about about Drupal's > technical capabilities. > > > > > Seems like the main (only?) pro that Django has over Drupal is that it's > > written in python instead of PHP. > > > Because many management scripts are written Python, this is > an opportunity to avoid duplicate code. These scripts can be executed from > PHP as well, but you don't get the same level of interoperability and > reuse, > although that's not a show stopper. > > > > > 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. > > > > I don't have a personal or technical preference for Djano or Drupal (they > are really different beasts anyway), the reason I bring this up is solely > because Django makes more sense to me from a code reuse standpoint. > > Seems like a moot point anyway, from what David said, the plan is to stick > with Drupal. Also, Drupal probably requires less up-front work. The code > that exists works fine now, the functionality is just being repeated, which > may or may not be worth the extra effort to correct. My intent was to bring > that issue to light and see how people felt about it. > > -- > Jeremy > _______________________________________________ > 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. > _______________________________________________ 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.
