Vulcan or Cavo 2.8 ?
in [Visual Objects]
|
Prev: WIN32SDK Reference
Next: Date converting
From: Karl Faller on 19 Jan 2008 04:57 On Sat, 19 Jan 2008 08:33:51 +0000, Will Chapman <nbQuidditch(a)dsl.pipex.com> wrote: >So if your objective >is simply to create a Windows version of your Clipper app then >VO may well be the easiest route (Vulcan is not yet fully mature >and I doubt that there are any people out there who have done >a Clipper -> Vulcan conversion). FTR, Rod da Silva has a Clipper-DotNet migration Tool based on CULE - you might have a look at http://www.softwareperspectives.com/culeplace/Default.aspx?tabid=61 HAND Karl
From: jotinhaPT on 19 Jan 2008 15:13 I'm familiar with Java, which is, as far as I know, similar to C#. About choosing a new environment, the big questions are the ability to deal with my databases, how easy it is to develop an entire application and the future as a programming language. For example, about Visual Objects, there are few resources on the net, looks like that it will end in a near future. VO or Vulcan, as far as I know, can use some parts of the Clipper code, without having to rewrite them, but if neither VO or Vulcan are the best choice, I'm open to move to other language.
From: Ginny Caughey on 19 Jan 2008 16:11 Do your databases need to remain DBF files? Do you need to be able to access them simulaneously with Clipper applications? -- Ginny www.wasteworks.com Software for the Solid Waste Industry "jotinhaPT" <carnaxide(a)tugamail.pt> wrote in message news:47925a02$0$27833$a729d347(a)news.telepac.pt... > I'm familiar with Java, which is, as far as I know, similar to C#. > About choosing a new environment, the big questions are the ability to > deal with my databases, how easy it is to develop an entire application > and the future as a programming language. For example, about Visual > Objects, there are few resources on the net, looks like that it will end > in a near future. > VO or Vulcan, as far as I know, can use some parts of the Clipper code, > without having to rewrite them, but if neither VO or Vulcan are the best > choice, I'm open to move to other language. >
From: Will Chapman on 20 Jan 2008 01:31 Graham McKechnie wrote: > Why would someone who doesn't know VO even contemplate going to Vulcan > when the rest of the world has already gone C#. > Because his legacy code is in Clipper? Of course, it is difficult to make good judgement without seeing the coding style, but it shouldn't take him very long to try converting his code in the free versions of C# and Vulcan (and his existing copy of VO2.8). He has, however, indicated ted that his code is heavily reliant on DBF-based data and IMO that suggests that he will have quite a bit of business logic that will be more straightforward to convert to VO or Vulcan. -- Will Chapman Save Our Waterways www.SaveOurWaterways.org.uk
From: Geoff Schaller on 27 Jan 2008 20:46
From scratch? You are probably better going with C#, especially if you have some Java knowledge. The language and syntax will be familiar. But you should also grapple with the conversion of your DBFs to SQL. Geoff "jotinhaPT" <carnaxide(a)tugamail.pt> wrote in message news:47918fb6$0$27804$a729d347(a)news.telepac.pt: > Hi again > > Today I read about the Vulcan .NET for the first time. My doubt now is: what > fits better my purpose of migrating Clipper apps to Windows, CAVO 2.8 or > Vulcan ? > > I appreciate any opinions and advices from the grupou community. > > TIA |