Re: Xcode does seem hard on newbies(was Xcode release notes)
Re: Xcode does seem hard on newbies(was Xcode release notes)
- Subject: Re: Xcode does seem hard on newbies(was Xcode release notes)
- From: "Theodore H. Smith" <email@hidden>
- Date: Thu, 5 Aug 2004 14:45:06 +0100
This little exchange between a relative newcomer (?)
to Xcode and the
head of developer tools at Apple (I'm not sure about
that title,
Godfrey) strikes me as indicative of a systemic
problem with Xcode: the
developers of Xcode do not appear to have a good
understanding of the
users of Xcode.
i have to agree as i am finding Xcode/Interface
Builder/the whole Apple development environment to be
more obtuse, complicated and convoluted than i was
expecting. i've been trying to create a simple
program to manage a small inventory using a mySQL
database as the datasource. i was able to get mySQL
up and running(despite the bad documentation on their
site) and was even able to use Xcode to get some c
type programs to read and write to the database.
however, i've spent more time and in fact had to break
down and buy aaron hilligases book on cocoa
programming to make any real headway (the doc on the
apple web site is unfortunately very complex and
difficult to navigate on it's own). i find the
interface builder to Xcode connections to be
particularily weak (why are these two separate
products btw?)
They should be integrated into one. In fact, there shouldn't need to be
any manual editing of .h files or using filemerge when you add new
outlets or actions to a class, it should all be done automatically.
Also, the .h files should be automatically maintained from the .m
files, that is, having to add stupid declarations is such a
productivity and moral killer. Java doesn't need this. In fact, no
language needs .h files. .h files are a product of linear thinking, a
way of yesterday. Java is old enough as it is and it doesn't need .h
files.
To do without a .h file, the compiler must re-scan the document, but
thats no problem. First it scans for classes/structs, and makes a list
of them. Then it scans for functions/methods and properties, and makes
a list of them. Then it scans the code, and compiles it, using the
pre-made listing of classes, structs, functions methods and properties.
That's 3 re-scan operations, but seriously it is incredibly fast to do
string searching, I know because I've written many heavy duty string
processing apps. gcc is slow because it isn't well designed, not
because its got a hard task on it's plate.
--
Theodore H. Smith - Software Developer.
http://www.elfdata.com
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.