Re: [Cctools-cchost] modularization strategy

[Jon P. <jo...@cr...>]

I'm wrong...removing that cc-bpm.php removes the bpm...my bad :)

Jon

On Fri, 2006-09-08 at 18:21 -0700, Jon Phillips wrote:
> So, I'm wanting to genericize some things and move some code around here
> early on in the next cycle. I'm wondering what you all think about
> moving things out of cclib/ccextras into another location that is not
> auto-loaded into another SVN module like cchost-extras or something so
> we can start a repository of modules that make cchost function
> differently. We could then put out this as another package from our
> project...
> 
> NOTE: The ccextras folder's contents are auto-initialized by ccHost upon
> initialization. Thus, think of it as a plugins folder.
> 
> One good example is the cc-bpm.php file in ccextras. It adds a bpm
> functionality to cchost (however, I just realized that the bpm field is
> still a part of the upload forms).
> 
> The other approach is to have a top-level enabling of the extras in the
> admin interface. That way, any extras can stay in this folder and we
> don't have to move anything, and we can enable and disable extras and
> keep this info in the database.
> 
> VS and others, what do you think?
> 
> I'm really wanting to focus on genericizing cchost for different types
> of media for the next 3.1 release cycle...
> 
> Jon
-- 
Jon Phillips
jo...@cr...
cell: 510.499.0894

Software Engineer
Creative Commons
www.creativecommons.org