ANN: Facelift Professional for VO - v1.04
in [Visual Objects]
|
From: Ginny Caughey on 12 Aug 2010 11:39 Sounds good. Does it do WPF as well? -- Ginny Caughey www.wasteworks.com
From: Willie Moore on 12 Aug 2010 12:02 Erik, Vulcan is a really nice dotNet compiler. When the transporter was started, everyone said VO compatibility. Facelift is NOT VO compatibility. It is native Winforms/WPF forms. When I moved my main VO app, I went with Winforms and redrew all of my vo screens (wish facelift had been there for that). I did transport my business logic but I don't use any of the VO compatibility classes. I like the idea that someone wrote a product that will take some of the pain of redrawing the screens. BTW, for VN2, Fabrice has some extensions that reformats the keywords and does declaration/assignment aligning. But you have to be running VS 2010 to be able to use those. Regards, Willie __________ Information from ESET NOD32 Antivirus, version of virus signature database 5361 (20100812) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Willie Moore on 12 Aug 2010 12:05 Jorge, I am doing a session at VODC on "After the Transporter". I will be covering how to integrate the 3rd party products with their new Vulcan equivalents. I will also be covering how to deal with code that the transporter doesn't handle. Hope to see you in Stuttgart in November! Regards, Willie "Jorge" <jorgeaccinelli(a)dextrasistemas.com.ar> wrote in message news:d33c4853-777d-4493-8899-f90921288cb6(a)5g2000yqz.googlegroups.com... > On 11 ago, 09:57, "Ginny Caughey" > <ginny.caughey.onl...(a)wasteworks.com> wrote: >> Congratulations, Paul! Very useful. I look forward to trying it out. >> >> -- >> >> Ginny Caugheywww.wasteworks.com > > > > Hello ! > > IF I have a vo application with extended use of bBrowser, > bArrayserver, seuixp classes, RightSle etc. What equivalences > I will meet in the new .net solution ? I know there is > in vulcan net version of all these classes , But what will > happen If I try a direct conversion ? > > Best Regards > Jorge Accinelli > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 5361 (20100812) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 5361 (20100812) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: E®!k /!$$E® on 12 Aug 2010 16:03 Willie, Nobody (at least as far as I know) ever stated VO compatibility only works when Win32 API functions are used. Like the Vulcan runtime functions, most/all of them are wrappers around .Net framework methods. I would think a logic next step is not to use tons of pInvokes to get a datawindow, but to rewrite it using the Winform class. Same story for all VO controls, dataserver This is not a trivial task at all, even I could do it. In fact I did it for the dialog window class (I did not use the datawindow very often lately in VO) and for the VO2ADO-dataserver, at least for the functionality I use. But not in Vulcan of course, but that does not really matter. This all can be done with the same level of VO compatibility as Vulcan has. OK, the event handling is different so that needs manual changes, but I would choose for some good old handwork with a full .NET result rather than a run-once transporter resulting a Win32 bound solution. My VO apps run fine on Win32 so why would I want to port that towards .NET? So the fact a devteam member launches a 3pp for the VO binaries to port to ..NET, it means Vulcan itself is not going to move further towards a real ..NET environment. Erik "Willie Moore" <williem(a)wmconsulting.com> schreef in bericht news:i415vc$e1g$1(a)speranza.aioe.org... > Erik, > > Vulcan is a really nice dotNet compiler. When the transporter was started, > everyone said VO compatibility. Facelift is NOT VO compatibility. It is > native Winforms/WPF forms. > > When I moved my main VO app, I went with Winforms and redrew all of my vo > screens (wish facelift had been there for that). I did transport my > business logic but I don't use any of the VO compatibility classes. > > I like the idea that someone wrote a product that will take some of the > pain of redrawing the screens. BTW, for VN2, Fabrice has some extensions > that reformats the keywords and does declaration/assignment aligning. But > you have to be running VS 2010 to be able to use those. > > Regards, > Willie > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 5361 (20100812) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > >
From: E®!k /!$$E® on 12 Aug 2010 16:03
Ginny, See my comment towards Willie Erik "Ginny Caughey" <ginny.caughey.online(a)wasteworks.com> schreef in bericht news:4c6408b1$0$9842$c3e8da3(a)news.astraweb.com... > Erik, > > I think Facelift is a different vision than what many people want with > Vulcan. It is not a transport-compile-run sort of conversion. It does a > lovely job of moving the form binaries to Windows.Forms (and apparently > WPF as well), but you'd still have to write your own event handlers. > Probably in Vulcan you could reuse a lot of VO code for this, but it isn't > no-touch. And unless it's smart enough to figure out all the ways I've > used inheritance and Classmate to get my controls to behave the way I > want, there's a manual step there too, mainly for masked edits which are a > different control type. In fact I'd like to see some configuration options > as to how my controls map to .NET ones. And maybe Paul has that already. > > -- > > Ginny Caughey > www.wasteworks.com > > > > |