You actually don't have to change layout of framework's D2W pages.
I usually start a project by subclassing all the D2W-pages
(InpsectPage extends ERD2WInspectPage, ListPage extends
ERD2WListPage, MessagePage extends ERD2WMessagePage, etc) and use
project-specific html markup. Java files for these pages most often
have no logic at all.
There is a script for creating a "look framework" which basically
does what you're saying. I have a project independent look framework
which subclasses a lot of the ERD* classes and only implements its
own HTML.
So, all our projects have both admin and front-end driven by D2W. I
also agree with Anjo saying that having session is not a problem
since it's just memory and thinking about saving memory on the
early stages of project sounds like a premature optimization to me.
You normally get much more in return.
That doesn't work for me, as I need URLs that can be bookmarked,
crawled by search engines, send via E-Mail and so on. So basically
all my Admin apps are DirectToWeb to a certain degree and nearly all
my "frontend" applications are DirectAction based.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/email@hidden
