Hi, Could a start on Cocoon IDE tools make use of dtd's or schema's for xmap and other Cocoon xml control docs? Involve a post schema validation infoset http://xml.apache.org/xerces2-j/samples-xni.html#PSVIConfiguration and assist learning xmap, xsp, etc.? Something that shows the constraints, possible attributes/children elements and possible values where applicable? Is there an open source active effort on custom, smart, xml editor|viewer|uml code that could be capitalized on or used as a starting point for a Cocoon specific tool?
I've toyed with xslt transforms of xmap to dynamic svg visuals to assist in learning...click and xpath to element etc. ... Anything about Lenya that could be used as a starting point? Are the schemas under .\cocoon-2.1\src\documentation\xdocs\drafts meant to be used? If so, are there uri's and local schemas that any well formed xmap or xsp could point to for tools to utilize them? --Roger ----- Original Message ----- From: "Rod Giffin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 15, 2003 10:37 AM Subject: Re: Cocoon activity > On Sat, 2003-11-15 at 00:43, Geoff Howard wrote: > > Rod Giffin wrote: > > > > >>the truth is that cocoon is not (beginners-dev)-friendly > > >>because many parameters (the pipeline-approach, missing IDE, less debug > > >>tools) > > >> > > >>after 2 years here and with cocoon in production from the first 2.0rc is > > >> still difficult for me to do something without to see an example. > > >> > > >>.. but i like cocoon and believe in cocoon power (thats the reason i'm > > >>here) > > > > > > > > > I'm also a beginner, after 1 year here. I agree, Cocoon is a complex > > > tool, with a very steep learning curve that has given me some difficulty, > > > partly because of having to build from source. > [SNIP] > > Now, out of curiosity since we have to live in the here and now for a > > bit, what did you find hard about building cocoon from source? > > Just to be clear, I did not have a *bad* experience with it, I just had > some extra things that I had to learn before I got Cocoon to work the > way I wanted... Things like, what blocks I want to include, and what > blocks I want to exclude. The net result of having to consider this is > that I understand Cocoon a little more than when I simply downloaded and > installed a binary. > > I think in fact that now that I feel more comfortable with the process > that I will probably continue to use the source release even when a > pre-compiled alternate is available again. > > Rod. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
