You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eric Everman <ev...@precedadesign.com> on 2003/05/05 23:23:03 UTC
Images during development
The *easy* way to use place non-dynamic images in html pages is to simply
use straight html <img> tags. This allows (most) pages to be created w/o
.page files and doesn't require 'double specifying' the image (once as an
asset and again with an explicit path for WYSIWYG editing).
If I place my pages under WEB-INF or under the classpath, its impossible to
take work the *easy way*, because the access paths to the images are
necessarily different during WYSIWYG editing and runtime. A solution is to
place pages (and components) under the context, when the development vs
runtime paths are the same. However, as best I can tell it looks like
pages placed under the context directory cannot be in sub-directories.
Is there a way combine easy WYSIWYG editing with a structured application
(ie separate directories for different areas of the site)?
Thanks,
Eric Everman
Preceda Design LLC
www.precedadesign.com