Re: Making a WO app look pretty
Re: Making a WO app look pretty
- Subject: Re: Making a WO app look pretty
- From: Janine Sisk <email@hidden>
- Date: Mon, 4 Jun 2007 21:20:29 -0700
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 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 which acts like a content
placeholder for parent content.
For example you may have a reusable component for your header, one
for the footer, and perhaps a page wrapper that has html HEAD
stuff, the page header, WOComponentContent, and page footer. Then
for new pages, you just drop in the wrapper.
Navigation menu, if it never changes may also be in the PageWrapper
or have a number of reusable Nav menus that are dropped into
appropriate pages.
If you have not been using reusable components and CSS, you have a
bit of a learning curve, but don't give up. When you have mastered
reusable components, you will find yourself creating reusable page
building blocks all the time and building apps becomes easier and
easier and More Fun (TM).... and the CSS, well this brings a whole
new meaning to reusability and flexibility.
Ideally HTML has semantic meaning and all styling should be done
via CSS. The Dan Cederholm book is easy to digest and will help you
get the sense of it really quickly ....
Regards, Kieran
On Jun 4, 2007, at 11:20 PM, Janine Sisk wrote:
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 server side
includes and with a very fancy templating system, neither of which
are available here. I haven't been able to find anything in the
WO docs that talks about this sort of thing - surely the answer
isn't to paste the HTML into every page-level component! :)
thanks,
janine
On Jun 4, 2007, at 8:11 PM, Kieran Kelleher wrote:
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=8-1
I also recommend having YUI reset-fonts-grids as a base
foundation to your CSS ....... it makes it easier to have cross-
browser/cross-platform CSS consistency.
http://developer.yahoo.com/yui/
HTH, Kieran
On Jun 4, 2007, 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
any sort of documentation on how this should be done. I'm still
searching, but thought I would also ask for pointers here.
What's the "best practice" for a simple app?
thanks,
janine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden