In the time since my last Drupaltin blog post a lot of things have happened. Probably one of the biggest is the release of vbDrupal 5. I want to start off by saying that Drupaltin and vbDrupal are not the same. vbDrupal is a fork of Drupal which is a heavily modified version of Drupal with it's own code thrown in the mix. It all sounds fine and dandy except the code is not built by hundreds of developers and tested by thousands and used by hundreds of thousands. What does this mean? Well it means buggy code, security holes, performance issues, slow updates for major releases of Drupal, far less compatibilty, and more.
But I am not here to bash on vbDrupal or any other script. vbDrupal is a very good script and I respect the developers who make it possible. I am simple stating that script takes a different approach to bridging vBulletin and Drupal, so the release of vbDrupal 5 is mostly irrelivent to Drupaltin.
Just because there have not been any blog posts for a while does not mean that coding has stopped. In fact it is just te opposite of that, the time I would have spent posting blogs has gone into coding. I have made some great advancements in the script and it is looking better by the day.
The core of Drupaltin has been built on the proven code of Drupal. While it may not be noticable from an end-users point of view, the core of the Drupaltin Control Panel is built using the Drupal core as an inspiration. That means the user-interface of Drupaltin will be rock solid and the code will be familiar to developers. There is something that might look odd to a developer though and that is the fact that Drupaltin 2 uses Object-oriented programming (OOP). The Drupal code which it is built from has been converted over to OOP, mostly to eliminate the possiblity of conflicts.
I need some feedback from you. Recently I have started a discussion on the Drupaltin 2 plugin/module system and I need feedback. You can find everything in the forums here: http://forums.theoverclocked.com/showthread.php?t=2437
It wish I could keep going about the lastest developments but it is time to get back to coding. Last night and today I have been working on my unique database layer which interfaces Drupal-Drupaltin-vBulletin together. I have been focusing on performance, ease of use, and flexibility. For those of you who might have heard, yes I am on vacation now. I have been in Boston, MA since July 21. Drupaltin development doesn't ever stop, even for vacation ;)