DevExpress offering Metro-inspired Tile control for Delphi VCL, plans to drop support for Delphi 7

By tim, on July 11th, 2012 Follow tim on Twitter

DevExpress has released an update to its VCL component suite, version 12.1, which includes a Metro-inspired tile control. That is, it looks like a Windows 8  Metro-style application, but in reality it runs as a desktop application. The VCL components support Embarcardero’s Delphi and C++ Builder, but not the FireMonkey library that runs cross-platform.

The new release also adds a “Server Mode” for  the ExpressQuantumGrid grid control, which retrieves only those rows needed to populate the current view.
DevExpress CTO Julian Bucknall has posted about the update. He says it is time to drop support for Delphi 7 (though this is supported in 12.1):

12.1 will be the last version to support Delphi and C++Builder 2010. I will sound a further note of caution: it’s likely that in 2013 we shall drop support for Delphi 7 and Delphi 2007 (what you might call the “ASCII IDEs”), so that we can concentrate on the latest run-times and environments.

Delphi 7 is significant because it was the last version to use its own dedicated IDE built with Delphi itself, and by today’s standards is delightfully small and fast.
Bucknall has reservations about Embarcadero’s move to Clang and LVVM for 64-bit C++ Builder and eventually for the other languages too:

I’m going to say we shall treat it with kid gloves. Re-engineering a compiler so fundamentally says “breaking changes” to me, especially given the necessary extensions that are present in the current C++Builder to interface with Delphi. So, fair warning: if the changes are too severe, we shall not support 64-bit C++Builder in 12.2. It took us long enough to support 64-bit Delphi across our entire product line, and this year we don’t have the resources. That doesn’t mean we won’t ever do this (after all, Embarcadero are saying that they’ll switch completely to Clang/LVVM at some point), just that we won’t this year.

Returning to the Tile Control: it will be fascinating to see if this sort of approach, mimicking Metro with a desktop app, becomes popular. Microsoft is promising some of the same with Office 15, though we have not seen much of this officially yet. The advantage is that you can make desktop apps just as touch-friendly as Metro apps. The disadvantage is that you do not get Windows Store support, Contracts, app isolation, or other benefits of the Windows Runtime which underlies the Metro side. Users may be confused.
I doubt Microsoft will mind though. It all helps to promote the Metro style which is the distinctive feature of Windows 8.

More at http://www.itwriting.com/blog/6008-devexpress-offering-metro-inspired-tile-control-for-delphi-vcl-plans-to-drop-support-for-delphi-7.html

Standard MDI Applications - VCL vs Metropolis

Exploring Delphi XE3

Downloaded XE3 Trial last week and now putting it through its paces ...

An Introduction to the TBatchMove Component in Delphi and C++ Builder

By: Borland Staff

Abstract: TBatchMove can move data between tables with the same database or a different database

Problem:
What is the TBatchMove component and how do I use it with InterBase 
(or any other database)?

Solution:
An Introduction to the TBatchMove component
=====================================

1. What is it?

TBatchMove is a VCL component that lets you perform operations on 
groups of records in a table. The operations are named with intuitive 
names that basically tell what they do.  

Listed below are the operations or "modes" that the TBatchMove 
component supports.  

- batAppend     => 
   appends all records from the source table to the end of the destination
   table.

- batAppendUpdate     =>  
   Appends all records from the source table to the end of the destination
   table and updates those records with the same primary index in the
   destination table with the same records from the source table.
 
- batCopy     =>  
  Copies a table and its records to a new table

- batDelete     =>  
  Delete all records in the destination table that also appear in the 
  source table.

- batUpdate      =>  
  Update existing records in the destination table with their counterparts
  in the source table.


2. How do I  use it?
Listed below are steps to setup and run a TBatchMove component to 
upsize Paradox data to InterBase.

a.  Put two TTable objects on the form, one for source and one for 
destination.
1. Click on "Data Access" tab.

2. Click on table icon.

3. Click on form.

4. Press  to go to the Object Inspector.

5. Define the Database property for table1 to be the BDE alias that 
points to the directory where Paradox tables are located.  In this case, 
we are using the DBDEMOS alias hat is installed by default when you 
do a full install of Delphi 3. 

6. Define the TableName property in object inspector for table1 to be the 
Paradox table name, In this example, the table name will be the "orders" 
sample table that comes with Delphi.  Since we have already specified the 
location of the tables, you can easily fill in the TableName property setting 
by selecting the table from the picklist of the TableName property.

7. Repeat steps 2.a.1 - 2.a.4 for table2

8. Define the database on table2 to be an alias that points to the InterBase
database, in this case employee.gdb, by selecting the BDE alias that points
to the employee database.

9. Define TableName  property for table2 to be the table name you want 
created in InterBase. For simplicity, call it "orders" as well.

10. Configre the TBatchMove component
a.   Put the  TBatchMove component on the form.
1. Click on the Mode property's edit box.

2. Click on the BatchMove icon.

3. Click on the form.

b.  Define the source and destination for TBatchMove
1. Hit  to go to the object inspector.

2. Set the Source property of TBatchMove to be table1.

3. Set the Destination property of TBatchMove to be table2.

d.   Specify the mode for TBatchMove
1.  Click on the Mode property's edit box.
2.  Click on the down arrow that appears to get a picklist of modes to 
     choose from.
3.  Click on  "batCopy" to select it from the list.

d. Activate TBatchMove 
1. Right click on TBatchMove component
2. Click on  "Execute" on the pop-up menu that appears.

e. What happens when TBatchMove fails?

You can tell TBatchMove to document what happened when you run 
a batch move operation by setting the following properties. They tell 
Delphi to create a local Paradox table containing records that were 
not successfully part of the batchmove operation.

ChangedTablename  => Records that were modified by the batch 
                                    move operation

KeyvioltableName  => Records that could not be added because they 
                                 violated a uniqueness constraint.

ProblemTableName  => Records that could not be added for one reason
                                   or another.

More at http://edn.embarcadero.com/article/25620

How to transfer a Delphi Profile from One PC to another

Assuming that Delphi and the other VCLs are is installed in the same folder at the new PC, then the migration is fairly easy if you are comfortable working with regedit.

The information is stored in the Registry under  a key called HKEY_CURRENT_USER\Software\Borland\Delphi\5.0 or something like that. You'll find all the registration information under that key, including a list of installed packages.

Just export the keys to a registry file, copy it to the new computer and install it by double-clicking on it