Re: WOLips: Project Triangles do not work.
Re: WOLips: Project Triangles do not work.
- Subject: Re: WOLips: Project Triangles do not work.
- From: Chuck Hill <email@hidden>
- Date: Wed, 23 Jan 2008 13:27:33 -0800
Hi David,
On Jan 23, 2008, at 12:31 PM, David Elliott wrote:
On Jan 23, 2008, at 2:25 PM, Mike Schrag wrote:
You'll get really used to it. I often hate Eclipse but
nevertheless it saves me countless hours of work. So, it's a
love and hate relationship.
For what it's worth, I feel the same. For every huge annoyance,
there are like 10 really cool things.
Well for what it's worth, I think Eclipse is the worst IDE ever.
I blame myself for initiating this. </dead-horse-beating>
Yes, I realize it is beating a dead horse, but maybe something
useful can come out of it. Before settling on the WO5.4 on Tiger
hack I did some work getting the Tiger tools to work on Leopard in
conjunction with Xcode 2.5 for Leopard. When I get a moment I'm
going to try to figure out the rest of the problems but for now I'm
just trying to get some work done. The short rundown is that
you'll need to grab the Libstreams source, provide an
implementation for [NSObject forward::] and use dyld environment
variables to preload your fixing dylib.
Of course this isn't a long-term solution. The long-term solution
is for me to sit my ass down for some marathon coding sessions and
write decent replacement tools since no one else is willing to do it.
I'd hazard a guess that most of feel that we already have replacement
tools that are not only decent, but far superior to what we had.
EOModeler is just flat out buggy. WOBuilder did have a nice WYSIWYG
interface with drag and drop that worked just fine if you did all
your layout with HTML tables and used little or no CSS or
JavaScript. For anything more modern than that, it is pretty well
useless. Xcode had a very simple UI, but then again it did not do
much other than run a make file. And the whole targets metaphor was
far from clear.
I find the current tools so detrimental to my development
experience that it's becoming increasingly cost effective for me to
write them even if I never release them.
You are in a minority of six to 10 people here, at least that I have
heard from. I'd be asking myself what it was that I was not seeing.
Sure there are some nice things (like a WYSIWYG interface with drag
and drop for Component Editor) but these are very hard to do right
unless you are using a very restrictive subset of what WO and HTML
can do. You might find your energies more profitably directed into
improving what is there now.
That's an important point because I don't think I'd ever be able to
sell these tools so I'll have to justify the cost of writing them
based on the benefit of not wanting to hurl a hammer through my
monitor every time I work on a WO app. The cinema displays aren't
cheap so that would be very costly.
Or perhaps some Anger Management counseling? :-P
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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