On Monday, Nov 11, 2002, at 11:29 Europe/London, Joseph Ottinger wrote:
It's okay. Actually, you guys were right: why should we bother writing ourYes, but it would be fantastic to have a real world app that uses Open Symphony components in the way that their creators intended them to be used. That way, it's possible for newbies to get started a _lot_ faster, which helps the mindshare of the project as a whole. The Roller project is a good example of a project that introduces a newbie to various tools, and how they fit together.
own? Snipsnap is getting data and not underperforming, IMHO; all it needs
is a port away from Jetty and you'd be off and running, with very little
work involved. Writing a wiki for opensymphony would involve reinventing
wheels, and time that nobody really wants to spend... and it'd need some
maturing. Development time costs money and mindshare best spent elsewhere.
Webwork's great, and I'm sure that OSWorkFlow is also the bee's knees. OSUser and OSAccess can probably solve a heap of problems (some of the perennial "how do I secure my WW app?" questions, perhaps) The missing piece of the puzzle is a show case app which demonstrates how it all fits together.
Regards,
Simon
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
