Berikut adalah fitur-fitur baru yang ada di DelphiXE5 :
- the REST client library, a new cross-platform framework for easy access of REST-based web services
- REST debugger
- the full integration of FireDAC
- IDE support for MacinCloud
- Extendible IDE mobile design devices
- the awesome IDE Insight functionality (
Ctrl+.orF6) is no longer a modal dialog but is now a search box - style support for the freshly released iOS 7
- swipe to delete feature on mobile platforms
TListViewsearch filtering support- the removal of the long defunct WebSnap and InternetExpress (with the suggestion to use IntraWeb and WebBroker instead for similar functionality)
The full Delphi target platform sekarang menjangkau:
- 32-bit Windows
- 64-bit Windows
- 32-bit OS X
- iOS Simulator (Intel)
- iOS (ARM)
- Android (ARM)
Mempunyai lumayan banyak compiler:
- dcc32 – Embarcadero Delphi for Win32 compiler version 26.0 – your regular Win32 Delphi, the latest version updated over many versions since Delphi 2
- dcc64 – Embarcadero Delphi for Win64 compiler version 26.0 – the 64-bit Windows targeting compiler
- dccosx – Embarcadero Delphi for Mac OS X compiler version 26.0 – the Delphi compiler that generates 32-bit OS X apps
- dccios32 – Embarcadero Delphi Next Generation for iPhone Simulator compiler version 26.0 – the NextGen Delphi compiler that builds Intel executables that run in the iOS simulator
- dcciosarm - Embarcadero Delphi Next Generation for iPhone compiler version 26.0 – the NextGen Delphi compiler that builds ARM executables that run on iOS devices
- dccaarm – Embarcadero Delphi for Android compiler version 26.0 – the NextGen Delphi compiler that builds ARM executables that run on Android emulators and devices
Persyaratan Android
Karena compiler Delphi menghasilkan instruksi mesin asli, output-nya adalah prosesor khusus. Dengan kata lain itu tidak menargetkan Dalvik Virtual Machine, di mana aplikasi Android biasa berada, yang pada dasarnya Java p-kode yang dieksekusi oleh varian dari Java VM. Sebaliknya menghasilkan kode mesin mentah, karena semua gelombang saat Delphi compiler lakukan (yang lama pergi Delphi untuk. NET adalah pengecualian untuk aturan umum). Jadi karena itu compiler menyusun instruksi mesin asli dukungan Android Delphi memiliki persyaratan sebagai berikut:
- there must be a GPU
- the CPU must be ARMv7 with NEON instruction support
- the OS on the target device must be one of:
- GingerBread: Android 2.3.3+ (MR1 or later), which is API level 10
- Ice Cream Sandwich: Android 4.0.3+ (MR1 or later), which is API level 15
- Jelly Bean: Android 4.1+ (release, MR1, MR2 or later), which are API levels 16, 17 and 18
- you can run the app on an Android emulator if:
- the emulator is set to use the host GPU
- the emulator is running Ice Cream Sandwich (MR1 or later) or Jelly Bean (release or later)
- the emulator is not running in a Virtual Machine
How do you find out if your device is supported? Well, the OS version you can find out in the Settings. The path and menu items may vary but goes roughly like this: Settings, About phone (or tablet), Software information, Android version.
To check the CPU details you’ll need to run one of the tools from the Android SDK against your connected device. Delphi installs the Android SDK and NDK if you don’t tell it you have it pre-installed. The Android SDK gets installed into a directory something like: C:\Users\Public\Documents\RAD Studio\12.0\PlatformSDKs\adt-bundle-windows-x86-20130522\sdk. In the platform-tools subdirectory from there is the Android Debug Bridge, adb.exe.
To run a command against your device it needs to be connected, typically by USB. This requires you to install an appropriate USB driver for your device as the ones located by Windows typically don’t do the job. Refer to the helpful The Delphi Geek blog post on the matter, XE5 and USB Drivers, for more information and links to drivers for the more common Android phone manufacturers.
When your phone is connected you’ll need to launch a command prompt and run an
just to prove that your device can be seen by the Android tool chain. Assuming it can, run:
This will show you CPU information something like this:
DOWNLOAD DELPHIXE5 UPDATE1
DOWNLOAD OTHER DELPHI
To check the CPU details you’ll need to run one of the tools from the Android SDK against your connected device. Delphi installs the Android SDK and NDK if you don’t tell it you have it pre-installed. The Android SDK gets installed into a directory something like: C:\Users\Public\Documents\RAD Studio\12.0\PlatformSDKs\adt-bundle-windows-x86-20130522\sdk. In the platform-tools subdirectory from there is the Android Debug Bridge, adb.exe.
To run a command against your device it needs to be connected, typically by USB. This requires you to install an appropriate USB driver for your device as the ones located by Windows typically don’t do the job. Refer to the helpful The Delphi Geek blog post on the matter, XE5 and USB Drivers, for more information and links to drivers for the more common Android phone manufacturers.
When your phone is connected you’ll need to launch a command prompt and run an
adbcommand. This may be easiest if you change directory to the platform-tools subdirectory (or Shift+right-click on the platform-tools folder in Windows Explorer and choose Open command window here). Firstly run the command:adb devicesjust to prove that your device can be seen by the Android tool chain. Assuming it can, run:
adb -d shell cat /proc/cpuinfoThis will show you CPU information something like this:
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 13.52
processor : 1
BogoMIPS : 13.52
processor : 2
BogoMIPS : 13.52
processor : 3
BogoMIPS : 13.52
Features : swp half thumb fastmult vfp edsp thumbee neonvfpv3 tls vfpv4
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x06f
CPU revision : 0
Hardware : UNKNOWN
Revision : 0003
Serial : 0000000000000000Check the Processor line to ensure you are running ARMv7. In the Features line check that neon is included in the CPU feature listDOWNLOAD DELPHIXE5 UPDATE1
DOWNLOAD OTHER DELPHI
0 comments: