drupaleasypodcast

Biscotti Labs is a mobile app development company started by Jeff Linwood. After using Drupal for several projects, he saw that Drupal made an ideal platform for building mobile applications for iPhones, iPads, and Android devices. Jeff Linwood Jeff has over ten years of software development experience, and started developing mobile apps in 2009. He is the co-author of several books for Apress, with the most recent book being Pro Hibernate 3, 2nd Edition.

I’m excited to announce progress on my new e-book on PhoneGap, Drupal, and jQuery Mobile! I gave an interview on using Drupal with PhoneGap to Brian Lewis at Modules Unraveled last month. In addition to the podcast, which I really enjoyed making, I recorded a screencast on setting up PhoneGap, which I hope you enjoy.

Open Outreach developers Nedjo Rogers and Rosemary Mann of Chocolate Lily Web Projects are launching an exciting new pilot project inviting groups to apply to have an Open Outreach site built for them for Cdn$1,000.

Drupal Drupal\Component\$component Drupal\Core\$subsytem Drupal\Module\$module Drupal\Hook and Drupal\Module\$module\Hook

Modules and themes (and engines) would have a namespace such as namespace drupal\taxonomy; or namespace drupal\bartik; Function prefixes, such as 'taxonomy_' would be dropped. However, this makes Drupal code really ugly. Calling functions not in a module from a module would look like this: \drupal\set_message(); Calling a db function would look like this: \drupaldb\select('node'); Calling an API function in another module would look like: \drupal\taxonomy\select_nodes(); The solution?

At the very least (if we are on PHP 5.3) we could have something like: namespace drupal\dblog; at the top of every file. Files in the includes directory would have: namespace drupal; The only time 'drupal' would be seen in a function name would be when calling an API function in a different module, e.g. \drupal\system\flush_caches();

1) We've been discussing how and if to leverage PHP namespaces in Drupal 8, now that we have access to them in PHP 5.3. To date most of the discussion has been on tricking out modules-as-namespace, a discussion that has stalled as it is a much more complicated problem space than it seems at first glance.

There are three ways to access a file in a file system: Relative file name like foo.txt. This resolves to currentdirectory/foo.txt where currentdirectory is the directory currently occupied. So if the current directory is /home/foo, the name resolves to /home/foo/foo.txt. Relative path name like subdirectory/foo.txt. This resolves to currentdirectory/subdirectory/foo.txt. Absolute path name like /main/foo.txt. This resolves to /main/foo.txt.

After a good chunk of discussions, all were in agreement to scale back the scope of the initiative to just the "Web Services" piece, and spin off the Layout/blocks/related-UI parts to a separate effort. Furthermore, some efforts, such as PSR-0 and Unified Plugin system, were only semi-related to the WSCCI initiative in the first place, and just happened to become relevant for it. Work on those efforts will continue as part of the general Framework community efforts.

This module contains code to create an iCal feed in Views. It has been pulled out of the Calendar iCal module because it has no dependency on Calendar and it could be used on any view. The code has also been generalized so that it will work for any entity, not just nodes. It creates an 'iCal' view mode for every entity type that can be used to to configure the description used in the iCal feed, and adds theme suggestions to tell Drupal to look for an iCal version of the entity template.