FeedAPI: More processors in sight

Events happening in the community are now at Drupal community events on www.drupal.org.
aron novak's picture

Last week and today I achieve the following results (basically I followed the last week report's todo):

  • I resolved the namespace conflict
  • It's possible to create a feed without installed proper parsers/processors, and after the creation you can assign the submodules.
  • The node processors (feed and item) now has many settings
  • It seems that PHP4 support is ok.
  • I created the permission system (two permissions are present now)
  • Extended hook system, i created a summary of the reasons and the new possibilities below

Previously I imagined the parsing with a strict collaboration of parsers, feed processors and item processors. It seems that works fine, but it seems to restrict the expandable property of the API. I mean that every connected module should be (parser || processor) , there is no exception. To write a (parser || processor), you have to implement a well declared set of hooks. This makes impossible for eg. an item processor to know something about feed creating. This is not enough adaptable. That's why I created feedapi_"op"_after hooks (where op can be load, refresh, etc, etc).
Todo: see the title. Aggregator-like processors can be expected next Monday.

Comments

Alpha release

aron novak's picture

FYI: an alpha release of FeedAPI was created (with the Aggregator-like processors)

SoC 2007

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: