Re: WOBuilder Replacement
Re: WOBuilder Replacement
- Subject: Re: WOBuilder Replacement
- From: Jean Pierre Malrieu <email@hidden>
- Date: Thu, 5 Jul 2007 12:53:41 +0200
That is collective action. You are never sure others will behave in
a cooperative way. But you must trust others in order to get anything
happening. So perhaps, instead of saying what you think others will
do, you should tell us about what you can be reasonably sure about:
what price you or your company would pay or donate for such a product.
And I no longer use WOBuilder. It keeps crashing, you need to have
xCode open to get bindings workings, when you have WOBuilder and
WOComponentEditor editing the same file, you are never sure you are
not overwriting changes... We need an IDE, not a bunch of partial,
unstable solutions.
I agree with you that 500$ is perhaps a high price, compared to what
you can get on the market for Eclipse plugins. On the other hand, you
are working all day long with these tools, and if something really
neat can be used, you will not hesitate very long.
JPM
Le 5 juil. 07 à 12:34, Jerry W. Walker a écrit :
Although $500 might be a fair reward for such a tool, I truly doubt
that enough parties would pay it to cover Chuck's and Mike's
estimates.
I think that there are few on this list who individually, or whose
companies, would pony up $500 per developer head for an undeveloped
piece of software. That would mean that either some one or two
companies underwrites the development, or the developers work for
about a year on no pay until they have a product to market, then
they might get paid, but only after people have taken the time to
download and test the resulting product and found it worthy. That
latter activity can take a few months for many in the community.
Once they have the new WOBuilder in hand, how many of them will
hold the old WOBuilder in the other hand and say, "Hmmm... $500
for this one and the old one is FREE along with the WO frameworks,
all the other development tools and Project Wonder! Does it make
sense for me to spend $500 on this one tool. Nah, we can get by
with the old tools till they cease to function, then we can keep a
couple workstations running the old versions of Mac OS X and WO to
get by for a few more years.
To Chuck and Mike, was your "... estimate of US$100,000 to US
$150,000 ..." based on starting from scratch, or on building from
the original WOBuilder's Objective C codebase? If Apple provided
the code base, would that reduce the estimate in your opinion?
I think building a new WOBuilder is a worthy objective, but I don't
realistically believe that whoever does it will recoup the money
indicated by estimates of the sizes given.
Regards,
Jerry
On Jul 5, 2007, at 4:58 AM, Simon McLean wrote:
On 5 Jul 2007, at 09:53, Jean Pierre Malrieu wrote:
Let's say 500$ for a fully functional, polished EntityModeler /
WOBuilder bundle...
That would be a fair reward, considering all the stuff Mike gave
to the community.
Now that is a fine idea.
Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
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