Delphi ha sido tradicionalmente una herramienta excepional para trabajo con bases de datos, su propio nombre fué elejido como la herramienta para trabajar con Oracle (The Oracle at Delphi), de esto yá hace muchísmos años.

A lo largo del tiempo la forma en que Delphi trabaja con Bases de Datos ha ido variando.  La tecnología que Delphi promueve actualmente para su uso en desarrollo es DBX (dbExpress). Sin embargo no es la única ya que también soporta componentes de conexión nativos (conexiones directas a la BD o usando el protocolo nativo de la BD), ODBC y ADO.

Desde la época de Borland, Delphi viene con Interbase siendo esta la BD por default.  Interbase tiene en Firebird a su vástago OpenSpurce. Interbase/Firebird es una BD madura de nivel comercial que lleva varios años de delantera sobre muchas BD usadas en la actualidad (incluídos mySql, Postgres).

Delphi puede usarse con una amplia variedad de Bases de Datos comerciales y libres que se usan en la actualidad por ejemplo:

• Interbase/Firebird:  IBX (incluído), IBObjects, ZeosLib, dbExpress (incluído)
• MS SQL Server: dbExpress, dbGo (ADO),  SDAC, ZeosLib
• Access: dbGo (ADO)
• Oracle: dbExpress, ODAC, ZeosLib
• MySql: dbExpress,  MyDAC, ZeosLib, DAC for MySQL, ZeosLib
• Postgres: dbExpress, PgDAC, PostgresDAC, ZeosLib
• Sybase: dbExpress, from Sybase, ZeosLib
• DB2: dbExpress

Además existen motores de bases de datos embebidos (incrustados) que pueden usarse con Delphi. Esotos motores pueden usarse para replicación local en aplicaciones Cliente/Servidor, para almacenamiento temporal, o cuando se requiera aplicaciones autocontenidas sin dependencias externas. Entre los más conocidos tenemos:

• SQLLite , usando la dll propia de SQLLite, existe tambien ports completos a Delphi
• NexusDB, compila directamente en el EXE.
• elevatedb,  compila directamente en el EXE.
• Absolute Database, compila directamente en el EXE.
• Firebird, usando una dll.
• Accuracer Database,  compila directamente en el EXE.

Otra forma de manejar datos es usando tablas en memoria (Memory tables), muy útil para datos temporales:

• ClientDataset de Delphi puede usarse para este fin.
• VirtualTable
• SQLMemTable
• NexusDB, incluye un componente para tablas en memoria, que se puede usar en conjunto con la BD normal.
• kbmmemtable

Como se ve Delphi posee un arsenal muy completo para atacar el desarrollo de aplicaciones de Base de Datos, tal es así que algunas herrmientas para BD están desarrollados en Delphi, por ejemplo:

• TOAD (para MS SQLServer, Oracle, MySQL, DB2),
• MySQL Administrator,
• PL/SQL Developer,
• EMS SQL Manager

1. Adicione ao form 2 TSpeedButton (Palette additional). Na propriedade caption do primeiro speedbutton escreva ‘Minha lista de reprodução’ e no segundo speedbutton ‘Salvar lista de reprodução’.

2. Adicione mais uma coluna no ListView1 e  trabalhe o listview como segue:

3. No primeito item (TListColumn), altere a propriedade width para 20. Em ‘Tempo’ width=50 e em ‘Músicas’ width=550.

4. Chame o código do botão adicionar música  a lista de reprodução (btadicionar) e faça a seguinte alteração:

Declare em var a variável nome:string;

begin
for x := 0 to FileListBox1.Items.Count-1 do
if FileListBox1.Selected[x] then
begin
arquivo:= DirectoryListBox1.Directory+’\'+FileListBox1.Items.Strings[x];
nome:= FileListBox1.Items.Strings[x];
ListView1.AddItem(arquivo,ListView1);
ListView1.Items.Item[ListView1.Items.Count-1].SubItems.Add(TMusicas(arquivo));
ListView1.Items.Item[ListView1.Items.Count-1].SubItems.Add(nome);
ListView1.Items.Item[ListView1.Items.Count-1].Checked := true;
end;

5. Selecione o speedbutton ‘Salvar lista de reprodução’ e no evento OnClick adicione o seguinte código:

