Data compression methods generally operate by determining a model for the data, and then
transforming the data into codes based on the model. The model of the data represents the
probability of occurrence of certain symbols or strings of symbols in the data. More
probable sequences of symbols are represented by shorter codes. Less probable sequences
are represented by longer codes. This generally results in encoded data that takes less space
than the decoded data.
A common technique for encoding data based on probability of occurrence is Shannon-
Fano coding. This method was developed independently by Claude Shannon and R.M. Fano
at the Massachusetts Institute of Technology. Each character is given a unique code with a
different byte length. Shannon-Fano codes are easily arranged into a binary tree structure.
Traversing a Shannon-Fano tree to search for the symbol given its code is very fast.
A similar technique is Huffman coding which is slightly more efficient than Shannon-Fano
coding because it creates shorter codes for the most common elements. Since it requires
roughly the same amount of computation, Huffman coding is more commonly used.
Simple compression techniques use static models of sample data to represent all similar data.
If the actual data to be compressed is not similar to the model, this technique performs
poorly. More modern techniques use adaptive modeling, which allows the model of the data
to be updated as the document is compressed. As the document is decompressed, the model
controlling the decompression is also updated. The first commonly known adaptive
algorithm was developed in 1977 by Jacob Ziv and Abraham Lempel, and is known as LZ77.
A significant feature of LZ77 is that it uses an adaptive dictionary technique.
Dictionary techniques are often used in concert with statistical modeling techniques.
Dictionary techniques allow for brief replacements of commonly used phrases. This is
similar to techniques used for references in a technical document. For example, once an
author has referred to “See Knuth, D.E., The Art of Computer Programming, Volume 1.,
Fundamental Algorithms, Stanford, 1973,” it is possible to use simply “See Knuth” at later
points in the document.
Dictionary techniques generally fall into two categories: static and adaptive. A static
dictionary technique creates the dictionary and then uses it for the complete compression
process. An example of a static dictionary might be a list of common phrases. As a phrase is
matched in the uncompressed text, a code is stored to represent the phrase.
An adaptive dictionary is modified as compression occurs. This allows the dictionary to be
built as processing occurs, and also improves the compression technique because the
dictionary is built using the data under consideration. A simple method of creating an
adaptive dictionary is to use a window of previously occurring text as the dictionary. As
processing continues, the window slides forward to look at recent data. This is known as a
sliding dictionary technique.
In 1978 Lempel and Ziv published “Compression of Individual Sequences via Variable-Rate
Coding” in IEEE Transactions on Information Theory. The technique, known as LZ78, does
not use a sliding window technique, but rather maintains a dictionary of previously seen
phrases. The uncompressed data is converted to a series of tokens. The tokens have two
components: a phrase location and the character that follows the phrase. The phrase
dictionary is initialized with only a null string. When a phrase in the uncompressed stream
is not found in the dictionary, it is added, one character at a time, to the dictionary.
Theoretically, the dictionary can grow in an unlimited fashion. As the dictionary size
increases, the code size must increase.
In 1984, Terry Welch published a variant of LZ78 that is known as LZW (Lempel-Ziv-
Welch). It improves on LZ78 by initializing the dictionary with all single symbol phrases
possible in the alphabet. Another common improvement to LZ78 is to monitor the
performance of the compression, and thus determine if the dictionary is poorly matched to
the input. If so, it may be advantageous to clear the dictionary and rebuild it with the new
input.

link download

http://www.ziddu.com/download/19019632/tpabbrevia_3_04.zip.html

