Hi everyone, This message is going to be a bit verbose so please bear with me. The subject is about a photo plugin that I originally wrote for Wordpress a long time ago and want to port a newer derivative/design to Habari. My thought process is to cover the design, see what people think, and ask a few Habari API/functionality questions. If this is of no interest, abort now. :) If this is an abuse of this discussion list, please let me know, 'cause I certainly don't want to do that.
Feature Overview: Without getting into a big discussion of "Why create something that already exists in Gallery 2 or other tools and plugins?" Let's just say that I have my own reasons for features that I'm thinking about and because I just want to see if I can do it. :) In a nutshell, I want to write a plugin that gives me the ability to add photos and group them into sets (like Flickr). I want to be able to nest sets and have the ability to browse the entire gallery from a page (or something like that). In addition I want an easy mechanism to add individual photos as well as sets to posts and pages. Javascript for simple cropping/selecting portions for thumbnails. Possibly pluggable for different javascript or flash editors like picnik. Some "nifty" functionality I would like to have is the ability to tag parts of a photo similar to Flickr and Facebook and have those tags added to the tag list for the photo. I want to be able to display the photo metadata (exif, etc.) An even loftier goal would be to make the backend be pluggable (using silos?) so that different photo sources could be used but have one common interface. I've either written much of this in my Wordpress plugin or played with various pieces in test code so I'm not looking for someone to write it. Where I am lacking is the various pieces needed to adapt it to the Habari infrastructure. Questions: So I can take advantage of the Habari comment and tag functionality, I was thinking of creating new content types: ex. gallery and photo so comments could be created for them individually. In playing, when I've created these new types, I end up with four additional menu options: create gallery and photo, and manage gallery and photo. While I can certainly create views for all these, it seems a bit much to add that many menu items when really all I would really need is one: manage gallery. Is there a way to "hide" the others so I don't clutter the menu? OwenW already pointed me to a podcast for modifying the formUI so that I can update the post and page views. One question I was curious about here was what happens if multiple plugins modify the same view? Is there a priority or order to which plugins are processed? With the Post::add_new_type method, I noticed it takes an "activated" parameter, as well as having methods for activating and deactivating types, what does it mean when a type is deactivated? Finally, do the various pieces (at least that bind to Habari) seem doable. I'm still slowly spinning up on the Habari code. The pieces that I seem to need cat a better handle on are silos, plugin infrastructure, new content types. Any comments, advice, etc? Thanks for being patient with this. Bill --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
