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: David BON <email@hidden>
- Date: Mon, 6 Aug 2007 02:42:41 +0000
Thanks a lot,
Comments in the text.
David.
Le 6 août 07 à 02:11, Guido Neitzer a écrit :
On 05.08.2007, at 19:48, David BON wrote:
I have already solved this problem by designing my own Frenchy
buttons. I was just wondering why that happens (I've seen that in
the context when I use the WOImageButton, the Form was filled with
the correct data but not in the case where I use the WOHyperlink
where it was void).
That is just because a hyperlink does not submit a form.
I'm already found good advices on WONDER but as I begin with WO, I
preferred until now using the tools already packaged by Apple
(more "ready to use"). It seems that I have to install ECLIPS /
WOLIPS and WOPROJECT to be able to setup WONDER (or at least to
find an install doc I can use). I am currently trying to install
all that and learn these new tools. I'm also still searching more
docs on WONDER to see what's in it, how to install it, how to use
it, what limitations could be...
One really good advice:
Start with Eclipse / WOLips from the beginning. Use the tutorials
here:
http://wiki.objectstyle.org/confluence/display/WOL/Home
I've just finished to install all that stuffs. Let's play with them
now to discover that.
If you don't want to reinvent the wheel all over the place, use
Wonder. It'll save you some serious headache.
That's exactly what I don't want to do: reinvent squared wheel when
there's so many goods thing available.
I don't know if I will keep using D2W for the real application as
it seems to me a bit long to build the different views (I've got
lots of broken pipe today in the Run Log)...
Then somethings wrong with your environment. I did D2W the whole
day and had no problems at all. It really depends on what you're
doing. E.g. if you use list pages and you have a lot of objects in
the database, it takes them long to load --> use Wonder and the
ERXBatchingDisplayGroup.
In fact, I have a lot of tables with many relationships but (today)
very few data (just enough to test).
The templates are normally only slow when they are loaded the first
time - as is the rule system. My D2W application is not slower
than any other WO application I wrote so far.
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...
But, and that is what I strongly believe: DirectToWeb is NOT for
beginners. You have to have some experience with WebObjects to
really use it. Or you need someone helping you all the time for a
couple of days. Don't get me wrong, I think that D2W is one of the
greatest web technologies and ideas around and I love to use it. In
fact, I wouldn't be able to do a lot of my work without it as I
just wouldn't have enough time to build all those stupid pages.
But, it is a complicated, not easy to understand technology. You
must be "fluid" in WebObjects, understand most of the concepts of
it, understand a lot of other stuff AND like the way rule base
development works to actually handle it.
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.
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