whit wrote:
hey, if the werewolf wants to be on the framework team I say more the
merrier ;)
+1 for having Martijn Faassen in the framework team.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
Hi Hanno!
hannosch wrote:
Added: plone.transforms/trunk/plone/transforms/interfaces/transform.py
==
--- (empty file)
+++ plone.transforms/trunk/plone/transforms/interfaces/transform.py Wed Jun
20 21:18:48 2007
@@
Alexander Limi wrote:
On Fri, 23 Mar 2007 05:00:45 -0700, Daniel Nouri wrote:
Do you want to tell (core) add-on developers to not make use of the
niceties
of plone.app.controlpanel because their thing is too complex?
Uhm, if people can't use zope.formlib anywhere else than
Hi!
Alexander Limi wrote:
- Archetypes
- After we removed JS from checkboxes, they no longer stick
(really!). Might have to put that back, even though it sucks
- There's something strange going on with enabling comments, it
only works on the initial
Hanno Schlichting wrote:
Nope. Windows support for zopectl is a lot harder then just some path
fiddling. But the real issue with it is not really something that is an
argument for ploneout, I just took the time to implement it in it, it
could be a separate package as well. The basic problem
Hanno Schlichting wrote:
Daniel Nouri wrote:
Hanno Schlichting wrote:
Nope. Windows support for zopectl is a lot harder then just some path
fiddling. But the real issue with it is not really something that is an
argument for ploneout, I just took the time to implement it in it, it
could
ploneenv is a one module Python script that builds heavily on workingenv and
setuptools. What it does:
- It creates a Zope instance for you. You always provide the
``mkzopeinstance.py`` script that you want to use as an argument.
E.g.::
ploneenv ~/myzopeinstance \
I'm obviously for ploneenv/workingenv. I wouldn't have developed ploneenv
otherwise. So here is my pro-ploneenv reactions.
Martin Aspeli wrote:
First of all, I think this is great. :) The important thing here is that
people can use what they feel comfortable with - at the end of the day,
all
Hello there!
I created a script install-plone.py that should help at least get an
idea of how the deployment of Plone 3.0 should look like.
Note that this is work in progress. I hope that people will help me
with figuring out the problems with this, and help me improve it.
You can download it
I forgot another obvious problem:
- Should not depend on the user to have workingenv.py installed. The
script should download it if it's not there.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
Martin Aspeli wrote:
whit wrote:
my opinion is a little elbow grease to get this worked out now rather
than later would go a long way. eggs are bit of pain, but we don't
need to wait for any zope gods to descend from on high to make things
better.
I agree in principle, I just can't bring
whit wrote:
You could call it temporary in that Zope will hopefully get better at
development eggs and therefore render a weaved-together bundle like this
obsolete (instead, you'd have a bundle with eggs and then you'd
easy_install each one). To be honest, I find the bundle fairly
Hi!
Martin Aspeli wrote:
Hi Daniel
From Saturday to Tuesday, I attended 4 days of presentation, discussion
and hands-on experience with KSS. First of all, thanks to Godefroid for
hosting a very nice sprint and to the whole team for the good time I had!
I want to share some experiences
Martin Aspeli wrote:
Daniel Nouri wrote:
whit wrote:
Martin Aspeli wrote:
Hi Hanno,
I'm happy to write the plone / plone.app announcement, and I can
write the bit about guidelines for when to use them. However, I'm
not too sure how we do the svn organisation.
- are we recommending
14 matches
Mail list logo
