Re: Speeding up XCode?
Re: Speeding up XCode?
- Subject: Re: Speeding up XCode?
- From: Dave McCaldon <email@hidden>
- Date: Mon, 17 Oct 2005 18:54:31 -0400
Having built a syntax coloring editor out of an NSTextView, I can see
why Xcode is slow (my editor is only just fast enough using
NSTextView). There are some tricks to make it faster, but
ultimately, the architecture isn't built for that kind of speed,
especially for more complex languages that involve full parsing with
each key press.
I would love to see Apple provide a lighter-weight, faster edit
control specifically for code editing. The engine could be much
simpler than NSTextView, everything would be the same font, all it
has to do is layout the text and color based on a buffer of
attributes that can be applied in one shot (or for a range) rather
than having to constantly make calls to color ranges of text, passing
in an NSDictionary each time!
I'm sure there are OSS editors out there, probably even for the Mac
that could be packaged into a Cocoa style Objective-C control and
dropped into a framework.
Dave.
On Oct 17, 2005, at 2:08 PM, Stefan Werner wrote:
Even with all the workarounds and friendly "don't use large files"
advice (which reminds me of the old "doctor, it hurts when I do
this!" - "Stop doing that." joke), the incredibly slow text editing
in Xcode is a problem that needs to be addressed. Even 0.5s are a
long time for loading a text file when you're stepping through some
source in the debugger. In VS.net, stepping through code is
instantly - before I lift my finger from the F10 key, both source
code and variable view have updated already. If faster source
handling requires dropping the complex Cocoa rich text control,
well, then just drop it. I understand how it's convenient to use it
and that reimplementing some of the required functionality can be a
pain, but seriously: It just isn't fit for this purpose, and faster
text editing appears to be one of the most popular requests on this
mailing list. I can live with dictionary and PGP services in my
source editor if I get speed instead. Take a look at TextMate for
example to see how there can be a fast text editor on OS X without
having to give up Cocoa.
-Stefan
On Oct 17, 2005, at 10:49 AM, email@hidden
wrote:
Message: 5
Date: Mon, 17 Oct 2005 08:18:27 -0700
From: Rob Lockstone <email@hidden>
Subject: Re: Speeding up XCode?
To: Xcode Users <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"
Fwiw, the Console app is especially useful for opening up large files
because it's essentially a GUI for 'tail' and only opens the last
128K of the file by default. You can then cmd-R and request variable
amounts of the file to be opened. Of course, very large files do
still take a few minutes to load, but if what you're looking for is
more recent (often the case when examining log files), Console is
great. Also, it will continually update with new data (a la tail),
and you can also (simply) filter the results.
Rob
On Oct 17, 2005, at 01:23 , Jerry wrote:
There are other sorts of files which are useful to open in XCode,
such as log files, XML and so on. We have a log file generated by a
server which I often need to look at and I've lost count of the
number of times I've tried without thinking to open it in XCode,
had to force quit XCode to get my system back and then opened the
file in CodeWarrior.
Jerry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40intersystems.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden