One way to mitigate this — and make Plone seem a bit more modern
along the way — could be to apply the new typography/theme that I'm
currently applying to trunk. This is essentially the typography from
the plone.org redesign along with a color-neutral design for the
navigation and other UI
Alexander Limi wrote:
On Tue, 05 May 2009 15:56:36 -0700, Ricardo Alves
wrote:
Steve McMahon wrote:
My only concern about calling Hanno's incremental change list 4.0 is
that we don't suffer from big-number expectation syndrome.
This is the biggest risk I guess, a major release with just a
Alexander Limi wrote:
On Sat, 09 May 2009 05:09:07 -0700, Martin Aspeli
[..]
We'd also need to find a way to not break all existing themes.
It will "break" (ie. slightly change) themes that reuse parts of the
original Plone CSS as part of their theme. Luckily, the fix is easy: make a
On Sat, 09 May 2009 05:09:07 -0700, Martin Aspeli
wrote:
I'd support this, *if* it follows the usual PLIP process and we actively
encourage outside review from the get-go. That process may mean the
theme change gets a thumbs-down.
Of course.
We'd also need to find a way to not break al
There was already quite a lot of work done in this precise direction
during the Plone Conference 2007 Theme sprint.
http://www.openplans.org/projects/plone3-example-themes/capri-theme
accessibility and more stuff where considered, also. I don't
particulary like the final (uncomplete) design o
Can we please stop the cc-o-rama? Seeing the entire thread tree times is
a bit much..
Previously Martin Aspeli wrote:
> I'd support this, *if* it follows the usual PLIP process and we actively
> encourage outside review from the get-go. That process may mean the
> theme change gets a thumbs-down
Martin Aspeli wrote:
Alexander Limi wrote:
On Tue, 05 May 2009 15:56:36 -0700, Ricardo Alves
wrote:
Steve McMahon wrote:
My only concern about calling Hanno's incremental change list 4.0 is
that we don't suffer from big-number expectation syndrome.
This is the biggest risk I guess, a major
Alexander Limi wrote:
On Tue, 05 May 2009 15:56:36 -0700, Ricardo Alves
wrote:
Steve McMahon wrote:
My only concern about calling Hanno's incremental change list 4.0 is
that we don't suffer from big-number expectation syndrome.
This is the biggest risk I guess, a major release with just a m
On Tue, 05 May 2009 15:56:36 -0700, Ricardo Alves
wrote:
Steve McMahon wrote:
My only concern about calling Hanno's incremental change list 4.0 is
that we don't suffer from big-number expectation syndrome.
This is the biggest risk I guess, a major release with just a minor set
of visible
On 05.05.2009, at 23:44, Steve McMahon wrote:
So, a couple of questions for us all:
1) If we call it Plone 4.0, can we restrict ourselves to a modest list
of improvements that will actually get coded this summer and tested
this fall?
that should be the litmus test for any feature IMHO, simple
Steve McMahon wrote:
My only concern about calling Hanno's incremental change list 4.0 is
that we don't suffer from big-number expectation syndrome.
This is the biggest risk I guess, a major release with just a minor set
of visible (UI) improvements, will bring bad publicity.
If we start t
My only concern about calling Hanno's incremental change list 4.0 is
that we don't suffer from big-number expectation syndrome.
If we start thinking that 4.0 "has to be big enough" to justify the
numbering jump, and start expanding too much on the "yes" list, we
won't get this out in 2009. And, it
12 matches
Mail list logo