procedure TFmediaplayer.SpeedButton2Click(Sender: TObject);
var//declare as variáveis
I,J : Integer;
Lista : TStringList;
begin
Lista:= TStringList.Create;
try
for I := 0 to ListView1.Items.Count-1 do
begin
//salvando a lista
Lista.Add(ListView1.Items[I].Caption);
// salvando os subitens
for J:= 0 to ListView1.Items[I].SubItems.Count-1 do
Lista.Add(#9+ListView1.Items[I].SubItems[J]);
end;
Lista.SaveToFile (ExtractFilePath(Application.ExeName)+ ‘lista de reproducao.txt’);
finally
Lista.Free;
end;
end;

Neste código salvamos os itens do Listview em um arquivo txt na pasta do programa,ou seja, do projeto.

6. Selecione o speedbutton ‘Minha lista de reprodução’ e no evento OnClick, adicone o código abaixo:

procedure TFmediaplayer.SpeedButton1Click(Sender: TObject);
var
Lista : TStringList;
NewItem : TListItem;
I : integer;
begin
NewItem := nil;
// chamar os items
Listview1.Items.Clear;
Lista:= TStringList.Create;
try
Lista.LoadFromFile(ExtractFilePath(Application.ExeName)+ ‘lista de reproducao.txt’);
for I := 0 to Lista.Count – 1 do
if lista[I][1]=#9then
NewItem.SubItems.Add(Trim(Lista[I]))
else
begin
// novo item
Newitem:= Listview1.Items.Add;
NewItem.Caption := Lista[I];
end;
finally
Lista.Free;
end;
end;

No código acima, chamamos os itens salvos no arquivo txt.

Importante: Crie com o bloco de notas um arquivo txt com o nome  ‘lista de reproducao’ e salve-o na pasta do projeto em estudo.

7. Se  desejar,  que ao abrir o programa o listview mostre  a lista de reprodução salva, selecione o form e adicone o código acima (SpeedButton1) no evento OnShow do form.

Imagem do programa em execução:

By 667 BC, a Greek ruler by name of Byzas, from Megara, established his kingdom here, on the advice of an oracle of Delphi, and named it Byzantium. But it was besieged by the Romans in AD 196, and became part of the Roman Empire. The ravaged city was rebuilt by the Roman Emperor, Septimus Severus, and temporarily given the name of ‘Augusta Antonina’. But in 306 AD, Emperor Constantine the Great made Byzantium the capital of the entire Roman Empire, and from then on, the city was called Constantinople. The Byzantium Empire was more or less influenced by Greek culture, and was also a hub of Greek Orthodox Christianity, which resulted in the construction of several magnificent Christian architectural wonders, the prominent among them being the Hagia Sophia, which remained the world’s largest cathedral till 1850.

The Roman Empire passed through much turmoil due to attack from various sources, especially the Barbarians, not to mention their internal problems, and finally, in 532 AD, during the reign of Justinian I, the city was totally destroyed due to anti government riots. Though much favored for its ideal location, that made trade and transport between continents an easy affair, this very factor also proved to be the doom of Constantinople. For several hundred years hence, it had to face a lot of assault from the Arabs, Nomadic, Persians, as well as the Fourth crusaders, who periodically occupied it.

At last, in 1453, Constantinople was attacked and conquered by the courageous Ottoman Turks led by Sultan Mehmet II, who renamed it Istanbul. It continued to function not just as an important cultural, political and commercial hub, but also as their main centre for military operations too, till World War I, after which it was occupied by the Allies.

Sultan Mehmet II was supposed to have given the city a cosmopolitan social outlook. After deporting the remaining Byzantine population, a great many changes were made to the existing architecture in general. The old world Christian city was gradually transformed into a Muslim conurbation as the Emperor started rebuilding all churches so as to convert them to mosques. The great mosque and the Fatih College were built on the old burial grounds of the erstwhile Byzantine Emperors at the Church of the Holy Apostles. The Hagia Sophia too was converted to a mosque. But to his credit, the Sultan held a cosmopolitan outlook and for the greater part, allowed people of all faiths to settle in the vast city, and made effective use of their varied skills. Tolerance was a great virtue that was practiced by Sultan Mehmet II, and it was reflected all over the empire.Istanbul acquired a status of great importance in the eyes of all Muslims, after the conquest of Egypt, and its glory increased from leaps and bounds in the hands of its various rulers, many of whom were great patrons of art and architecture.

Although the capital of Turkey was changed from Istanbul to Ankara by Kemal Ataturk, in 1923, Istanbul still retained its attractions and continued to expand majestically. But gradually, due to the mass exodus of the various nationalities, especially after the war between Greece and Turkey, it became a prominent Muslim nation.

The many historic monuments of yesteryears, that are to be found there, like the various museums, castles, palaces, mosques, churches, etc contribute greatly to the increase in the tourism industry today. In fact, many of its historic architectures have been added to the UNESCO’s list of world heritage sites. Though no more a capital city, Istanbul, which is considered to be Turkey’s cultural and financial center, still retains its old world attraction and continues to generate its own individual history through out the ages.

sumber: http://www.hagia-sophia.net/history.htm

http://id.wikipedia.org/wiki/Hagia_Sophia

Anonimous methods (aka Closures) are rare visitors in Delphi code. I have upgraded to Delphi 2009 a year before and never used the anonimous methods. But last week it finally happened.
I was writing the unit tests for fast fourier transform code. The idea of some tests was to compare the results of fast fourier trasform and discrete fourier transform of arbitrary function, and it appeared that the anonimous method is the best way to pass the function to the test.

type
  TRealFunc = reference to function(N: Integer): Extended;

type
  TTestFFT = class(TTestCase)
  private
    procedure TestRealFunc(Func: TRealFunc; Count: Integer);
  published
    procedure TestRealFFT00;
    ...
  end;

All checks are done within TestRealFunc procedure. It receives a function to transform as an argument, makes fourier transform of the function using two different methods and compares the results:

procedure TTestFFT.TestRealFunc(Func: TRealFunc; Count: Integer);
var
  FFTData: array of Extended;
  DFTData: array of TksComplex;
  M, N: Integer;
  Arg: TksComplex;

begin
  SetLength(FFTData, Count);
  SetLength(DFTData, Count);
  for M:= 0 to Count - 1 do begin
    FFTData[M]:= Func(M);

// discrete Fourier transform;
    DFTData[M]:= 0;
    for N:= 0 to Count - 1 do begin
      Arg.Re:= 0;
      Arg.Im:= (2 * Pi * N * M) / Count;
      DFTData[M]:= DFTData[M] + Func(N) * TksComplex.Exp(Arg);
    end;
  end;

// fast Fourier transform
  RealFFT(@FFTData[0], Count, False);

  CheckEquals(FFTData[0], DFTData[0].Re, 1E-15);
  CheckEquals(FFTData[1], DFTData[Count shr 1 - 1].Re, 1E-15);
  CheckEquals(0, DFTData[0].Im, 1E-15);
  CheckEquals(0, DFTData[Count shr 1 - 1].Im, 1E-15);
  for N:= 1 to Count shr 1 - 1 do begin
    CheckEquals(FFTData[2 * N], DFTData[N].Re, 1E-15);
    CheckEquals(FFTData[2 * N + 1], DFTData[N].Im, 1E-15);
    CheckEquals(FFTData[2 * N], DFTData[Count - N].Re, 1E-15);
    CheckEquals(FFTData[2 * N + 1], - DFTData[Count - N].Im, 1E-15);
  end;
end;

The test procedures themselves just calls the TestRealFunc with different arguments. For example,

procedure TTestFFT.TestRealFFT00;
begin
  TestRealFunc(
    function(N: Integer): Extended
    begin
      Result:= Sin(pi / 4 * N) + 0.5 * Sin(pi / 2 * N + 3 * pi / 4);
    end,
    8
  );
end;

Though the syntax looks cumbersome, the solution based on anonimous methods is very logical.

Erica and I have a tradition of visiting small towns in Indiana. During my two years there, we went on outings to communities like Crawfordsville, Kokomo, Frankfort, and even Otterbein. So when Erica asked me what I wanted to do on my visit, I answered without hesitation that I really wanted to visit a random small town. We decided on Logansport. Delphi was just a bonus.

On the way into town, Erica told me about how the community had raised money to create a replica of an old canal boat, and then it was burned down by an old man. We had heard that another one was built, so we tried to find it. The closes we got, though, was this playground.

Looks like they are building some sort of interpretive center in the park though. Maybe on future visits to Delphi (it might happen), I can check it out.

Meanwhile, there are lots of other sites to check out in Delphi… like old buildings!

And some newer buildings:

And some old buildings attempting to look newer:

Or just this awesome Chinese restaurant.

With very bright bricks!

There is, of course, the town War Memorial, but this one looks more threatening than most.

What with the pointy guns on each corner and all.

But the best place to visit in Delphi? The Stone House Bakery.

It’s the kind of place where you can sit at the counter and enjoy some baked goods in peace.

Or meet up with an old girlfriend (or possibly your mom) and enjoy a slice of pie.

Or where the display of cookies looks so tempting that you say, “I’ll take one of each!”

Apparently they are re-routing the major highway so it won’t go through Delphi anymore, but the cookies are worth the extra miles.

Aún no he usado mucho Delphi 2010 pero se ve bastante bueno y más sólido que las últimas versiones , bueno teniedo en cuenta que la versión que uso en el día a día es el venerable Delphi 7!!!!

Cosas interesantes (con respecto a Delphi 7, muchas de estas cosas ya habian creo que desde la 2005) son por ejemplo:

• Agrupamiento de las unidades según el directorio donde se encuentran.  Fundamental para nosotros ya que manejamos diversos directorios.
• La disstribución de las ventanas es algo a lo me tendré que acostumbrar, por que preferia las ventans flotantes de Delphi 7.
• Hay una opción de debug para crear tus propios visores de variables, esto esta SUPER!!! y lo vamos a usar bastante.
• La parte de modelamiento parece que ya está más pulida.
• IDE Insigth, es un buscador dentro del IDE que encuentra de todo!!!, se ve prometedor.
• El parser de XML que usabamos (OpenXML) viene incluído, más adelante haré un post sobre este tema.
• El OTA es ahora mucho más abierto, ya sueño con mis propios diseñadores, visualizadores y herramientas para aligerarnos el trabajo.
• El RTTI ha sido extendido, ahora no sólo se pueden ver las propiedades published, si no prácticamente todo, mmm podemos usarlo.
• Ahora que Embarcadero soporta Firebird, puedo ver mistablas desde la IDE.
• Soporte para Generics y Argumentos, Closures y otras cosas que todavia tengo que ver como sacarles provecho ya que requieren un cambio en la concepcion mental de las cosas.
• El Help está mejor que en versiones previas en las que no había nada!

Finalmente una imágen vale más que mil palabras….

Jaja no escribo nada desde el 2008, y claro y es que nadie me lee jiji.

Bueno para que quede registrado mi último post fue en espera al Delphi 2009 (a.k.a. Tiburón). Finalmente ya salió el Delphi 2010.

Ahora estoy haciendo pruebas de migración a Delphi 2010 y mis pesadillas con esta nueva versión ppor el soporte de Unicode, poco a poco se han ido desvaneciendo.

Sin embargo aún no esta todo dicho, y sin embargo so far so good.

Mi principal pesadilla era la migración de los componentes que usamos, la mayoria tiene versión para 2010, y los otros han compilado casi sin despeinarse. Despues de haber leido tantos blogs con historias de terror sobre la materia, parece que no hay mucho.

La verdad de la milanesa aún esta por descubrirse, por que el que compile no es seguridad de que corra…., pero primero que compile por lo menos.

Para el manejo del protocolo y nuestro framework de persistencia de objetos, creo que la cosa está peluda, ya que usamos mucho char y arimética de punteros. Tenemos que analizar como vamos a manejar nuestra premisa de usar el mínimo espacio posible en el protocolo, ahi vislumbro problemas en el horizonte.

You can read a nice review of Delphi 2010 in TechRepublic.

Summary

If you want to do Windows development, and you want to work with native code in a native style, I think that Delphi 2010 is a very productive tool. It combines a lot that really saves time (such as DataSnap and IDE Insight) with the power and flexibility of native code. If you need support for certain functionality (especially touch-related items), it is the only shipping product on the market that does these things.

Every time I work with the Embarcadero team, I feel like they are writing the tools that they would love to use; they really are “developers’ developers,” and they understand the development process very well and implement it as tools quite nicely.

If you don’t mind learning a new system, a new language, and a new way of doing things, Delphi 2010 is worth a long look for .NET and Visual C++ developers.

A exemplo do que postei anteriorment sobre colorir as linhas de um StringGrid, é possível definir a cor das linhas de um DBGrid, o que além de melhorar a estética do componente, também melhora sua ergonomia, já que a alternância das cores, facilita a leitura das inoformações linha a linha.
Pois bem, para colorir as linhas de um DBGrid, basta incluir no evento OnDrawColumnCell do DBGrid o seguinte código:

If Odd(TDBGrid(Sender).DataSource.DataSet.RecNo) then begin
   // Cor para linhas ímpares
   TDBGrid(Sender).Canvas.Brush.Color:= clWhite;
end
else begin
   // Cor para linhas pares
   TDBGrid(Sender).Canvas.Brush.Color:= $00EFEFEF;
end;

// Testa se o registro da linha atual está selecionado
If gdSelected in State Then Begin
   // Cor de fundo do registro selecionado
   TDBGrid(Sender).Canvas.Brush.Color:= clNavy;
   // Cor do texto para o registro selecionado
   TDBGrid(Sender).Canvas.Font.Color:= clYellow;
End
Else
   // Cor do texto para registros não selecionados
   TDBGrid(Sender).Canvas.Font.Color:= clBlack; 

   // Desenha o retângulo da célula
   TDBGrid(Sender).Canvas.FillRect(Rect);
   // Apresenta o texto da célula
   TDBGrid(Sender).Canvas.TextRect(Rect, Rect.Left + 2,
      Rect.Top, Column.Field.DisplayText);

Apollon (griechisch Ἀπόλλων, lateinisch Apollo, deutsch Apoll) war in der griechischen und römischen Mythologie der Gott des Lichts, der Heilung, des Frühlings, der sittlichen Reinheit und Mäßigung sowie der Weissagung und der Künste, insbesondere der Musik, der Dichtkunst und des Gesanges. Als Sohn des Zeus und der Göttin Leto gehörte er wie seine Zwillingsschwester Artemis zu den zwölf Hauptgöttern des griechischen Pantheons. Das Heiligtum in Delphi, die bedeutendste Orakelstätte der Antike, war ihm geweiht.

Das Foto habe ich im Sudermann-Park in Blankensee aufgenommen und habe leider nur die Information, das es sich um einen griechischen oder römischen Gott handeln soll. Da die Büste auf einem Buch ruht, hatte ich die Idee, das es sich vielleicht um Apollo/Apollon handeln könnte.

Delilah and the Space-Rigger by Robert A. Heinlein
Part of the The Green Hills of Earth anthology
Mass Market Paperback: 288 pages
Publisher: Baen Books; Reprint edition (February 1, 2000)
ISBN-13: 978-0671578534

It’s a well known fact that women are a serious and often dangerous distraction on high risk jobs, such as constructing a space station. At least, that’s the attitude held by Tiny Larsen, the crew chief in charge of building Space Station One. He works with an all-male crew, trying to get this monumental task accomplished while maintaining order among the men. That all seems to be in jeopardy when G. Brooks McNye is sent up to the station to replace a man who was fired.

Gloria Brooks McNye is the first and currently only woman on a space station crewed entirely by men. Larsen fears for her safety and the respectfulness of his men, as loudly and obnoxiously as he possibly can. He goes completely out of his way to try and keep her sequestered from the rest of the crew while he hustles to get a male replacement sent up.

This is a humorous story poking fun at the sheer ridiculousness of judging competence and character based on gender. McNye sets out to prove from the beginning that she can do anything boys can do, and in some cases, better. It’s up to her and rest of the crew to convince Larsen that women have as much right to help build this huge undertaking for as men do. It’s a funny story, and I recommend it and the rest of The Green Hills of Earth for any Heinlein lovers and any newbies alike.

*****************************************************************
The Girl Who Was Plugged In by James Tiptree, Jr.
Part of The Hugo Winners: Volume 3 anthology
Hardcover: 603 pages
Publisher: Doubleday (January 1, 1977)

P. Burke is a social pariah, deformed in body and in possession of not much mind. The near-future society in which she lives is utterly devoted to the worship of beautiful people. They are seen as gods, striding above the rest of the population on a wave of adoration. Every holocam is pointed in their direction. Burke cannot even hope to be noticed by such people and in the end, her existence becomes too much to bear. She tries to kill herself. And is miraculously offered the chance of a lifetime while recovering in the hospital.

Become a Remote for a new god. No one will ever know that P. Burke is really the brain running the beautiful doll body of lovely little Delphi, the newest splash on the celebrity scene. Burke sits five hundred feet below ground, hooked up to wires and controls and circuits, her own body nearly lifeless, and lives the life of Delphi. But why would she be offered such a chance? What’s the catch?

A set of stringent laws called the Huckster Laws have banned nearly all forms of advertising. The only way you are allowed to advertise is either on or in your product, or during an in-store demonstration. No more billboards, no more TV commercials, no more painted buses. And that just doesn’t work for the corporate men. So they’ve found a way around it. Create celebrities beloved by all, and have them showcase select products in their “everyday” lives. The millions of people who watch their broadcasts won’t fail to notice what brand of toothpaste or what kind of shoes their living gods are wearing.

P. Burke and her alter-ego, Delphi, will be a living advertisement. But when Burke/Delphi falls in love and grows a conscience about breaking the ad laws, her life is irreparably changed.

Tiptree’s deft hand in this story is wonderful to read. The narrative style is great, and the descriptions of corporate life, evil machinations, and the desire to simply be loved for who and what you are, are absolutely captivating. This is a fantastic peek at where are own world could be headed, with our reality TV shows and the incessant consumer culture we live in. Read this story, and weep for Delphi. Then break your TV.

O Delphi 2010 tem muitos novos recursos que provam que a ferramenta está evoluindo muito. Uma nova feature que eu estou achando muito interessante é a nova RTTI e os novos recursos adicionados a ela.

A RTTI existe deste as primeiras versões do Delphi porém era muito mais complexo utilizar e dava um bom trabalho pois o uso de ponteiro a meu ver era exagerado.

Agora ficou mais fácil procurar campo ou propriedades em classes, chamar métodos em Run time e várias coisas legais.

Eu estava procurando na internet achei um blog muito bom do Cobus Kruger que é desenvolvedor em Delphi há muito tempo e postou um artigo interessante e bem prático mostrando como fazer a ligação entre um objeto de negócio e os campos de um formulário neste link.

Com o exemplo mostrado no post podemos separar as regras de negócio da camada visual em nossa aplicação, deixando nosso código mais modularizado e mais fácil de reutilizar nossa camada de negócio.

One of the most important principles in building complex software systems, is detaching  the business logic from the screens that allow users to view and edit information.

You’ll notice I said “most important” and not “most popular.” Sad but true – all modern IDEs make it so easy for a programmer to simply whack together a bunch of user interface controls, that there are probably far more forms with embedded business logic than without.

The fact is that for simple systems, this can often be convenient and harmless. But for more complex ones, it nearly always spells disaster (or at least chronic pain). The gold standard for these kinds of systems is to have a set of business objects and a set of screens that merely displays and edits them.

Building a proper business object framework is a complex topic all of its own, but Delphi (and all the other modern languages) give us more than enough riches in the object model to implement what we need in this regard.

What environments like Delphi don’t do very well, is give developers the tools to build a form that can capably display and edit business objects without knowing too much about them. And very generic entry forms only work well for very generic data. Invariably, specialised data require specialised forms that give the user appropriate functionality and a sensible layout.

So you end up with lots and lots of code like this:

procedure TCustomerForm.LoadForm(Customer: TCustomer);
begin
  NameEdit.Text := Customer.Name;
  EmailEdit.Text := Customer.Email;
end; 

procedure TCustomerForm.PostForm(Customer: TCustomer);
begin
  Customer.Name := NameEdit.Text;
  Customer.Email := EmailEdit.Text;
end; 

And this kind of boiler-plate code is yet another reason while lots of programmers throw structure to the hounds and just integrate the business logic into the form.

Well, no need.

Delphi’s RTTI framework has always allowed one to access and manipulate all the published properties and fields on an object and I have been using a framework based on that for over ten years now. Simply publish all the properties you want to represent on the form and you can match object properties to screen controls by name and type.

Delphi 2010 has of course overhauled the RTTI framework completely and I quickly adapted my code to use that instead. Truth be told, the new RTTI is a little finicky and brittle, but it is also far richer in functionality and I found it well worth the effort to overhaul my classes.

What I am about to present here is not based in any way on the framework in our system, but illustrates very nicely how that works. Having said that, what I will show here is also simplified to the point that you will definitely want to extend it a little before you go gold with it.

Exploring The Cliff Faces

There is no real limit to the data types that you can have on your business object, but VCL controls almost all use simpler types to represent their values. So the first thing you’ll need is some sort of mapping of how you will want to represent information.

Here is a quick table of reasonable mappings:

I’m sure you can think of a few more and probably disagree with me on a few, but you get to pick your own.

The plan is to have a completely autonomous business object and a very simple screen that can display and modify the business object without knowing much about it.

Here is the business object I am going to use:

TPerson = class
private
  FName: string;
  FAge: Integer;
  FOccupation: string;
public
  property Name: string read FName write FName;
  property Age: Integer read FAge write FAge;
  property Occupation: string read FOccupation write FOccupation;
end;

And my form is as simple as they get too:

The load button predictably loads the content of a TPerson instance into the form, the Save button does the reverse and Clear Form… well OK.

Here is the code for the Load and Save buttons:

procedure TCustomerForm.LoadButtonClick(Sender: TObject);
begin
  Binding.Load;
end;

procedure TCustomerForm.SaveButtonClick(Sender: TObject);
begin
  Binding.Save;
end;

That is about as simple as it gets, right? An obvious enhancement is to make the form validate the values before assigning them to the form, but let’s not get ahead of ourselves.

The Binding variable above is of the TObjectBinding class which links together any TWinControl and any object. Before I show that – here are a few things you probably know, but let’s cover them anyway:

1. All controls placed on a form at design time get their own published fields. This lets the streaming system know what should go into the form file and what shouldn’t.
2. Not all public properties on your business object necessarily need to be displayed on the form. And none of those properties that you want to display will be published unless you made them so.
3. Properties have names. So do screen controls. They may even match, but lots of programmers prefer to have their controls named something like AgeEdit or EdtAge instead of just Age.
4. Not all properties are writeable. In fact, you could (probably shouldn’t) even create properties that can be written to but not read.

Clearly then, we can find the relevant controls by using Delphi’s new RTTI framework to iterate the published fields that are controls. Finding the relevant business object fields can be as simple as grabbing all the public and published properties or it can involve checking attributes. Or only properties with an even-length name. My class has a method to pick out valid fields and another to pick out valid properties. Modify these to your heart’s content.

And in production code you may want to pick up some of the form’s properties as well. Works well when you need to override some of the basic functionality.

Building The Narrow Bridge

Here is the class declaration – I’ll discuss the methods as we go along:

TObjectBinding = class
private
  // Quick way to get from the object
  // field to its screen control.
  PropFieldMapping: TDictionary<TRttiProperty, TRttiField>;
  // Needed for RTTI.
  Context: TRttiContext;
  ControlType: TRttiType;
  ObjType: TRttiType;
  // The control (normally form) and
  // the object it represents.
  Control: TWinControl;
  Obj: TObject;
  // Finds the object properties that have corresponding
  // fields and stores them in the dictionary.
  procedure CreateMappings;
  function FindField(Prop: TRttiProperty; out Field: TRttiField): Boolean;
  function FieldClass(Field: TRttiField): TClass;
  // Modify these to change the rules about what
  // should be matched.
  function IsValidField(Field: TRttiField): Boolean;
  function IsValidProp(Prop: TRttiProperty): Boolean;
  // Modify these to change the mappings of property type
  // to VCL control class.
  procedure AssignField(Prop: TRttiProperty; Field: TRttiField);
  procedure AssignProp(Prop: TRttiProperty; Field: TRttiField);
  // Used from AssignField/AssignProp. Extend these to
  // support a wider range of properties.
  function GetPropText(Prop: TRttiProperty): string;
  procedure SetPropText(Prop: TRttiProperty; const Text: string);
public
  procedure Load;
  procedure Save;

  constructor Create(Control: TWinControl; Obj: TObject);
  destructor Destroy; override;
end;

Load and Save can easily be supplemented here with Validate, which will use attributes specified on the business object properties to decide whether the current screen values are valid. If not, we don’t call Save at all.

The constructor and destructor do what you expect. They create and destroy the objects held in those private fields. The constructor also calls CreateMappings, which is where a lot of the fun stuff happens.

constructor TObjectBinding.Create(Control: TWinControl; Obj: TObject);
begin
  inherited Create;

  Self.Control := Control;
  Self.Obj := Obj;
  Context := TRttiContext.Create;
  ControlType := Context.GetType(Control.ClassInfo);
  ObjType := Context.GetType(Obj.ClassInfo);
  PropFieldMapping := TDictionary<TRttiProperty, TRttiField>.Create;
  CreateMappings;
end;

destructor TObjectBinding.Destroy;
begin
  PropFieldMapping.Free;
  ObjType.Free;
  ControlType.Free;
  Context.Free;

  inherited;
end;

procedure TObjectBinding.CreateMappings;
var
  Props: TArray<TRttiProperty>;
  Prop: TRttiProperty;
  Field: TRttiField;
begin
  Props := ObjType.GetProperties;
  for Prop in Props do
    if IsValidProp(Prop) and FindField(Prop, Field) then
      PropFieldMapping.Add(Prop, Field);
end;

CreateMappings scans through all the properties on the business object and attempts to find fields on the form to match them to. If a match is found, they are stored in the PropFieldMapping dictionary for future reference.

Notice the IsValidProp function. That is where you should impose any additional rules about whether or not a property should be taken into account. The default implementation simply grabs all the public and published properties.

function TObjectBinding.IsValidProp(Prop: TRttiProperty): Boolean;
begin
  Result := Prop.Visibility >= mvPublic;
end;

Also, there is a FindField function. This little guy does a bit more than just grab all the published fields. Again, there is an IsValidField function for you to toy with. But it first attempts to find a control with a name that matches exactly with that of an approved property. If not, it also checks for a few common variants of the name (AgeEdit and EdtAge as mentioned before). This list will obviously need to grow if you support many more controls.

function TObjectBinding.FieldClass(Field: TRttiField): TClass;
begin
  Result := GetTypeData(Field.FieldType.Handle).ClassType;
end;

function TObjectBinding.IsValidField(Field: TRttiField): Boolean;
begin
  Result := (Field <> nil) and (Field.Visibility = mvPublished) and
    (Field.FieldType.TypeKind = tkClass) and
    (FieldClass(Field).InheritsFrom(TControl));
end;

function TObjectBinding.FindField(Prop: TRttiProperty; out Field: TRttiField): Boolean;
const
  Embelishments: array [0..5] of string =
    ('Edt', 'Edit', 'Combo', 'ComboBox', 'Lookup', 'Lkp');
var
  Emb: string;
begin
  Field := ControlType.GetField(Prop.Name);
  if IsValidField(Field) then
    Exit(True)
  else for Emb in Embelishments do
  begin
    Field := ControlType.GetField(Prop.Name + Emb);
    if not IsValidField(Field) then
      Field := ControlType.GetField(Emb + Prop.Name);
    if IsValidField(Field) then
      Exit(True);
  end;
  Result := False;
end;

Now that we have a dictionary of business object properties and the screen fields that we want to link them to, we can take a look at the very similar-looking Load and Save methods.

procedure TObjectBinding.Load;
var
  Prop: TRttiProperty;
begin
  for Prop in PropFieldMapping.Keys do
    AssignField(Prop, PropFieldMapping[Prop]);
end;

procedure TObjectBinding.Save;
var
  Prop: TRttiProperty;
begin
  for Prop in PropFieldMapping.Keys do
    AssignProp(Prop, PropFieldMapping[Prop]);
end;

AssignProp and AssignField are probably the two most difficult functions to write in this entire class. The problem is that Delphi’s TValue structure used in the new RTTI framework makes no attempt whatsoever to convert data. Instead, you need to do any conversions yourself and assign to the exact type you need. That isn’t too much of a problem, but it means lots of individually-crafted conversion blocks.

To keep my example manageable, I opted to convert everything to strings and back using GetPropText and SetPropText. And I only support string, Integer, Double and TDateTime. I didn’t use Double and TDateTime on my TPerson business object, but they do require a special trick that I wanted to show.

procedure TObjectBinding.AssignField(Prop: TRttiProperty; Field: TRttiField);
var
  NestedControl: TControl;
  PropText: string;
begin
  NestedControl := Field.GetValue(Control).AsObject as TControl;

  PropText := GetPropText(Prop);
  if NestedControl is TCustomEdit then
    TCustomEdit(NestedControl).Text := PropText
  else if NestedControl is TCustomComboBox then
    TComboBox(NestedControl).Text := PropText;
end;

procedure TObjectBinding.AssignProp(Prop: TRttiProperty; Field: TRttiField);
var
  NestedControl: TControl;
  FieldText: string;
begin
  NestedControl := Field.GetValue(Control).AsObject as TControl;

  if NestedControl is TCustomEdit then
    FieldText := TCustomEdit(NestedControl).Text
  else if NestedControl is TCustomComboBox then
    FieldText := TComboBox(NestedControl).Text
  else
    FieldText := '';

  SetPropText(Prop, FieldText);
end;

procedure TObjectBinding.SetPropText(Prop: TRttiProperty; const Text: string);
var
  V: TValue;
begin
  case Prop.PropertyType.TypeKind of
    tkInteger: V := StrToIntDef(Text, 0);
    tkFloat:
      if Prop.PropertyType.Handle = TypeInfo(TDateTime) then
        V := StrToDateDef(Text, 0)
      else
        V := StrToFloatDef(Text, 0);
    tkUString: V := Text;
    // And other types handled in similar ways
  else
    Exit; // Or some reasonable default action
  end;

  Prop.SetValue(Obj, V);
end;

function TObjectBinding.GetPropText(Prop: TRttiProperty): string;
var
  V: TValue;
begin
  V := Prop.GetValue(Obj);
  case Prop.PropertyType.TypeKind of
    tkInteger: Result := IntToStr(V.AsInteger);
    tkFloat:
      if Prop.PropertyType.Handle = TypeInfo(TDateTime) then
        Result := DateToStr(V.AsType<TDateTime>)
      else
        Result := FloatToStr(V.AsType<Double>);
    tkUString: Result := V.AsString;
    // And other types handled in similar ways
  else
    Result := ''; // Or some reasonable default
  end;
end;

Firstly, the AssignProp and AssignField functions each has a check for every supported VCL control base class. So to support TCheckBox or TCheckListBox this is where you would add the additional support code.

Then take a look at GetPropText and SetPropText. They mirror one another of course, so we can learn what we need by inspecting GetPropText.

First thing to notice is that string properties use the tkUString type and not tkString as in pre-Unicode versions of Delphi. Also, we can simply read TValue.AsInteger when reading an integer value.

The trouble arises when we look at Double and TDateTime. TDateTime is actually a type alias for Double and they both show up as tkFloat. This is why I compare the type info from my property with the type info for TDateTime. The alternative would be to check the type name, but that thought makes me queasy. The same kind of thing will be needed to tell Boolean from other enumerated types.

Also, both Double and TDateTime are incompatible with TValue.AsExtended, which is of course a floating point type of a different size. So taking care of all these type conversions become really cumbersome, but of course you only need to write the code once.

And that’s it

Hooking all of this together, you can now have business objects that are completely detached from their editing screens. You’ll find that the screens become really trivial to develop – most cases involve little more than slapping on the controls, naming them and calling Load and Save. And that last bit can be done is a base class.

You also get to take advantage of all the other advantages that come with a proper split. You will find it easier to modify your business rules, easily use the same business logic in other contexts (say a bulk import versus the capture screen) and also be able to validate your business rules using automated tests. Good idea!

I can now show you my super-complex test app in action. Note that the first screen shot shows the names of both edit boxes and the combo box. Despite the different naming conventions, they all link up automatically to the correct properties.

1. Starting up.

2. Click Load Form.

3. Mess around with the values and click Save to Object.

4. Click Clear Form.

5. And finally, load again.

(arstechnica.com) Microsoft plans to transition its Windows Azure cloud computing platform from preview to full production capacity on January 1 next year, Chief Software Architect Ray Ozzie announced at the annual PDC conference on Tuesday.  The service, currently operating as a free Community Technology Preview (CTP), will remain no-cost throughout January; from February 1 it will start accumulating charges. The cost schedule was previously announced in July.

Azure will also support PHP and the Java(tm) platform:

• http://phpazure.codeplex.com/
• http://www.windowsazure4j.org/

Client / Server Developement ( Chat and Gaming ) ===================================== Client Features ————– # Integrated Chat supporting font types and styles. # Top section of main chat lobby shows the game tables… (Budget: $750-1500, Jobs: .NET, Delphi, Game Design, Social Networking)
Bid on this project

Instalando o Rxlib no Delphi 2009

1.  Adicione  as Units do  rxLib  no  directory (…RxLib_2009\Units)

Selecione:

Tools  -> options

- Environment Options

- Delphi Options

- Library – Win32 | Library Path

2.  Abra o projeto de IDE:

File->Open: …\RxLib_2009\packages\Delphi2009\Rxlib.groupproj

3. Compile todos os pacotes (all packages):

Project-> Build All projects

4. Instale  all packages:

Clique com o botão direito do mouse em  dclrxbd120.bpl  no Project Manager.

Selecione:  Install

View -> Project Manager

Download:

RxLib   para Delphi 2009

Continuação da linha de código do Projeto MediaPlayer no Delphi 2009

1.  Para configurar  RxTrayIcon, Vá até Object Inspector e em propriedades faça as seguintes alterações:

Active: True
Interval: 150
Name: RxTrayIcon1
PopupMenu: PopupMenu1 (link o RXTrayIcon com o PopupMenu1 do form)

2. Clique na propriedade  Icons do RxTrayIco   e  adicione as imagens de sua preferência.

3. Selecione o PopupMenu1 e configure cada item como segue abaixo:

Tocar
Propriedades
Tag: 1

Name: Play1

ImageIndex: 2

Evento

OnClick: ToolButton1Click

Pausar
Propriedades
Tag: 2

Name: Pause1

ImageIndex: 3

Evento

OnClick: ToolButton1Click

Stop
Propriedades
Tag: 3

Name: Stop1

ImageIndex: 6

Evento

OnClick: ToolButton1Click

Next
Propriedades
Tag: 4

Name: Next1

ImageIndex: 5

Evento

OnClick: ToolButton1Click

Prior
Propriedades
Tag: 5

Name: Retorna1

ImageIndex: 5

Evento

OnClick: ToolButton1Click

4.  Declare as seguintes funções:

function AcrescentarZero(sender:String;_tam:integer):String;

function TMusicas(sender:string):string;

function TFmediaplayer.AcrescentarZero(sender: string; _tam: Integer):string;

var //declare as variáveis

x :integer;

begin

Result := ”;

for x := 1 to _tam-Length(sender) do

Result := Result+’0′;

Result := Result+Sender;

end;

function TFmediaplayer.TMusicas(sender: string):string;

var //declare as variáveis

mn,ms : double;

MPlayer1 : TMediaPlayer;

begin

MPlayer1 := TMediaPlayer.Create(Self);

MPlayer1.Parent := Self;

MPlayer1.Visible := False;

MPlayer1.close;

MPlayer1.FileName := sender;

MPlayer1.Open;

mn     := (MPlayer1.Frames div 100) div 60;

ms     := (MPlayer1.Frames div 100) mod 60;

result :=  FormatFloat(‘00:00′, StrToInt(AcrescentarZero(FloatToStr(mn),2)+AcrescentarZero(FloatToStr(ms),2))) ;

FreeAndNil(MPlayer1);

end;

5. Selecione o Timer: Musica  e acrescente o seguinte código:

procedure TFmediaplayer.MusicaTimer(Sender: TObject);

var // declare as variáveis

x,i : integer;

ntempo : ttime;

begin

i := 0;

ntempo := StrtoTime(‘00:00:00′);

for x := 0 to ListView1.items.Count-1 do

if ListView1.Items.Item[x].Checked then

begin

inc(i);

ntempo := ntempo + StrToTime(‘00:’+ListView1.Items.Item[x].SubItems.Strings[0]);

end;

lbltempototal.Caption := TimeToStr(ntempo – StrToTime(‘00:’+lbltempdecorrido.Caption));

end;

6. Selecione o Timer: Tempo e adicione o código que segue:

procedure TFmediaplayer.TempoTimer(Sender: TObject);

var // declare as varáveis

TheLength: LongInt;

mn,ms : double;

begin

if (MediaPlayer1.Mode = mpPlaying) then

begin

TrackBar1.Max      := MediaPlayer1.Length;

TrackBar1.Position := MediaPlayer1.Position;

mn           := (MediaPlayer1.Frames div 100) div 60;

ms           := (MediaPlayer1.Frames div 100) mod 60;

lblduracao.Caption  := FormatFloat(‘00:00′, StrToInt(AcrescentarZero(FloatToStr(mn),2)+AcrescentarZero(FloatToStr(ms),2))) ;

mn    := (MediaPlayer1.Position div 1000) div 60;

ms    := (MediaPlayer1.Position div 1000) mod 60;

lbltempdecorrido.Caption       := FormatFloat(‘00:00′, StrToInt(AcrescentarZero(FloatToStr(mn),2)+AcrescentarZero(FloatToStr(ms),2))) ;

Application.Title := lblmusica.Caption+’ [ '+lbltempdecorrido.Caption+' ]‘;

end;

if not (MediaPlayer1.Mode = mpPlaying) then

begin

Tempo.Enabled := False;

MediaPlayer1.close;

ListView1.Items.Item[Musicas].Checked := false;

if Musicas >= ListView1.Items.Count-1 then

begin

MediaButn(3);

Exit;

end;

MediaButn(4);

end;

end;

7. Crie o procedimento MediaButn. Neste procedimento iremos configurar os Buttons para que ao receberem o click executem os comandos de acordo com a funcionalidade de cada Button.

Importante: Lembre de verificar a propriedade tag dos buttons se você marcou corretamente:

Play: tag=1; Pause: tag:2; Stop: tag=3; Next:  tag=4 e  Prior: tag=5.

procedure TFmediaplayer.MediaButn(Sender:integer);

var //declare a variável

x: integer;

begin

Tempo.Enabled := False;

//estamos trabalhando com 5 buttons

if Sender  in [0,4,5] then

MediaPlayer1.close

Else if (Sender  in [2])  and (MediaPlayer1.Mode = mpPlaying) then

MediaPlayer1.Pause

Else if (Sender  in [3]) and (MediaPlayer1.Mode = mpPlaying) then

MediaPlayer1.Stop;

Play.Enabled  := Sender in [0,2,3];

Pause.Enabled := Sender in [1,4,5];

Stop.Enabled  := Sender in [1,4,5];

Next.Enabled  := Sender in [1,4,5];

Prior.Enabled := Sender in [1,4,5];

Play1.Enabled  := Sender in [0,2,3];

Pause1.Enabled := Sender in [1,4,5];

Stop1.Enabled  := Sender in [1,4,5];

Next1.Enabled := Sender in [1,4,5];

Retorna1.Enabled := Sender in [1,4,5];

if ListView1.Items.Count <= 0 then

begin

MediaPlayer1.close;

AtualizaLabels;

exit;

end;

if Sender = 3 then

begin

TrackBar1.Max      := 0;

TrackBar1.Position := 0;

AtualizaTempo;

end

Else if Sender = 4 then

begin

inc(Musicas);

if Musicas > ListView1.Items.Count-1 then

Musicas := 0;

end

Else if Sender = 5 then

begin

Dec(Musicas);

if Musicas < 0 then

Musicas := 0;

end;

if Sender  in [1,4,5] then

begin

if (MediaPlayer1.Mode = mpPaused) then

MediaPlayer1.Play

else

begin

if Musicas < 0 then

Musicas := ListView1.ItemIndex;

if ListView1.Items.Item[Musicas].Checked  then

TrackBar1.Max         := 0;

TrackBar1.Position    := 0;

MediaPlayer1.FileName := ListView1.Items.Item[Musicas].Caption;

lblmusica.Caption     := ExtractFileName(ListView1.Items.Item[Musicas].Caption);

MediaPlayer1.Open;

MediaPlayer1.play;

ListView1.ItemIndex := Musicas;

if Fmediaplayer.Active then

if pcprincipal.ActivePageIndex = 0 then

ListView1.SetFocus;

end;

end;

Tempo.Enabled := Sender  in [1,4,5];

RxTrayIcon1.Animated := (MediaPlayer1.Mode = mpPlaying);

if (MediaPlayer1.Mode = mpPaused) then

RxTrayIcon1.Hint := ‘Em Pausa’

else if (MediaPlayer1.Mode = mpPlaying) then

RxTrayIcon1.Hint := ‘Em Reprodução – ‘+lblmusica.Caption

else if (MediaPlayer1.Mode = mpStopped) then

RxTrayIcon1.Hint := ‘Parado’

else if (MediaPlayer1.Mode = mpRecording) then

RxTrayIcon1.Hint := ‘Gravando’

Else

RxTrayIcon1.Hint := ‘Músicas’;

end;

8. Adicione o  código abaixo no evento OnClick do TollButton, lembrando-se de acrescentar o código em todos os Buttons .

procedure TFmediaplayer.ToolButton1Click(Sender: TObject);

begin

MediaButn(TToolButton(sender).tag);

end;

Ex:

ToolButton1

Propriedade – name: Play

Evento   – OnClick:ToolButton1.Click

ToolButton2

Propriedade – name: Pause

Evento   – OnClick:ToolButton1.Click

.

.

.

9. Selecione o RxTrayIcon  e em  Eventos selecione  OnDblClick:

procedure TFmediaplayer.RxTrayIcon1DblClick(Sender: TObject);

begin

Fmediaplayer.Show;

end;

10. Selecione o btadicionar (BitBtn do segundo Tabsheet) e adicione o código abaixo:

procedure TFmediaplayer.btadicionarClick(Sender: TObject);

var

arquivo:string;

x:integer;

begin

for x := 0 to FileListBox1.Items.Count-1 do

if FileListBox1.Selected[x] then

begin

arquivo:= DirectoryListBox1.Directory+’\'+FileListBox1.Items.Strings[x];

ListView1.AddItem(arquivo,ListView1);

ListView1.Items.Item[ListView1.Items.Count-1].SubItems.Add(TMusicas(arquivo));

ListView1.Items.Item[ListView1.Items.Count-1].Checked := true;

end;

//AtuaTempo;

if not (MediaPlayer1.Mode = mpPlaying) then

begin

ListView1.ItemIndex := 0;

MediaButn(0);

end;

end;

11. Selecione o form (pcprincipal) , selecione Eventos e clique em  OnClose para adicionar o código abaixo:

procedure TFmediaplayer.FormClose(Sender: TObject; var Action: TCloseAction);

begin

pcprincipal.ActivePageIndex := 0;

Action := caNone;

Hide;

end;

12. Ainda em eventos do form, selecione OnCreate e adicione o código que segue:

procedure TFmediaplayer.FormCreate(Sender: TObject);

begin

RxTrayIcon1.ShowDesign := True;

MediaPlayer1 := TMediaPlayer.Create(Self);

MediaPlayer1.Parent := Self;

MediaPlayer1.Visible := False;

end;

13. Ainda  no component ListView1, selecione o evento OnKeyDown e adicione o código:

procedure TFmediaplayer.ListView1KeyDown(Sender: TObject; var Key: Word;

Shift: TShiftState);

var

MesmaMusica : bool;

x : integer;

begin

if key = 46 then

begin

MesmaMusica := (lblmusica.Caption = ListView1.Items.Item[Musicas].Caption);

if (MediaPlayer1.Mode = mpPlaying) and (Mesmamusica) then

MediaButn(3);

ListView1.DeleteSelected;

if (MediaPlayer1.Mode = mpStopped) and (Mesmamusica) then

MediaButn(4);

if ListView1.Items.Count = 0 then

Musicas := 0;

end;

end;

14. Adicione o código abaixo no componente  ListView1 (primeira TabSheet) utilizando o  Evento OnClick .

procedure TFmediaplayer.ListView1Click(Sender: TObject);

begin

MediaButn(3);

if ListView1.ItemIndex >= 0 then

begin

Musicas := ListView1.ItemIndex ;

MediaButn(1);

end;

end;

Com o intuito de facilitar o estudo, estou disponibilizando o arquivo do projeto com código fonte  e o compenente RxLib –  Delphi 2009 para download. Qualquer problema com o link de download , entrem  em contato utilizando o formulário de comentários.

Download:

Projeto MediaPlayer Delphi 2009

Company is looking for experts in Delphi for single project. Candidates must be fast and had at least 3 years of experience. (Budget: $750-1500, Jobs: Delphi)
Bid on this project

General Motors trotted out preliminary financial results for the first time this morning since it sloughed off bad assets to the government and emerged from bankruptcy this summer: GM saw a net loss of $1.15 billion between July 10 and September 30 of this year, but ended the quarter with $42.6 billion in cash on hand (cash and marketable securities), according to the company’s reporting, which has not been audited and does not comply with GAAP standards.

Much of GM’s cash reserves have been earmarked for existing expenses, including payments to parts supplier Delphi, but as David Welch notes over on BusinessWeek, the automaker is now “closer to making money than it has been for years.” That milestone can’t come too soon for GM. The extended-range electric Chevy Volt, which GM gave a starring role in its financial viability plans, is now closing in on a late-2010 commercial launch that’s likely to be anything but a money-maker in the near term.

In addition, having ditched the Hummer, Subaru, Pontiac and Saturn brands, GM is banking on new models under the Chevrolet nameplate (including the Volt, the 40 MPG Cruze compact and the automaker’s first minicar, the Spark) to help boost sales.

GM said today the company will be able to start repaying government loans in December — more than five years ahead of schedule. Don’t expect the company to finish the year with a bang, however: GM anticipates negative cash flows in the fourth quarter of this year as it makes payments to Delphi, the governments of Canada, Ontario, the U.S. and Germany and continues restructuring. Plus, Dow Jones Newswires reports that while “GM’s spending on marketing and new-product development came to a virtual standstill during its bankruptcy proceedings,” the automaker plans to ramp up spending on advertising and engineering this year.

Lux Research analyst Jacob Grose told us this summer, on Day 1 of the New GM, he sees an “inherent contradiction” between the company’s very ambitious and expensive push to launch the Volt late next year and its relatively shaky bottom line.

But if the pervasive 230 MPG campaign GM rolled out for the Volt earlier this year provides any hints, we can expect the Volt — already an estimated billion-plus-dollar investment for the company — to get a fat slice of the automaker’s advertising budget in coming months, as it tries to cast a green glow across its lineup and gain an edge in segments where GM sees some of the highest growth potential: young and environmentally-motivated car buyers.

http://www.cheat-sheets.org/

Site com várias referências rápidas em pdf. O objetivo dos cheat sheets é criar uma referência rápida de cada linguagem de programação. Há referências para boa parte das linguagens existentes, como: C, C#, C++, Tex, PHP, SQL, VIM, Linux, Delphi entre outros.

Vale a pena dar uma conferida.

Sambil coba share sedikit yang saya tahu, ini merupakan coding delphi untuk mengosongkan/menghapus isi table sekaligus. Persiapkan sebuah Form, Table (paradox) yang telah diisi data, DBGRID dan Button. Ini coding selengkapnya.

procedure TFrm_SPK.Button3Click(Sender: TObject);
begin
tb_spk_temp.Close;
tb_spk_temp.EmptyTable;
tb_spk_temp.Active:=true;
tb_spk_temp.Refresh;
end;

Catatan : agar tidak terjadi error maka program dijalankan pada file executable nya setelah menutup program delphi nya

Gente, achei dois artigos muito interessantes no site invasao.com.br. O primeiro fala como descobrir senha do hotmail através de engenharia social e outros métodos, o segundo fala de como montar um trojan em delphi sem conhecimento avançado necessário.

Você pode ler os artigos acima nestes links:

http://www.invasao.com.br/2008/02/17/descobrindo-senha-de-hotmail/

http://www.invasao.com.br/2008/03/08/como-montar-um-trojan-em-delphi-sem-saber-nada/

Visto que é algo muito util e um pouco complicado estarei postando como fazer passo a passo.
Então vamos começar.

Dica:
Para quem não esta acostumado e sequer sabe sobre manipulação de memória recomendo que de uma boa lida em artigos sobre manipulação de memória para que haja uma facilidade de entendimento ao seguir a leitura do tutorial.

O que é Code Injection?
Code injection nada mais é do que injetar uma DLL e fazer com que o processo remoto execute a tal função.
Para fazer isso precisaremos de uma DLL que a função em seja exportada
Ex:no delphi o fim do código seria

exports
FazerExitProcess;

Outro detalhe importante é que precisaremos de privilégios necessários.Para evitar quaisquer eventuais problemas, definiremos o privilégio como o de debug e tambem depois de executada a rotina, não temos mais porque deixar os parametros utilizados na execução da mesma no target, isso só iria ocupar espaço, então nós liberaremos toda a memória escrita no processo remoto.

Preparando um Code Injection

Antes de mais nada precisaremos de uma estrutura para os parametros do nosso Code Injection então declare
a seguinte type no seu form.

type
TInjectParams = record
LoadLibrary: function (lpLibFileName: PAnsiChar): Cardinal; stdcall;
LibName: PAnsiChar;
GetProcAddress: function (hModule: Cardinal; lpProcName: PAnsiChar): Pointer; stdcall;
ProcName: PAnsiChar;
end;
PInjectParams = ^TInjectParams;

Com essa estrutura,o usuário no final do code injection só precisará de pegar o Process ID(PID) do processo,Portanto declare na uses da sua unit a biblioteca TlHelp32 e nas funções declare a seguinte função.

function GetProcess(proc: string): Cardinal;
var
Snap: THandle;
pe: TProcessEntry32;
begin
Snap:=CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS,0);
if Snap = 0 then Exit;
if Process32First(Snap,pe) then
begin
repeat
if proc = pe.szExeFile then
begin
Result:=pe.th32ProcessID;
break;
end;
until not Process32Next(Snap,pe)
end
end;

