Recap of the first topic of my last message, for emphasis:
The obvious topic for the March newsletter is the DrupalCon, of course. There are over 800 people here, though and we need to recruit people to write up their favorite session/s. If you are at the conference, please write up at least one session, and/or find three other people who can write up a session. We only need a paragraph or two, but feel free to write up a whole big article if you're inspired.
Sneak preview of this discussion (if you decide not to click through to the rest of this discussion topic): http://drupal-newsletter.org/issue/2008/01
This DrupalCon has been phenomenal! We had an impromptu BoF session yesterday for the Drupal Newsletter. The three big things that came out of that were a plan for March's newsletter, the newsletter length, and building a stand-alone site for the newsletter.
The obvious topic for the March newsletter is the DrupalCon, of course. There are over 800 people here, though and we need to recruit people to write up their favorite session/s. If you are at the conference, please write up at least one session, and/or find three other people who can write up a session. We only need a paragraph or two, but feel free to write up a whole big article if you're inspired.
To the second item, we plan to use a system of teasers for the next issue. We'll put each section and/or article in the groups, and just link a manually created teaser in the digest that gets e-mailed and posted on d.o. We'll refine that process as we continue creating future newsletters.
Which is yet another strong case for a stand-alone newsletter site, bringing us to the third item of discussion. We created a working group, currently consisting of Alex UA, mlsamualson, and myself, to create a proof-of-concept stand-alone site. You can see it at http://drupal-newsletter.org/issue/2008/01 (which is just filler, as you'll see).
Jacob Redding (jredding), Robert Scales, and John Zhu conducted a panel about Drupal in China yesterday at DrupalCon. We all learned about why and how China is beginning to embrace Drupal.
I plan to do a better write-up for the Drupal Newsletter, so you'll have to wait till then to hear more about it. However, I did manage to sneak in quick 20 minutes during the panel and write Embedded Media Field support for Tudou.com, the Chinese version of YouTube. As a side-note, tudou translates roughly to 'soil tofu', or 'potato'.
You can see a higher-res version of the video at Jacob's blog wiredgeek.com.
So I was just updating the Contributed Modules Status page at gdo to reflect that I plan to work on upgrading Embedded Media Field to Drupal 6.x during DrupalCon, and noticed that fago also plans to work on Workflow-ng "after the drupalcon". So I scanned through the list to see if anyone else was planning module development this week, and that was it.
Now the way I am at these conferences is that I get into overdrive. I already spend my 8 hours a day at work buried in Drupal, and an additional 8-10 hours a week of my personal time. But, apart from periodically calling my partner & daughter to let them know I'm still alive and remember them fondly ;), I spend every waking moment at a Drupal conference thinking about Drupal, how it can "save the world", and how I can do my bit to help that happen. I find myself so energized by being around other like-minded people at these events, that I throw myself into making cool modules, upgrading other cool modules, etc.
I know I'm not the only one like that.
Since the word of the day is "Drupal 6", I'm curious who else is going to be working on porting their modules during DrupalCon. So I did a 5 minute google right now on "upgrade drupal 6 drupalcon" and found nothing there. But I know it'll happen. Either folks are keeping it under wrap, are too busy to blog about it, or don't realize yet that that's what they're going to do. (Time for me to brush up on the Coder module...)
Whatever the case, March 10 should be an exciting day in the world of Contributed Modules. I'd put money on some of your favorite modules being ready for d6 the week after the conference (maybe not deployment-ready, but certainly testing-ready). And I wouldn't be surprised to see a quiet module or two come out of the conference that will rock the world of Drupal, and send waves through the Internet.
So I had a dream last night. About Drupal, as I often do. I envisioned a way to make Embedded Media Import, which is bundled with Embedded Media Field, far more useful than it currently is. And I don't think it'll be too difficult to implement either.
I plan to work on this at DrupalCon, if anyone's interested. Alex Urevick-Ackelsberg and I plan to do some work towards updating the module to Drupal 6 at that time anyway.
emImport currently works by pasting the URL of a playlist, currently only from Flickr, but easy enough to implement for other providers such as YouTube, into a text field. You are then presented with a screen of captured media, with checkboxes, to import them as nodes, complete with titles, descriptions, media, and tags.
The next step is to allow this to automatically aggregrate playlists. In my dream, it was a new module, which I dubbed Embedded Media Aggregrator. However, after thinking about it this morning, I think it would be better to simply integrate that into emImport. In either case, the functionality would simply be built on top of what's already there.
Following is my envisioned workflow from the editor's perspective...
I will be the lead presenter of the Drupal Multimedia panel at Boston DrupalCon next week. I am teaming up with James Walker (walkah), Darrel O'Pry (dopry), and Nate Haug (quicksketch) on Monday, March 3, in the Site Building track, with a live demonstration integrating images, video, and audio onto your sites.
I think the feedapi integration patch is all that's really holding up a release, if you want to go over there and help test it...
when you say near term, is that near as in the next couple of weeks or near as in the next year? I have a job right now that could make use of this, I would like to stall for time until some sort of release, so an indication of any sort of release would be awsome. (I would be a willing tester)
cheers,,,, looks awsome.
Interface building is already possible: http://drupal.org/project/atck
besides the benefits this technology brings (ajax stuff), we have to remain on our toes not to overload the system, because for example the sproutcore system is painfuly slow.
Kinda interesting, it would be cool to see drupal apps going in this direction
http://www.sproutcore.com/ http://ajaxian.com/archives/an-interview-with-280-north-on-objective-j-a...
From a design standpoint It would pretty neat to build apps in visual interface builder. Sproutcore is heading this direction already. http://developer.apple.com/documentation/DeveloperTools/InterfaceBuilder...
for these kind of apps SEO really isn't necessary.
My battle plan was to offer API to other modules to display their content in 2 steps:
step 1) this is the first time content is being displayed. this will dump plain HTML from the server to the user
step 2) this will take the content in step 1 and attach actions to it so that when user interacts with that content it will isolate individual sections and communicate it back to the server via AJAX at which point content will be served through JSON + AJAX bypassing module's own theming layers.
the flaw with step 2 is that the module will be limited only to theme functions that are currently defined by js_theming module.
I will take care to come up with with some solution that will enable misc modules expand the javascript theming functionality. the project is still in very early stage of it's life and it already supports item lists, table theme, handles drupal status messages in a smart and admin configured way, allows table themes to offer table sorts just like drupal core does. offers themes for l() and url() functions. i think i forgot to mention other things but as you can see its growing rapidly and pretty soon will include more features to aid user end javascript theming.