On Sunday, January 12, 2003, at 08:24 AM, Rickard Öberg wrote:
Hmmm, That thought has occurred to me more than once in the last few days. I am certainly not feeling much love for the direction xwork is headed in. I'd bow out and not care or be interested, unfortunately I can't do that as I have a lot invested in webwork, and would rather use something that is maintained and suchlike. So why not have the xwork crowd go ahead and xwork, and maybe others could work on webwork 1.4/2.0? xwork need not care about backward compatibility or have web as its main focus. Webwork would be considerate to existing users and still focus on the web (while not ruling out non-web clients).
So, given all of this, my resignation from XWork still holds. The requirements that have been voiced the last few days are not mine, and I don't think they're compatible with my goals, at least not without serious compromises that will only hurt the end result. The question then becomes: would it be useful to do *both* XWork and WebWork, but as separate projects with these different goals?
Hani
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
