Delphi XE2 News

----------------
UnitScope Names
-----------------

This beta release introduces UnitScope names to RAD Studio.
With support for multiple platforms (Win32, Win64, OS X) in Pulsar,
UnitScope names provide organizational and usability benefits for using the
libraries and frameworks in RAD Studio.
UnitScope names disallow ambiguity, and they provide a context for the RAD
Studio units, helping to categorize,articulate and better delineate the
boundaries between what units go with what part of the overall frameworks,
or are specific to a platform.

UnitScope names consist generally of words separated by a period ('.').

For Example:
System.Win.Registry.pas and Vcl.Forms.pas.

All cross-platform units such as Classes, SysUtils, Contnrs, RTTI,
etc., in the base RTL package are now prefixed with System.

OS/Platform specific units have a prefix indicating the platform
(Winapi.Windows, Macapi.CoreFoundation, Posix.Base, etc.).

Traditional Visual VCL units are prefixed with Vcl (Vcl.Menus,
Vcl.Graphics, Vcl.Forms, Vcl.Controls, etc.).

Core Database units are prefixed with Data (Data.DB,Data.DBCommon, etc.).

DataSnap units are prefixed with DataSnap (DataSnap.DBClient,DataSnap.Win.TConnect, etc.).

XML units are prefixed with Xml (Xml.xmldom, Xml.Win.msxmldom, etc.).

Internet units are prefixed with Web (Web.WebBroker, Web.Win.ISAPIApp, etc.).

Soap units are prefixed with Soap (Soap.SOAPHTTPClient, Soap.Win.CertHelper, etc.).

BDE units are prefixed with Bde.

You will not need to make any changes to your existing projects when you
work with them in Pulsar.
When you open an existing Delphi project in Pulsar, the project will
automatically be upgraded to use the appropriate UnitScope names.

When a new project is created, Pulsar will automatically ensure that the
search path includes the appropriate UnitScope prefixes, based on what
framework it will be using coupled with what platform it is targeting.

For example, a new FireMonkey application will contain
System, RTL, FMX, and Data as the platform agnostic UnitScope prefixes.
When you are targeting Windows, it will add Winapi,
and for OS X it will add Macapi.
When you add a unit to the uses list that is actually specific to an operating
system, such as Macapi,
it will fail to compile for Windows since there will be no Winapi.CoreFoundation.

The following top-level UnitScope names are globally reserved and
should not be used by third-parties or users, and they should not appear
anywhere in a UnitScope hierarchy.
o System
o Xml
o Vcl
o Fmx
o Data
o Datasnap
o Bde
o Web
o Soap

These following UnitScope names can be used, but should only
appear at the top level:
o Winapi
o Macapi
o Posix

-----
IDE
-----
The Object Gallery is filtered properly to enforce what files/modules can be
added to a project.
For example, you should not be able to add a FireMonkey form to a VCL application
and you should not be able to add a VCL form to a FireMonkey application.

To support application development for multiple platforms, the
main project icon, version information and manifest information are now
stored in the project file, and the information can be different for each
build configuration and platform.

Previously this information was stored in the project.res file.
Pulsar will automatically upgrade existing projects
and add the needed information to the project file.
If you have other information stored in the .res file,
Pulsar will separate the known resources from the unknown resources.

The unknown resources are added to a project.otares file which is added to
the project.

When build your project, if you receive this error:
[BRCC32 Error] Project1.vrc(58): resource file Project1_Icon.ico is not in
3.00 format

then your icon resource has been imported incorrectly.
We are aware of this problem, and we are working on a fix.
In the mean time you can correct the
problem by going to Project Options > Application > Appearance and select
Load Icon.
Enter "%BDS%\bin" and select the CBuilder or Delphi icon.
In the following dialog, select "Leave icon in the current directory". This
will allow your project to build.

--------------
FireMonkey
--------------
Several FireMonkey identifier names have been updated to be more precise
and consistent:
Identifier
New Name
CanFocused

CanFocus
OnCanFocused

OnCanFocus
EnterFocus

Enter
KillFocus

Exit
OnEnterFocus

OnEnter
OnKillFocus

OnExit
RotateAngle

RotationAngle
RotateCenter

RotationCenter
CanClipped

CanClip
OnBeforePaint

OnPainting
DragDisableHighlight

EnableDragHighlight
DesignHide

DesignVisible
ObjectByPoint

ObjectAtPoint
SetxRadius

SetXRadius
SetyRadius

SetYRadius
xRadius

XRadius
yRadius

YRadius
is*

Is*
*Vertexs

*Vertices
*Indexs

*Indices
Dotimer

-------
DoTimer
--------
Weve added some support for FireMonkey animations within the property
inspector.
Properties that can be animated are indicated with a greyed out
film strip icon.
For properties that are animated, this icon is bold.
Expanding a property with animations will list the animations associated
with that property.
Appropriate animations can be created using a dropdown
menu directly on those properties that can be animated. Wed appreciate your
feedback on this approach.
FireMonkey Print, Page Setup and Save File dialogs have been added.

Data Binding
------------
This Pulsar beta release introduces new Data Binding components for
FireMonkey:
TBindList fills a TListBox or TListView using expressions.
TBindNavigator FMX navigator for a bind scope component such as
TBindScopeDB.
TBindLink supports data editing using expressions. For example, a

TEdit may be used to edit a TField (TBindScopeDB is also required).

TBindScopeDB now supports editing and navigation.

A new component editor is provided for bind components TBindList,
TBindExpression and TBindLink. Use this editor to enter and test
expressions. Double click on TBindCompList, and then double click on a
binding component.

The Data Binding examples have been updated.
Download FireMonkeySamples.zip from the Pulsar beta site for the latest
FireMonkey and Data Binding examples.

Delphi Compiler
---------------
A new compiler hint has been added , "H1066 Lost Extended floating
point precision. Reduced to Double".

Overload resolution has been updated to favor Extended for
(untyped) intermediates. This resolves ambiguous overload errors when
calling a function with both a Double and Extended overload with an
expression.

Delphi RTL
-----------
Added CoreFoundation utilities unit (System.Mac.CFUtils).
TSize, TSizeF and TSmallPoint now include utility methods.
Introduced 10-byte compatibility type for streaming Extended on Win64.
Further improvements to our Windows SDK header translations.
There is a new TPropertyList to read/write .plist files.

DataSnap
---------
Added support in TSQLConnection and TDSRESTConnection for proxy
info (host, port, user, password) for DataSnap HTTP connections.

source: from a tyrkey site