Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #8491

Re: What is the future of CA Visual-Object (CAVO)

Path csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From "Wolfgang Riedmann" <wriedmann@gmail.com>
Newsgroups comp.lang.clipper.visual-objects
Subject Re: What is the future of CA Visual-Object (CAVO)
Date Wed, 7 Oct 2015 09:59:10 +0200
Lines 53
Message-ID <d7k1mhFeoskU1@mid.individual.net> (permalink)
References <dfdedf9e-f6d2-41e9-bdc3-c054404495af@googlegroups.com>
Mime-Version 1.0
Content-Type text/plain; charset=iso-8859-1
X-Trace individual.net U/zUtjY40o/vlJaMSB4KwAkmjSEYvewYJUWDnCeYm8+vUUFbk=
Cancel-Lock sha1:uyvv+boRVXOy1SmM9MI8xcEagWQ=
User-Agent XanaNews/1.18.1.6
Xref csiph.com comp.lang.clipper.visual-objects:8491

Show key headers only | View raw


Hi Hanz,

I'll try to answer your question:

CA-VO is coming from Clipper, in MS-DOS times one of the most used
programming languages for business software.

The architects of VO (short for Visual Objects) took several ideas from
Clipper, like codeblocks, arrays and the garbage collector combined
with the internal macro compiler and ported them to the Windows
platform, initially Win16 (Windows 3.1), and then Win32 (starting with
Windows 95).

Personally, I'm working with VO since it is available, and IMHO it is
still the most productive development platform you can find for the
Win32 platform.
On the one side, you have high level libraries like the GUI, the RDD
and the SQL classes, combined with potent string and array functions,
codeblocks and a very clean language.
On the other side, you can go down like with C and make manual memory
allocations, pointer aritmetics and other low level functions.

The main problem of VO now is the problem of the platform itself: Win32
has its age, and will be replaced sometimes by the .NET platform.
Therefore GrafX, the distributor of VO, has created a new product,
Vulcan.NET, that is highly compatible to VO, and now another company
has plans to launch another compatible product, XSharp (that currently
is in development). Vulcan.NET actually ships in version 4.

VO applications are rock solid, as is the development environment. One
of the revolutions of VO (unfortunately missing in Vulcan.NET and
XSharp) is the repository and the entity based compile process.

If you have other questions, please ask.

HTH

Wolfgang


> I'm really new to this company that i'm currently working. They gave
> me this assignments (CAVO) for my work. I would like to ask anyone
> with technical background to tell me if this has great future or
> something that is on a sinking ship. What's the current state of
> CAVO? What could I learn from this? If you don't mind, I would also
> like to hear about some history lesson. Googling this subject does
> not come up with too many results. Even troubleshooting is very
> difficult. Thank you.



-- 

Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

What is the future of CA Visual-Object (CAVO) Hanz Schultz <pemotongrumput92@gmail.com> - 2015-10-07 00:35 -0700
  Re: What is the future of CA Visual-Object (CAVO) "Wolfgang Riedmann" <wriedmann@gmail.com> - 2015-10-07 09:59 +0200
    Re: What is the future of CA Visual-Object (CAVO) Hans Schultz <pemotongrumput92@gmail.com> - 2015-10-07 01:13 -0700
      Re: What is the future of CA Visual-Object (CAVO) "Wolfgang Riedmann" <wriedmann@gmail.com> - 2015-10-07 11:01 +0200
      Re: What is the future of CA Visual-Object (CAVO) "Wolfgang Riedmann" <wriedmann@gmail.com> - 2015-10-07 15:49 +0200
  Re: What is the future of CA Visual-Object (CAVO) nicktekhne@googlemail.com - 2015-10-07 03:35 -0700

csiph-web