Thanks Eric. I'd not realized that the org.nuxeo.ecm.webapp sources was
just an example web interface rather than a module intended to be reused
through configuration -- I will experiment with various perturbations of
the webapp to see what I can change without breaking too much :)
I had imagined just changing CSS and some logo images, and changing the
"home page" to have application specific content hiding much of the
complexity of the full ecm, but with the demo domain/workspace/templates
view (i.e., /nuxeo/view_documents.faces) also available for 'advanced'
users. Given the modular nature of the rest of Nuxeo platform, I'd
thought I could do that by defining an additional module which
configures the webapp, but which leaves the core webapp undisturbed as a
"binary" module. However, it looks like I'll need to duplicate that
functionality instead (i.e. copy most of what's in the webapp into my
own webapp). Is that right?
Steve
On 4/4/2007 9:00 AM, Eric Barroca wrote:
...
> You can check nuxeo webapp about this. It's a complete demo of the
platform. :-)
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
