tapestry-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colin Sampaleanu <colin...@exis.com>
Subject Re: organising pages
Date Thu, 09 Oct 2003 21:16:42 GMT
But unless I'm missing something, this doesn't help resolve the relative 
image link issue. If you are in your source, and previewing something, 
images will be at a different relative location than when running inside 

Bryan Lewis wrote:

>Sorry to come to the party so late, but I'm unclear on something here.
>Why is Option A so bad?   It's only for the deployment layout -- the structure of the
war file -- and that's not designed for human consumption anyway.  Your source tree can be
laid out any old way you please.  Your ant build file does the remapping, of course.
>Typical source tree:
>   \--intranet
>      +--common
>      +--conf
>      \--view
>         +--home   // each dir contains the html/page/java trilogy
>         +--tabbedmenu
>         \--and so on for every page
>      \--web        // with images, css, .application, static htmls
>Deployment image (war):
>+--index.html       // static html files in root
>   +--Home.html     // *.page and html templates
>   +--Home.page
>   +--TabbedMenu.html
>   +--TabbedMenu.jwc
>   +--classes
>   |  \--intranet
>   |     +--common
>   |     \--view
>   |        +--home
>   |        |  \--Home.class    // just the classes, ma'am
>   |        \--tabbedmenu
>   |           \--TabbedMenu.class
>   \--web.xml
>Now that's only my preference for a source tree.  My little development group has only
programmers, no designers, so we don't care about separating the content.  (I tried to imitate
the jakarta cvs tree, actually.)  But if we wanted to separate the html we could, merely by
modifying the buildfile.  The deployment image wouldn't change at all.
>Yes, I have seen some examples where people made their source layout similar to the deployment
layout, with directory names like META-INF and WEB-INF.  (You ever try typing those names
in a hurry?!?)  I hope that's not the norm.
>----- Original Message ----- 
>From: "Eric Everman" <everman@precedadesign.com>
>To: "Tapestry users" <tapestry-user@jakarta.apache.org>
>Sent: Thursday, October 09, 2003 11:36 AM
>Subject: Re: organising pages
>>Not So Fast!
>>This question actually gets at one of my hang-ups with Tapestry.  As I
>>see it, you have two options to organize a web site.
>>_Option A_
>>Place .html and .page files in the application root (or other specified
>>location).  No sub directories are allowed.
>>_Option B_
>>Place .html and .page files on the class path and list each page in the
>>.application file.
>>As I see it, neither of these options are optimal.  Option A results in
>>an entire application in one directory.  Option B results in an
>>inflexible application in which each page addition to the site requires
>>modifying the .application file, which requires a restart and is a bit
>>Eric Everman
>>On Thu, 2003-10-09 at 10:35, Mindaugas Genutis wrote:
>>>The correct reference is this:
>>><span jwcid="@PageLink" page="login">Login</span>
>>>><span jwcid="@PageLink" page="login/login.html">Login</span>
>>>>but the '/' doesn't get encoded and seems to confuse Tapestry's request 
>>>>processing. Please feel free to tell me to RTFM -- just point me to the 
>>>>right one :-)
>>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

View raw message