Next piece I'm working on is modifying a basic Border component to provide only the shell and specific stylesheets. According to the Shell component you can provide many stylesheets to be applied by assigning an array or collection of IAsset. At this point I'm not sure where I should do that. Should it be in the engine that I define my list? I've got the entries as context-assets, can I just provide that as the expression? Gotta figure it out and record it.
Tuesday, September 21, 2004
Tapestry
Okay, so the Home service with Tapestry is HARD-CODED to resolve a blank URL to a Home.page. Well, the beauty of open-source is that you can modify that to your heart's content. I tried that, spent a couple hours on getting it to work and ended up just overriding the service with a local one (extends org.apache.tapestry.engine.HomeService & )
Next piece I'm working on is modifying a basic Border component to provide only the shell and specific stylesheets. According to the Shell component you can provide many stylesheets to be applied by assigning an array or collection of IAsset. At this point I'm not sure where I should do that. Should it be in the engine that I define my list? I've got the entries as context-assets, can I just provide that as the expression? Gotta figure it out and record it.
Next piece I'm working on is modifying a basic Border component to provide only the shell and specific stylesheets. According to the Shell component you can provide many stylesheets to be applied by assigning an array or collection of IAsset. At this point I'm not sure where I should do that. Should it be in the engine that I define my list? I've got the entries as context-assets, can I just provide that as the expression? Gotta figure it out and record it.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment