months for beta/release
candidate state should suffice.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework
fewer big ones.
If you have many small deadlines they effectively become meaningless
since people will just wait for the next one (to fly by). I've always
tried to advocate a more continuous development pattern and I love
Elizabeth's proposal.
Wichert.
--
Wichert Akkerman wich...@wiggy.net
On 9/21/10 10:49 , Martin Aspeli wrote:
Hi,
I know we have a process that says reviewers should add their notes in
text files in the review buildout. I think it'd be bad to change the
process now, but for next time around, can I suggest that we use Trac
for all comments, voting and official
On 9/20/10 17:58 , Rob Gietema wrote:
Author: robgietema
Date: Mon Sep 20 15:58:35 2010
New Revision: 40085
Added:
buildouts/plone-coredev/branches/4.1/plips/plip10778-review-robgietema.txt
Log:
Added review for PLIP10778.
Added:
every use case you want more control over handling login
behaviour than WSGI middleware can provide. It is much simpler to have a
simple API to an AAA service and use that than to try pushing this into
middleware.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things
, and for that reason everyone has switched to the random
based approach as implemented by uuid4().
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team
an adapter factory returning None. That makes the API a
bit awkward, so I would suggest to replace the IUUID adaptor based
approach with a simpler helper function.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard
to
interpret errors too often. The wrapper method has the advantage of
having a more intuitive name and can distinguish between missing UUID
support and a None UUID, while not loosing any functionality.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http
On 8/24/10 13:55 , Martin Aspeli wrote:
This is the kind of feature that's more fun to think of and implement
than it is actually useful to anyone. Those who need archive download
functionality usually have very specific reasons for wanting it, and
typically do not want to allow people to
their Google account on a Plone site? Or their facebook login?
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
. It
needs to be reverted.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http
On 6/3/10 03:11 , Laurence Rowe wrote:
http://dev.plone.org/collective/changeset/118407 – plone pas cookies
path set for /plone_site instead of always root - ticket #5665 –
introduced a couple of test failures in Plone:
I've reverted that change.
Wichert.
On 3/16/10 12:34 , Laurence Rowe wrote:
On 15 March 2010 09:13, Alexander Limil...@plone.org wrote:
2010/3/12 Hanno Schlichtingha...@hannosch.eu
On Fri, Mar 12, 2010 at 5:39 PM, Laurence Rowel...@lrowe.co.uk wrote:
On 12 March 2010 15:07, Hanno Schlichtingha...@hannosch.eu wrote:
On 3/16/10 18:40 , Alexander Limi wrote:
On Tue, Mar 16, 2010 at 4:45 AM, Wichert Akkerman wich...@wiggy.net
mailto:wich...@wiggy.net wrote:
I'ld like to see a list of pros and cons of using HTML 5 as well. I
am quite worried by the lack of proper support in existing browsers.
None
you can just delete the Plone directory it created.
I suspect he means uninstall support for add-on products. Neither
GenericSetup nor CMFQuickInstaller properly support that.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net
.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
will have to style two types of form
markup. z3c.form provides the hooks to fix that, but someone needs to do
the work.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
tools in a pulldown regardless of whether the new theme lands.
--
Alexander Limi · http://limi.net
On Wed, Sep 16, 2009 at 10:52 PM, Wichert Akkerman wich...@wiggy.net
mailto:wich...@wiggy.net wrote:
Shouldn't this be in a sunburst branch? I suspect this broke the
standard Plone skin
I found myself having the same need as Vincent so I looked a little bit
at z3c.form. The end result is very much a mixed blessing. As Vincent
discovered it is not very hard to get z3c.form 2.1 to manage a list of
items. In my example I have this interface which is repeated:
class
On 9/10/09 16:43 , Martin Aspeli wrote:
- z3c.form produces very awful HTML
Does that apply to the general case, or only to the case of nested
structures like this?
To the general case. There are lots of unneeded divs, weird things like
div class=errordiv class=errorerror message/div/div
it
requires writing CSS for two different markup patterns.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework
On 2009-8-20 06:54, Andreas Zeidler wrote:
On Aug 13, 2009, at 10:18 PM, Wichert Akkerman wrote:
On 2009-8-13 22:16, Alexander Limi wrote:
FWIW, Mozilla runs their entire project without a contributor agreement
— so we are already way ahead of what most large open source projects do
On 8/7/09 12:13 , Wichert Akkerman wrote:
I'm afraid I also don't buy the lookup mechanism mentioned in the PDF:
you are essentialy creating a persistent cache system, which means that
suddenly page views can trigger ZODB writes, which is very bad for high
performance sites. It also will miss
On 8/7/09 12:20 , Ralph Jacobs wrote:
Wichert Akkerman wrote:
On 8/7/09 12:13 , Wichert Akkerman wrote:
I'm afraid I also don't buy the lookup mechanism mentioned in the PDF:
you are essentialy creating a persistent cache system, which means that
suddenly page views can trigger ZODB writes
methods and b) this change transparently exposes all image where the
original code only hardcoded exposure of a field with the name 'iage'.
I don't quite see what the problem is with that code; can someone
explain that?
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things
On 7/30/09 2:00 AM, Martin Aspeli wrote:
2009/7/30 Erik Rosepsuc...@grinchcentral.com:
1) The current code base is located in the Collective. Since TinyMCE will
be
the default editor in Plone 4 should I move (copy) the code base to Plone
SVN?
-1. Why make it harder for people to contribute?
On 7/29/09 7:51 AM, Jon Stahl wrote:
On Tue, Jul 28, 2009 at 12:07 AM, Geir Bækholt · Jarnbaekh...@jarn.com wrote:
There is a step missing here: contributors must not only have signed the
agreement, they must explicitly allow that specific code to be donated to
the foundation. Signing the
On 7/29/09 8:09 AM, Martin Aspeli wrote:
Jon Stahl wrote:
On Tue, Jul 28, 2009 at 12:07 AM, Geir Bækholt ·
Jarnbaekh...@jarn.com wrote:
There is a step missing here: contributors must not only have signed
the
agreement, they must explicitly allow that specific code to be
donated to
the
On 7/27/09 10:52 PM, Geir Bækholt · Jarn wrote:
On 27. juli. 2009, at 22.12, Jon Stahl wrote:
Absolutely. Getting the code into the Foundation's long-term
conservancy is very much worth doing if it's not too terribly hard.
I've not been through the process before of moving Collective code to
On 7/27/09 4:56 PM, Rob Gietema wrote:
This shouldn't be an issue at all since 99.9% of the code is done by me,
just some small bugfixes by others who also have commit access to Plone
SVN and I'm sure won't mind.
That's not good enough: you need explicit approval.
Wichert.
On 7/27/09 1:38 PM, Rob Gietema wrote:
Hi,
I'm currently working on TinyMCE for Plone 4 and would like some
feedback on two issues:
1) The current code base is located in the Collective. Since TinyMCE
will be the default editor in Plone 4 should I move (copy) the code base
to Plone SVN?
-0
: SHA1
On May 26, 2009, at 10:21 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
The CMF eggs, even on trunk, still advertise compatibility with Zope
2.10. I believe we had agreed to target Zope 2.12 with trunk - please
correct me if that's wrong. If we do want Zope 2.12 I would like
in two weeks. If any changes are necessary we will make another
release candidate and repeat the process.
Regards,
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
.
Personally, I think it's a good idea, but in the past, we've had a lack
of commitment/follow-up with CSS/theme stuff, and a last-minute rush to
put in dozens of template and CSS changes which then cause breakage in
release candidates.
+1
Wichert.
--
Wichert Akkerman wich...@wiggy.net
promise to never break
stability in the 3.x, something I feel quite strongly about.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team
releases try very
hard to maintain compatibility, so this should not be problematic.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team
maintenance and not to
security support.
Just as important: we should communicate this policy clearly. I suggest
a post to plone-announce describing this policy and an easily findable
document on plone.org (preferably reachable in 2 or 3 clicks from the
frontpage).
Wichert.
--
Wichert Akkerman wich
: Nikolay Kim fafhr...@gmail.com
To: Wichert Akkerman wich...@wiggy.net
CC: check...@zope.org
Previously Nikolay Kim wrote:
Log message for revision 98920:
do not use z3c.autoinclude
Out of curiosity: why?
too slow. i create z3c.recipe.autoinclude instead of z3c.autoinclude
On 4/6/09 4:03 PM, Andreas Zeidler wrote:
On Apr 6, 2009, at 2:14 PM, Wichert Akkerman wrote:
This is possibly a valid concern for us as well. I wonder if there is
room for optimization here - our startup time is already quite slow.
have you informed/asked ethan about this?
I couldn't find
candidate and repeat the process.
Regards,
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team
On 4/2/09 9:42 AM, Vincent Fretin wrote:
Hi Wichert,
Can you release Products.CMFEditions 1.2? There is an i18n fix in it.
Can you port those changes to trunk first? I don't want to cut a release
until all fixes have been merged to trunk to prevent future regressions.
Wichert.
On 3/31/09 6:12 AM, Jon Stahl wrote:
Wichert Akkerman wrote:
I have tagged and uploaded Plone 3.3rc1. This is a first release
candidate, so please everyone: test the hell out of it!
If no critical bugs are found we will release this unmodified as 3.3
final in two weeks. If any changes
Previously robert rottermann wrote:
Wichert Akkerman schrieb:
I have tagged and uploaded Plone 3.3rc1. This is a first release
candidate, so please everyone: test the hell out of it!
hi there,
Is there a way to use buildout for this?
If you have a Plone 3.2 buildout just change
the process.
Regards,
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http
buildout.
http://plone.org/products/plone/releases/3.3, which seems the most
logical place, offers no clue.
That is simply because the installers have not yet been generated. I
expect Steve and Sidnie to finish them soon.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make
scheduling conflicts for future meetings. Then we can
reconcile that information and schedule a regular meeting.
Workdays do not work for me. Mornings in the weekend are probably best.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
are never doable for me. Saturday mornings (say 10h CET or so)
are probably best for me.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
I have tagged and uploaded Plone 3.3b1. This is a first beta release, so
please everyone: test the hell out of it!
Unless any unexpected problems surface I intend to make a release
candidate release in 3 weeks.
Regards,
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make
: Adapterise the Extensible Indexable Object Wrapper
Andreas Zeidler:
- PLIP 241: Clean up auto-sort: auto-order code
- PLIP 246: View for rendering events as an iCalendar file
Ethan Jucovy:
- PLIP 247: Automate ZCML Loading for Plone Plug-ins
Regards,
Wichert.
--
Wichert Akkerman wich...@wiggy.net
On 2/5/09 9:45 AM, Raphael Ritz wrote:
Andreas Zeidler wrote:
hi wichert,
On Feb 4, 2009, at 10:11 AM, Wichert Akkerman wrote:
The deadline for the PLIP review report was four days ago. From what I
can see not all reviews are in, and no report has been written yet.
Can I please get
.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo
).
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo
On 2/4/09 5:48 PM, Steve McMahon wrote:
Hi Wichert,
Does this give you what you need? If not, I'll be happy to add detail.
Please add some detail. In particular for rejected PLIPs it should state
why they were rejected and what the PLIP author has to do to get them
accepted in the next
On 1/31/09 2:18 PM, Tom Lazar wrote:
i've updated my local buildout and the the site works fine now, i do
get some 404 for the images in the timeline
(http://localhost:8080/newsite/history_compare_with_current.png) etc,
no showstopper, obviously, but if you can fix that still today i can
give
On 1/27/09 1:28 PM, Andreas Zeidler wrote:
On Jan 13, 2009, at 12:01 AM, Martin Aspeli wrote:
Martin Aspeli wrote:
Why on earth is Products.NuPlone not in the Plone 3.2 egg?
Is this in purpose or just a gross oversight?
Ok, I've released Products.NuPlone 1.0b3.
you got the release year
-minute review rush!
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http
]
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
to reflect that inline edit is disabled by
default, and can be enabled through the ZMI.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework
case recently where there were separate workflows for edit
and view permissions.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework
for PLIPs?
I was wondering the same thing. It very much looks like the framework
team selection process somehow always invented a new PLIP process behind
closed doors.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard
is added to the framework team.
Regards,
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
On 12/18/08 11:43 AM, Tom Lazar wrote:
and therefore should be reflected in the membership of the
group which makes decisions based on those factors.
i think that conclusion is the only part where we disagree. can we
agree at least on that? ;-)
Not without a way to guarantee that user
correctly that the group of people that selected the
framework team (which does not include those selected people itself) has
also gone one step further and defined a whole new process for how that
team will work?
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http
releases are still listed as
supported. Is there a reason that those aren't listed as unsupported
since there is a 3.1 that would supersede them?
Why bring this up on the framework team list? The framework team is not
a governing body.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED
On 12/10/08 5:24 PM, Calvin Hendryx-Parker wrote:
On Dec 10, 2008, at 11:22 AM, Wichert Akkerman wrote:
Previously Calvin Hendryx-Parker wrote:
I just noticed that on the PSC the Plone 2.5.5 release is listed as
not supported. I'd suggest that unless we have sent an email to the
announce
.
It's definitely too late for 3.3.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
for the documentation team to update/extend
other documentation.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team
Previously Israel Saeta Pérez wrote:
On Sat, Nov 15, 2008 at 5:08 PM, Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
I do agree that documentation should be part of PLIPs. One simple thing
would be to just have a free-text on the PLIP that identifies the
documentation
before the deadline, and the framework team will try to review PLIPs as
soon as they are submitted. PLIPs submitted after the deadline will have
to wait for 3.4.
Steve and Jon will be asked to manage the process and make sure everyone
is playing by the rules.
Wichert.
--
Wichert Akkerman [EMAIL
It would be nice if the team will have a balance between those
qualities.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing
/recept) and if the result
is a reject a rationale for the rejection. We can then post that list to
plone-announce so everyone sees what has been decided and why.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make
improves the currently situation quite a bit.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team
make sense.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org
Might I remind everyone that the review deadline is this Monday? Will
someone gather the results and report them?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
in the current object.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http
the default portlet renderer template
and replace it with a site action.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing
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
to take that role during their meeting this week.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team
.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo
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
is that you don't know this in advance
so the view should somehow provide this property sheet.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team
/ which works
perfectly for reading the list. And you can use your normal email client
to post to the list.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
For example, I think we are missing a trick currently with the way we
manage maintenance releases. We do a good job of setting deadlines and
not missing them by too much. What we don't do, is build any
Previously Martin Aspeli wrote:
[1] Perhaps the KSS vs. Bling debate of yore came close
dexterity vs devilstick could be the next one
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
several people.
The full PLIP can be found here:
http://plone.org/products/plone/roadmap/228
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Wichert Akkerman wrote:
I guess I'm the first one. I want to propose PLIP 228 for Plone 3.3.
Ok, second, Hanno got there first :)
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
for newly created sites to
disabled.
Please note that I do not propose to disable inline field validation in
edit screens: that is a very useful and desirable feature.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard
?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo
seems to fit with what you're doing at the
conference :)
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework
those at
the conference, providing immediate feedback to the PLIP authors.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team
ever written a PLIP during
a conference, which is perfectly understable: both of you are way too
busy preparing your talks, talking to people, organizing various and
socializing. That was true of previous conferences and will be true for
this one as well.
Wichert.
--
Wichert Akkerman [EMAIL
schedule one or more discussions
there to discuss these PLIPs, if possible with the PLIP authors present.
Wichert.
--
Wichert Akkerman[EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
may spwan a PLIP, or they may not.
There is no way to tell in advance.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing
| 6th | 12th
wiggy | |
raphael | |
danny | |
martijn | |
I won't be in DC.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
when planning the next release(s).
Wichert.
--
Wichert Akkerman[EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http
.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo
of the content in places like search
results. Perhaps something to consider for Plone 4 :)
Wichert.
--
Wichert Akkerman[EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
: it describes what the object is about. As such it does not
have business appearing in view templates, especially not in the way
it does now. That is a mistake Plone made long ago, and something we
should fix at some point.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make
(so content types, tools, etc).
Or when you want the quickinstaller to be aware of your package.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Thanks to all the hard work from the PLIP authors we have finished
merging all the PLIPs in the Plone 3.1 tree. A total of 16 PLIPs
have been merged:
#184: Include more/improved portlets (Jon Stahl)
#195: Support product dependencies (Wichert Akkerman)
#200: Kupu formlib widget (Martin
1 - 100 of 195 matches
Mail list logo
