And now the news from VODC Germany
in [Visual Objects]
|
Prev: Vo 2.7 Garbage Collector
Next: CRC32
From: Don Caton on 14 Nov 2006 13:41 "ThomasO(a)cpas.com" <ThomasO(a)cpas.com> wrote in message news:1163528382.804650.175720(a)f16g2000cwb.googlegroups.com: > Don, > Thank you very much for this explanation. > Will you also support Classmate GUI classes? > We have several applications written using ClassMate GUI classes. > It would be nice way to convert them to .Net using Transporter. That is our intention, to export them to Vulcan using the transporter. We haven't tried that, we are still working on getting the VO SDK to compile (and we're very close). -- Don
From: GSchaller on 14 Nov 2006 16:42 Excellent... then I won't expect any further responses from you about me. Things should get quieter now. "Jamal" <vodotnet???@???yahoo.com> wrote in message news:6wm6h.5569$dh7.3636(a)trnddc01: > Just to let you know, you're now on my ignore list! No hard feelings but I'd > like to have some peace. >
From: hei_mue on 15 Nov 2006 01:42 Don, thank you for the answers. But there are a few more on my side now ;-) 1. How can I edit a VULCAN-Form (which means a transported VO-Window) in VS? 2. If 1. ist true: Can I add some new .NET-Controls to this VULCAN-Forms and can they interact with the VULCAN-Controls? 3. If 1 is false: Can I add .NET-Controls to the VULCAN-Form by code? Heiko Mueller
From: Ginny Caughey on 15 Nov 2006 07:45 Heiko, The second question is not really a Vulcan question: the way to add .NET controls to a Win32 form or the reverse is to use COM to glue the parts together. Microsoft even has a tool that automates that for interrop between VB6 and VB.Net apps. As to whether this is something you would want to do, that is up to you... Here is the link if you want more info: https://www.microsoft.com/downloads/details.aspx?FamilyId=98C38C1D-C630-4D9A-8BB5-7F1FC088A7C4&displaylang=en Obviously this tool is for VB language apps, but the concepts are the same between VO and Vulcan or between Win32 VO GUI forms written in Vulcan and Winforms forms written in Vulcan (or any other .NET language.) As for editing VO forms once they are in Vulcan, clearly this is something that Grafx could do since they already have the code inside the VO IDE that can generate VO code from a forms editor. They did not show such a tool at VODC, but they did say this was something they were still thinking about. More interestingly, Chris Pyrgus who is developing a VO-like IDE for Vulcan in Vulcan showed an early version of a tool to create VO GUI forms at VODC. Now Chris is a pretty smart guy, but I think if he can do it and he doesn't even have the source code to the VO IDE, then surely the guys at Grafx can too <g> so I suppose this isn't really rocket science. (And I don't mean any disprespect to Chris at all - his VIDE project is very nice and getting better all the time.) And one thing anybody could do is just continue to use VO to generate VO forms and re-Transporter them back into Vulcan. The attendees at VODC got a beta copy of the Vulcan Getting Started guide that makes all these things easier to visualize. I understand that this guide will be generally available on the web before too long. -- Ginny "hei_mue" <h.mueller(a)wincontent.de> wrote in message news:1163572955.807060.212580(a)k70g2000cwa.googlegroups.com... > Don, > > thank you for the answers. But there are a few more on my side now ;-) > > 1. How can I edit a VULCAN-Form (which means a transported VO-Window) > in VS? > > 2. If 1. ist true: Can I add some new .NET-Controls to this > VULCAN-Forms and can they interact with the VULCAN-Controls? > > 3. If 1 is false: Can I add .NET-Controls to the VULCAN-Form by code? > > Heiko Mueller >
From: Don Caton on 15 Nov 2006 09:36
"hei_mue" <h.mueller(a)wincontent.de> wrote in message news:1163572955.807060.212580(a)k70g2000cwa.googlegroups.com: > Don, > > thank you for the answers. But there are a few more on my side now ;-) > > 1. How can I edit a VULCAN-Form (which means a transported VO-Window) > in VS? We're still working on that, there are a couple of different ways we can handle that and we haven't decided which will be the best way. > 2. If 1. ist true: Can I add some new .NET-Controls to this > VULCAN-Forms and can they interact with the VULCAN-Controls? > > 3. If 1 is false: Can I add .NET-Controls to the VULCAN-Form by code? Neither of these scenarios will be officially supported, at least in 1.0. The VO GUI classes and Windows Forms have architectural differences, but some very preliminary testing has shown that Windows Forms windows can coexist with VO GUI classes windows. And there is a new NativeWindow class in .NET 2.0, so theoretically it should be possible to wrap a VO GUI class window in one of these and have it operate in the context of a Windows Forms-based application. I don't know whether this would be possible or practical for individual controls though. Our focus for 1.0 is just to get the VO GUI classes working in Vulcan so you can recompile your VO apps. in Vulcan. After that we can take a closer look at various migration options. Something like this would certainly make a good conference presentation. -- Don |