Sure, we can treat as a separate PLIP if you think it's a bad idea for
4.3. In my mind, it was part of the same stream of work, just
something that I couldn't land in time, but I can see how it's
technically at least quite separate.
In any case, I'd love some FWT input.
On 2 November 2012 16:40,
Er...as a member of the framework team, my recollection was that we
approved that PLIP and you merged it. Plone 4.3 isn't really open to new
features right now; we're trying to get it out the door. I'll make sure
the fragment thing is on the agenda for the next meeting though.
David
On 11/2/1
Yes. It's not really described in that PLIP, but it's part of the same
work (i..e trying to get our non-Python/filesystem theme development
story to stack up). Hence, it fits with the same branch and timing, at
least.
On 2 November 2012 11:42, Matthew Wilkes wrote:
>
>
> Alex Clark wrote:
>>
>> I
Alex Clark wrote:
I'm not on the FWT, just trying to follow: where is that PLIP? All the
Diazo related PLIPs I can find are closed:
I believe Martin means this one:
https://dev.plone.org/ticket/12227
Matt
___
Framework-Team mailing list
framework-
On 2012-11-02 08:21:50 +, Martin Aspeli said:
That's the whole point: There's a PLIP for 4.3 with Diazo
improvements, and this is part of that. Hence I'd like some review
before I merge this part of it.
I'm not on the FWT, just trying to follow: where is that PLIP? All the
Diazo related
Also, JSON support for content is a completely orthogonal concern.
On 2 November 2012 01:50, Alec Mitchell wrote:
> FWIW, I'm also -1 without this going through the PLIP process. A
> plugin would be fine. Personally, I'd rather see JSON representations
> for content and listings than either thi
That's the whole point: There's a PLIP for 4.3 with Diazo
improvements, and this is part of that. Hence I'd like some review
before I merge this part of it.
On 2 November 2012 01:50, Alec Mitchell wrote:
> FWIW, I'm also -1 without this going through the PLIP process. A
> plugin would be fine.
I'm +1 on this. It seems well defined, limited in scope, simple,
powerful and optional. It seems like a situation where there's high
reward *if* it gets used, and little downside if it doesn't. It's the
best answer I've heard yet to the problem of how to go beyond Diazo/XSLT
*and* how to avoid f
FWIW, I'm also -1 without this going through the PLIP process. A
plugin would be fine. Personally, I'd rather see JSON representations
for content and listings than either this or the contentlistings type
hackery.
Alec
On Thu, Nov 1, 2012 at 5:55 PM, Elizabeth Leddy
wrote:
> I'm technically no
I'm technically not on the FWT but -1 for doing this like a bug fix. I am in
agreement with djay, but more importantly we have been very good about going
"add-on first, core second". I can see this being a product bump (like tinymce
is at the moment) for a good couple of months and then getting
Guys,
I'd really like some FWT input on
https://github.com/plone/plone.app.theming/pull/10
It's ready to merge, but there seems to be different opinions about merit:
* Laurence and I see it as an important way to solve a certain class
of problems, where Plone's markup isn't sufficient as a bas
11 matches
Mail list logo
