> I know that there are some things that I had NO IDEA HOW TO DO, that
> took me forever to figure out (like adding custom images to an action)
> that would have been made a lot easier by a more detailed
> documentation for Plugin development. I would rather the QSB team
> focus on getting QSB running smoothly and adding more features to that
> than to bog them down with having to write development docs, and I
> feel like there are enough people who have successfully built and
> distributed plugins that we could come up with some tips and tricks
> ourselves. However, pages are turned off for this group (which would
> be my first choice for documentation related to plugin development).
> Any ideas?
Gordon,
We are headed in that direction. We have set up http://code.google.com/p/qsb-mac-plugins/
for a common repository for plugin storage and development. I would
be more than happy to add yourself and other plugin developers to the
committers list so that we could flesh out the site. I would love to
hear feedback from the plugin developers on manu j's list about moving
their plugins from the assorted repositories that they are currently
stored in to qsb-mac-plugins.
Some advantages we see:
a) one stop shopping for people looking for plugins
b) hopefully prevent bitrot because we could always be checking to
make sure plugins are up to date/working with latest code.
c) a centralized location for plugin developers to work from (and put
documentation).
What do you think? We are planning on moving some plugins that are
currently core QSB over there in the near future.
Cheers,
Dave
No interest by anyone? hmm.. that's unfortunate.
Cheers,
Dave
I think a centralized place for Plugins/Documentation is a wonderful idea. It would allow for a QuickSilver-like ability to browse available plugins from within QSB in theory, and would allow for a single spot for documentation.IMHO, one of the reasons for a lackluster response to your query has been the (externally apparent) lack of updates and new builds. I realize there were reasons (Chrome for Mac) the development slowed down, but I think this also slowed some of the early adopter momentum as well. Hopefully we'll start seeing some new builds soon which might help to energize the community around this effort.
Cheers,
Dave
--
You received this message because you are subscribed to the Google Groups "QSB Mac Developer Discussion" group.
To post to this group, send email to qsb-m...@googlegroups.com.
To unsubscribe from this group, send email to qsb-mac-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/qsb-mac-dev?hl=en.
--
Thanks,
Matt
--
You received this message because you are subscribed to the Google Groups "QSB Mac Developer Discussion" group.
To post to this group, send email to qsb-m...@googlegroups.com.
To unsubscribe from this group, send email to qsb-mac-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/qsb-mac-dev?hl=en.
I’d be happy to.
Martin