Graphics4VO to vulcan
in [Visual Objects]
|
From: Fred Killet on 4 Nov 2009 07:23 Hello. can someone estimate how much is the effort, to rewrite Graphics4VO to Vulcan? Some people have the source code of Graphics4VO. Maybe someone already has translated the software to Vulcan? Kind regards, Fred -- Fred Killet killet-nospam(a)killetsoft.de
From: Brian on 4 Nov 2009 10:04 Fred, > can someone estimate how much is the effort, to rewrite Graphics4VO to > Vulcan? > Some people have the source code of Graphics4VO. Maybe someone already has > translated the software to Vulcan? Having never seen the code for Graphics4VO it would be hard to give you an _Exact_ answer, however in General: If GrafX4VO compiles under Visual Objects 2.8 SP3 with no errors with all warnings turned on, then it should be a few of day project. It will also help if your familiar with VS2008 but, language wise, Vulcan is extremely close to Visual Objects. About 98% of all code will simply compile & run in .NET If you can make it to VODC in Stuttgart this year (next week) I'm sure you can leave with a working version ! If not, send us the code, and we'll give you less speculative answer after VODC. BTW, Vulcan.NET support == "News1.cavo.com" with your favorite news group reader. Brian GrafXsoft http://www.GoVulcan.NET http://www.GrafXsoft.com
From: Fred Killet on 4 Nov 2009 10:46 Hi Brian, nice to heare from you! I wrote an email to your private email address. Now I have installed Visual Objects 2.8 SP2 (2830). On this version Graphics4VO compiles with the compiler options "Warnings all" and "Warnings as Errors" without any errors and warnings. Later I will send you the source of Graphics4VO to get a less speculative answer. Thank you! Fred -- Fred Killet killet-nospam(a)killetsoft.de
From: Dave Francis on 4 Nov 2009 11:05 Hi Fred, I've imported highly modified Graphics4VO code into Vulcan. Just like any other VO project, it is a case of working through warnings in 2.8 to produce perfectly clean code. In Graphics4VO's case, this was mainly redefining INT and DWORD variables or casting results. There were a couple of errors caused by ASSIGNS with the same name as METHODS. Then I think there are are 3 places where a callback function has to be rewritten to use a delegate. But that is less than 20 lines of code. In all, it took me about half a day. Be warned, though, that I have not yet run this library in anger, so there may be other issues. However, if the rest of the VO code we transported is anything to go by, there won't be. And I could not see anything in your code that looked "alien" to me :o) Of course, to convert it to pure .net means replacing all the Win32 graphics calls, but that is just a slog. Your graphics model fits better onto .net than it did on Win32, so you were ahead of the game! Great library, Fred Dave Francis "Fred Killet" <killet-nospam(a)killetsoft.de> wrote in message news:4af1725e$0$6562$9b4e6d93(a)newsspool4.arcor-online.net... > Hello. > > can someone estimate how much is the effort, to rewrite Graphics4VO to > Vulcan? > > Some people have the source code of Graphics4VO. Maybe someone already has > translated the software to Vulcan? > > Kind regards, > Fred > > -- > > > Fred Killet > killet-nospam(a)killetsoft.de >
From: Ginny Caughey on 4 Nov 2009 11:55 Dave, I have found the very same (minor) issues moving my VO serial class to Vulcan. And I have run it in anger <g> with a serial scale indicator sending constant output for hours and it works perfectly. -- Ginny Caughey www.wasteworks.com "Dave Francis" <dave(a)suilven.com> wrote in message news:7ldn2oF3c94prU1(a)mid.individual.net... > Hi Fred, > > I've imported highly modified Graphics4VO code into Vulcan. Just like any > other VO project, it is a case of working through warnings in 2.8 to > produce perfectly clean code. In Graphics4VO's case, this was mainly > redefining INT and DWORD variables or casting results. There were a couple > of errors caused by ASSIGNS with the same name as METHODS. Then I think > there are are 3 places where a callback function has to be rewritten to > use a delegate. But that is less than 20 lines of code. > > In all, it took me about half a day. Be warned, though, that I have not > yet run this library in anger, so there may be other issues. However, if > the rest of the VO code we transported is anything to go by, there won't > be. And I could not see anything in your code that looked "alien" to me > :o) > > Of course, to convert it to pure .net means replacing all the Win32 > graphics calls, but that is just a slog. Your graphics model fits better > onto .net than it did on Win32, so you were ahead of the game! > > Great library, Fred > > Dave Francis > > > > "Fred Killet" <killet-nospam(a)killetsoft.de> wrote in message > news:4af1725e$0$6562$9b4e6d93(a)newsspool4.arcor-online.net... >> Hello. >> >> can someone estimate how much is the effort, to rewrite Graphics4VO to >> Vulcan? >> >> Some people have the source code of Graphics4VO. Maybe someone already >> has translated the software to Vulcan? >> >> Kind regards, >> Fred >> >> -- >> >> >> Fred Killet >> killet-nospam(a)killetsoft.de >> > >
|
Next
|
Last
Pages: 1 2 Prev: bBrowser and getting a value to set a filter with Next: Please how translate code C to VO? |