Comments are not handled in the same way as other xml nodes.
better would be to use another xml namespace, e.g. "tap" to combine the two
types in a single document.
|---------+---------------------------->
| | Ron Piterman |
| | <[EMAIL PROTECTED]|
| | de> |
| | Sent by: news |
| | <[EMAIL PROTECTED]|
| | rg> |
| | |
| | |
| | 13/05/2005 13:18 |
| | Please respond to|
| | "Tapestry |
| | development" |
| | |
|---------+---------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: merging html and jwc/page files
|
>-------------------------------------------------------------------------------------------------------------------------------|
hi,
Whereas in the users list there apears a thread on simplicity,
complaining about doing the same thing in 3 different way, I had an
Idee, beacuase of the annoying thing haviong 3 files for each component...
As *my* practice shows, putting the component definitions in the
.jwc/.page is less compfortable than just putting them in the html.
I still however have to define properties, parameters, assets beans aso
in the jwc/page.
So I thought if there could be a way to put them also in the html, and
making tapestry optionally use *two* files: the html and the class.
Since Wysiwig or whatever editability of the html files is an important
issue, I thoght of doing that using comments...
first thought was, putting a comment on the top of the html.
This would not work if one uses an xhtml format (which I am not sure is
supported by tapestry...) - any way, xml definition leaves an optional
"<?xml" definition at the very start.
Then I thought - one could use a special comment: <!--!tapestry!
...
!>
Now I think -
why not embed an xml processing instruction in the html as
tapestry
page/component definition?
something like :
<?tapestry
<!DOCTYPE
page-specification PUBLIC
"-//Apache Software Foundation//Tapestry
Specification 3.0//EN"
"
http://jakarta.apache.org/tapestry/dtd/Tapestry_3_0.dtd";>
<page-specification
...
</page-specification>
?>
So if the
page/component-specification points to a jwc/page, it will be
parsed as
usual.
If it points to an html, the processing instruction will be parsed,
also
as usual...
I think reducing tapestry files in a third will make *me*
very happy in
navigating through my project...
Cheers,
Ron
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
For
additional commands, e-mail: [EMAIL PROTECTED]
***************************************************************************
The information in this e-mail is confidential and for use by the addressee(s)
only. If you are not the intended recipient (or responsible for delivery of the
message to the intended recipient) please notify us immediately on 0141 306
2050 and delete the message from your computer. You may not copy or forward it
or use or disclose its contents to any other person. As Internet communications
are capable of data corruption Student Loans Company Limited does not accept
any responsibility for changes made to this message after it was sent. For
this reason it may be inappropriate to rely on advice or opinions contained in
an e-mail without obtaining written confirmation of it. Neither Student Loans
Company Limited or the sender accepts any liability or responsibility for
viruses as it is your responsibility to scan attachments (if any). Opinions and
views expressed in this e-mail are those of the sender and may not reflect the
opinions and views of The Student Loans Company Limited.
This footnote also confirms that this email message has been swept for the
presence of computer viruses.
**************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
