• 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: Documentation frustrations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation frustrations


  • Subject: Re: Documentation frustrations
  • From: Brandon Sneed <email@hidden>
  • Date: Tue, 5 Jul 2005 14:35:12 -0500

here's just a few off the top of my head...

- it generates completion information in the background based on the source files rather than a dummy project (ala xcode). this lets me use includes in other places w/o me having to add an entry to the "include paths" option. i had to add a dummy project to get the indexing in xcode, despite the dir of those includes being set in my include path. it was more hassle than it probably should be all in all.

- editing a resource in a c++ MFC/WTL/.NET project automagically updates the code as i go. I can double-click on a button in a dialog, and fill in the handler on the spot. I can add a new button and it inserts a template for a handler, or i can right-click and select which handler to override, and it generates the code to do so and takes me to it. In IB, i don't get any of this, and when i'm done, i have to diff it by hand. Big pain in the butt. In MFC, it uses comment markers (like //// for instance, or //$$, i would need to go look to give an exact match) to do the source marking for the designer. .NET code uses something different, but it serves the same purpose. I would rather have some stuff like this in my code than diff the thing by hand any time i made a change.

- the ide knows how to deal with most files in a given compiling scenario, like idl files (it generates a .c and .h from it), rc files (builds a .res, and links it into the binary).. etc.

those are just a few major ones i can think of.. i had also written quite a few ide plugins to do various other things, like automating remote debugging to copy a group of binaries to the target machine and then kick off the debugger.. that was a really useful one. Xcode's remote debugging appears to force me into doing it via ssh, setting up key pairs, my app has to be in the same dir remotely as it is on my local machine, so on so forth. Even Codewarrior would copy the binary to the target automagically. I know the SSH/keypair stuff is there for security reasons, but it really gets in the way, when security isn't an issue for me 90% of the time since i have both machines sitting next to each other on a private or company internal network.

most of the other things i can think of are more specific to windows programming in general and i can't htink of an equivalent in xcode.

the biggest feature of all is that vs.net is EXTREMELY extensible. Even better than that is that those extension interfaces are documented as well <nudge>. I added a new debug handling mechanism (as noted above) in just a few hours. I walked into it having never even attempted writing a vs.net extension before. I'm trying to do the same thing in xcode, and i just can't find any samples or documentation on the subject at all. I can see where the plugin needs to go, and that it needs a .pbplugin extension probably, but nothing else. I may just be looking in the wrong place, but i feel like i've been breaking my neck thinking of things to search for on google that will give me hints on making one.


Brandon

On Jul 5, 2005, at 1:51 PM, Chris Hanson wrote:

On Jul 5, 2005, at 9:46 AM, Brandon Sneed wrote:

Despite VS.NET's UI being awful, writing code that works is made extremely easy by the good quality documentation and automation of common tasks.


Can you elaborate on your latter point (automation of common tasks) a bit?


  -- Chris





_______________________________________________
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


References: 
 >re: Documentation frustrations (From: George Warner <email@hidden>)
 >Re: Documentation frustrations (From: Brandon Sneed <email@hidden>)
 >Re: Documentation frustrations (From: Chris Hanson <email@hidden>)

  • Prev by Date: Re: Header search path with XCode 2.1
  • Next by Date: Re: Documentation frustrations
  • Previous by thread: Re: Documentation frustrations
  • Next by thread: Re: Documentation frustrations
  • Index(es):
    • Date
    • Thread