I'm too late for my own deadline, so I have no expectation that the
framework can review this on time time. If you guys have a bit of spare time
I would appreciate it though :)
I want to propose PLIP 242 for Plone 3.3: Move manage-portlets link to site
actions.
Motivation
==
Both
Another one from Danny..
http://plone.org/products/plone/roadmap/231
Optionally copy roles from parent when blocking inheritance
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Previously Raphael Ritz wrote:
I think we have this on the radar already
(seeing comments from most team members
on the plip page)
The framework team desparately needs someone who coordinates things and
keeps lists of PLIPs that are being reviewed. I hope that the team can
elect someone to
There appear to be a fair number of PLIP that are marked as being
proposed but never made it to this list. I would like to encourage the
framework team to take a look at the current list of PLIPs and see if
there are any that should be rejected or should be considered for 3.3 or
4.0.
Wichert.
Raphael Ritz wrote:
Wichert Akkerman wrote:
I'm too late for my own deadline, so I have no expectation that the
framework can review this on time time. If you guys have a bit of
spare time I would appreciate it though :)
Hi Wichert,
don't worry too much.
At least I planned to start
I think Danny wanted to propose this for 3.3 but forgot to mail this
list? The workflow status shows that he proposed it.
Motivation
==
The display menu is a setting that controls how an object presents
itself to the user. Right now it suggests it is a switch that every user
can change
Wichert Akkerman wrote:
I'm too late for my own deadline, so I have no expectation that the
framework can review this on time time. If you guys have a bit of
spare time I would appreciate it though :)
Hi Wichert,
don't worry too much.
At least I planned to start reviewing only after
the
Wichert Akkerman wrote:
I did mention that on the web-version of the PLIP. Site actions works since
it mostly contains rarely-used items, which includes manage portlets. But
you are very correct in that document actions would technically be more
correct.
Not all views include
Wichert Akkerman wrote:
A PLIP from Michael Dunlap and Florian Schulze which is marked as being
propsed in its workflow state but apparently not mailed to this list (I
sense we need a content rule for this stuff..)
after the upgrade to Plone 3 ;-)
(and once the trigger on workflow state
Wichert Akkerman wrote:
First: remove the Display menu and add a field to the settings tab of
the edit form where it belongs.
-1 for 3.x.
- This breaks existing documentation and expectations.
- The display menu is not specific to Archetypes or any particular
content type implementation.
On Thu, Oct 9, 2008 at 12:54, Raphael Ritz [EMAIL PROTECTED] wrote:
Yup, I guess most of us consider Andy to be that one
but I know he sees this differently.
Anyone from the team willing to take this on?
/me steps back smartly. I won't be able to take this; as it is I am
hardly covering all
Hi,
Ethan Jucovy wanted to propose a PLIP for 3.3, which I've seconded. He
has been having problems with plone.org and his laptop, but the text is
pasted below. We'll get it moved to a real PLIP soon, but I'd appreciate
it if you could review it.
Cheers,
Martin
Automate ZCML Loading
On 9 okt 2008, at 11:29, Martin Aspeli wrote:
Wichert Akkerman wrote:
I did mention that on the web-version of the PLIP. Site actions
works since it mostly contains rarely-used items, which includes
manage portlets. But you are very correct in that document actions
would technically be
On 27 sep 2008, at 16:15, Wichert Akkerman wrote:
I want to propose PLIP 238: Disable inline editing by default
Motivation
--
I suspect that by now most of us have realized that the current
inline editing
behaviour in Plone 3 is not very practical. It has two main problems:
* it
On 28 sep 2008, at 07:47, Martin Aspeli wrote:
Wichert Akkerman wrote:
I guess I'm the first one. I want to propose PLIP 228 for Plone 3.3.
I feel that removing the removal of the 'Add Item' dropdown in many
places in Plone 3 is a regression in behaviour, and makes adding
content
a lot
It seems that this plip has a few valid comments that seem to extend
it. What will the plip exactly be? Is it only about direct linking or
also a better way to use it to link internally? For the latter you
could imagine a different widget that either uses the yet-to-come
Sounds good but for my understanding could you please give me more
info and refresh my memory of what this sorting was for originally?
On 5 okt 2008, at 16:47, Andreas Zeidler wrote:
hi,
i'd like to propose PLIP 241[*] for plone 3.3: removing the unused
auto-sorting, -ordering code would
On 6 okt 2008, at 03:22, Raphael Ritz wrote:
David Glick wrote:
I'd like to propose PLIP #240 for inclusion in Plone 3.3:
http://plone.org/products/plone/roadmap/240
This PLIP is intended to provide several avenues toward
addressing the problem of content accidentally getting left in a
On 9 okt 2008, at 11:32, Martin Aspeli wrote:
Wichert Akkerman wrote:
First: remove the Display menu and add a field to the settings tab of
the edit form where it belongs.
-1 for 3.x.
- This breaks existing documentation and expectations.
Mmm.. change the docs then ;-)
- The display
19 matches
Mail list logo
