hey guys,

I've got a task to customize Plumi installation a bit and found it quite
a challenge since Plumi by default installs everything (all extra
content types, theme, etc...) to provide best experience it can. But for
custom work - which I usually do - I would like to use only bits of
Plumi (eg. in current project only video CT and transcoding daemon).

Ofcourse I could create product which would uninstall whats not needed
in my project while still keeping stuff that I need installed. But if
the project would have more modular structure i wouldn't need to
uninstall anything in the first place, right?

so to cut the story short, I would like to:
 - create Plumi package would work in same manner
 - separate code from plone.(app|content|skin) into separate packages
plumi.(video|audio|callout|...) and installed them while
 - migrate plumi.skin theme to diazo theme.

above structure would provide me (or anybody else) to reuse only part of
Plumi while users who want full Plumi experience will still make this
possible.

would anybody object changes above? ofcourse nothing is set to stone, so
if you want to talk with me about what/how i plan to change stuff i'm
online (garbas on freenode) so just ping me. if not ... i'll be working
on a branch and hopefully you could review my changes and merge them
upstream.


Another question, regarding transcoding daemon. What there any specific
reason you didn't went with socket.io to get back the info when video is
transcoded? I might have few hours this weekend to play with idea of
using socket.io+pyramid+celery as a transcoding daemon.


_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss

Reply via email to