Plone notes/thoughts are what's left with js integration
Nathan Van Gheem <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAL8hw9GP-Z1uc5kT1dNng7NMvGToo4V3Y7G82Rr-Vg3oQpRUXg@mail.gmail.com> |
Hi all, The last couple days I've been looking at our final js issues. We're actually pretty close to being done. Here are a few thoughts on what is left and I'm hoping I get some responses in anyone has disagreements: - let's not get hung up on getting EVERYTHING into "patterns". We should be okay with having non-pattern js files in our code. Those non-pattern js-files should utilize/work with requirejs and our other patterns. I'm thinking of things like reqistry control panel/plone.app.event/etc. I think some of these js files don't fit easier into "pattern" space. - we should try and get rid of plone.app.jquerytools - we need to get rid of plone_javascript_variables--all that data should be on the body attrs now - it's hard to reproduce consistently, but I think we might have an ordering issue with legacy js/css import step - theming control panel is broken, needs lots of js love and some css love(since it's "unthemed") - Dexterity Types editor will need some re-work. I have a pretty bit project that I'm starting on that will be Plone 5 finally so I should be working on lots of this stuff now. Feel free to ping me. -Nathan ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers