I use Dreamweaver. Here's what we do.
We get an html file that will be a template from a designer.
i.e.
<html>
<head>
<!-- stylesheet stuff -->
</head>
<body>
<table>
<tr>
<td>Hello!<td>
</tr>
</table>
</body>
</html>
First thing is to isolate the head stuff using jwcid="$content$" - tapestry
ignores anything outside this
<html>
<head>
<!-- stylesheet stuff -->
</head>
<span jwcid="$content$">
<body>
<table>
<tr>
<td>Hello!<td>
</tr>
</table>
</body>
</span><!-- end of jwcid="$content$" -->
</html>
So the hardcoded stylesheet stuff is ignored by Tapestry but is still there
if one
views the template in Dreamweaver.
But we'll still need Tapestry to use style sheets: use a Shell component
<html>
<head>
<!-- stylesheet stuff -->
</head>
<span jwcid="$content$">
<span jwcid="shell">
<body>
<table>
<tr>
<td>Hello!<td>
</tr>
</table>
</body>
</span><!-- end of jwcid="shell" -->
</span><!-- end of jwcid="$content$" -->
</html>
The Shell will handle stylesheets (Head tag oriented stuff)
If we are using Tapestry generated javascript, we need a Body component
<html>
<head>
<!-- stylesheet stuff -->
</head>
<span jwcid="$content$">
<span jwcid="shell">
<body jwcid="Body">
<table>
<tr>
<td>Hello!<td>
</tr>
</table>
</body>
</span><!-- end of jwcid="shell" -->
</span><!-- end of jwcid="$content$" -->
</html>
Follows is the same template but I''m replacing the table with
dynamic stuff using the Cool component
<html>
<head>
<!-- stylesheet stuff -->
</head>
<span jwcid="$content$">
<span jwcid="shell">
<body jwcid="body">
<table jwcid="Cool">
<tr>
<td>Hello!<td>
</tr>
</table>
</body>
</span><!-- end of jwcid="shell" -->
</span><!-- end of jwcid="$content$" -->
</html>
The template is still completely viewable in Dreamweaver
Now about the MegaComponent thing. Going the other way (Developer to
Designer)is tougher.
You could grab some HTML source generated by the MegaComponent and paste it
in
(either with a jwcid="MyMegaComponent", or by wrapping the static source
with <span jwcid="$remove$">)
But that's a pain as you have to staticly resolve all the images and links
in the static version of the MegaComponent
to make it look good in Dreamweaver.
We usually give up on having the templates completely viewable in
Dreamweaver once we use MegaComponents.
Its easier to have the designer put in a placeholder of an appropriate size.
That works for us.
Geoff
----- Original Message -----
From: "Jonathan Carlson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 13, 2002 11:07 AM
Subject: [Tapestry-developer] Tapestry with Dreamweaver
One of the selling points for Tapestry is the superior integration with HTML
layout tools so Java developers can leave most of the layout concerns to
others.
Here's my question:
If a page makes extensive use of embedded and mega components, then would a
design person using Dreamweaver (or please suggest a better tool if you know
of one) still be able to see what the whole page will look like before there
is a complete server running? (Assuming they have access to the component
templates).
In other words, can Dreamweaver be set up to include the mega-component
templates in the right place? Or are most Tapestry apps not yet using
mega-components much so this hasn't really been an issue?
Thanks in advance for your perspective.
Jonathan Carlson
Minneapolis, Minnesota
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about
your web server security? Click here for a FREE Thawte
Apache SSL Guide and answer your Apache SSL security
needs: http://www.gothawte.com/rd523.html
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about
your web server security? Click here for a FREE Thawte
Apache SSL Guide and answer your Apache SSL security
needs: http://www.gothawte.com/rd523.html
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