Como ja foi dito,nos precisaremos de escrever na memória do processo remoto,portanto é necessário alocar a memória para a escrita,para facilitar vamos declarar as funções.

function WriteString(Process: Cardinal; s: string): Pointer;
var
bytes: Cardinal;
begin
Result:=VirtualAllocEx(Process, nil, length(s) + 1, MEM_COMMIT or MEM_RESERVE, PAGE_EXECUTE_READWRITE);
WriteProcessMemory(Process, Result , pchar(s), length(s) + 1, bytes);
end;
function WriteData(Process, dwSize: Cardinal; RemoteData: pointer): pointer;
var
bytes: Cardinal;
begin
Result:=VirtualAllocEx(Process, nil, dwSize, MEM_COMMIT or MEM_RESERVE, PAGE_EXECUTE_READWRITE);
WriteProcessMemory(Process, Result, RemoteData, dwSize, bytes);
end;

Com quase tudo pronto nós precisaremos de uma função para executar o código no processo remoto então declare mais essa função também.

procedure RemoteFunction(Parametros: PInjectParams); stdcall;
var
proc: procedure; stdcall;
begin
proc:=Parametros^.GetProcAddress(Parametros^.LoadLibrary(Parametros^.LibName),Parametros^.ProcName);
proc;
end;

