Re: WebObjects 5.4 is out.
Re: WebObjects 5.4 is out.
- Subject: Re: WebObjects 5.4 is out.
- From: Mike Schrag <email@hidden>
- Date: Sat, 27 Oct 2007 06:50:48 -0400
However, its treatment of Mike's "lazy tags" wasn't ideal from my
perspective.
WOLips in the 3.3.x builds makes this much better. In the 3.2.x
branch, I treated them all like a paragraph tag that you left off the
closing tag for. In 3.3.x it knows that some lazy tags really are
single tags that don't have closing tags and turns them properly into
<br/>. I would recommend going to Eclipse 3.3.1 with WOLips nightly,
especially since you are going to 5.4 -- The fixes I put in for 5.4
this weekend will only appear in nightly.
Does Component Editor offer this format in some option that I
haven't discovered?
Yes :) in 3.3.x.
This smells like a Component Editor bug, but what do I know?
I'll have to just try this one out ... This might be on purpose
actually. I seem to recall that I got burned with a <script .. />.
I believe Firefox (at least) does not consider that valid and will
skip over script tags with no explicit closing tags.
I seem to recall also that some browsers actually do not like the
<link> tag with a closing tag (even close-in-place with <link .. />
and ignore it), so just keep an eye out for that.
Also, the use of Java generics in the API declarations in the WO
5.4 frameworks may generate lots of warnings in your custom WO 5.3
code. I like to eliminate all warnings, but to do so, one must try
to understand Java generics. Be prepared to be flummoxed. To be
backward compatible with pre-generics Java, compromises in the
generics implementation had to be made. These compromises make
eliminating these compiler warnings by changing one's code
difficult in some cases. Java 1.5 has added the '@SuppressWarnings
("unchecked")' directive to tell the compiler to shut the &*^% up.
You should probably get familiar with the various @SuppressWarnings
directives if you want to eliminate compiler warnings when all else
fails.
Eclipse offers quick fixes for most of these -- Press cmd-1 over top
of a warning and it will offer suggestions on how to either fix or
suppress the corresponding warning. It's pretty useful. And I
definitely agree that some of the 1.5 generics warnings can be
terribly confusing. It takes time to get used to it. A lot of
warnings can be removed by converting your EOGenerator templates over
to use generics. Of course you can't even USE eogenerator in
5.4 ...... soooo... That doesn't help much :) I have have a word on
this one soon.
I hope to survive the Xcode -> Eclipse and WO 5.3 -> 5.4 migration
pain in one big lump rather than stringing it out over two
successive migrations. I think I see a light at the end of the
tunnnel, but maybe it's just a huge locomotive heading my way.
It really depends on what level of craziness you do in the
frameworks. Wonder had a good ole' time converting to 5.4 ... There
are quite a few of the less common API's that were modified that hit
Wonder. However, we also know the fixes for most of them as a
result, so if people run into specific API's and don't know what the
equivalent is, I can probably look it up in Wonder to see.
ms
_______________________________________________
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