Re: Bringing back the dev tools
Re: Bringing back the dev tools
- Subject: Re: Bringing back the dev tools
- From: David Elliott <email@hidden>
- Date: Sat, 23 Feb 2008 17:55:06 -0500
Hi Thomas,
On Feb 23, 2008, at 3:47 AM, Thomas wrote:
Dave,
I'm interested, but I'm wondering about a few things:
- XHTML 4.0 standard html?
As far as I know, this has more to do with the implementation of the
web components and elements. You will of course be using the 5.4
frameworks on Leopard. You can also of course pull the WO 5.4
frameworks onto Tiger and develop against those frameworks on your
Tiger system. This way you're still using the most-modern framework.
I had been doing that but it was inconvenient for me to do all my WO
development on a second system so I thought I'd just make the tools
work on Leopard.
- WO 5.4 inline tags like <wo:string value="[whatever]"/>
- html/api-only (no wod) components?
You can of course do some components in WebObjects Builder and others
without it. Or you can even use WebObjects Builder but write some new-
style tags directly into the HTML. It will simply see them as generic
XML tags. If you want to edit the objects using the RAD features
they'll have to of course be the old-style webobject tags with
separate bindings. I'm not sure why this is a problem though.
All I've really done here is give people the choice to use the old
tools, perhaps in addition to the new tools, even on the same
project. Even on the same component if you want!
Not all WO coding is designing perfect components. And not all WO
coding is RAD either. I use a mix of both. Often times I use the RAD
features to knock something out quickly then go back and generalize
it. It's nice to be able to use both the new and old tools. It would
of course be even nicer if the new tools could do everything the old
tools could do. But they can't. At least not yet. There's no
evidence to suggest anyone is really interested in taking the time to
write these features either so in the meantime I'm giving myself the
freedom to run the old tools to do what they were good at.
- those bugs I used to swear at all the time, but mercifully seem to
have forgotten... like pasting a tag from one component into another
page, and all the quoted attributes disappear, like
whatever: WOKeyValueConditional {
key = "session.something";
value = "some text";
negate = true;
}
becomes
whatever: WOKeyValueConditional {
negate = true;
}
Yeah, I'm well aware of that bug. My workaround was to use a
different tool. If you sort your wod in occurrence order then it's
not too difficult to either use Builder's built-in source editor or an
external editor to manually copy/paste the relevant portions of the
html and wod files. You might even use the WOLips component editor to
do it. Or you might use VIM. Or you might even use Emacs if you're
of that persuasion.
I seem to swear as much at Eclipse as I used to swear at WO Builder,
but I'd be very wary of going back to XCode now that I have become
more-or-less productive with Eclipse...
You don't have to go back to it. You can use Eclipse for most stuff
and use the old tools sparingly when you really need them.
I'm by no means trying to claim that the old tools were perfect. All
I'm saying is that they did some things very well and that being able
to use the right tool for the job can only be a good thing.
Sadly the mere mention of the old tools brings out all of the Eclipse
fanboys who try to argue that Eclipse has enough new features that you
can learn to live without the old tools. That's a bunch of bull, an
argument predicated on Eclipse+WOLips being mutually exclusive with
the old tools.
-Dave
_______________________________________________
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