Agora precisaremos de um método para saber o tamanho dessa rotina descrita acima, pois na hora de escrevê-la no target é necessário por o tamanho. Para isso faremos outro método logo abaixo desse, e depois é só pegar o endereço dele e subtrair do endereço da rotina “RemoteFunction”.
Então declare o procedimento :

procedure RemoteFunctionEnd; stdcall;
begin;
end;

E como ja foi dito nos preciaremos de privilégios de DEBUG então declare a função.

procedure ChangePrivilege(szPrivilege: PChar; fEnable: Boolean);
var
NewState: TTokenPrivileges;
luid: TLargeInteger;
hToken: THandle;
ReturnLength: DWord;
begin
OpenProcessToken(GetCurrentProcess(), TOKEN_ADJUST_PRIVILEGES, hToken);
LookupPrivilegeValue(nil, szPrivilege, luid);

NewState.PrivilegeCount := 1;
NewState.Privileges[0].Luid := luid;
if (fEnable) then
NewState.Privileges[0].Attributes := SE_PRIVILEGE_ENABLED
else
NewState.Privileges[0].Attributes := 0;

AdjustTokenPrivileges(hToken, False, NewState, SizeOf(NewState), nil, ReturnLength);
CloseHandle(hToken);
end;

Pronto, agora só falta montar a função final, mas depois de tudo isso, para quem realmente entendeu a lógica fica fácil.

