Internet Explorer is a deathly trap for web developers. In fact a good amount of time is allotted to just ensuring a website's experience is uniform across different versions of the browser. The problem plaguing Internet Explorer is that each version has generally been released alongside a new iteration of the Windows operating system. With this life cycle certain operating systems get left behind (the dreaded era of Windows XP with IE8 is finally, somewhat over.)
When using Drupal we all know there are two themes: default and administrative. By having two diferent themes site managers have a better user experience by knowing "this is public," and "this is administrative." It also proves beneficial to have specific administration themes due to the kinds of content and forms that a site manager has to interface with.
Drupal does provide the option of letting site builders decide if adding or editing a node takes place in the default theme or the administrative theme. Chances are, at least in all of my cases, you have "Use the administrative theme when editing or creating content" checked. There's just one drawback: what if one specific node (or other entity for that matter) should be edited through the default theme?
Turns out at Microsoft's Build 2014 it was announced that the company with be partnering with Xamarin (maker of Mono) to start the .Net Foundation. Right now it seems the .Net Foundation's primary goal is to foster open-source development projects based on the .Net framework, verus open sourcing the framework itself.
Last week I was down at the amazing Florida Drupal Camp and gave my first Drupal Camp presentation! I've been meaning to do a write up, but life is just too busy right now. So here's the slides at least!
When it comes to Drupal I love entities. Entity display modes provide simplicity in managing how your content is displayed. I used to be hardcore "Fields only" when it came to using Views and displaying content. Yeah, it gives you more control, but it is a pain in the ass when you have to replicated your field settings multiple times (if you have to.) Wouldn't it be super easy to just say "Hey Views, render this entity!" and BAM it is all there for you.