Unicode
VC8
Preparing for 64 Bit
Multicore processors
ATIL
Migration and CUI Customization
.NET / Windows Forms
Unicode support
Customers sharing data across continents
AutoCAD was localized a long time ago
But current solution has limitations
Unicode is the standard now
It addresses most data input issues
Multi-language support throughout the product
Customers just enjoy the benefits
Developers need to port software or add string conversion layer
•char type to contain character data
•Strings is typically defined using a char* or a char[]
•Unicode character data g requires use of the wchar_t
•Strings are typically wchar_t* pointers or wchar_t[] arrays.
•wchar_t is the ANSI C++ standard keyword for the Unicode type.
•wchar_t is a 16-bit value in Visual C++, roughly equivalent to an unsigned short.
Preparing for 64 Bit
§Use the /Wp64 compile switch
§Or set “Detect 64-bit Portability Issues’ to Yes in all build configurations in vcproj files.
Windows Longhorn Technologies
Biggest change since DOS to Windows
Windows Future Storage (WinFS) is out of Longhorn
Longhorn UI will work on Windows XP as well
.NET and managed code:
Managed code is secure, stable, easy to develop, port & install
APIs for managed code (C# programming)
Windows Forms UI (Layer dialog)
Majority of AutoCAD code will remain in unmanaged C++
Next generation print path
Easier printing/plotting
NET
Managed wrapper classes
Write programs in VB .NET and C#.
The ObjectARX managed wrapper classes include
Selection
Jig
prompt support
complete events coverage previously available only to C++ reactors
application object model for readily discoverable access to the properties of the application, document, editor, and window objects of AutoCAD.
.NET applications can easily create dockable palettes and tool palettes and extend tabbed dialogs.
The geometry library includes 2D curves, and support for external references is also present.
support for the .NET API’s moving forward.
| 
[复制链接]
发表于 2005-7-21 17:10:00
置顶卡
变色卡
显身卡