pprocedure Inject(process, dll, code: string);
var
PID, hProcess, ThreadId, ThreadHandle: Cardinal;
RemoteData,RemoteFunc,LibFileName,ProcName: pointer;
Parametros: TInjectParams;
begin
//Pega o Handle do processo
PID:=GetProcess(Process);
//Seta o privilégio de debug
ChangePrivilege(’SeDebugPrivilege’, True);

//Abre o processo
hProcess := OpenProcess(PROCESS_ALL_ACCESS, False, PID);

//Define os parâmetros que serão usados para executar a procedure
LibFileName:=WriteString(hProcess, dll);
ProcName:=WriteString(hProcess, code);
Parametros.LoadLibrary:=GetProcAddress(GetModuleHandle(’kernel32′), ‘LoadLibraryA’);
Parametros.LibName:=LibFileName;
Parametros.GetProcAddress:=GetProcAddress(GetModuleHandle(’kernel32′), ‘GetProcAddress’);
Parametros.ProcName:=ProcName;

//Abre um novo espaço de memória para guardar os parâmetros
RemoteData:=WriteData(hProcess, sizeof(Parametros), @Parametros);

//Abre um novo espaço de memória para guardar a procedure
RemoteFunc:=WriteData(hProcess, integer(@RemoteFunctionEnd) – integer(@RemoteFunction), @RemoteFunction);

