apis

Hi Everyone, just wanted to put out a quick note about a new module that we'd love feedback on. It's called Content API, and is a drop-in solution for making all your content available via web APIs with no programming necessary. We built it as a part of the redesign of FCC.gov, and is being used there to power the new website. More information is available at the project page: http://drupal.org/project/contentapi. For those of you at CapitalCamp a couple of months ago, this is the module I previewed in my API publishing talk.

Say Hey!

About a dozen Facebook API developers and application designers are getting together at the A's game tomorrow night (Weds - 5/18) to cheer on the local squad, have a beer or two and talk tech in a casual, fun environment. Your TICKETS are FREE, but it's first come, first serve. Weather is due to dry up this afternoon, and should be delightfully brisk by tomorrow evening. Game starts at 7pm - take BART in / out of the city.

Contact me to reserve your spot today and I'll see you at the yard tomorrow night.

Nick Cawthon
ncawthon@gmail.com
510 542 7364

Hi

First, excuse me if theres already some solution for.
I've surfed drupal.org and also the groups but didn't find something...

What I've to do is building a "stack" like Acquia but with advanced functionality.

For this I'll need to grab some already existing Modules and change some of their functions to work "cleaner" with other or mine, too. Because of this it would make updating Core and also Modules a horrobale job I'm looking for a standardize solution to let Modules communicate with each other without bigger modifying.

Anyone have suggestions about where we should start with this group? Some of the things I think would be helpful are...

After several weeks of tangling with code I have release a new version of the JQuery Menu module that now provides an api for parsing hierarchical arrays into jquery click and expand menus. I have also released two new modules which make use of this api: the Advanced Taxonomy Blocks and the Advanced Book Blocks modules.

Moved to official ideas list: http://drupal.org/node/237907

I want to propose a project for building a module that pulls news content from a global news service called Daylife (http://daylife.com)

Daylife is a global news aggregation service that offers an Open API platform called DayPI (http://developer.daylife.com) for any developer, blogger, news service to pull stories and photos about any topic in the world. The API returns data in XML, JSON and PHP serialized formats. You can read the Daylife About page at http://www.daylife.com/page/about to learn more about the company. All platform documentation is on http://developer.daylife.com/docs

.

.

As some of you know, I've recently taken over maintenance of Inline and Image Assist, and initiated the Wysiwyg project. That was not only caused by personal interest, but also to take the necessary steps to realize the long awaited Inline API. You might ask yourself, what those three modules have in common or to do with each other at all: They deal with user input, allow to embed complex contents into a content, and provide an interactive GUI for that. If you already had the chance to work with them, you already know that there is a rather hidden, non-obvious hard-dependency between them.

Although I'd really like to discuss both topics (Inline and Wysiwyg support) separately, the gained experience on these topics enforces us to discuss them concurrently. The following mockup hopefully explains why: (see attachment to view in full size)

Myself and a few developers are about to make some rather big changes to the userpoints module API which would force all contributed modules (contribed to the userpoints module that is) to change. We'd like to get as much feedback on these changes as possible.

If you use userpoints and/or any of the userpoints contributed modules please take a minute to comment on these two threads
http://drupal.org/node/153626
http://drupal.org/node/151037

Thanks!

Per snelson's (creator of these amazing sites) description of the Services module:

Here's the low-down on the upcoming.org integration module:

Per the developers description: The upcoming.org module enables you to import events and venues from upcoming.org and display them in a calendar using the event module. Upcoming.org is a website that helps you share and keep track of your events. Synchronizing (using upcoming.org as the master repository) is also supported. Additionally, this module exposes the upcoming.org REST API, making clients written to use it interoperable with Drupal. This makes it possible to build a whole network of websites sharing their events, all using a defined API.