Re: What I'd like to see gsoc achieve: plone distributions

> Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]> kirjoitti 2.4.2015 kello 12.02:
> I haven't used a legacy portlet in 5 years. They should really die since nowhere else lets you put ZPT code inside the content space and where content editors can screw it up and break the page. In fact can't we drop it in plone5?

Well, someone could refactor it into optional add-on.

Context portlet configuration (with inheritance and blocking) is still something, which cannot be fully solved with Diazo. Even blocks / deco / mosaic is still lacking missing that.

>> I did an experimental branch, where you can define restricted python view methods for fragment views:
>> 
>> https://github.com/collective/collective.themefragments/commit/75c194b26a5dd9a3827c2d43876042fb3cd860c2
> 
> Can you call python directly from diazo?

I hope not. Why would you want to?

> Is there any differences from what you've added to fragments and erics proposal?

- those were standalone files with methods, these are one method per file (like PythonScripts or ZClass methods) and bound to template (like a method in class based view)

- Eric's script accept parameters, but in the examples those were only to get the context for the method; in fragment scripts have "self.context" (and parameters don't make much sense when view methods are called from a template)

- Eric planned to use zope.untrustedpython, where I still used the old RestrictedPython (maybe Eric could help me to fix that)

Cheers,
Asko
------------------------------------------------------------------------------
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/