In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.

Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.

New Sample DbfData6

Xailer professional forum in English
Responder
Aguiar Costa
Mensajes: 115
Registrado: Jue Jun 01, 2006 7:21 pm

New Sample DbfData6

Mensaje por Aguiar Costa »

Hello !!!
Some answers, please :)
1 - TFormFolder is a class to add a form to a folder, or to have a form as
folderpage. Right ?
2 - Is this class a generic to use with other applications ?
3 - To just add a form to a folder, methods New() and Create() from
TFormFolder are sufficient. Right ?
4 - Are InsertComponent() and RemoveComponent() methods of XFolderPage ?
When are they called ? Is there some documantation about them ?
5 - How did you created those classes that comes from TFormfolder (like
TFrmClientes)? That's a regular form that you changed the "From" part
directly in the code ? Right ?
6 - In method New() from TFormFolder why do you call ::Createform() if it is
Virtual (i thought a virtual method does nothing...what does Virtual means?)
?
Sorry for all these questions, just trying to understand a little bit more
of Xailer and OOP!
TIA.
Aguiar !!!
Avatar de Usuario
ignacio
Site Admin
Mensajes: 9441
Registrado: Lun Abr 06, 2015 8:00 pm
Ubicación: Madrid, Spain
Contactar:

New Sample DbfData6

Mensaje por ignacio »

Aguiar,
That is the project we showed in Xailer free technical journeys and it uses
some complex programming techniques that is difficult to explain on a few
lines. It took more than 8 hours to see the all project. BTW I try to give
you some clues, but you should learn through code I am afraid.
> 1 - TFormFolder is a class to add a form to a folder, or to have a form as
> folderpage. Right ?
This is part of the new form inheritance. TFormFolder ia a inherited class
from TFolderPage, that's all. When you indicate that your form inherits from
it is just saying that it will be a FolderPage on runtime rather than a
Form.
> 2 - Is this class a generic to use with other applications ?
Yes. Just add the TFormFolder to any of your projects.
> 3 - To just add a form to a folder, methods New() and Create() from
> TFormFolder are sufficient. Right ?
Yes. Take a look at the code on Main form:
::oTabFac := TFrmFacturas():New( ::oFolder1 )
> 4 - Are InsertComponent() and RemoveComponent() methods of XFolderPage ?
> When are they called ? Is there some documantation about them ?
No, they are internal and internally called. You should not concern about
them.
> 5 - How did you created those classes that comes from TFormfolder (like
> TFrmClientes)? That's a regular form that you changed the "From" part
> directly in the code ? Right ?
Is just a regular form. And yes we just change the "From" part directly in
the code.
> 6 - In method New() from TFormFolder why do you call ::Createform() if it
> is Virtual (i thought a virtual method does nothing...what does Virtual
> means?)
Inheritance magic :-). CreateForm() is defined on lower classes like
TFrmClientes and it is the responsable of controls creation. We prototype as
VIRTUAL just to indicate that this class must be deployed by its child
classes. Is just a good programming practice.
Regards,
Ignacio Ortiz de Zúñiga
[OZ Software]
https://www.ozs.es
--
[Equipo de Xailer / Xailer team]
https://www.xailer.com
NoName
Mensajes: 531
Registrado: Vie Feb 03, 2006 7:27 pm

New Sample DbfData6

Mensaje por NoName »

Aguiar,
That is the project we showed in Xailer free technical journeys and it uses
some complex programming techniques that is difficult to explain on a few
lines. It took more than 8 hours to see the all project. BTW I try to give
you some clues, but you should learn through code I am afraid.
> 1 - TFormFolder is a class to add a form to a folder, or to have a form as
> folderpage. Right ?
This is part of the new form inheritance. TFormFolder ia a inherited class
from TFolderPage, that's all. When you indicate that your form inherits from
it is just saying that it will be a FolderPage on runtime rather than a
Form.
> 2 - Is this class a generic to use with other applications ?
Yes. Just add the TFormFolder to any of your projects.
> 3 - To just add a form to a folder, methods New() and Create() from
> TFormFolder are sufficient. Right ?
Yes. Take a look at the code on Main form:
::oTabFac := TFrmFacturas():New( ::oFolder1 )
> 4 - Are InsertComponent() and RemoveComponent() methods of XFolderPage ?
> When are they called ? Is there some documantation about them ?
No, they are internal and internally called. You should not concern about
them.
> 5 - How did you created those classes that comes from TFormfolder (like
> TFrmClientes)? That's a regular form that you changed the "From" part
> directly in the code ? Right ?
Is just a regular form. And yes we just change the "From" part directly in
the code.
> 6 - In method New() from TFormFolder why do you call ::Createform() if it
> is Virtual (i thought a virtual method does nothing...what does Virtual
> means?)
Inheritance magic :-). CreateForm() is defined on lower classes like
TFrmClientes and it is the responsable of controls creation. We prototype as
VIRTUAL just to indicate that this class must be deployed by its child
classes. Is just a good programming practice.
Regards,
Aguiar Costa
Mensajes: 115
Registrado: Jue Jun 01, 2006 7:21 pm

