Re: [PLIP-Advisories] [Plone] #9352: Improved search results
#9352: Improved search results +--- Reporter: laurenskling| Owner: spliter Type: PLIP| Status: assigned Priority: major | Milestone: 4.2 Component: Infrastructure |Keywords: search +--- Comment(by spliter): Hello, I am planning to re-arrange the search filters we have on the search results page and make it becave as a normal dropdown we have in Plone (for personal tools, etc.) without fancy animation (putting the column on the left doesn't work in fixed-width sites). Problem is that dropdown.js responsible for providing the effect is restricted to authenticated users only. What would be the best way to do the same in the new search? Remove the restriction from dropdown.js or provide copy of the behavior in search.js (plone.app.search specific javascript)? -- Ticket URL: http://dev.plone.org/plone/ticket/9352#comment:77 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #9352: Improved search results
#9352: Improved search results +--- Reporter: laurenskling| Owner: spliter Type: PLIP| Status: assigned Priority: major | Milestone: 4.2 Component: Infrastructure |Keywords: search +--- Comment(by mj): Don't duplicate JS code, simply make dropdown.js available for anonymous as well. -- Ticket URL: http://dev.plone.org/plone/ticket/9352#comment:78 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #11300: Switch to HTML5
#11300: Switch to HTML5 ---+ Reporter: spliter| Owner: spliter Type: PLIP | Status: assigned Priority: major | Milestone: 4.2 Component: Templates/CSS |Keywords: ---+ Changes (by spliter): * cc: plip-advisories@… (added) Comment: So, I supose the conclusion about HTML5/Diazo can be made as: plone.app.theming should give HTML5 doctype in the output. I suppose we can postpone tinkering with core Diazo, when served from Apache or Nginx, for now. This is great. Ideal situation would be, of course, as Alec mentions to serve whatever doctype is defined in the theme though. But it's for p.a.theming PLIP. About the current PLIP. In order to have this PLIP finished, I actually, need to introduce some JS shim for Internet Explorer. I would definitely want to have Modernizr in Plone and don't agree with Laurence that it is not suitable for a point release. Modernizr should not break backwards- compatibility in Plone but instead should let authors write HTML5 and, what can be important as well, eliminates any separate stylesheets for IE- only styles. Modernizr applies special CSS class like ie-6 or ie-7, etc. on html element. Also no need in conditional comments for IE-specific stylesheets in head. Alec, I suppose I need to submit a new PLIP for Modernizr's integration. Is it correct? -- Ticket URL: http://dev.plone.org/plone/ticket/11300#comment:29 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #11300: Switch to HTML5
#11300: Switch to HTML5 ---+ Reporter: spliter| Owner: spliter Type: PLIP | Status: assigned Priority: major | Milestone: 4.2 Component: Templates/CSS |Keywords: ---+ Comment(by alecm): Having looked at the Modernizr docs, it looks like a pretty good idea to me. However, if it's not required for implementing some aspect of the HTML5 transition, I'm not sure that it belongs here instead of in a separate PLIP. Similarly, I'm not sure it makes sense to PLIP it on its own unless the PLIP provides some specific ways that Plone can make direct and immediate use of Modernizr features. If it's just something people can use to help implement better HTML5 themes and content (e.g. compatible across browsers), then it may be best to just create an add-on that installs it in Plone (similar to collective.js.jqueryui). -- Ticket URL: http://dev.plone.org/plone/ticket/11300#comment:30 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #11300: Switch to HTML5
#11300: Switch to HTML5 ---+ Reporter: spliter| Owner: spliter Type: PLIP | Status: assigned Priority: major | Milestone: 4.2 Component: Templates/CSS |Keywords: ---+ Comment(by spliter): Replying to [comment:30 alecm]: Having looked at the Modernizr docs, it looks like a pretty good idea to me. However, if it's not required for implementing some aspect of the HTML5 transition, I'm not sure that it belongs here instead of in a separate PLIP. In order to complete this PLIP, we need to introduce support for HTML5 elements in Internet Explorer. More reading on the topic — http://html5doctor.com/how-to-get-html5-working-in-ie-and-firefox-2/. Even though we are not going to introduce any new HTML5 elements now, the end integrators will do so and Plone should support the elements out of the box. Hence we need a shim to provide the support in IE. There are 2 ways: * we add shim-only JS (like http://remysharp.com/2009/01/07/html5 -enabling-script/) * we add Modernizr that has shim integrated together with other features. At some point Modernizr should be part of Plone in my opinion. So, integrating separate shim and then, hopefully, Modernizr doesn't really make sense to me if we can integrate Modernizr now and get the shim. Similarly, I'm not sure it makes sense to PLIP it on its own unless the PLIP provides some specific ways that Plone can make direct and immediate use of Modernizr features. If it's just something people can use to help implement better HTML5 themes and content (e.g. compatible across browsers), then it may be best to just create an add-on that installs it in Plone (similar to collective.js.jqueryui). Modernizr does provide features that Plone might start using right away: * aforementioned HTML5 elements support in IE * special CSS classes on html element for writing IE-specific styles that are valid CSS (not, silly * html hacks). With this we could deprecate ie.css an ie.js (or whatever they are called) since both of those can take advantage of the CSS classes. * In addition we get the main feature of Modernizr — feature detection. This lets us build future proof application that just get better and better over time when browsers support more and more of HTML5 natively. Second point requires main_template.pt changes so, integration of Modernizr through an add-on doesn't feel like the right thing to do. -- Ticket URL: http://dev.plone.org/plone/ticket/11300#comment:31 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
Re: [PLIP-Advisories] [Plone] #11300: Switch to HTML5
#11300: Switch to HTML5 ---+ Reporter: spliter| Owner: spliter Type: PLIP | Status: assigned Priority: major | Milestone: 4.2 Component: Templates/CSS |Keywords: ---+ Comment(by alecm): Sounds like a good set of reasons to keep it a part of this PLIP then! -- Ticket URL: http://dev.plone.org/plone/ticket/11300#comment:32 Plone http://plone.org Plone Enterprise Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-plip-advisories
