Hi, Just a small comment but I feel that a lot of the problem issues, and especially some of the complexity might be tied to where and how Cocoon sets the the interface between Java and XSLT. I have many examples in mind but in general I feel that more of the framework should be in xslt and that if every time you need to do something, you have to go back and forth between java and xslt, you will be duplicating data structures and adding overhead and logic issues, apart from tricky technological and mind frame switching issues.
Both Java and XSLT are important and they are complementary but this complementarity requires a design interface, not just an API (or a set of APIs). Still Cocoon is very interesting and a dynamic collaboration. Thank you, Regards, ac -----Message d'origine----- De : Argyn Kuketayev [mailto:[EMAIL PROTECTED]] Envoye : 27 juin, 2002 09:57 A : '[EMAIL PROTECTED]' Objet : RE: Giving up! Cocoon too big, slow and confusing > -----Original Message----- > From: Piroumian Konstantin [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 27, 2002 9:41 AM > To: '[EMAIL PROTECTED]' > Subject: RE: Giving up! Cocoon too big, slow and confusing > > > > From: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] > > > > Good post :) > > > > Wake up, guys! John raised a real issue. You can't simply say > > "Don't give > > up, be patient, read mailing-list, look into sources..." and > > so on. If you > > want this framework to catch the train, then there must be > > better support > > What do you mean by "better support"? Maybe I'm suffering from dislexia, but reading the docs in xml.apache.org/cocoon helped me only to understand the highest level concepts. There were lots of tiny little issues which are not covered anywhere in the documentation. "What's the best way to do this and this?". No answers anywhere but here, in the mailing list. Ok, I have a habit to look into sources when I've time, but sometimes there's no time. You came here and ask a question, hopefully soon you get an answer. Then comes another issue, then another and so on. Finally, you spend whole day on some stupid problem which could be resolved with good FAQ. I have to admit that things are improving with docs. FAQs are becoming real FAQs, not those short "read mailing list" as they were before. IBM's tutorials are a very positive step, I recommend them to everybody. They help a lot. Again, I'm not complaining I just want to say that there's an issue, and I'm glad that the situation with documentation is improving. I think that the biggest issue with Cocoon is its docs. > > > and better documentation. > > > > I'm not complaining, by the way. I'd love Cocoon become a mainstream > > framework. > > So, help us make it better. raising the issue is my help :) --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
