[Zope3-dev] Re: Zope 3 Newsletter: Issue 10

[Chris Withers]

Jim Fulton wrote:

> On IRC mainly.  Given how controversal this is, and was bound to be,
> we really should have done a proposal.  I suppose it's not to late
> to do so.

Does that mean it gets backed out until the proposal is agreed by everyone?
<0.7 wink>

>> What's the rational.
> 
> See my note on "Scripters vs developers". Scripters want quick and
> dirthy solutions.

As someone who supports systems I don't.
Do we HAVE to give peopel more guns pointed at their toes...
Most people only have 10 toes and some thign in Zope 2 have taken care of a good 
fiew of those ;-)

> Speed is important. Disciplione is not important.

Sorry, but you can't start off with that as a premise and, at ANY level, expect 
to not end up with an unmaintainable mess at some point.

> a lot of sense.  If I have a one-off page and some code
> that's needed only for that page, the quickest easiest thing I can do
> is to include that code in the template. 

Indeed, and I'd love this, but I am prepared to sacrifice it for not having to 
unpick the twisty turds I'm sure some developers will create out of this...

> Alternatively, I have to stick
> some other Python thing in the folder with the template and manage that
> Python thing as well. This extra Python thing now clutters up my content.

Yes, but it's seperate, and at least there's the hope of code re-use. Although 
the coporphiliacs mentioned above would probably avoid this at all costs and 
just write lots of little similar-but-slightly-different python scripts...

> This would be OK if it was going to be shared among multiple pages,
> but if it's only going to be used for a single page, it might even
> be cleaner to embed it in the page.

Again, I agree with this, but the risk is too great...

> This choice only makes sense for
> active content, where we are actually doing things in content space.

Hmmm, 'active content'? I know it's not cold in here so I must be shivering for 
another reason ;-)

> BTW, I think that a more common use of script tags will be to actually
> embed moduleish things:
> 
>   <script>
>      <!--
> 
>     from foo,bar import baz
> 
>         def something():
>            ...
> 
>         def somethingelse(x, y):
>            ...
> 
>      -->
>   </script>

Damn, these are tempting, but they still feel more like heroin to me :-(

Chris