|
Hi Rok, thanks for the email. What you outline here is a lot of what we've been thinking, we just haven't had the time to do it. Plumi definetly packages up way to much and a more modular approach is definitely the direction we should be going in. This is some work Anna did earlier in the year thinking about a "PlumiLite" http://plumi.org/wiki/PlumiLite If you look at milestone 4.5 in particular some of the issues are there http://plumi.org/report/3, but they are also dotted throughout the tracker. I'd be great if you wanted to make a crack at this - we can set you up with a login to the Trac also so you can document/ticket things if you need to. If it's done well I imagine we'd certainly want to bring it back in to trunk. Dimo and Mike can provide you with much more detail on the architecture side of things and also any questions about Transcode Daemon. One other thing to note is that we are planning a full redesign and reskin by the end of the year - you'd need to again talk with Dimo and Mike in terms of how that might impact what you are doing. In anycase, if you are in working on a branch you can obviously do anything you want - but the more we can coordinate the more likely we can bring it into trunk later. Any other thoughts do let us know. We also hang out a bit in freenonde #plumi. And. On 2/09/11 9:37 PM, Rok Garbas wrote: 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 |
_______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