New Sample DbfData6

Mensaje por Aguiar Costa »

Ignacio,
Your answers were just fine...I will study the sample a little more...
Thanks.
Regards
Aguiar !!!
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> escreveu na mensagem
news:449ab8fc$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Aguiar,
>
> That is the project we showed in Xailer free technical journeys and it
> uses some complex programming techniques that is difficult to explain on a
> few lines. It took more than 8 hours to see the all project. BTW I try to
> give you some clues, but you should learn through code I am afraid.
>
>> 1 - TFormFolder is a class to add a form to a folder, or to have a form
>> as folderpage. Right ?
>
> This is part of the new form inheritance. TFormFolder ia a inherited class
> from TFolderPage, that's all. When you indicate that your form inherits
> from it is just saying that it will be a FolderPage on runtime rather than
> a Form.
>
>> 2 - Is this class a generic to use with other applications ?
>
> Yes. Just add the TFormFolder to any of your projects.
>
>> 3 - To just add a form to a folder, methods New() and Create() from
>> TFormFolder are sufficient. Right ?
>
> Yes. Take a look at the code on Main form:
>
> ::oTabFac := TFrmFacturas():New( ::oFolder1 )
>
>> 4 - Are InsertComponent() and RemoveComponent() methods of XFolderPage ?
>> When are they called ? Is there some documantation about them ?
>
> No, they are internal and internally called. You should not concern about
> them.
>
>> 5 - How did you created those classes that comes from TFormfolder (like
>> TFrmClientes)? That's a regular form that you changed the "From" part
>> directly in the code ? Right ?
>
> Is just a regular form. And yes we just change the "From" part directly in
> the code.
>
>> 6 - In method New() from TFormFolder why do you call ::Createform() if it
>> is Virtual (i thought a virtual method does nothing...what does Virtual
>> means?)
>
> Inheritance magic :-). CreateForm() is defined on lower classes like
> TFrmClientes and it is the responsable of controls creation. We prototype
> as VIRTUAL just to indicate that this class must be deployed by its child
> classes. Is just a good programming practice.
>
> Regards,
>
>
>
Aguiar Costa
Mensajes: 115
Registrado: Jue Jun 01, 2006 7:21 pm

New Sample DbfData6

Mensaje por Aguiar Costa »

Ignacio,
Your answers were just fine...I will study the sample a little more...
Thanks.
Regards
Aguiar !!!
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> escreveu na mensagem
news:449ab8fc$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Aguiar,
>
> That is the project we showed in Xailer free technical journeys and it
> uses some complex programming techniques that is difficult to explain on a
> few lines. It took more than 8 hours to see the all project. BTW I try to
> give you some clues, but you should learn through code I am afraid.
>
>> 1 - TFormFolder is a class to add a form to a folder, or to have a form
>> as folderpage. Right ?
>
> This is part of the new form inheritance. TFormFolder ia a inherited class
> from TFolderPage, that's all. When you indicate that your form inherits
> from it is just saying that it will be a FolderPage on runtime rather than
> a Form.
>
>> 2 - Is this class a generic to use with other applications ?
>
> Yes. Just add the TFormFolder to any of your projects.
>
>> 3 - To just add a form to a folder, methods New() and Create() from
>> TFormFolder are sufficient. Right ?
>
> Yes. Take a look at the code on Main form:
>
> ::oTabFac := TFrmFacturas():New( ::oFolder1 )
>
>> 4 - Are InsertComponent() and RemoveComponent() methods of XFolderPage ?
>> When are they called ? Is there some documantation about them ?
>
> No, they are internal and internally called. You should not concern about
> them.
>
>> 5 - How did you created those classes that comes from TFormfolder (like
>> TFrmClientes)? That's a regular form that you changed the "From" part
>> directly in the code ? Right ?
>
> Is just a regular form. And yes we just change the "From" part directly in
> the code.
>
>> 6 - In method New() from TFormFolder why do you call ::Createform() if it
>> is Virtual (i thought a virtual method does nothing...what does Virtual
>> means?)
>
> Inheritance magic :-). CreateForm() is defined on lower classes like
> TFrmClientes and it is the responsable of controls creation. We prototype
> as VIRTUAL just to indicate that this class must be deployed by its child
> classes. Is just a good programming practice.
>
> Regards,
>
>
>
Responder