At this time, the component reference is still raw, ugly HTML. It has to be, because it has in-place examples that require full HTML ... not the tiny slice that Forrest's xdoc format transforms into. Perhaps we'll need to create an extended xdoc for Tapestry with extra elements (to create iframes and load example HTML from them perhaps?). Sometimes I get ideas while I type ...
In addition, we could concievable convert the users guide and the future tutorial to use the book format supported by Forrest. It looks like their own take on DocBook ... but the important thing is figuring out how to get Forrest to generate single-page HTML, chunked HTML or PDF from the same source the way DocBook does.
No comments:
Post a Comment
Please note that this is not a support forum for Tapestry. Requests for help will be deleted. Please subscribe to the Tapestry user mailing list if you are in need of support, or contact me directly for professional (for pay) support.
Spammers: Don't bother. I delete your comments and it's a waste of time for both of us. 垃圾邮件发送者:不要打扰。我删除您的评论和它的时间对我们双方的浪费