The components in Abbrevia implement PKZIP-compatible, TAR, GZip, and (on Windows)
Microsoft CAB file format data compression and archiving.
PKZIP (the originator of .ZIP files) is a widely used tool for data compression and file
archival, developed by Phil Katz of PKWare, Inc. PKZIP is distributed via shareware and
commercial channels. The PKZIP file formats and algorithms are published by PKWare.
TAR and GZip are well known tools on the Linux platform for creating compressed
collections of files. TAR (an acronym for Tape ARchive) is a method for concatenating a
number of files into a single large file.  It was originally used for backing up files to tape
storage, hence the name.
GZip is a format for compressing data using a method similar to that of PKZIP.  Unlike Zip,
however, the GZip format does not handle enclosing multiple files well, so the nearly
universal practice is use TAR to make a collection of the set of files and then GZip the
resulting “TARBall” to compress it.
Abbrevia provides routines and components that can handle TAR Archives, GZips
containing a single file, and the common combination of a GZipped TAR.
Abbrevia includes classes for creating compound files that essentially encapsulate an entire
file system within a single disk file. Abbrevia’s compound file is roughly equivalent to
Microsoft’s Structured Storage model, but without COM interfaces. Files within a
compound file are automatically compressed when they are added and decompressed when
extracted.
The Abbrevia cabinet components implement CAB file format data compression and
archiving via the Microsoft CABINET.DLL. The Microsoft CABINET.DLL is a system DLL
that is installed with 32-bit versions of Microsoft Windows. Cab files can be created using
MSZip or LZX compression, or simply stored.
Abbrevia provides automatic disk spanning compatible with that performed by PKZIP.
When an archive fills a removable disk or reaches a configurable threshold size, Abbrevia
automatically prompts for another disk. Abbrevia can also extract files from spanned disk
archives. (Note: On Linux this functionality is subject to proper floppy drive mount and
unmount permissions, and the floppy file system should be mounted as a DOS Compatible
FAT format of some type.)
Abbrevia also provides automatic file spanning to files of a specified size. When an archive
reaches a configurable threshold size, Abbrevia automatically prompts for a new file name
(or can generate a default). Abbrevia can also extract files from Abbrevia created spanned
file sets (this function is special to Abbrevia and is not part of the formal ZIP file
specification, so other ZIP handling programs will likely not recognize such spanned file
sets).
Abbrevia supports creation of self-extracting Zip archives. A self-extracting archive is an
executable file that, when executed, can extract files contained within itself. Abbrevia can
read and manipulate existing self-extracting archives or create new ones. The programmer
can create custom self-extracting “stub” programs for this purpose.
Abbrevia provides both non-visual and visual components with full source code.

Command Possible responses
AT+CGMI
Note: Get manufacturer identification
WAVECOM MODEM
OK
Note: Command valid, Wavecom modem

•   If the SIM detect pin indicates “absent”, the response to AT+CPIN? is “+CME ERROR 10” (SIM not inserted).

•   If the SIM detect pin indicates “present”, and the inserted Card is a SIM Card, the response to AT+CPIN? is “+CPIN: xxx” depending on SIM PIN state.
•   If the SIM detect pin indicates “present”, and the inserted Card is not a SIM Card, the response to AT+CPIN? is CME ERROR 10.
•   These last two states are not given immediately due to background initialization. Between the hardware SIM detect pin indicating “present” and the previous results the AT+CPIN? sends “+CME ERROR: 515” (Please wait, init in progress).

When the SIM detect pin indicates card absence, and if a SIM Card was previously inserted, an
IMSI detach procedure is performed, all user data is removed from the product (Phonebooks,
SMS etc.). The product then switches to emergency mode.

Background initialization
After entering the PIN (Personal Identification Number), some SIM user data files are loaded into
the product (Phonebooks, SMS status, etc.). Please be aware that it might take some time to
read a large phonebook.
The AT+CPIN? command response comes just after the PIN is checked. After this response
user data is loaded (in background). This means that some data may not be available just after
PIN entry is confirmed by ’OK’. The reading of phonebooks will then be refused by “+CME
ERROR: 515” or “+CMS ERROR: 515” meaning, “Please wait, service is not available, init in
progress”.
This type of answer may be sent by the product at several points:

