inline... On 03/09/11 06:56, Andrew Lowenthal wrote: > 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 >
great ... I see that ideas are the same as I've listed in my email, so nothing new to you. If I'm going to do anything in this direction I would definitely let you know in advance. > 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 see that some of the features you planned for 4.5 I would already need. I guess haviing them earlier it wouldn't be a problem, right? > 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. > sure login to Trac would be nice so I document what I do. > Dimo and Mike can provide you with much more detail on the architecture > side of things and also any questions about Transcode Daemon. > I'll try to catch them on #plumi (what are their nicknames) if they have time to share thoughts on this. > 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. > great .. i need the new design by the end of Monday so I'll continue on this in branch. In short what the plan is: - make ``plumi.skin`` "optional" not installed by default with ``plumi.app``. - create a design for my client using plone.app.theming and make sure all templates are included in ``plumi.content``. I saw some of this work already being done, maybe its already done. I guess until I try create to Plumi theme without ``plumi.skin`` I will never know. - since my clients theme will look a lot like plumi theme i could also create package ``plonetheme.plumi``. - additionally I'll also test if Plumi can be upgraded to Plone4.2a2 I guess once I receive trac login I might write this in some ticket. > 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. > See you on #plumi. _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
