And now the news from VODC Germany
in [Visual Objects]
|
Prev: Vo 2.7 Garbage Collector
Next: CRC32
From: Jamal on 14 Nov 2006 11:53 Just to let you know, you're now on my ignore list! No hard feelings but I'd like to have some peace. "GSchaller" <geoxff(a)soft_ware.com.au> wrote in message news:45597a00(a)dnews.tpgi.com.au... > Jamal, > >> You say that you will evaluate Vulcan, I say, don't! Because you will >> just >> create so many useless threads and jump on people throats as always! It's > > Hmmm... so you are already predicting that there will be many problems. > Interesting. However, I will do what is professionally responsible to do. > I was part of the original putsch for Vulcan and I intend to see it > through. > >> BTW, Ginny has been very nice to you but you have been very abusive. >> You're >> just pushing you luck because you will end up in a lot of people's ignore >> list! > > Abusive? ...there we go again. Is your skin that thin? What I've said here > is nothing in comparison to what you've said to me in this forum so go > take a happy pill and a nice lie down. > > There. Pleasant enough for you? <g> > > Geoff > >
From: Don Caton on 14 Nov 2006 12:09 "hei_mue" <h.mueller(a)wincontent.de> wrote in message news:1163411549.537382.62660(a)m7g2000cwm.googlegroups.com: > Good to know that my decision to switch to C# was the absolut right > one. This facts say to me, that a conversion to .NET without rewrite > the most GUI-Code is not possible. This way of 'Transportation' is only > feasible with VO-StandardWindows and VO-StandardControls. All > CustomControls and the most of our own methods in derived classes will > not work correct / or will not work correct after this way of > conversion. I think this will break many many code and is one of the > fact that a switch from VO to VULCAN is not much differently from a > switch from CLIPPER to VO - and you guys should know what this means... > > Be I the only one who can see this fact? There are no facts in your message. I don't know what leads you to believe that custom controls and your own methods in derived classes would not work properly after this hypothetical "conversion". The transporter performs two functions. The first one is to "clean up" your existing VO code. The Vulcan.NET compiler is stricter than VO, and is based on a very well-defined set of language rules. VO's compiler is less strict and allows a number of things that are syntactically questionable or inconsistent. The transporter will change things like "NEXT i" to "NEXT // i", "FOR x = ..." to "FOR x := ...", "WHIL" to "WHILE" and so on. These are minor syntactical changes that do not affect how the code is compiled or executed, and it is important to understand that these changes do _NOT_ result in code that is incompatible with VO. The second function that the transporter does is to export an application from the VO repository into .prg and .rc files, and the creation of a Visual Studio project file. The transporter does nothing to break your code, and as we have said repeatedly over the last two years, Vulcan.NET is designed to be as compatible with VO as we can possibly make it. That includes the GUI and other classes in VO. We have never said that these would not be compatible, in fact we have said on numerous occasions that VO-compatible GUI and other classes will in fact be supplied with Vulcan.NET. Whether moving to C# was the right decision for you is something only you can determine, but your speculations about what will and will not compile in Vulcan are incorrect. -- Don
From: hei_mue on 14 Nov 2006 12:45 > Whether moving to C# was the right decision for you is something only > you can determine, but your speculations about what will and will not > compile in Vulcan are incorrect. That wasn't a speculation but a description how I understand the 'transporter'. So here are my final question: I have a window with two SingleLineEdits (class mySingleLineEdit) and two CustomControls (with very heavy drawing and many interactions). When I use the transporter to switch to Vulcan this Window/Code is converted in Classes that are derived from the converted VO-Framework in VULCAN and NOT from TextBox (Sle's) and UserControl (CustomControls) - the window is not derived from Form-Class. After the transport this Window can not be edited in VS FormDesigner? To Edit the Window in the VS-Designer I must use a second Window which is also created by the 'Transporter'? The Controls in this Window are two TextBox and two UserControls but this Controls know nothing from my own functionality (in mySingleLineEdit and my own CustomControl classes)? So to convert the window in a window that I can edit in the VS-Designer I must rewrite the classes mySingleLineEdit and myCustomControls based on TextBox and UserControl? Is this correct or how works it really? Heiko Mueller
From: Don Caton on 14 Nov 2006 13:14 "hei_mue" <h.mueller(a)wincontent.de> wrote in message news:1163526319.567135.123780(a)h54g2000cwb.googlegroups.com: > > Whether moving to C# was the right decision for you is something only > > you can determine, but your speculations about what will and will not > > compile in Vulcan are incorrect. > That wasn't a speculation but a description how I understand the > 'transporter'. So here are my final question: > > I have a window with two SingleLineEdits (class mySingleLineEdit) and > two CustomControls (with very heavy drawing and many interactions). > When I use the transporter to switch to Vulcan this Window/Code is > converted in Classes that are derived from the converted VO-Framework > in VULCAN and NOT from TextBox (Sle's) and UserControl (CustomControls) > - the window is not derived from Form-Class. After the transport this > Window can not be edited in VS FormDesigner? To Edit the Window in the > VS-Designer I must use a second Window which is also created by the > 'Transporter'? The Controls in this Window are two TextBox and two > UserControls but this Controls know nothing from my own functionality > (in mySingleLineEdit and my own CustomControl classes)? So to convert > the window in a window that I can edit in the VS-Designer I must > rewrite the classes mySingleLineEdit and myCustomControls based on > TextBox and UserControl? Is this correct or how works it really? No, this is not correct. Your existing VO code will export unchanged. The transporter does not "convert" anything, except for the syntactical cleanup things I mentioned. The code exported by the transporter is semantically and functionally identical to what it is in VO. There are a few minor things which are different in Vulcan, and if the transporter finds any of these, a note will be made in the log file alterting you to anything which may need to be reviewed. For example, operator methods in Vulcan have a different signature than in VO, so those will have to be modified in order to work in Vulcan. Existing VO windows classes cannot be edited in the Visual Studio forms editor. We are working on a way to edit those windows but the VS windows editor only works with Windows Forms-based windows. If (and I stress _IF_) you would like to migrate your existing VO-GUI Class-based windows to Windows Forms, another utility will be able to take an existing VO window entity and generate a Windows Forms window. This will not convert any code such as event handlers since the event handling model for the VO GUI classes is a little different than for Windows Forms. But it gives you a starting point by duplicating the window layout and anything else that maps 1:1 from the VO GUI classes to Windows Forms. But this is something completely separate from exporting code and compiling it in Vulcan. The GUI classes in VO will be available in Vulcan if you choose to continue to use them. This is only an option if you want to migrate existing windows from the VO GUI classes to Windows forms, and it allows you to do it one form at a time. -- Don
From: ThomasO on 14 Nov 2006 13:19
Don Caton wrote: > "hei_mue" <h.mueller(a)wincontent.de> wrote in message > news:1163411549.537382.62660(a)m7g2000cwm.googlegroups.com: > > > Good to know that my decision to switch to C# was the absolut right > > one. This facts say to me, that a conversion to .NET without rewrite > > the most GUI-Code is not possible. This way of 'Transportation' is only > > feasible with VO-StandardWindows and VO-StandardControls. All > > CustomControls and the most of our own methods in derived classes will > > not work correct / or will not work correct after this way of > > conversion. I think this will break many many code and is one of the > > fact that a switch from VO to VULCAN is not much differently from a > > switch from CLIPPER to VO - and you guys should know what this means... > > > > Be I the only one who can see this fact? > > There are no facts in your message. I don't know what leads you to > believe that custom controls and your own methods in derived classes > would not work properly after this hypothetical "conversion". > > The transporter performs two functions. The first one is to "clean up" > your existing VO code. The Vulcan.NET compiler is stricter than VO, and > is based on a very well-defined set of language rules. VO's compiler is > less strict and allows a number of things that are syntactically > questionable or inconsistent. > > The transporter will change things like "NEXT i" to "NEXT // i", "FOR x > = ..." to "FOR x := ...", "WHIL" to "WHILE" and so on. > > These are minor syntactical changes that do not affect how the code is > compiled or executed, and it is important to understand that these > changes do _NOT_ result in code that is incompatible with VO. > > The second function that the transporter does is to export an > application from the VO repository into .prg and .rc files, and the > creation of a Visual Studio project file. > > The transporter does nothing to break your code, and as we have said > repeatedly over the last two years, Vulcan.NET is designed to be as > compatible with VO as we can possibly make it. That includes the GUI > and other classes in VO. We have never said that these would not be > compatible, in fact we have said on numerous occasions that > VO-compatible GUI and other classes will in fact be supplied with > Vulcan.NET. > > Whether moving to C# was the right decision for you is something only > you can determine, but your speculations about what will and will not > compile in Vulcan are incorrect. > > -- > Don 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. Thank you Thomas Olszewicki CPAS Systems Inc. |