•   when trying to execute another AT command before the previous one is completed (before response),
•   when switching from ADN to FDN (or FDN to ADN) and trying to read the relevant phonebook immediately,
•  when asking for +CPIN? status immediately after SIM insertion and before the product has determined if the inserted card is a valid SIM Card.

• If command syntax is incorrect, an ERROR string is returned.
• If command syntax is correct but with some incorrect parameters, the +CME ERROR:

<Err> or +CMS ERROR: <SmsErr> strings are returned with different error codes.

•  If the command line has been performed successfully, an OK string is returned.

In some cases, such as “AT+CPIN?” or (unsolicited) incoming events, the product does not
return the OK string as a response.
In the following examples <CR> and <CR><LF> are intentionally omitted.

syntax: function AnimateWindow(hWnd: HWND; dwTime: DWORD; dwFlags: DWORD): BOOL; stdcall;

3 parameters:

• hWnd is windows handle
• dwTime is how long the process is running
• dwFlags is model of animate

Ok next …

let’s get started..

• Create new apllication
• add two button like in picture in form1
• change the caption show and hide
• add form2
• add label1 to form2 and change the caption like the picture
• write code in button click on each button like this

procedure TForm1.Button1Click(Sender: TObject);
begin
 AnimateWindow(form2.handle, 2000, AW_CENTER Or AW_ACTIVATE);
end;

procedure TForm1.Button2Click(Sender: TObject);
begin
  AnimateWindow(form2.handle, 2000, AW_CENTER Or AW_HIDE);
end;

Source

unit Unit1;

interface

uses
  Windows, Messages, SysUtils, Variants,
  Classes, Graphics, Controls, Forms,
  Dialogs, StdCtrls;

type
  TForm1 = class(TForm)
    Button1: TButton;
    Button2: TButton;
    procedure Button1Click(Sender: TObject);
    procedure Button2Click(Sender: TObject);
  private
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form1: TForm1;

implementation

uses Unit2;

{$R *.dfm}

procedure TForm1.Button1Click(Sender: TObject);
begin
 AnimateWindow(form2.handle, 2000, AW_CENTER Or AW_ACTIVATE);
end;

procedure TForm1.Button2Click(Sender: TObject);
begin
  AnimateWindow(form2.handle, 2000, AW_CENTER Or AW_HIDE);
end;

end.

unit Unit2;

interface

uses
  Windows, Messages, SysUtils, Variants,
  Classes, Graphics, Controls, Forms,
  Dialogs, StdCtrls;

type
  TForm2 = class(TForm)
    Label1: TLabel;
  private
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form2: TForm2;

implementation

{$R *.dfm}

end.

source DFM

object Form1: TForm1
  Left = 172
  Top = 174
  Width = 195
  Height = 251
  Caption = 'Form1'
  Color = clBtnFace
  Font.Charset = DEFAULT_CHARSET
  Font.Color = clWindowText
  Font.Height = -11
  Font.Name = 'MS Sans Serif'
  Font.Style = []
  OldCreateOrder = False
  PixelsPerInch = 96
  TextHeight = 13
  object Button1: TButton
    Left = 40
    Top = 32
    Width = 75
    Height = 25
    Caption = 'Show'
    TabOrder = 0
    OnClick = Button1Click
  end
  object Button2: TButton
    Left = 40
    Top = 72
    Width = 75
    Height = 25
    Caption = 'Hide'
    TabOrder = 1
    OnClick = Button2Click
  end
end

object Form2: TForm2
  Left = 380
  Top = 174
  Width = 359
  Height = 250
  Caption = 'Form2'
  Color = clBtnFace
  Font.Charset = DEFAULT_CHARSET
  Font.Color = clWindowText
  Font.Height = -11
  Font.Name = 'MS Sans Serif'
  Font.Style = []
  OldCreateOrder = False
  PixelsPerInch = 96
  TextHeight = 13
  object Label1: TLabel
    Left = 16
    Top = 64
    Width = 309
    Height = 37
    Caption = 'ANIMATE WINDOW'
    Font.Charset = DEFAULT_CHARSET
    Font.Color = clRed
    Font.Height = -32
    Font.Name = 'MS Sans Serif'
    Font.Style = [fsBold]
    ParentFont = False
  end
