• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Speeding up XCode?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Speeding up XCode?


  • Subject: Re: Speeding up XCode?
  • From: Rob Lockstone <email@hidden>
  • Date: Mon, 17 Oct 2005 11:26:48 -0700

I don't disagree with you. Xcode, or better yet Cocoa, needs to be fixed to deal better with large files. However, to date, Apple has not done very much to improve the situation. I wonder if they've ever profiled the code internally to see where the hot spot(s) are. I can't imagine they haven't! I imagine one approach would be to allow various text editing "bells and whistles" to be optionally turned on/ off. But, I suppose it depends on what, exactly, is slowing things down.

I was simply pointing out a viable, and often better, option for viewing large log files. Log files being a specific type of file mentioned by Jerry, below.

Rob

On Oct 17, 2005, at 11:08 , 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:

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: This email sent to email@hidden
  • Follow-Ups:
    • Re: Speeding up XCode?
      • From: Dietmar Planitzer <email@hidden>
References: 
 >Re: Speeding up XCode? (From: Stefan Werner <email@hidden>)

  • Prev by Date: Re: Having Image PICT NIB problem ?
  • Next by Date: Re: 10.2.8 and alloca.h
  • Previous by thread: Re: Speeding up XCode?
  • Next by thread: Re: Speeding up XCode?
  • Index(es):
    • Date
    • Thread