Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #7462 > unrolled thread
| Started by | Kuno Egger <kuno@retailsoftware.com> |
|---|---|
| First post | 2014-11-20 19:09 -0800 |
| Last post | 2014-11-27 15:26 +0000 |
| Articles | 16 on this page of 36 — 13 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
No More Excuses!! Kuno Egger <kuno@retailsoftware.com> - 2014-11-20 19:09 -0800
Re: No More Excuses!! "Fred Killet" <info@killetsoft.de> - 2014-11-21 12:25 +0100
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-11-21 21:06 +0100
Re: No More Excuses!! tibbspaul70@yahoo.com - 2014-11-21 13:20 -0800
Re: No More Excuses!! "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-11-23 12:06 +0100
Re: No More Excuses!! tibbspaul70@yahoo.com - 2014-11-24 01:25 -0800
Re: No More Excuses!! "Valery N." <mustangsoftcom@gmail.com> - 2014-11-24 03:32 -0800
Re: No More Excuses!! "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-11-24 14:11 +0100
Re: No More Excuses!! "Valery N." <mustangsoftcom@gmail.com> - 2014-11-24 07:26 -0800
Re: No More Excuses!! "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-11-24 16:59 +0100
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-11-24 23:25 +0100
Re: No More Excuses!! "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-11-25 07:34 +0100
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-11-25 22:53 +0100
Re: No More Excuses!! "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-11-26 08:26 +0100
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-11-26 17:47 +0100
Re: No More Excuses!! Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2014-11-24 21:53 +0100
Re: No More Excuses!! "Valery N." <mustangsoftcom@gmail.com> - 2014-11-25 09:56 -0800
Re: No More Excuses!! tibbspaul70@yahoo.com - 2014-11-25 11:57 -0800
Re: No More Excuses!! "Valery N." <mustangsoftcom@gmail.com> - 2014-11-25 12:17 -0800
Re: No More Excuses!! fischer.erhard@yahoo.com - 2015-11-03 13:14 -0800
Re: No More Excuses!! Mathias <mathias.hakansson@consultec.se> - 2014-11-26 00:01 -0800
Re: No More Excuses!! "Valery N." <mustangsoftcom@gmail.com> - 2014-11-26 13:10 -0800
Re: No More Excuses!! Mathias <mathias.hakansson@consultec.se> - 2014-11-27 06:47 -0800
Re: No More Excuses!! Mathias <mathias.hakansson@consultec.se> - 2014-11-27 07:24 -0800
Re: No More Excuses!! "Valery N." <mustangsoftcom@gmail.com> - 2014-11-27 09:01 -0800
Re: No More Excuses!! "Jamal" <someone@example.com> - 2014-11-24 11:23 -0500
Re: No More Excuses!! Johan Nel <johan.nel@xsinet.co.za> - 2014-11-25 22:44 -0800
Re: No More Excuses!! "Jamal" <someone@example.com> - 2014-11-26 13:28 -0500
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-11-26 23:07 +0100
Re: No More Excuses!! Carlos Rocha <FreeTheMusic@ascap.com> - 2014-11-27 15:35 +0000
Re: No More Excuses!! "Jamal" <someone@example.com> - 2014-11-27 16:39 -0500
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-11-29 14:24 +0100
Re: No More Excuses!! "Willie Moore" <williem@wmconsulting.com> - 2014-12-04 15:14 -0600
Re: No More Excuses!! D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2014-12-05 00:34 +0100
Re: No More Excuses!! Johan Nel <johan.nel@xsinet.co.za> - 2014-11-26 22:56 -0800
Re: No More Excuses!! Carlos Rocha <FreeTheMusic@ascap.com> - 2014-11-27 15:26 +0000
Page 2 of 2 — ← Prev page 1 [2]
| From | Mathias <mathias.hakansson@consultec.se> |
|---|---|
| Date | 2014-11-26 00:01 -0800 |
| Message-ID | <eed417e5-e547-4501-ab52-e18d9faae6e8@googlegroups.com> |
| In reply to | #7510 |
Hi Valery, Thanks for your kind Words about MathiasSLE. Would you share some of your improvements? I havent't done any improvements for a very long time. The only addition I did was adding clipper key support in a separate ClipperKey class. I Think it also has been posted here. /Mathias Den tisdagen den 25:e november 2014 kl. 18:56:49 UTC+1 skrev Valery N.: > Hi, Karl! > > I started working with CA-Vo2.5. At that time RightSLE contained errors which led to messages 5333. As soon as I understood the reason, I asked a question: it will be better to correct RightSLE or to create the library? > > I found MathiasSLE (Mathias Hakansson). Very good and useful library. I added the lacking elements there. I added rules of alignment for monetary values (such alignment appeared only in the latests version of RightSLE), improved operation with the keypad. Then I improved appearance of a control for a case when PushButton is added (a week ago I spread the test version on a forum). Now prompted me the best option of a combination with other elements of management. It has to reduce a code and accelerate work. > > Now friends prompted me the best option of a combination with other elements of management. It has to reduce a code and accelerate work. > > RightSLE is a good library. But, I have the best decision. And I use him.
[toc] | [prev] | [next] | [standalone]
| From | "Valery N." <mustangsoftcom@gmail.com> |
|---|---|
| Date | 2014-11-26 13:10 -0800 |
| Message-ID | <8369287b-cf53-4e2c-93c6-553936577f07@googlegroups.com> |
| In reply to | #7522 |
Hi, Mathias! I suggest to arrive as follows: Give to me, please, a direct link on your library (MathiasSLE) that I added it to the list of third-party products on the site. The matter is that I don't remember where I found it. After a while I will finish experiments with my class. After that, I will send you its code and an example. It will be good if you look at it, estimate and you will find errors. After that, we will decide - to give this code in general use or it remains only at us. I think, it will be so correct. I help those who helps me, and I share with that who jointly with me carries development.
[toc] | [prev] | [next] | [standalone]
| From | Mathias <mathias.hakansson@consultec.se> |
|---|---|
| Date | 2014-11-27 06:47 -0800 |
| Message-ID | <f81c3387-89b6-4ccc-b69a-1d5fe527253c@googlegroups.com> |
| In reply to | #7533 |
Hi All, MathiasSLE was available on www.cavo.com, or www.knowVO.com, or whatever it's name was. I have now put it on my company server, see link below. The sample requires bBrowser as it uses MathiasSLE in a datawindow. The sample also contains code for saving and restoring column settings (visible columns, grid type, and selection type). http://www.consultec.se/refDok/produkter/84/Mathias%20SLE%20and%20Browser.AEF /MathiasH Den onsdagen den 26:e november 2014 kl. 22:10:50 UTC+1 skrev Valery N.: > Hi, Mathias! > > I suggest to arrive as follows: > Give to me, please, a direct link on your library (MathiasSLE) that I added it to the list of third-party products on the site. The matter is that I don't remember where I found it. > After a while I will finish experiments with my class. After that, I will send you its code and an example. It will be good if you look at it, estimate and you will find errors. > After that, we will decide - to give this code in general use or it remains only at us. > I think, it will be so correct. I help those who helps me, and I share with that who jointly with me carries development.
[toc] | [prev] | [next] | [standalone]
| From | Mathias <mathias.hakansson@consultec.se> |
|---|---|
| Date | 2014-11-27 07:24 -0800 |
| Message-ID | <a3e9e3a5-144f-4e56-800f-3c521972c494@googlegroups.com> |
| In reply to | #7536 |
New link... It seems like my server did not like aef-files. http://www.consultec.se/refDok/produkter/84/MathiasSLE.zip Den torsdagen den 27:e november 2014 kl. 15:47:14 UTC+1 skrev Mathias: > Hi All, > > MathiasSLE was available on www.cavo.com, or www.knowVO.com, or whatever it's name was. I have now put it on my company server, see link below. The sample requires bBrowser as it uses MathiasSLE in a datawindow. > > The sample also contains code for saving and restoring column settings (visible columns, grid type, and selection type). > > http://www.consultec.se/refDok/produkter/84/Mathias%20SLE%20and%20Browser.AEF > > /MathiasH > > Den onsdagen den 26:e november 2014 kl. 22:10:50 UTC+1 skrev Valery N.: > > Hi, Mathias! > > > > I suggest to arrive as follows: > > Give to me, please, a direct link on your library (MathiasSLE) that I added it to the list of third-party products on the site. The matter is that I don't remember where I found it. > > After a while I will finish experiments with my class. After that, I will send you its code and an example. It will be good if you look at it, estimate and you will find errors. > > After that, we will decide - to give this code in general use or it remains only at us. > > I think, it will be so correct. I help those who helps me, and I share with that who jointly with me carries development.
[toc] | [prev] | [next] | [standalone]
| From | "Valery N." <mustangsoftcom@gmail.com> |
|---|---|
| Date | 2014-11-27 09:01 -0800 |
| Message-ID | <9a9c6a1d-3e64-4d80-bd4b-89050c716ccd@googlegroups.com> |
| In reply to | #7537 |
Hi, Mathias! I downloaded your new file. Soon I will see his contents. If you don't object, soon I will add the reference to MathiasSLE in my list of third-party products. If at you his description is ready - please, send it to me, and I will add it. Good luck! Valery.
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <someone@example.com> |
|---|---|
| Date | 2014-11-24 11:23 -0500 |
| Message-ID | <m4vm1c$qa0$1@speranza.aioe.org> |
| In reply to | #7462 |
Kuno, You are assuming that VO is still being developed. VO as per Grafx is no longer being developed since sp4a was released and that Vulcan is the future of VO. In .NET you can set the background of push button and much more. Quote from Sept 24, 2013 "... the last build of Visual Objects SP4 is the "B" version. Build number is 2838. .... This (VO 2838) is the last build of Visual Objects that will be released to the public by Grafx Software. The official "Sunset Date" of Visual Objects is December 31 2013. Of course you will be able to continue to use VO so long as Microsoft continues to support 32bit PE (Portable Executable)". I am not sure if Grafx is doing a good job on promoting Vulcan.NET and I see delays in catching up with Visual Studio updates by almost a year.; there is not much activity either on the Grafx public news group except for Phil Hepburn (Pearls notes/project). Some portions of Vulcan still use 32bit like the DBFCDX. I am hoping it moves to 64bit. I may again consider Vulcan as development accelerates. Jamal "Kuno Egger" wrote in message news:59d491d9-a3f2-4130-a40b-4e1a404490d6@googlegroups.com... It's high time for the VO WED to have a convenient background color property setting for push buttons. I can't believe it's not there.
[toc] | [prev] | [next] | [standalone]
| From | Johan Nel <johan.nel@xsinet.co.za> |
|---|---|
| Date | 2014-11-25 22:44 -0800 |
| Message-ID | <dbe73d1c-aa4f-41c0-9950-6cffa9ce1408@googlegroups.com> |
| In reply to | #7487 |
Not to anybody in particular, but if the glove fits... Unfortunately you should be grateful for Grafx that is keeping the VO language alive and extend it further via Vulcan.NET. http://msdn.microsoft.com/en-us/vfoxpro/bb190225.aspx : Visual FoxPro 9.0 provides the tools you need to create and manage high-performance, 32-bit database applications and components. Note that Visual FoxPro 9.0 is the last version and was published in 2007. For a great solution for building modern business applications, take a look at LightSwitch in Visual Studio 2012. Now if I take a look at LightSwitch it gives me two options to programme in C# & VB.NET. So if I was a VFP devoloper get stuck in the past or learn c# and/or VB.NET, until I become like COBOL programmers (almost obsolete). If I am a VO developer, keep on bitching and stay in the past or use the bitching time to realign you with the future which in my eyes are Vulcan.NET. I conclude my case. Johan Nel Vulcan VIP Durban, South Africa.
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <someone@example.com> |
|---|---|
| Date | 2014-11-26 13:28 -0500 |
| Message-ID | <m5564i$peh$1@speranza.aioe.org> |
| In reply to | #7519 |
Johan, Vulcan.NET does not offer much of an advantage except for the VO syntax (which I do not like in the .NET world). Just because some developer uses Vulcan.NET does not mean somehow he/she lives in in the future and somehow a more advanced developer than the rest of the "bitching" VO developers who are probably using VB.NET, C# for desktop and web applications. I am afraid, Vulcan.NET will not survive for a long time. Outside of the VO community and VPS, hardly anyone heard of it. Will it be financially profitable to Grafx to continue developing it knowing its appeal and popularity is almost nil except for the VPS group which is very very tiny? May be the glove fits you now, but will it be if Grafx decided to abandon it. Surely, Grafx has done a great job in bringing VO to a very stable state, however, you cannot dispute the fact that VO is more popular than Vulcan.NET and I think many VO developers who do not want Vulcan, who are still living in the "past" as you termed it, would be grateful if Grafx decides to reverse its decision and support VO with bugs fixes and some additional features so that applications they developed in VO can continue to be even more stable. As for issues like background for push buttons, that's something trivial I am not worried about; I can simply use an icon. I am sure an updated VO version will appeal to many VO developers and may be a good financial decision to Grafx. Jamal "Johan Nel" wrote in message news:dbe73d1c-aa4f-41c0-9950-6cffa9ce1408@googlegroups.com... Not to anybody in particular, but if the glove fits... Unfortunately you should be grateful for Grafx that is keeping the VO language alive and extend it further via Vulcan.NET. http://msdn.microsoft.com/en-us/vfoxpro/bb190225.aspx : Visual FoxPro 9.0 provides the tools you need to create and manage high-performance, 32-bit database applications and components. Note that Visual FoxPro 9.0 is the last version and was published in 2007. For a great solution for building modern business applications, take a look at LightSwitch in Visual Studio 2012. Now if I take a look at LightSwitch it gives me two options to programme in C# & VB.NET. So if I was a VFP devoloper get stuck in the past or learn c# and/or VB.NET, until I become like COBOL programmers (almost obsolete). If I am a VO developer, keep on bitching and stay in the past or use the bitching time to realign you with the future which in my eyes are Vulcan.NET. I conclude my case. Johan Nel Vulcan VIP Durban, South Africa.
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2014-11-26 23:07 +0100 |
| Message-ID | <r7jc7aduvlinm8m013iiqiv6lhokktb1bn@4ax.com> |
| In reply to | #7531 |
On Wed, 26 Nov 2014 13:28:41 -0500, "Jamal" <someone@example.com> wrote: Hello Jamal, > >Vulcan.NET does not offer much of an advantage except for the VO syntax >(which I do not like in the .NET world). A second advantage is that it can fully work with DBFCDX the way we are used to do it with VO. Unfortunately only 32 bits (which meant we couldn't use Vulcan for a webservice requiring 64 bits DLL's, and hence used C# and MySQL for that instead). But still, it is a real advantage of Vulcan. I use it for anything I can not do (easily) in VO, e.g. creating a .jpg file from graphical clipboard content, certain lay out requirements which can be done with WPF and more. >Just because some developer uses Vulcan.NET does not mean somehow he/she >lives in in the future I agree with you on that. >I am afraid, Vulcan.NET will not survive for a long time. Outside of the VO >community and VPS, hardly anyone heard of it. I can understand this comment, but remember that this is written since 2006 and (somehow...) Vulcan still exists. >would be grateful if Grafx decides to reverse its decision and support VO with bugs fixes and some additional >features so that applications they developed in VO can continue to be even >more stable. I am sure an updated VO version will appeal to many VO developers and may be a >good financial decision to Grafx. > I understood that this is not the case. VO 2.8 upgrade sales have been disappointing, the same for the VO only VOPS. I think most 2.8 users who are still using it are not willing to pay for an upgrade nowadays and probably none of the users who are still working with < 2.8. Dick
[toc] | [prev] | [next] | [standalone]
| From | Carlos Rocha <FreeTheMusic@ascap.com> |
|---|---|
| Date | 2014-11-27 15:35 +0000 |
| Message-ID | <m57gbh$maa$1@news.albasani.net> |
| In reply to | #7534 |
D.J.W. van Kooten formulated on quarta-feira : >> would be grateful if Grafx decides to reverse its decision and support VO >> with bugs fixes and some additional features so that applications they >> developed in VO can continue to be even more stable. I am sure an updated >> VO version will appeal to many VO developers and may be a good financial >> decision to Grafx. >> > > I understood that this is not the case. VO 2.8 upgrade sales have been > disappointing, the same for the VO only VOPS. I think most 2.8 users > who are still using it are not willing to pay for an upgrade nowadays > and probably none of the users who are still working with < 2.8. > Dick, It would depend on the fixes. I have paid for every single upgrade in the past, and the last one (SP4) is the best ever, but still misses the essential. In fact the last upgrades provided by GrafX was oriented to Vulcan users (VPS members). -- Carlos Rocha --- Este e-mail foi verificado em termos de vírus pelo software antivírus Avast. http://www.avast.com
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <someone@example.com> |
|---|---|
| Date | 2014-11-27 16:39 -0500 |
| Message-ID | <m585n1$e5f$1@speranza.aioe.org> |
| In reply to | #7534 |
Hi D.J.W, >> A second advantage is that it can fully work with DBFCDX the way we are used to do it with VO. << This is not much of an advantage as you cannot use DBF file as datasets to which can be manipulated like SQL. There .NET libraries like Apollo that does this nicely. Once big disadvantage that cannot create websites or Web Applications in Vulcan.NET may be because of licensing issues from Microsoft. May be someone created some hacks to do so, but I could not find anything that shows a live web application written in Vulcan. So, why waste time when it can be done in VB.NET or C# language easily. Anyway, I think (in my opinion) Grafx should have instead focused on .NET tools/libraries to bring VO developers to .NET using either VB.NET or C# and forget about Vulcan. May it can use all the knowledge and development invested in Vulcan.NET to create such tools! Jamal "D.J.W. van Kooten" wrote in message news:r7jc7aduvlinm8m013iiqiv6lhokktb1bn@4ax.com... On Wed, 26 Nov 2014 13:28:41 -0500, "Jamal" <someone@example.com> wrote: Hello Jamal, > >Vulcan.NET does not offer much of an advantage except for the VO syntax >(which I do not like in the .NET world). A second advantage is that it can fully work with DBFCDX the way we are used to do it with VO. Unfortunately only 32 bits (which meant we couldn't use Vulcan for a webservice requiring 64 bits DLL's, and hence used C# and MySQL for that instead). But still, it is a real advantage of Vulcan. I use it for anything I can not do (easily) in VO, e.g. creating a .jpg file from graphical clipboard content, certain lay out requirements which can be done with WPF and more. >Just because some developer uses Vulcan.NET does not mean somehow he/she >lives in in the future I agree with you on that. >I am afraid, Vulcan.NET will not survive for a long time. Outside of the VO >community and VPS, hardly anyone heard of it. I can understand this comment, but remember that this is written since 2006 and (somehow...) Vulcan still exists. >would be grateful if Grafx decides to reverse its decision and support VO >with bugs fixes and some additional >features so that applications they developed in VO can continue to be even >more stable. I am sure an updated VO version will appeal to many VO >developers and may be a >good financial decision to Grafx. > I understood that this is not the case. VO 2.8 upgrade sales have been disappointing, the same for the VO only VOPS. I think most 2.8 users who are still using it are not willing to pay for an upgrade nowadays and probably none of the users who are still working with < 2.8. Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2014-11-29 14:24 +0100 |
| Message-ID | <eihj7ad2jltmvf4adu3cp68sq5vneih31k@4ax.com> |
| In reply to | #7541 |
On Thu, 27 Nov 2014 16:39:48 -0500, "Jamal" <someone@example.com> wrote: Hello Jamal, > >This is not much of an advantage as you cannot use DBF file as datasets to >which can be manipulated like SQL. There .NET libraries like Apollo that >does this nicely. Well, I can, using ADS. I can create for example a full bBrowser showing data from multiple linked DBF files with a single SQL statement. It also means I can transport VO code with minimal change and more important, I do have all commands available to work with DBF I have in VO. I've been looking at quite a few alternatives and none did everything I wanted. Apollo costs $ 399 per developer, is still 32 bits. For just $ 100 more you have full Vulcan, so why bother with Apollo then? > >Once big disadvantage that cannot create websites or Web Applications in >Vulcan.NET I am not sure which limitations you mean? If you create websites e.g. with ASPX and a Vulcan .Net DLL, it will work - with the disadvantage that your ISP must allow 32 bits apps to run. >Anyway, I think (in my opinion) Grafx should have instead focused on .NET >tools/libraries to bring VO developers to .NET using either VB.NET or C# and >forget about Vulcan. >May it can use all the knowledge and development invested in Vulcan.NET to >create such tools! Probably. I think Grafx really wanted to get rid of CA by leaving VO. But I also doubt if anyone wants to get .Net functionality while keeping programs in VO. If you want that, you don't need to buy tools & libraries; you just create (or download) whatever you need in C# (or Vulcan!) and use it in VO. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Willie Moore" <williem@wmconsulting.com> |
|---|---|
| Date | 2014-12-04 15:14 -0600 |
| Message-ID | <m5qirt$7jh$1@speranza.aioe.org> |
| In reply to | #7534 |
Dick, If you are not using DBF or macros you can use corlib to remove the 32bit info on your dll. I wrote an post over a year ago about how to do that on pearls. I use quite a few vulcan dlls on my web servers (hosted by godaddy) where the provider does not allow 32bit dlls. It has never been an issue for me. I use the postbuld events in visual studio to automatically touch my dlls with corlib so I don’t have to remember to do it every time I make a build. Regards, Willie Vulcan VIP
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2014-12-05 00:34 +0100 |
| Message-ID | <apr18a9guptd0sjohjj8f829od43h7gs5d@4ax.com> |
| In reply to | #7576 |
On Thu, 4 Dec 2014 15:14:36 -0600, "Willie Moore" <williem@wmconsulting.com> wrote: Hello Willie, >If you are not using DBF or macros you can use corlib to remove the 32bit >info on your dll. I wrote an post over a year ago about how to do that on >pearls. Ah that could be quite interesting indeed! I must have missed that. I did solve this by using C# and that was good for increasing my C# knowledge, but I still have to look up lots more than I would do in Vulcan. Thanks! Dick
[toc] | [prev] | [next] | [standalone]
| From | Johan Nel <johan.nel@xsinet.co.za> |
|---|---|
| Date | 2014-11-26 22:56 -0800 |
| Message-ID | <57919fd6-7f2e-4e6c-a571-77e2092ce393@googlegroups.com> |
| In reply to | #7531 |
Hi Jamal,
> Vulcan.NET does not offer much of an advantage except for the VO syntax
> (which I do not like in the .NET world).
The future is .NET from a MicroSoft perspective. Vulcan gives me a 90-95% VO compatibility to take what I have in VO into .NET. Try c#, vb.net or any other language you will have to do a 100% conversion from your VO code.
> Just because some developer uses Vulcan.NET does not mean somehow he/she
> lives in in the future and somehow a more advanced developer than the rest
> of the "bitching" VO developers who are probably using VB.NET, C# for
> desktop and web applications.
I agree Vulcan.NET is not the future of programming, for the moment .NET is and Vulcan is just a tool to provide me a migration path to it quickly. If you compare going from Clipper to VO, you were able to port business logic. Your GUI you had to rewrite 100%. Now I don't hear anybody complaining about that. With the transporter we have 90-95% portability. And everybody complains...
> I am afraid, Vulcan.NET will not survive for a long time. Outside of the VO
> community and VPS, hardly anyone heard of it. Will it be financially
> profitable to Grafx to continue developing it knowing its appeal and
> popularity is almost nil except for the VPS group which is very very tiny?
> May be the glove fits you now, but will it be if Grafx decided to abandon
> it.
Well if Grafx abandon Vulcan.NET, so what, all my assemblies will still run in .NET and I can easily add enhancements to all my code using c#, vb.net or any other .NET tool. That is the beauty of .NET it is progamming language agnostic.
> Surely, Grafx has done a great job in bringing VO to a very stable state,
I have to second that and I thank Grafx for the futuristic vision they had, which still lives on in Vulcan.NET.
> however, you cannot dispute the fact that VO is more popular than Vulcan.NET
> and I think many VO developers who do not want Vulcan, who are still living
Well I will mention my observation. There are more postings on the Grafx public ng's than in c.l.c.vo and c.l.c combined...
> in the "past" as you termed it, would be grateful if Grafx decides to
> reverse its decision and support VO with bugs fixes and some additional
> features so that applications they developed in VO can continue to be even
> more stable.
My impression was that the last upgrade did not appeal to many, it is a money game, I need to recover my money that I invest in a product.
Just some background, I decided my VO 2.6 was stable enough for what I do. So yes although I had to rewrite my VO code with my favourite transporter tool (Copy, Replace <x> with <y>) it took me less than 2 months (part-time) to be fully functional in Vulcan with all my VO applications. Where was the biggest change I needed?
1. You cannot declare a method somewhere to an internal class anymore.
Encapsulate the internal class with INHERIT and add the method and change your code to use the new class.
2. Init
There is no init anymore, change your code to use CONSTRUCTOR() and create OVERLOADED CONSTRUCTORS and METHODS. Yes maybe lots of work, because we were getting lazy with VO, that is not VO's fault, it just provided the option.
3. Events
VO allowed me to have a method with the same name as a button/menutiem e.g. that the underlying language automatically fire, or if it did not find it fire some default "Trap event".
Solution go the the Event and change
METHOD SomeMenuEvent(oMCE)
LOCAL o AS OBJECT
o := oMCE:Control
to
METHOD MenuEvent(o AS OBJECT, e AS EventArgs) AS VOID
And where SomeMenu was used add
oSomeMenu:Click += EventHandler{SELF, @MenuEvent()}
Well if you did not do some undocumented/not recommended abuse with your code, I think you now already 99% there and the grafx ng lurkers are quite willing to help you to sort out that last 1%.
> I am sure an updated VO version will appeal to many VO developers and
> may be a good financial decision to Grafx.
Unfortunately not. Even with no knowledge about Grafx, from my observations there would be NO WAY that I will risk my capital in VO. I rather spend that money to move Vulcan forward.
Johan Nel
Vulcan VIP
Durban, South Africa.
[toc] | [prev] | [next] | [standalone]
| From | Carlos Rocha <FreeTheMusic@ascap.com> |
|---|---|
| Date | 2014-11-27 15:26 +0000 |
| Message-ID | <m57fsc$lau$1@news.albasani.net> |
| In reply to | #7531 |
After serious thinking Jamal wrote : > Johan, > > Vulcan.NET does not offer much of an advantage except for the VO syntax > (which I do not like in the .NET world). > Just because some developer uses Vulcan.NET does not mean somehow he/she > lives in in the future and somehow a more advanced developer than the rest of > the "bitching" VO developers who are probably using VB.NET, C# for desktop > and web applications. > > I am afraid, Vulcan.NET will not survive for a long time. Outside of the VO > community and VPS, hardly anyone heard of it. Will it be financially > profitable to Grafx to continue developing it knowing its appeal and > popularity is almost nil except for the VPS group which is very very tiny? > May be the glove fits you now, but will it be if Grafx decided to abandon it. > > Surely, Grafx has done a great job in bringing VO to a very stable state, > however, you cannot dispute the fact that VO is more popular than Vulcan.NET > and I think many VO developers who do not want Vulcan, who are still living > in the "past" as you termed it, would be grateful if Grafx decides to reverse > its decision and support VO with bugs fixes and some additional features so > that applications they developed in VO can continue to be even more stable. > As for issues like background for push buttons, that's something trivial I am > not worried about; I can simply use an icon. I am sure an updated VO version > will appeal to many VO developers and may be a good financial decision to > Grafx. > > Jamal > +1 -- Carlos Rocha --- Este e-mail foi verificado em termos de vírus pelo software antivírus Avast. http://www.avast.com
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web