end

Link Download source

http://www.ziddu.com/download/18582686/animasiwindow.rar.html

OK.. next we go to the source

this step by step

• create new project application
• add two labels components
• add two edit components
• add tbutton and change the caption with Login
• add Twebbrowser from Internet Pallet
• on button click write this codes

procedure TForm1.Button1Click(Sender: TObject);
begin
  WebBrowser1.Navigate('https://login.yahoo.com/config/login_verify2?&.src=ym');
  while WebBrowser1.ReadyState <> READYSTATE_COMPLETE do application.processmessages;
  WebBrowser1.OleObject.document.forms.item(0).elements.item('login').value:=edit1.Text;
  WebBrowser1.OleObject.document.forms.item(0).elements.item('passwd').value:=edit2.Text;
  webbrowser1.OleObject.document.forms.item('login_form').submit;
end;

source code

 
unit Unit1;

interface

uses
  Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
  Dialogs, StdCtrls, OleCtrls, SHDocVw;

type
  TForm1 = class(TForm)
    WebBrowser1: TWebBrowser;
    Edit1: TEdit;
    Edit2: TEdit;
    Button1: TButton;
    Label1: TLabel;
    Label2: TLabel;
    procedure Button1Click(Sender: TObject);
  private
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form1: TForm1;

implementation

{$R *.dfm}

procedure TForm1.Button1Click(Sender: TObject);
begin
  WebBrowser1.Navigate('https://login.yahoo.com/config/login_verify2?&.src=ym');
  while WebBrowser1.ReadyState <> READYSTATE_COMPLETE do application.processmessages;
  WebBrowser1.OleObject.document.forms.item(0).elements.item('login').value:=edit1.Text;
  WebBrowser1.OleObject.document.forms.item(0).elements.item('passwd').value:=edit2.Text;
  webbrowser1.OleObject.document.forms.item('login_form').submit;
end;

end.

source dfm

object Form1: TForm1
  Left = 192
  Top = 124
  Width = 702
  Height = 514
  Caption = 'Yahoo Mail & Delphi'
  Color = clBtnFace
  Font.Charset = DEFAULT_CHARSET
  Font.Color = clWindowText
  Font.Height = -11
  Font.Name = 'MS Sans Serif'
  Font.Style = []
  OldCreateOrder = False
  PixelsPerInch = 96
  TextHeight = 13
  object Label1: TLabel
    Left = 24
    Top = 32
    Width = 45
    Height = 13
    Caption = 'Yahoo ID'
  end
  object Label2: TLabel
    Left = 24
    Top = 64
    Width = 46
    Height = 13
    Caption = 'Password'
  end
  object WebBrowser1: TWebBrowser
    Left = 0
    Top = 144
    Width = 686
    Height = 332
    Align = alBottom
    TabOrder = 0
    ControlData = {
      4C000000E6460000502200000000000000000000000000000000000000000000
      000000004C000000000000000000000001000000E0D057007335CF11AE690800
      2B2E126208000000000000004C0000000114020000000000C000000000000046
      8000000000000000000000000000000000000000000000000000000000000000
      00000000000000000100000000000000000000000000000000000000}
  end
  object Edit1: TEdit
    Left = 80
    Top = 32
    Width = 121
    Height = 21
    TabOrder = 1
  end
  object Edit2: TEdit
    Left = 80
    Top = 64
    Width = 121
    Height = 21
    PasswordChar = '*'
    TabOrder = 2
  end
  object Button1: TButton
    Left = 80
    Top = 96
    Width = 75
    Height = 25
    Caption = 'Login'
    TabOrder = 3
    OnClick = Button1Click
  end
end

link download source

http://www.ziddu.com/download/18579550/yahoomail.rar.html

for example like this picture :

next…on

for the first time copy dialogs unit to our project/folder program

