Torsten Curdt wrote:
> Probably best to move it back to scratchpad. I have some time offI saw that you have done so with precept, and at first it seemed ok, but there is a problem with it.
and I
> could look into the servlet, but the code in the PHP servlet
itself might
> be more work than I'm willing to put into it... perhaps we could
just
> file
> a bug against the PHP servlet :)
Ok, if nobody comes up in the next days, I'll move it away into
scratchpad.
...what about marking the block "unstable"? so nobody needs to move things around...
On Avalon we did it with Excalibur, and it was a real mess, because developers and users were not really aware of what was unstable and what not.
Now we have a sandbox module, to make it clearer than ever where the unstable code is.
So I'm quite strongly in favor of moving unstable stuff to scratchpad.
By moving them to blocks we found dead code. Now I don't want to see dead code in blocks too...
BTW, what about "precept"? Is it really still scratchpad? Is there a possibility of merging it to a unified form handling system, or I'm way off target?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
