system library vulcan
in [Visual Objects]
|
From: RBaeuerle on 6 Feb 2010 09:24 Hello All, 1.) how do i get the ErrorSystem work in Vulcan? I have a VO implementation in 2.8. It seem that this Lib isnt´t linked automatic like in VO. 2.) I have several problems with the Transport of FABLib, FabPaint & FABZip. Are there any fixed Versions? greetings Ronald
From: Fabrice Foray on 6 Feb 2010 11:46 On Feb 6, 3:24 pm, RBaeuerle <rb-...(a)t-online.de> wrote: > Hello All, > > 1.) how do i get the ErrorSystem work in Vulcan? I have a VO > implementation in 2.8. > It seem that this Lib isnt´t linked automatic like in VO. > > 2.) I have several problems with the Transport of FABLib, FabPaint & > FABZip. Are there > any fixed Versions? > > greetings Ronald Hi Ronald, Fab Misc. Lib must/may be transported without any major trouble. I currently have a running version of FabZip in Vulcan, without multi- archive and SFX (Multi-Volume is on the way) For FabPaint, it depends of your needs : but I'm still working on it. Regards, Fabrice
From: Willie Moore on 6 Feb 2010 13:31 Ronald, I can email you a sample that I did at VODC (my ng provider will not let me make attachments but it is free so I get what I pay for). It shows how to do some logging in Vulcan. The errorblock that you would do in VO is not supported in Vulcan but the try catch finally is such a better way of doing things. With Vulcan, you can handle the errors in your lower level and what you do not explicetly trap for will be passed up to your top level where you log the errors. Regards, Willie williem(a)wmconsulting.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4842 (20100206) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Geoff Schaller on 6 Feb 2010 19:16 Willie, You have touched on one of the big negatives of Vulcan. You are correct to suggest that the error handling methodology in Dot Net is vastly superior to that which we had in VO but the problem for most of us is that we buried that error handling deep into our class structures. VO2Ado for instance. DBF and window and control classes another. This is where the conversion experience from VO to Vulcan can vary dramatically. Image and graphics management is another. My suspicion is that those who want to convert to Vulcan should probably abandon certain classes and mechanisms and replace them with a pure Dot Net version. There is a code rewrite here no matter how much you paint the picture with roses. This is what we are doing for things like image display, email, MS Office integration and so on. Once we've taken these elements out of our VO app then the conversion to Dot Net (not necessarily Vulcan) will be a lot easier. In our case we won't be converting our VO apps ever but we do build new functionality in Dot Net as COM and then use it in our VO apps with minimal coding. I guess this is still "migration" but now it is done in manageable chunks and only as we need to. Geoff "Willie Moore" <williem(a)wmconsulting.com> wrote in message news:hkkciu$je1$1(a)speranza.aioe.org: > Ronald, > > I can email you a sample that I did at VODC (my ng provider will not let me > make attachments but it is free so I get what I pay for). It shows how to do > some logging in Vulcan. The errorblock that you would do in VO is not > supported in Vulcan but the try catch finally is such a better way of doing > things. With Vulcan, you can handle the errors in your lower level and what > you do not explicetly trap for will be passed up to your top level where you > log the errors. > > Regards, > Willie > williem(a)wmconsulting.com > > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4842 (20100206) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com
From: Willie Moore on 6 Feb 2010 19:35
Geoff, Can't say that I disagree with you <g>. I am doing a lot of work in Vulcan but I take the business logic and put it in a dll. But even the business logic gets touched as I am switching out the VO error system for the dotNet and changing a lot of the other classes to the dotNet classes when I touch a module. I always did my business logic as a COM object so the approach works for me although I did transport and move my VO apps to Vulcan as the first step. I find that they are more stable running under dotNet. Once I had them over, I started changing out pieces for the dotNet as opportunity presented itself. It has been a lot of work but the customers seem to like it. Regards, Willie ps. I have most of rightSLE working under winforms now. Should have it finished up before DevShare. "Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> wrote in message news:eDnbn.6027$pv.2593(a)news-server.bigpond.net.au... > Willie, > > You have touched on one of the big negatives of Vulcan. You are correct to > suggest that the error handling methodology in Dot Net is vastly superior > to that which we had in VO but the problem for most of us is that we > buried that error handling deep into our class structures. VO2Ado for > instance. DBF and window and control classes another. > > This is where the conversion experience from VO to Vulcan can vary > dramatically. Image and graphics management is another. My suspicion is > that those who want to convert to Vulcan should probably abandon certain > classes and mechanisms and replace them with a pure Dot Net version. There > is a code rewrite here no matter how much you paint the picture with > roses. > > This is what we are doing for things like image display, email, MS Office > integration and so on. Once we've taken these elements out of our VO app > then the conversion to Dot Net (not necessarily Vulcan) will be a lot > easier. In our case we won't be converting our VO apps ever but we do > build new functionality in Dot Net as COM and then use it in our VO apps > with minimal coding. I guess this is still "migration" but now it is done > in manageable chunks and only as we need to. > > Geoff > > > > "Willie Moore" <williem(a)wmconsulting.com> wrote in message > news:hkkciu$je1$1(a)speranza.aioe.org: > >> Ronald, >> >> I can email you a sample that I did at VODC (my ng provider will not let >> me >> make attachments but it is free so I get what I pay for). It shows how to >> do >> some logging in Vulcan. The errorblock that you would do in VO is not >> supported in Vulcan but the try catch finally is such a better way of >> doing >> things. With Vulcan, you can handle the errors in your lower level and >> what >> you do not explicetly trap for will be passed up to your top level where >> you >> log the errors. >> >> Regards, >> Willie >> williem(a)wmconsulting.com >> >> >> >> __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 4842 (20100206) __________ >> >> The message was checked by ESET NOD32 Antivirus. >> >> http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4842 (20100206) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4842 (20100206) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com |