DFM Binary to Text - Felix John COLIBRI.

• abstract : This project converts the .DFM file in Binary format to the ASCII Text format
  
• key words : .DFM, CONVERT.EXE, WinExec, conversion BinToTxt
  
• software used : Windows XP, Delphi 6
  
• hardware used : Pentium 1.400Mhz, 256 M memory, 140 G hard disc
  
• scope : Delphi 1 to 2005 for Windows
  
• level : Delphi developer
  
• plan :
  
  • Introduction
    
  • The Dfm BinToTxt converter
    
  • Download the Sources
    

1 - Introduction

• a binary format, which is a Windows Resource, and loads very quickly. This was the first Delphi 1 format
  
• a textual format, which has the same content, but has an ASCII Format
  

This simple tool simply finds all the .DFM files, and converts them into their textual format.

2 - The Dfm BinToTxt converter

2.1 - Organization

• detects all the .DFM files in a path
  
• for each .DFM file, CONVERT.EXE is launched from Delphi
  
• after all the conversion, the .txt files can be changed into .dfm files
  

• the syntax of CONVERT.EXE is not published. We only know that
       CONVERT my_dfm.DFM
  does the following:
  • if the file in already in ASCII format, nothing is done
    
  • if the file is in binary format, it is converted and saved as a .TXT file
    
  Maybe CONVERT.EXE can save the file with the .DFM extension, maybe the utility can convert a whole path, maybe there are other options. This utility did not cost much time, so we chose to go ahead rather than spend hours to figure out the details of CONVERT.EXE
  
• to launch a DOS .EXE requires the use of CreateProcess. This is a rather uncomfortable endeavour:
  • the errors are not always acknowledged (it depends on the .EXE which is launched)
    
  • if the execution results in the creation of files, there might be some delays before they are visible. You cannot simply use FileExists or GetFileDate to check the result. Obviously there are some threading issues. To avoid any problem, we simply let the WinExec quietly finish its work, and start other handling after that
    
  Certainly Windows gurus will find this approach laughable, but I have more interesting things to do than spelunk into the Windows innards.
  

2.2 - Detection of the Files

and this procedures calls our call-back function:

2.3 - WinExec

2.4 - Additional handling

• the files to convert (the .DFM and the .PAS) are copied to a target path. Therefore, we do not touch the original files (just in case...)
  
• we can display the size difference. The ASCII file is always larger than the binary version, and this gives us a visual clue that the conversion somehow succeeded
  
• the .TXT resulting from the conversion can replace the binary .DFM using the "change_the_txt_into_dfm_" button: we erase the .DFM and rename the .TXT.
  
• if you click on a .DFM in the DirectoryListBox, and the view_dfm_ TabSheet is selected, the .DFM is loaded. You then can see the textual version of the .DFM
  

2.5 - Mini Manual

	copy the .DFM and the corresponding .PAS in a directory of your choice
	copy CONVERT.EXE from C:\Program Files\Delphi\BIN\ to the EXE directory
	compile convert_dfm_to_txt.dpr and execute
	select the directory using the DirectoryListBox
	click "all_dir_recursive_"
	the .PAS and .DFM will be copied into the _data\_dfm_to_txt\ path, and all binary .DFMs will be converted to their .TXT counterpart

• to check the size difference, click "check_"
  
• to erase the binary .DFM and rename the .TXT, click "change_the_txt_into_dfm_"
  
• to view an ascii .DFM
  

  	select the proper path using the tDirectoryListbox
  	select the "view_dfm_" tab
  	click on the .DFM

3 - Download the Sources

• convert_dfm_to_txt.zip: the project with the parser and the data structure (15 K)
  

• the main program (.DPR, .DOF, .RES), the main form (.PAS, .DFM), and any other auxiliary form
  
• any .TXT for parameters, samples, test data
  
• all units (.PAS) for units
  

• are self-contained: you will not need any other product (unless expressly mentioned).
  
• for Delphi 6 projects, can be used from any folder (the pathes are RELATIVE)
  
• will not modify your PC in any way beyond the path where you placed the .ZIP (no registry changes, no path creation etc).
  

• create or select any folder of your choice
  
• unzip the downloaded file
  
• using Delphi, compile and execute
  

The Pascal code uses the Alsacian notation, which prefixes identifier by program area: K_onstant, T_ype, G_lobal, L_ocal, P_arametre, F_unction, C_lass etc. This notation is presented in the Alsacian Notation paper.

As usual:

• please tell us at fcolibri@felix-colibri.com if you found some errors, mistakes, bugs, broken links or had some problem downloading the file. Resulting corrections will be helpful for other readers
  
• we welcome any comment, criticism, enhancement, other sources or reference suggestion. Just send an e-mail to fcolibri@felix-colibri.com.
  
• or more simply, enter your (anonymous or with your e-mail if you want an answer) comments below and clic the "send" button

  Name :
  E-mail :
  Comments * :

• and if you liked this article, talk about this site to your fellow developpers, add a link to your links page ou mention our articles in your blog or newsgroup posts when relevant. That's the way we operate: the more traffic and Google references we get, the more articles we will write.
  

4 - Conclusion

5 - Other Papers with Source and Links

6 - The author