Re: Feature Requests...
Re: Feature Requests...
- Subject: Re: Feature Requests...
- From: Nicolas Zinovieff <email@hidden>
- Date: Tue, 31 Jan 2006 15:53:32 +0100
Jeff LaMarche wrote:
https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa
File it as a bug using the bug reporter, and for the "type" of bug,
change to "Enhancement Request". You should be able to select Xcode
from the "Development Tools" category IIRC.
Thing is, we have close to no feedback on those, it amounts roughly to
sending an email to email@hidden
Besides, we don't know if anyone had an even remotely connected idea, if
there is anyone looking into it, or even if it has been taken into
consideration (although I personally think that some people *do* read these)
What we have discussed in great length over the forums, mailing lists,
and face to face with other developers, is rather along the lines of a
plugin API.
It is a *developer tool*! Thoses who develop know about bugs (therefore
we don't mind "almost stable" releases as long as the major bugs have
been removed), we want features! And we all have different ways to write
our programs... and to work. To be able to customize entirely our
worflows by integrating our own functionalities would really be a killer.
And I know we can use shell scripting and applescripting and whatnots.
However, for some tools, you need authentication. How can we do than via
shell script since we don't have a full two-ways interaction with it?
How can we use different ways to synchronize our code with a repository?
How can we add a new compiler? (I know it's doable, I've had a working
codewarrior bridge working for a couple of years now, but it really is
complicated to implement)
How can we treat new build options? (just like the original post, adding
a package builder for example)
Etc etc etc...
In some ways we work like artists, and we all have our style, our way of
doing things and our little habits. Why not make our common tool
something expandable, rather than something that compell us all to work
the same way?
I'm not saying that Xcode should or should not be open source. That's
not the point, Apple has every right to hold whatever information they
want about the way their apps work. But *every* professional tool out
there has a plugin API. I'd just like to see developers treated as
professionals as well.
--
Nicolas Zinovieff
Custom developments from France
*-------------------------------*
Fortune:
It's always darkest just before it gets pitch black.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden