Alternatives
in [Visual Basic]
|
From: "Bill McCarthy" TPASoft.com Are Identity on 22 Jan 2009 21:53 Hi Olaf, "Schmidt" <sss(a)online.de> wrote in message news:OBPnYyFfJHA.4868(a)TK2MSFTNGP05.phx.gbl... > > "Bill McCarthy" <TPASoft.com Are Identity Thieves> schrieb im Newsbeitrag > news:%23Bt5yODfJHA.3668(a)TK2MSFTNGP03.phx.gbl... > >> > You have to use the WinApi -Keyword instead of "Declare" >> > >> Thanks. I would never have guessed that one. Why the change ? > I assume there will be additional Keywords, to indicate > different OS-Platforms. That still doesn't require a change. As you said, they would be *additional* keywords. > > >> Okay but how do I do EnumChildWindows or CopyMemory ? >> I can't get AddressOf, or VarPtr etc to work. >> Is As Any supported too ? > Please ask in the appropriate Forum - I'm not the > developer - if I'd be Manuel I'd probably ask you: > What do you want to achieve? > And then recommend the appropriate Java-Classes. > And that is exactly my point. First, the way you do this in Vb6 does NOT work. The answer is not bovious. There's no docuemtnation, so you have ot psot ot a forum to try ot find out how to do what you already cna do in Vb6. And then the likely answer is to be to use some Java class instead, of which you are unlikely ot find any sampels of it's use in Jabaco, instead the samples will all be in Java. So as I said earlier, your VB6 code doesn't port to Jabaco, and if you are going to learn Java, then best to actually learn Java. Lots more tools and samples and documentation for the offering and you aren't tied to one man's proprietary work. > >> >> Type libraries: not supported. >> > That's COM - for COM there's already a great tool >> > out there, you know... >> > >> And you can't integrate with it. > Why should I use a tool which offers access to the > whole world of Java-Classes and then use COM, > if the same functionality is already available "natively"? > Because you have exisitng code assets or want to work with your exisitng code. In this aspect, VB.NET is miles better than Jabaco as you can use your exisitng assets as COM components. You can use COM inside VB.NET and Vb.NET from COM. > OMG - I can only hope, that more .NET-devs think > like you about that "integration-topic" - the more > COM you integrate into your .NET-Apps the better - > that long will VB6 work too - fine, wonderful - another > extra-decade on top of the VB6-lifespan. :-) > Well I think they do. Most are very pragmatic actually. And the COM/VB6 runtimes are indeed with Vista, Windows 2008 and Windows 7, so yes at least another 7 years if not ten. Guess that's another reason to avoid Jabaco until it addresses that huge gap it currently has. >> >> As I said, there is no roadmap or inidcation of where he >> is taking it. > Not yet... > Yet another reason.. > >> Well there's that or plenty of other ones. And there is >> COM interop. Jabaco has none of these. > Again - why COM-Interop, when we have pure COM > available with VB6? > Existing code assets. >> Visual Studio is in broad use within Microsoft as is the >> .NET framework. > LOL > VS6 was in broad use within Microsoft as well as the > COM-environment....(just a reminder). > Right and still is. > >> I said it doesn't work with most of my VB6 code. > As well as .NET does for my VB6-Code. > I get a lot more of my VB6 code to work in .NET than I can with Jabaco, by a mile !! And stuff that doesn't convert easily I can still use via COM. Jabaco doesn't offer that, instead you have to re-write, redesign everything.
From: Schmidt on 23 Jan 2009 08:14 "Bill McCarthy" <TPASoft.com Are Identity Thieves> schrieb im Newsbeitrag news:uerciXQfJHA.5496(a)TK2MSFTNGP02.phx.gbl... > >> Okay but how do I do EnumChildWindows or CopyMemory ? > >> I can't get AddressOf, or VarPtr etc to work. > >> Is As Any supported too ? > > Please ask in the appropriate Forum - I'm not the > > developer - if I'd be Manuel I'd probably ask you: > > What do you want to achieve? > > And then recommend the appropriate Java-Classes. > > And that is exactly my point. First, the way you do this in > Vb6 does NOT work. In the same way as my Declares have to be retyped (or at least "double-checked again") in .NET. > The answer is not bovious. There's no docuemtnation, > so you have ot psot ot a forum ... I can only repeat - the project has just started - give it some time... > And then the likely answer is to be to use some Java > class instead, Yep - in the same way as you should use a .NET-class, if there's already an SysAPI-wrapper available in the framework... > of which you are unlikely ot find any sampels of it's > use in Jabaco, instead the samples will all be in Java. In either case you will have to know (or learn) your lib which you program against in either case. And there's no different calling convention for different class-types of the Java-Lib - once you understood the VB-style Java-Lib-access, the entire Java-functionality is "at your fingertips". > So as I said earlier, your VB6 code doesn't port to > Jabaco, ... And as I said earlier - that holds true also for .NET. > and if you are going to learn Java, then best to actually > learn Java. Why? Java (also .NET/Mono) are mainly class-libraries, which can be accessed with different languages (you can use the Java Libs in Basic-style now, but also with many different languages). > Lots more tools and samples and documentation for the > offering and you aren't tied to one man's proprietary work. Better to be tied to a one mans proprietary work who *does* care (and is in the long run backed up by a community), than to be tied to MS, which apparently do *not* care. > Because you have exisitng code assets or want to work > with your exisitng code. Heh, seems you got it now Bill - we want our existing code assets (proven and tested code) to work further. It just is not possible currently, because the worlds largest software-vendor does not care about its customers. So, why not choose alternative offers from other vendors - that's the trust topic we talk about here for many years now. > In this aspect, VB.NET is miles better than Jabaco ... No - definitely not - see above. > Well I think they do. Most are very pragmatic actually. Great news - then I can safely use my VB6 further. > And the COM/VB6 runtimes are indeed with Vista, > Windows 2008 and Windows 7, so yes at least > another 7 years if not ten. Thanks for confirmation. > Guess that's another reason to avoid Jabaco until it addresses > that huge gap it currently has. Give-it-some-time-it-has-just-started... > >> Well there's that or plenty of other ones. And there is > >> COM interop. Jabaco has none of these. > > Again - why COM-Interop, when we have pure COM > > available with VB6? > > > Existing code assets. Which I can use within VB6 for another 10 years as you just wrote above. > >> I said it doesn't work with most of my VB6 code. > > As well as .NET does for my VB6-Code. > > I get a lot more of my VB6 code to work in .NET ... "A lot more" is by far not enough Bill - and then there's the already mentioned "trust-topic" on top of that. Olaf
From: Mike Williams on 23 Jan 2009 10:43 "Bill McCarthy" <TPASoft.com Are Identity Thieves> wrote in message news:uerciXQfJHA.5496(a)TK2MSFTNGP02.phx.gbl... > There's no docuemtnation, so you have ot psot ot a forum Docuemtnation! Ot psot ot a forum! Have you been on the sheep dip again, McCarthy?
From: C Kevin Provance on 23 Jan 2009 16:11 "Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote in message news:%23oRsjFXfJHA.3716(a)TK2MSFTNGP06.phx.gbl... | Docuemtnation! Ot psot ot a forum! Have you been on the sheep dip again, | McCarthy? Or rather, dipping in the sheep. <g>
From: "Bill McCarthy" TPASoft.com Are Identity on 24 Jan 2009 00:51
Hi Olaf, "Schmidt" <sss(a)online.de> wrote in message news:e%23$$k0VfJHA.2180(a)TK2MSFTNGP05.phx.gbl... > > I can only repeat - the project has just started - give it > some time... > Well given it has no documented roadmap and remains proprietary, NOT open source, I fail to see why I should give it anything. >> And then the likely answer is to be to use some Java >> class instead, > Yep - in the same way as you should use a .NET-class, > if there's already an SysAPI-wrapper available in the > framework... > The point you are missing is there are many samples for .NET, and many samples for Java. >> of which you are unlikely ot find any sampels of it's >> use in Jabaco, instead the samples will all be in Java. > In either case you will have to know (or learn) your lib > which you program against in either case. Again, the examples (and free and open source tools) for Java are all generally in Java. so to learn to use the Java libraries, the best startign point would be Java as then you also understand why there are issues with things like VarPtr, StrPtr, determinalistic finalization etc, etc. > >> So as I said earlier, your VB6 code doesn't port to >> Jabaco, ... > And as I said earlier - that holds true also for .NET. > Nonsense. There's the upgrade wizard and some great third party ones. And, most importnatly you can use your exisitng VB6 code via COM. >> and if you are going to learn Java, then best to actually >> learn Java. > Why? Java (also .NET/Mono) are mainly class-libraries, Because of the wealth of exampels already out there in Java and the wealth of open source tools out there too. > >> Lots more tools and samples and documentation for the >> offering and you aren't tied to one man's proprietary work. > Better to be tied to a one mans proprietary work who > *does* care Cares about making a buck. If he cared about the community he would make it open source . >> Because you have exisitng code assets or want to work >> with your exisitng code. > Heh, seems you got it now Bill - we want our existing > code assets (proven and tested code) to work further. Huh huh. And Jabaco does NOT provide that at all. Vb.NET is miles ahead of it on that front. IF you think VB.NET is not good at that, then Jabaco is beyond hope. |