Thanks to Jerry and everyone else who replied and sent sample code!
Fortunately this is one of the few concepts I've encountered in WO
World which was actually familiar; I've used a very similar sort of
nested templating in the past.
I really appreciate all the help, though - this communi
Marinating it and letting it soak in a bit first makes it easier to
chew ;-)
On Jun 5, 2007, at 7:18 AM, Jerry W. Walker wrote:
The advice you've gotten is good advice but may be a bit hard to
chew on your first WO app.
___
Do not post admin requ
Hi, Janine,
The advice you've gotten is good advice but may be a bit hard to chew
on your first WO app.
To make it easier, I'm providing a sample textual schematic of a
simple WO application with:
* a page header
* a page footer
* a page wrapper (that invokes the header, the foote
Hello Janine;
now I want to make it look nice, and I'd like to do something a bit
more sophisticated and less inefficient than putting duplicate HTML
I've also got an interesting bent on the "page wrapper" idea which
you may like to read about to get some ideas...
http://homepage.m
Thanks, Kieran (and David)!
This is the first WO app I've built, so although I do have a lot to
learn, I also don't have too much to unlearn. Let's hope that's an
advantage here. ;)
janine
On Jun 4, 2007, at 8:50 PM, Kieran Kelleher wrote:
No copying and pasting is required! You just make
No copying and pasting is required! You just make reusable
components stateless with manual binding sync is better
http://homepage.mac.com/kelleherk/iblog/C1133025376/E1896801830/
index.html
If you want a component that wraps content, then just put a
WOComponentContent in the component
That's what I thought ;-)
You use a PageWrapper component that contains a WOComponentContent.
This will be a page-level component.
Then you make all your current "pages" partial pages wrapped in your
PageWrapper component. You can make reference to the CSS stylesheet
in the header section
Thanks, Kieran, that looks like a great book.
I need to be more specific, however; this is a very WO-centric
question. I want to be able to have a header and footer on each
page, include a CSS, and so forth. What's the best way to do that?
In past lives I've done this sort of thing with
On 4-Jun-07, at 10:59 PM, Janine Sisk wrote:
I've got my application working more or less the way I want it to;
now I want to make it look nice, and I'd like to do something a bit
more sophisticated and less inefficient than putting duplicate HTML
in all my components. But I can't find an
This is my favorite book on making it look pretty (you may need to
remove line-breaks from these long URLs):
Web-Standards-Solutions-Handbook
http://www.amazon.com/Web-Standards-Solutions-Handbook-Pioneering/dp/
1590593812/ref=pd_bbs_sr_1/002-4168457-0812804?
ie=UTF8&s=books&qid=1181012633&sr
I've got my application working more or less the way I want it to;
now I want to make it look nice, and I'd like to do something a bit
more sophisticated and less inefficient than putting duplicate HTML
in all my components. But I can't find any sort of documentation on
how this should be
11 matches
Mail list logo
