Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ANN] Xcode + Leopard at WWDC this year



Everyone here taking time to post wish-lists of stuff may way to file radars
for them instead (if you haven't already).  If you're serious about a
feature or enhancement, use radar; you'll definitely won't get anything on
your wish-list if you never 'vote' for it via radar.  Otherwise, you're just
practicing your typing.  If you're "too busy" to file a radar for an item,
then it's probably not as important to you as you think.




On 7/18/06 5:25 AM, "Ruslan Zasukhin" <email@hidden> wrote:

> On 7/18/06 12:08 PM, "Steve Baxter" <email@hidden> wrote:
> 
>> I can't make WWDC either unfortunately, but I would second the 64-bit
>> support.
>> 
>> My three would be:
>> 
>> (1) We need a full 64-bit version of Mac OS where *all* parts of the
>> system are 64-bit (including Carbon, OpenGL etc).  Without this,
>> Apple cannot compete with Windows x64 (which is a full 64-bit OS as
>> opposed to the half-baked "non-GUI" 64-bit support in Mac OS as it
>> stands).  A clear direction on x64 support is needed too.
>> 
>> (2) I would like the indexing in Xcode to work as well as it did in
>> CW.  Xcode does not reliably seem to manage to index files that are
>> in the C paths but not in the project - it really should.
>> 
>> (3) Fix the "Find in files" in Xcode.  It needs to be as fast as CW.
>> In fact, if they just took the CW dialog and replicated it, that
>> would be great.
>> 
>> (2) and (3) are the only features I miss in CW now - Xcode 2.3 works
>> so well, these would make it perfect!
> 
> I miss much more things from CW !!
> 
> 1) Ability to open virtual methods with the same name in the separate window
>         this is reported to xcode team
> 
> 2) ability to see in debug dynamic type of objects.
>         this is reported to xcode team
>         It seems they say it works for dlls also, but with some magic steps
> 
> 3) we must avoid this "magic steps" !!
>     
>     it is too often xcode/gcc DEFAULT behavior is NOT expected natural
> behavior. Few times I self have got in this traps already. To get DEFAULT
> NATIRAL EXPECTED for C++ developer behavior you must use some secret/magic
> linker or compiler switches.
> 
> 4) ToolTips in debugger
> 
> 
> 5) Much more fast and smart intellesence.
>         Visual Studio + third party plugin Visual Assist for Visual
>         do great things in this regard.
> 
>         Also I like how REALbasic works. Fast and comfortable.
> 
>         In CW this was nightmare. Almost never work. Slow and Ugly.
> 
>         In xcode also I do not feel many help from this feature.
> 


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden

References: 
 >Re: [ANN] Xcode + Leopard at WWDC this year (From: Ruslan Zasukhin <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.