This is true, but I think you will find the same problem with any *framework* application (not sure I can think of any others right now); as opposed to stand-alone development environments; the secret is to compile/test often and do it in small incremental portions... we can learn a lot from agile methodologies.
FWIW, the CocoonWiki has a helpful section on using views: http://wiki.cocoondev.org/Wiki.jsp?page=DebuggingWithViews >>> [EMAIL PROTECTED] 2003/11/14 07:00:50 PM >>> <snip> My main concern with cocoon is the time it takes to debug anything.. The system is so complex (different files, different places the pipeline can fail, diferent protocols, generators, etc. ) that finding where the problem is takes too much time doing trial and error. Maybe a good IDE integration with debugging supported would be a "great leap forward" for the cocoon framework. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