next..

• open dialogs unit
• to change font message we must change font of label message like this
• search function CreateMessageDialog
• at TMessageForm(Result).Message := TLabel.Create(Result); 
•  change font color by add code Font.Color:=clred;
• this example for delphi 7
  

function CreateMessageDialog(const Msg: string;
  DlgType: TMsgDlgType;
  Buttons: TMsgDlgButtons): TForm;
const
....
....
...
    TMessageForm(Result).Message := TLabel.Create(Result);
    with TMessageForm(Result).Message do
    begin
      Name := 'Message';
      Parent := Result;
      WordWrap := True;
      Caption := Msg;
      Font.Color:=clred;
      BoundsRect := TextRect;
      BiDiMode := Result.BiDiMode;
      ALeft := IconTextWidth - TextRect.Right + HorzMargin;
      if UseRightToLeftAlignment then
        ALeft := Result.ClientWidth - ALeft - Width;
      SetBounds(ALeft, VertMargin,
        TextRect.Right, TextRect.Bottom);
    end;

Next… on

How to change font button..?

• Import sql text by shellexecute to call mysql.exe or call batch file
• Using Tzconnection
• Using ZSQLProcessor
• Using TZQuery
• or may be using ado component witch connected with ODBC

In this section I will give example how to create MySQL database using Tzconnection

Next… on

The first time create new application and save all (project and unit). and then

• add Tzconnection
• add button
• onbutton clik write codes :

1. make connection to mysql
2. if success then create database
3. create table

procedure TForm1.Button1Click(Sender: TObject);
var sdatabase,A,B,Csql:string;
begin
  sdatabase:='CREATE DATABASE IF NOT EXISTS SCHOOl';
  A:='USE SCHOOL;';
  B:='DROP TABLE IF EXISTS TSISWA;';
  Csql:='CREATE TABLE TSISWA ( ' +
   ' NIS varchar(9) default NULL,' +
   ' NAMA varchar(9) default NULL,' +
   ' ALAMAT varchar(9) default NULL'+
   ' )ENGINE=MyISAM DEFAULT CHARSET=latin1; ';
 ZConnection1.Disconnect;
 ZConnection1.HostName:='localhost';
 ZConnection1.User:='root';
 ZConnection1.Protocol:='mysql';
 ZConnection1.Port:=3306;
 ZConnection1.Password:='';
// connect
  try
  ZConnection1.Connect;
  except
    on E: Exception do showmessage(E.Message);
  end;
  //create database
    Try
    ZConnection1.ExecuteDirect(sdatabase);
    showmessage('success');
    except
     on E: Exception do showmessage(E.Message);
    end;
   //create table

    Try
    ZConnection1.ExecuteDirect(A);
    ZConnection1.ExecuteDirect(B);
    ZConnection1.ExecuteDirect(Csql);
    showmessage('success create table..!');
    except
      on E: Exception do showmessage(E.Message);
    end;

end;

source

unit Unit1;

interface

uses
  Windows, Messages, SysUtils, Variants, Classes,
  Graphics, Controls, Forms,
  Dialogs, StdCtrls, ZConnection;

type
  TForm1 = class(TForm)
    Button1: TButton;
    ZConnection1: TZConnection;
    procedure Button1Click(Sender: TObject);
  private
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form1: TForm1;

implementation

{$R *.dfm}

procedure TForm1.Button1Click(Sender: TObject);
var sdatabase,A,B,Csql:string;
begin
  sdatabase:='CREATE DATABASE IF NOT EXISTS SCHOOl';
  A:='USE SCHOOL;';
  B:='DROP TABLE IF EXISTS TSISWA;';
  Csql:='CREATE TABLE TSISWA ( ' +
   ' NIS varchar(9) default NULL,' +
   ' NAMA varchar(9) default NULL,' +
   ' ALAMAT varchar(9) default NULL'+
   ' )ENGINE=MyISAM DEFAULT CHARSET=latin1; ';
 ZConnection1.Disconnect;
 ZConnection1.HostName:='localhost';
 ZConnection1.User:='root';
 ZConnection1.Protocol:='mysql';
 ZConnection1.Port:=3306;
 ZConnection1.Password:='';