//Cria a thread que executará a procedure
ThreadHandle:=CreateRemoteThread(hProcess, nil, 0, RemoteFunc, RemoteData, 0, ThreadId);
WaitForSingleObject(ThreadHandle, 3000);

//Libera as alocações de memórias criadas
VirtualFreeEx(hProcess,LibFileName,0,MEM_RELEASE);
VirtualFreeEx(hProcess,ProcName,0,MEM_RELEASE);
VirtualFreeEx(hProcess,RemoteFunc,0,MEM_RELEASE);
VirtualFreeEx(hProcess,RemoteData,0,MEM_RELEASE);
end;

Agora chegou a parte que você ira realizar o code injection.
Como ja foi dito precisaremos de uma DLL com uma função que seja exportada então salve todo o seu projeto e crie um novo projeto de DLL.vou mostrar como ficou a minha dll de testes

library testdll;
uses
Windows,
SysUtils,
Classes;

{$R *.res}

procedure MsgBox;
begin
MessageBox(0,’Funcionou’,’Code Injection bem sucedido’,MB_OK+MB_ICONINFORMATION);
end;
exports
MsgBox;
begin
end.

Então agora é só no seu projeto do Injector você usar a função.

Inject(‘notepad.exe’,'C:\Dev\CodeInjection\testdll\testdll.dll’,'MsgBox’);

Agora pra quem não entendeu direito,ou não quer nem ler e quer tudo pronto eu coloquei um link com a source do injector e da testdll
http://www.4shared.com/file/101714263/63913ea/CodeInjection.html

Créditos: R0DR1G0.