Vulcan .Net and VO 2.8
in [Visual Objects]
|
From: Karl Faller on 20 Sep 2006 05:21 Geoff, >learning Dot net from VB or C# will be a lot >easier because that is what all the books and samples are written in Heiko, >With a simple Click >you can convert Code from VB.NET to C#. Of course you can view VULCAN >Code as C#... If it were quite so simple, it shouldn't present any problem to convert the "tons of C# or VB Samples" out there into Vulcan - so...? Karl
From: hei_mue on 20 Sep 2006 07:05 Karl Faller schrieb: > If it were quite so simple, it shouldn't present any problem to > convert the "tons of C# or VB Samples" out there into Vulcan - so...? There are two problems: First - Lutz Roeder must include the VULCAN-language into his Reflector. I dont think that hee will do this ;-) Second - and thats really more important: I think if Reflector would support VULCAN and you converted this to C# the result doesn' t look really like a typical C# Application that uses the Classes in the .NET Framework but more a wrapper around the Win32-Api Calls. A SingleLineEdit shows not like a .NET Windows.Forms.Textbox but more like Code from VO-SDK. What I will say : I dont think that a SingleLineEdit in VULCAN is really a .NET Textbox and you cant use methods and so on from Textbox to this SingleLineEdit. Its a bit like ClassMate and VO-Framework. VO-Framework is the standard (like .NET Framework) and ClassMate exists beside this but with now way to interface with the otherone. Of course this is only my opinion because I cant see how VULCAN couldt transform VO-Dialogs into .NET Forms. But if you interested in VULCAN of course you couldt also ask the Dev-Team how they plan to handle such things. I think the only thing that VULCAN can really do to VO-Programmers is to translate the Code that calls not in the end to Win32-API into ..NET-Classes. A simple convert of complete Apps will IMHO never end in a really .NET App (as 'really' means that this App uses the .NET Classes for GUI and such things). A really convert from VO to .NET is much much more than a recompiling of the VO-SDK with the VULCAN-Compiler. For this things you must complete rewrite the SDK under the use of .NET Classes instead of Win32-API. But maybe I'm wrong and GrafX do the job like this (I dont believe that this is possible at all)... Ask them! Heiko Mueller
From: Ginny Caughey on 20 Sep 2006 07:15 Heiko, >> I understand Heiko's frustration that Vulcan is taking so long, but I > You misunderstud me - it isnt a frustration. I'm happy with C# now - > for my legacy applications I use VO2.7 and I can perfect live with this > constellation. My intention was to warn other people to set on GrafX > for their long time business strategy. Perhaps frustration was the wrong word. Maybe disappointment is better. I like C# too and have been using it for production for many years now - it's an easy language to like. But I think it's a stretch to complain that Grafx's failure to release Vulcan before it was ready was a bad business strategy. If you (and I) need .NET apps now, then obviously C# is a good choice. But that doesn't mean that I don't also see an important place for a tool like Vulcan for migrating exisiting VO code to .NET. It's a lot cheaper than paying a developer to do a total rewrite, however easy that is using C#. > About VULCAN: GrafX tells that their goal is a maximum on compatibility > to VO in the language. I think this promise awakes in peoples mind a > hope that they can convert to .NET with a simple recompilation. I think > thats simple not true. A window that converts from VO via VULCAN to > .NET isnt really a .NET-Form. It depends entirely on how the conversion is done. If the Vulcan Transporter could read the VO binaries (well of course it could!) and generate Windows.Forms equivalents to the old forms, that sounds like the best of both worlds, since the Vulcan form editor is the same one used by C# and VB and generates Windows.Forms code. Of course if I were to refactor my big VO apps the way I now do my smaller C# apps, the business and data access layers would be separate from the GUI anyway. I hope to do this some day for the big apps, but the refactoring tools in VS are so good, and I am so busy with other work, that I'm content to wait for now. Ginny
From: Geoff Schaller on 20 Sep 2006 07:22 Karl, Really? Are you offering? I doubt GrafX is or will. That is my point. There will be very little support for Vulcan compared with what is available for C# and VB. Geoff > > If it were quite so simple, it shouldn't present any problem to > convert the "tons of C# or VB Samples" out there into Vulcan - so...? > > Karl
From: Ginny Caughey on 20 Sep 2006 07:34
Geoff, >2 weeks and you will be perfectly fluent in C# > 2 months and you will match your VO productivity (mostly) This is probably true. But how long is it taking you to recreate your big VO apps in C#? Or are you even attempting that? Ginny |