// connect
  try
  ZConnection1.Connect;
  except
    on E: Exception do showmessage(E.Message);
  end;
  //create database
    Try
    ZConnection1.ExecuteDirect(sdatabase);
    showmessage('success');
    except
     on E: Exception do showmessage(E.Message);
    end;
   //create table

    Try
    ZConnection1.ExecuteDirect(A);
    ZConnection1.ExecuteDirect(B);
    ZConnection1.ExecuteDirect(Csql);
    showmessage('success create table..!');
    except
      on E: Exception do showmessage(E.Message);
    end;

end;

end.

form

object Form1: TForm1
  Left = 192
  Top = 124
  Width = 427
  Height = 286
  Caption = 'Form1'
  Color = clBtnFace
  Font.Charset = DEFAULT_CHARSET
  Font.Color = clWindowText
  Font.Height = -11
  Font.Name = 'MS Sans Serif'
  Font.Style = []
  OldCreateOrder = False
  PixelsPerInch = 96
  TextHeight = 13
  object Button1: TButton
    Left = 168
    Top = 120
    Width = 75
    Height = 25
    Caption = 'Button1'
    TabOrder = 0
    OnClick = Button1Click
  end
  object ZConnection1: TZConnection
    Left = 128
    Top = 80
  end
end

• create new application
• save all to c:\myproject\
• put libmysql.dll to c:\myproject\
• put tzconnection from zeos pallet to form
• add button
• change button1 caption : connect
• on button1 click write this code

procedure TForm1.Button1Click(Sender: TObject);
begin
   // configuration pre connect
    ZConnection1.Disconnect;
    ZConnection1.HostName:='localhost';
    ZConnection1.Protocol:='mysql';
    ZConnection1.User:='root';
    ZConnection1.Password:='';
    ZConnection1.Port:=3306;
    ZConnection1.LoginPrompt:=false;

    // try connect to localhost
    try
     ZConnection1.Connect;
     showmessage('connecting success..!')
    except
     showmessage('connecting fail..!')
    end;
end;

source code unit

unit Unit1;

interface

uses
  Windows, Messages, SysUtils, Variants, Classes,
  Graphics, Controls, Forms,
  Dialogs, StdCtrls, ZConnection;

type
  TForm1 = class(TForm)
    ZConnection1: TZConnection;
    Button1: TButton;
    procedure Button1Click(Sender: TObject);
  private
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form1: TForm1;

implementation

{$R *.dfm}

procedure TForm1.Button1Click(Sender: TObject);
begin
   // configuration pre connect
    ZConnection1.Disconnect;
    ZConnection1.HostName:='localhost';
    ZConnection1.Protocol:='mysql';
    ZConnection1.User:='root';
    ZConnection1.Password:='';
    ZConnection1.Port:=3306;
    ZConnection1.LoginPrompt:=false;

    // try connect to localhost
    try
     ZConnection1.Connect;
     showmessage('connecting success..!')
    except
     showmessage('connecting fail..!')
    end;
end;

end.

form  code

object Form1: TForm1
  Left = 192
  Top = 124
  Width = 870
  Height = 500
  Caption = 'Form1'
  Color = clBtnFace
  Font.Charset = DEFAULT_CHARSET
  Font.Color = clWindowText
  Font.Height = -11
  Font.Name = 'MS Sans Serif'
  Font.Style = []
  OldCreateOrder = False
  PixelsPerInch = 96
  TextHeight = 13
  object Button1: TButton
    Left = 208
    Top = 96
    Width = 75
    Height = 25
    Caption = 'Connect'
    TabOrder = 0
    OnClick = Button1Click
  end
  object ZConnection1: TZConnection
    Left = 96
    Top = 88
  end
end