• 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
Framing the XCode usable Discussion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Framing the XCode usable Discussion


  • Subject: Framing the XCode usable Discussion
  • From: Brian Barnes <email@hidden>
  • Date: Thu, 06 Nov 2003 10:07:50 -0500

I like this list already, this is the first time I've been involved in a very personal discussion that didn't devolve into a flame war!

Side Note: I personally like multi-window interfaces, but I have to use VC++ & Net Beans (or Sun Studio One) all day so I'm also used to single window interfaces. I think XCode's interface should be able to handle both -- especially if people are going to be coming over from single window interfaces on the windows or java side.

So let's get a short list of what, IOHO (in OUR humble opinions) we think is missing. I get the idea that the powers that be really desire our input, but it's been a bit scatter-shot. I don't think they want to hear "do it the PB way" :) So, a good prioritized list might help.

*** Single window camp ***
1. Tabs to switch between windows
2. Build/Run window output (the hierarchal one) in the top-right pane
[Single window camp, help me out here ...]

*** Multiple window camp ***
1. Fix bugs with build window popup
2. Add run window popup preferences (only when console output, always)
3. Allow us to remove things like finds/warning&errors/etc from groups & files, because we'll be using popup windows


*** Both Camps ***
1. Overhaul the find (go back to PB way - remove from groups & files list)
2. Move build styles to children of targets

A couple more suggestions on my parts.

1. This has been discussed, but a XCode preference for "expert" target/build inspectors, where it would remove the collections draw and just lay out all the options (instead of a "all options" button.) Unless this is already what you are thinking. Net beans is this way.
2. This is so 1990s. I only bring this up because you never know :) It'd be nice if I could get the toolbar as a strip under the menu bar. Yeah, I know, but I prefer a thin and long project list, and there's not enough room for icons. Ah, forget it, I'll shut up now :)


So, are you guys gonna give us out betas for new builds because we are so helpful? :)

[>] Brian
_______________________________________________
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.

  • Prev by Date: -nofixprebinding
  • Next by Date: Getting values of settings with AppleScript
  • Previous by thread: Switching off recomputeHeadermap?
  • Next by thread: Getting values of settings with AppleScript
  • Index(es):
    • Date
    • Thread