Hi All,<div><br></div><div>Got an update on themes in <a href="https://dev.plone.org/ticket/13355" target="_blank" style="font-family:arial,sans-serif;font-size:13px">https://dev.<span class="">plone</span>.org/ticket/13355</a>.<br>
</div><div><br></div><div><div>I turned the three flavours of HTML5 Boilerplate into Diazo themes (several levels of difficulty). Try:</div><div><a href="https://github.com/TH-code/plonetheme.h5bp">https://github.com/TH-code/plonetheme.h5bp</a></div>
<div><br></div><div>This led me to mocking about with bootstrap a bit more. Try out:</div><div><a href="https://github.com/TH-code/plonetheme.bootstrap">https://github.com/TH-code/plonetheme.bootstrap</a></div></div><div>
<br></div><div>Have a go at them and give me some feedback :-)</div><div>THijs</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 30, 2012 at 10:01 PM, Dylan Jay <span dir="ltr"><<a href="mailto:djay@pretaweb.com" target="_blank">djay@pretaweb.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div class="im"><div><br></div><div><br>On 01/12/2012, at 3:08 AM, Nathan Van Gheem <<a href="mailto:vangheem@gmail.com" target="_blank">vangheem@gmail.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 30, 2012 at 9:03 AM, Thijs Jonkman <span dir="ltr"><<a href="mailto:t.jonkman@gmail.com" target="_blank">t.jonkman@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<div class="gmail_extra"><br>(Thanks Nathan)<br><br><div class="gmail_quote"><div>On Fri, Nov 30, 2012 at 3:02 PM, Nathan Van Gheem <span dir="ltr"><<a href="mailto:vangheem@gmail.com" target="_blank">vangheem@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi all,</div><div><br></div><div>Could everyone review these plips and implementations and give some thoughts. Thijs has already done some great work and I'm not sure the best route to go here and I'd hate to waste too much of his time.</div>
<div><br></div><a href="https://dev.plone.org/ticket/13355" target="_blank">https://dev.plone.org/ticket/13355</a><div><a href="https://dev.plone.org/ticket/13358" target="_blank">https://dev.plone.org/ticket/13358</a></div>
<div><br></div><div>What we're aiming for and thoughts:</div>
<div><br></div><div>- plone ship with default diazo theme</div><div>- so people has a very basic way to get started using diazo(they won't have to create their own theme if they want to make some tweaks to move elements around)</div>
<div>- should the theme still work without diazo? I think so.</div></blockquote><div><br></div></div><div>I think we don't need to have the old and new style of the same theme. Reasons:</div><div>- Avoid confusion for users (I have a sunburst theme under Themes and Diazo themes, what gives?)</div>
</div></div></blockquote><div>The idea is it'd give people an easy starting point to modify the theme via the diazo theme editor.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote">
<div>- Maintain two nearly identical css codebases that achieve the same through different routes (not DRY)</div></div></div></blockquote><div>Still keep all the css in the same spot--skins for now. Otherwise, we don't get portal_css merging and everything.</div>
</div></div></div></blockquote><div><br></div></div><div>We really need to come up with a way of doing merging that works better with diazo. It doesn't make sense for the CSS to be so decoupled from the theme. </div>
<div class="im"><div><br>
</div><br><blockquote type="cite"><div><div class="gmail_extra"><div class="gmail_quote">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div>- Why have two ways to achieve the same goal? </div>
</div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>I've created a sunburst and a classic one. I can see the classic theme being done old style and sunburst through diazo, showing both theming ways for people new to plone.</div>
<div> </div><div>Why do you think the theme should work without Diazo? To not have plone.app.theming be obligatorily installed?</div></div></div></blockquote><div>Yes. Think of all the people who have based their themes on sunburst and now their themes will break unless they're forced into using diazo. </div>
</div></div></div></blockquote><div><br></div></div><div>+1. We have a lot of diazo themes based on sunburst. Backwards compatibility is really important. Same applies to skins. We need to deprecate before we remove. </div>
<div class="im"><br>
<blockquote type="cite"><div><div class="gmail_extra"><div class="gmail_quote">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>- should we still use skin layers? I think so.</div></blockquote><div><br></div></div><div>I don't really see a reason for that with a Diazo theme either. Maybe for jbot fun? But if you're going that route for customization, you could add a browser layer. Or apply it to all of plone...</div>
</div></div></blockquote><div>plone core shouldn't require the jbot package.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">
<div class="gmail_quote">
<div><br></div><div>Why should we use them?</div></div></div></blockquote><div>Because everyone's current themes depend on it. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote"><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>- migration and upgrades</div><div>
- what package should we put the theme in? Would it be confusing for plonetheme.sunburst to have normal theme and diazo theme?</div>
</blockquote><div><br></div></div><div>I would move the plonetheme packages to a 2.0 version with Diazo themes and keep the old themes in the 1.x versions.</div></div></div></blockquote><div>That's a possibility.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Ideas anyone?</div><div><br></div></blockquote><div><br></div><div>I think Plip 13358 needs to be roled into plone asap, Plip 13355 can definitely use some input :-) </div></div></div></blockquote><div>Agreed.</div>
</div></div>
</div></blockquote></div><blockquote type="cite"><div><span>_______________________________________________</span><div class="im"><br><span>UI mailing list</span><br><span><a href="mailto:UI@lists.plone.org" target="_blank">UI@lists.plone.org</a></span><br>
<span><a href="https://lists.plone.org/mailman/listinfo/plone-ui" target="_blank">https://lists.plone.org/mailman/listinfo/plone-ui</a></span><br>
</div></div></blockquote></div>
</blockquote></div><br></div>