On Sep 23, 2008, at 1:34 PM, Bill wrote:
> > 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. Thanks for sharing! This is definitely the right place for these kind of questions, though once you have a fleshed out plugin the wiki would be a nice place to document it as well. > > > 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. :) I completely see your point – thanks for volunteering to build this! :) > [snip] > > 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. A silo would definitely be a good way to go about this – especially since your core interface should be built around the "publish photo" page. > > 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? Yes, you can do this. Your plugin should implement the 'adminhandler_post_loadplugins_main_menu' filter and unset the menu items which you want to hide. Something like this: http://pastoid.com/8w. > 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? Yes, plugins have a priority. I do not know how that priority is determined off the top of my head. Please note that FormUI works progmatically: multiple plugins can modify the same view, with each one adding and removing various fields. That will all be handled transparently until the final product (the form) is output. > 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? It means you cannot create new posts with that type. > 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. Yes, this is definitely doable (though no easy feat). The Habari community is always very glad to help. Thanks for working on this! > > > Any comments, advice, etc? I'd focus on getting the most basic functionality working to start with (publishing a single photo), and then publishing it to the developer list so we can comment on how you are doing things and assist you in developing the more advanced hierarchy. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
