You are not logged in.

Dear visitor, welcome to Jabaco - Community. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

nbarakat

Beginner

  • "nbarakat" started this thread

Posts: 11

Date of registration: May 24th 2010

  • Send private message

1

Monday, August 30th 2010, 1:08am

Referencing a sub class?

Hello community,

I was wondering if there is a way in Jabaco to create and reference a sub class (for example) similar to the ADODB referencing.

e.g.
Create a Recordset Class
Create an ADODB referencing the recordset class
in such a way that one can dim a variable like
Dim rs as ADODB.Recordset

and not Dim rs as Recordset

Thanks.

OlimilO

Intermediate

  • "OlimilO" is male

Posts: 277

Date of registration: Jan 18th 2009

Location: Germany

Occupation: software engineer

  • Send private message

2

Monday, August 30th 2010, 10:56am

Hi Nbarakat

Quoted

sub class

???

there is a certain windows-technologie called "subclassing" but compared to your problem it has nothing to do with it.
Answer to your question:
IF YOU HAD a namespace ADODB then you would use it in Jabaco like this:
A)

Jabaco Source

 
1

Dim rs As ADODB#Recordset

ADODB here is called a namespace.
A namespace is something like a basket where you group classes belonging together.
But IF YOU HAD a library you could reference the library with menu
Project->References
and import the namespace ADODB with

Jabaco Source

 
1

Import ADODB

then you could write, (and it's really the same like above A)
B)

Jabaco Source

 
1

Dim rs As Recordset

regards
OlimilO

nbarakat

Beginner

  • "nbarakat" started this thread

Posts: 11

Date of registration: May 24th 2010

  • Send private message

3

Monday, August 30th 2010, 9:00pm

Thanks OlimilO for the clarification and sorry about the terminology.



Iam working on a test program that reads DLL libraries (Classes, events, procedures/functions, and enumeration constants) for example the ADODB library and generates skeleton classes and modules that can latter (may)be imported into Jabaco. The skeleton procedure or sub could then be written to provide the same functionality as its VB counter part ...



Having to use the # between the namespace and class would still make it difficult to import code from vb referencing the ADODB library ... but maybe easier than to rewriting the code ???



Does anyone think this could be of help as personally even though I really like the Jabaco concept its still very difficult to get a mid to large size application to port without major changes. A lot of these changes will require a decent amount of Java programming which if acquired makes me wonder why not port directly to Java ...



Thanks again for your help

OlimilO

Intermediate

  • "OlimilO" is male

Posts: 277

Date of registration: Jan 18th 2009

Location: Germany

Occupation: software engineer

  • Send private message

4

Monday, August 30th 2010, 11:14pm

@Nbarakat Yes ... that depends on your point of view.

There is no explicit reason not to port your apps to any other programming language, and at the same time there is no special reason not to port your apps to Jabaco.

With Jabaco you could have the benefit and the chance to learn most of the software technologies that the Java-Framework deals with, even without the need to learn a completely new language in the first place.

regards

OlimilO

Similar threads

Rate this thread
WoltLab Burning Board