Sorry, I don't really understand this. What "resources" are you
talking about? Can you elaborate with an example?
Like you mentioned above: flowscript or form definition refers to a
pipeline, quite implicitly, working by association. You mentioned this
in another thread. It can't be too difficult to scan a flowscript for
calls to 'sendPageAndWait', check sitemaps for the pipeline mentioned.
Ok. See my previous answer to Stavros about "snippet wizards". Is
this what you're talking about?
I'll quote you here to ensure we are talking 'bout the same thing:
"Yup. The problem I see coming with the semantic model that we'll have
to build is that many files in Cocoon depend on other files, but this
dependency isn't explicit. For example a subsitemap depends on its
parent sitemap but doesn't link to it. Same applies to a form
definition, template and binding which are all glued together by a
flowscript."
This is *exactly* why Cocoon is difficult to teach. Or indeed any web
technology. Implicit interdependencies. The really appealing aspects
of Cocoon require a larger context. Larger then folks that are "into
it" realize. If you could combine technologies in a scenario or
wizard, the power of Cocoon would be more visible and it would be
easier to use.