Re: Newbie - WOHyperlink vs WOImageButton in D2W MenuHeader.wo template
Re: Newbie - WOHyperlink vs WOImageButton in D2W MenuHeader.wo template
- Subject: Re: Newbie - WOHyperlink vs WOImageButton in D2W MenuHeader.wo template
- From: Guido Neitzer <email@hidden>
- Date: Mon, 6 Aug 2007 14:16:42 -0600
On 05.08.2007, at 20:42, David BON wrote:
I've just finished to install all that stuffs. Let's play with them
now to discover that.
Cool. It pays of on the long run, as Eclipse helps you much more with
Java development than Xcode does. Also, you might miss something like
the WebObjects Builder for a short time, but you'll see, that it is
of limited help once you create a more complicated component model,
where a lot of the stuff is dependent on runtime information.
That's exactly what I don't want to do: reinvent squared wheel when
there's so many goods thing available.
Definitely take a look at Wonder. I can give you (and other starters
with Wonder) the tip, that just reading the class names and fly over
the descriptions of these classes here:
http://webobjects.mdimension.com/wonder/api/
helps to avoid writing duplicate (and mostly inferior) code. You can
limit the package you go through to ERExtensions and the
Ajax.framework. That should be a good start. If you use D2W,
definitely check out the tons of useful components in ERDirectToWeb.
As I'm currently always testing new functionnality of new features
(new to me of course), I'm very often in the case of a first
loading, that explain my frustration... I will wait for a first
stable releaseof of my application to really woring about
performance. And I still have to study all about deployement,
optimization, etc...
As I said: D2W is not really slower than normal WO applications. The
rule system and the templates take a bite from the performance, but
as all this is cached in deployment, it is absolutely no issue for us
here.
That's sure that the lack of a good knowledge of the whole
framework is real bottle neck to work with D2W as everything is
done "under the cover", using indirections like the rules, etc..
But up to now, I achieve to go on, by debugging, logging, searching
the net for similar problem, finding indications on methods I don't
know and studying them through reference documents. I'm sure that
if the mailing list is always so reactive I'll touch the target
rather sooner than later. I have already worked with some other
frameworks so I know pretty well the difficulty to enter in one of
it, get the whole view and "philosophy" of its concept before
starting to be efficient with it.
Okay, so some hints here:
1. Use Wonder with D2W! Your application WILL lockup under load with
editing context locks if you don't do that. Even if you use just a
couple of D2W pages inside your app. It is not a question WHETHER it
will lock up, only WHEN.
2. Add this to your PageWrapper.html / PageWrapper.wod:
html:
<webobject name="DebugFlags"></webobject>
wod:
DebugFlags : ERD2WDebugFlags {}
This is an incredible help! I use mostly the "D2W" and the "log4j"
entry there.
3. Don't use the D2W assistant. It creates total crap in your rule
files. Write your rules by hand, it's not really hard. Look into the
Wonder rule files to find examples, read the html / wod files of
components you want to use for "d2wContext.SOME_KEY" to find keys
like SOME_KEY you can use in your rules.
4. Enable rule tracing (this is for the use with Wonder):
er.directtoweb.rules.ERD2WTraceRuleFiringEnabled = Debug
And set the right-hand side logging e.g. for "componentName" or
whatever you want to trace on the "log4j" page accessible through the
DebugFlags.
5. Take a look at ERXNavigation. I really like it!
6. Create at least your own PageWrapper and MenuHeader components (or
change the existing crap to something useful) to get a better look &
feel.
7. Use the ERDirectToWeb framework to get some CSS capability into
your application. It is not really necessary to create your own look
framework, but for later, I'll encourage you to do so. You'll get
much more satisfaction from your own application if it doesn't look
like every other D2W app.
Okay, that's it so far - I go back to work on my stuff ... ;-)
cug
_______________________________________________
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