Re: Vulcan 1.0 (or 0.1?) released
I don't use DataWindows, but if you or Geoff like them, you can continue to
use them in Vulcan. If you choose to convert them to something else, then
maybe you have to learn a little bit about .NET data binding, which is
powerful, but there's nothing that requires you to change your code if you
"EŽ!k \/isser" <firstname.lastname@example.org> wrote in message
> Geoff has got a point IMO. Perhaps it is different if you use (classmate/)
> forms with your own gather/scatter, if you use datawindows and/or
> datadialogs it is a 'lttle' more work to do before you have a winform act
> the same. This is ofcourse not a mission impossible, but it is not only
> about changing the eventhandlers.
> I think it would be a good idea if (Chris?) the VO bin-editors in VIDE
> would be able to work inside VS as well.
> "Ginny Caughey" <email@example.com> schreef in bericht
>> Hi Geoff,
>> I guess you didn't read my previous messages. You can indeed use your VO
>> GUI form binaries Chris Pyrgas's VIDE already does that. I have seen it
>> working. It is so easy to use that even Dick (sorry Dick <g>) sees it as
>> a viable possibility. It doesn't store the forms in the same binary
>> format as VO, but it stores them in a format that allows you to edit them
>> using its forms editor that works much like VO and it generates normal
>> Vulcan code which you could use with Visual Studio or Notepad or whatever
>> you like. Since there's no repo with .NET, there's no import/export
>> hassle after the initial transporter step.
>> So you have two choices when you need to modify a form. 1) You can just
>> continue to modify it using VIDE and not change any of your Vulcan code.
>> Or 2) you can choose at that point to convert that one form to a
>> Windows.Forms.Form form, changing your event handlers slightly to match
>> the signature of Windows.Forms. You can still use these new forms
>> alongside all the others you didn't change yet so you can gradually
>> changed the forms in your app as they require maintenance.
>> Whether you choose 1 or 2 or 3) leaving the app in VO or 4) rewriting the
>> app from scratch or 5) writing new stuff in C# or Vulcan and exposing it
>> to VO as a COM server is up to you. I have some apps I've already
>> rewritten, some I've decided to leave in VO, and some I've decided to
>> break up into smaller apps and libraries for easier maintenance including
>> exposing functionality as COM, rewriting parts and keeping parts as they
>> are. I wouldn't presume to tell you which you should do with your apps.
>> But I will tell you when you make statements like such and such a thing
>> can't be done and indeed it can be done and quite easily. Amazingly there
>> are apparently a couple of people out there who read these newsgroup
>> posts who think you know what you're talking about, so I have to help you
>> when you get it completely wrong. <g>
>> "Geoff Schaller" <firstname.lastname@example.org> wrote in message
>>> Sorry Ginny but you are utterly wrong.
>>> It is you who is spreading misinformation by suggesting that a VO'er can
>>> take their app and fully port it to Vulcan. Yes it might (...might!)
>>> compile and even run but you WILL NOT BE ABLE TO EDIT windows, menu or
>>> server binaries. This is totally and utterly useless. No other word.
>>> Don't get me started in Vo2Ado....
>>> So what happens when you need a window mod?
>>> It is back to 2.8, modify your window and reconvert to Vulcan.
>>> What a nonsense.
>>> What a Joke!
>>> A sick joke in fact. All that effort for a product that only partially
>>> implements the framework and only partially supports VS and only
>>> partially converts from VO.
>>> Sheesh, is this the biggest con job we've seen yet?
>>> "Ginny Caughey" <email@example.com> wrote in message
>>>> > Well now here are where the bulk of us sit. But the bulk of us also
>>>> > use
>>>> > Window and server and menu editors. If your app relies on these
>>>> > things you
>>>> > will BE UNABLE TO USE VULCAN. Pure and simple.
>>>> Why do you say this? It is not correct. Spreading misinformation does
>>>> make people respect you or value your opinions.