You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jim Menard <ji...@io.com> on 2003/12/07 15:10:06 UTC
Fragmented HTML
I'm working on my first Tapestry application. I love it.
One of the benefits of Tapestry is that the HTML pages are really that:
HTML. Theoretically, the designers can code and edit the HTML and see
what the pages look like because of the "dummy" HTML that sits inside
the tags with Tapestry jwcid attributes. However, I've started to
create lots of layers (nested components) in my pages. So how can a
designer ever see the whole page without running the application?
Every page I've created uses a page wrapper, which holds the header,
side bars, and footer. The header contains a search box. The side bars
contain login boxes, browse boxes, etc. The boxes contain forms.
Is my approach too fragmented? It doesn't seem so, but it does make it
impossible for a designer to see an entire page as HTML.
Jim
--
Jim Menard, jimm@io.com, http://www.io.com/~jimm/
"All those who believe in psychokinesis raise my hand." -- Anon.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Fragmented HTML
Posted by Harish Krishnaswamy <hk...@comcast.net>.
There's an idea, although I have not written any ant tasks ever.
-Harish
Bill Lear wrote:
> On Sunday, December 7, 2003 at 10:25:29 (-0500) Harish Krishnaswamy writes:
>
>>Your approach is correct. The only way you can preview the entire page is to replicate the page
>>wrapper in all the pages and exclude the static wrapper in the actual rendering via the $content$
>>and $remove$ special components. The downside here is, whenever the wrapper changes you have to
>>change all the pages to change it so you can preview it properly. The only other thing I can think
>>of to do this is to create a small script in perl or something to merge the html before previewing.
>
>
> Let's write an Ant script to do this!
>
>
> Bill
>
> ---------------------------------------------------------------------
> 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
Mofidying the Workbench Example
Posted by ford prefect <fo...@yahoo.de>.
I want to add my own component to the tapestry work
bench example, just a simple table with a black border
around the chart graphic on the chart tab.
1. So if I call this border component MyBorder, do I
need to insert the following into the
workbench.application:
<component id="border" type="MyBorder"/> or
<component id="MyBorder" type="Border"/> ?
2. is the following within MyBorder.jwc sufficient?
<component-specification
class="org.apache.tapestry.workbench.components.Border"
allow-informal-parameters="no"/> ?
3. what do i need for the MyBorder.html? a @RenderBody
and a @Body and a @Shell or what is the minimum?
4. an finally the modified Chart.html:
<span jwcid="@MyBorder">
<img jwcid="@Image" image="ognl:chartImageAsset"/>
</span>
is that ok?
I am really struggeling with understanding how it all
fits together.
Thanks!
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Fragmented HTML
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Sunday, December 7, 2003, at 11:22 AM, Bill Lear wrote:
> On Sunday, December 7, 2003 at 10:25:29 (-0500) Harish Krishnaswamy
> writes:
>> Your approach is correct. The only way you can preview the entire
>> page is to replicate the page
>> wrapper in all the pages and exclude the static wrapper in the actual
>> rendering via the $content$
>> and $remove$ special components. The downside here is, whenever the
>> wrapper changes you have to
>> change all the pages to change it so you can preview it properly. The
>> only other thing I can think
>> of to do this is to create a small script in perl or something to
>> merge the html before previewing.
>
> Let's write an Ant script to do this!
You could accomplish it with some clever use of filtered <copy> using
filtersets. Or using <replaceregex> or with something I've gotten fond
of, VPP <vpp.sourceforge.net> (although I think $content$ stuff would
cause Velocity to choke).
We don't have any (real) designers on our current project, so we leave
things in pieces and just suffice that way. Good designers should be
familiar with web development and dealing with sites chopped up into
pieces... so I personally wouldn't worry about pages not looking
exactly like the site when edited directly, but rather make them look
decent enough. For example, for components, don't worry about any of
the border/header/footer stuff, just make enough HTML page that it'll
render the component itself decently. At some point it becomes more of
a hassle than it's worth to keep previewability working nicely for
every page, just make it (barely) good enough.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Fragmented HTML
Posted by Bill Lear <ra...@zopyra.com>.
On Sunday, December 7, 2003 at 10:25:29 (-0500) Harish Krishnaswamy writes:
>Your approach is correct. The only way you can preview the entire page is to replicate the page
>wrapper in all the pages and exclude the static wrapper in the actual rendering via the $content$
>and $remove$ special components. The downside here is, whenever the wrapper changes you have to
>change all the pages to change it so you can preview it properly. The only other thing I can think
>of to do this is to create a small script in perl or something to merge the html before previewing.
Let's write an Ant script to do this!
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Fragmented HTML
Posted by Harish Krishnaswamy <hk...@comcast.net>.
Your approach is correct. The only way you can preview the entire page is to replicate the page
wrapper in all the pages and exclude the static wrapper in the actual rendering via the $content$
and $remove$ special components. The downside here is, whenever the wrapper changes you have to
change all the pages to change it so you can preview it properly. The only other thing I can think
of to do this is to create a small script in perl or something to merge the html before previewing.
-Harish
Jim Menard wrote:
> I'm working on my first Tapestry application. I love it.
>
> One of the benefits of Tapestry is that the HTML pages are really that:
> HTML. Theoretically, the designers can code and edit the HTML and see
> what the pages look like because of the "dummy" HTML that sits inside
> the tags with Tapestry jwcid attributes. However, I've started to create
> lots of layers (nested components) in my pages. So how can a designer
> ever see the whole page without running the application?
>
> Every page I've created uses a page wrapper, which holds the header,
> side bars, and footer. The header contains a search box. The side bars
> contain login boxes, browse boxes, etc. The boxes contain forms.
>
> Is my approach too fragmented? It doesn't seem so, but it does make it
> impossible for a designer to see an entire page as HTML.
>
> Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Fragmented HTML
Posted by ford prefect <fo...@yahoo.de>.
Why would you want to view the templates in an editor
if you only work with components? Once I manage
working with tapestry I will only look at small
components and when they are fine the whole layout
will be correct without any missing tags. As all the
layout will be dynamic I would also not want to have a
"whole" page within a single file and edit it within
and editor. In think you only need to know what you
want it to look like and in the end it will turn out
to look that way.
Working with tapestry will be different/more
structured than working with scripting languages where
you modify the script, reload the browser, look at it,
modify it again and change it until it fits. You need
to have the concept before, and plan more in advance.
If you want to change something it will probably only
be the components the page consists of (e.g. different
colour, shape) or the overall layout which could also
be a component....
--- Jim Menard <ji...@io.com> schrieb: > I'm working
on my first Tapestry application. I love
> it.
>
> One of the benefits of Tapestry is that the HTML
> pages are really that:
> HTML. Theoretically, the designers can code and edit
> the HTML and see
> what the pages look like because of the "dummy" HTML
> that sits inside
> the tags with Tapestry jwcid attributes. However,
> I've started to
> create lots of layers (nested components) in my
> pages. So how can a
> designer ever see the whole page without running the
> application?
>
> Every page I've created uses a page wrapper, which
> holds the header,
> side bars, and footer. The header contains a search
> box. The side bars
> contain login boxes, browse boxes, etc. The boxes
> contain forms.
>
> Is my approach too fragmented? It doesn't seem so,
> but it does make it
> impossible for a designer to see an entire page as
> HTML.
>
> Jim
> --
> Jim Menard, jimm@io.com, http://www.io.com/~jimm/
> "All those who believe in psychokinesis raise my
> hand." -- Anon.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
__________________________________________________________________
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org