sorry i was busy finish work. I went with first idea to redo design with plone.app.theming instead of creating plumi.video package. i'll post more on that in separate email but i'll still give you comments on second one... below.
> >> - second idea - since we share similar vision - would be to start >> factoring out things from plone.(app|content|skins) into ``plumi.video``. >> >> >> currently I'm more leaning on the second one, but I would still like >> your input on it. I think best would be to write short proposal what to >> include into ``plumi.video`` to the list and then you comment on it. > > That's exactly what we've been thinking of doing: Replace plumi.content with > plumi.video and plumi.callout, since the callouts are a requirement specific > to engagemedia.org and most other Plumi users don't really need them. It's > important however not to break backward compatibility and there are a few of > open questions: > > * Should we keep the video schema as it is? Or maybe revise & simplify it? In > the current video add/edit form there are lots of fields in the form, some of > which are required, making the upload form rather unfriendly to users. We've > been thinking of redesigning the form and the fields to make it look a bit > more like youtube/vimeo/blip.tv where the user first uploads the video file > and after or during the upload she can fill in any available metadata. > > * Should we keep using Archetypes for the new plumi.video content type, or > maybe migrate to Dexterity? Or maybe forget about a having video content type > and instead use schemaextender to extend the standard File type when a video > file is uploaded. > > What do you think yourself? I tend to think that Dexterity is better suited > so that site admins can extend the schema through the web, but OTOH it may > break a lot of the existing functionality. > i believe it should be done in similar way collective.flowplayer is doing. its auto marking (with interface) content (be it File or any other content type). then all video features are bound to that interface. I think you should also move away from flowplayer and use mediaelementjs[1], there is already some integration done for plone[2] I beleive plumi.video should: - or use already started integration of mediaelementjs (or do it again if that one is not ok) - enable transcoding for default File content type. - provide easy hooks for integrators to use transcoding in their projects. I believe I wont have any projects with media coming up in next months so you can take this as comments only. But i definitely keep thump up (+1) for refactoring plumi to more reusable pieces. sadly none of my projects needs it at the moment. good morning :) [1] http://mediaelementjs.com/ [2] https://github.com/tomster/collective.mediaelementjs _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
