Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #4766 > unrolled thread
| Started by | macenzi@gmail.com |
|---|---|
| First post | 2013-02-12 14:51 -0800 |
| Last post | 2013-02-14 18:33 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
VO 2.8 ou Vulcan? macenzi@gmail.com - 2013-02-12 14:51 -0800
Re: VO 2.8 ou Vulcan? "Wolfgang Riedmann" <wriedmann@gmail.com> - 2013-02-13 09:29 +0100
Re: VO 2.8 ou Vulcan? D.J.W. van Kooten <public@ic2remove.this.com> - 2013-02-14 18:33 +0100
| From | macenzi@gmail.com |
|---|---|
| Date | 2013-02-12 14:51 -0800 |
| Subject | VO 2.8 ou Vulcan? |
| Message-ID | <63298464-78b2-4730-abfd-cd60b1574488@googlegroups.com> |
Good evening, Like an opinion on the use of VO 2.8. Will be continued or applications are now facing the Vulcan?
[toc] | [next] | [standalone]
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
|---|---|
| Date | 2013-02-13 09:29 +0100 |
| Message-ID | <ao117uFo9lcU1@mid.individual.net> |
| In reply to | #4766 |
Hello, > Like an opinion on the use of VO 2.8. Will be continued or > applications are now facing the Vulcan? I can only say what I'm doing: my "old" applications that are in continuos development at least for the next years will remain in Visual Objects (most current version, at the moment 2.8 SP4), and new developments will be made in Vulcan. But I'm studying to make mixed mode apps - partially in Visual Objects, partially in Vulcan, and at the same time try to migrate current Visual Objects apps to Vulcan. Visual Objects apps are rock solid, but for new developments the Win32 platform demonstrates its age, and Vulcan apps have more possibilities. Wolfgang --
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2013-02-14 18:33 +0100 |
| Message-ID | <s97qh85or7la5geqk59qchmshavtmeuqj2@4ax.com> |
| In reply to | #4766 |
On Tue, 12 Feb 2013 14:51:43 -0800 (PST), macenzi@gmail.com wrote:
Hello Macenzi,
>Good evening,
>Like an opinion on the use of VO 2.8. Will be continued or applications are now facing the Vulcan?
I just finished a small application Vulcan WPF application and this is
a good opportunity to explain.
Background of IC2 Teletekst Browser
As in many countries, TV's have Teletekst. For the public broadcasting
over here, the 'general' NOS maintains the teletekst pages. They can
also be watched on the website teletekst.nos.nl and until beginning
this month in a very nice small browser. Much of the news I got via
that browser. But NOS changed the lay-out and the maker of the
program, who sold it to NOS, announced on their website that the new
layout doesn't work in that program - it now gives empty pages. I
started to investigate things and found out that in the end .gif
pictures where retrieved from the NOS pages to show the content. And
so I got the idea to make a nice WPF Vulcan alternative for this
browser, fetching the pages from the NOS (knowing that deep linking is
allowed in Holland).
What did I do? I've first set up the program from scratch in VO. I
very much prefer the VO repo way of working above the .prg way of
working in Vulcan (or any other .Net language). I sort my entities on
date to see what I edited last and I can pick up any combination of
entities in any order. This is gone in .Net. You basically see all
your code in 1 long program and only have some collapse options to
hide code. This I consider the major drawback.
This having said, I believe that access to .Net technology is
something we will all need to get things done in the future. I
transported the application to Vulcan which works almost 100%, but I
don't think I would gain much by releasing the program as a Vulcan
application. Maybe stability, but the VO version seems stable to me
too. What I did is the following:
1 I downloaded a working C# project with a WPF window more or less
like the one I needed
2 I created a new WPF Vulcan project and pasted the XAML code from the
C# project, and started modifying it to my needs
3 For some of the code (code behind, as it's called) I programmed the
relevant .Net/WPF form code. Sometimes, I just used some C# code and
used Reflector to quickly translate it to Vulcan. "Business logic" I
could just take over from the transported application.
The result can be seen in
http://www.ic2.com/Teletekst/TeletekstStart.htm, and you can download
the program from
http://www.ic2.com/Teletekst/SetupIC2Teletekstbrowser.exe.
All is Dutch only!
So what is the advantage of .Net above VO? Basically we can make nicer
screens with XAML (take a look at the buttons and custom tooltips) and
it can be more precise controlled. E.g. while VO calls methods like
EditChange as a standard (easy!), in a WPF application you need to
tell which controls should generate what method on which occasion.
More work but well defined. Some stuff we need 300-400 lines of VO
(e.g. registry access) is a few lines in .Net. But on the other hand,
saving a .gif file from http was much easier in VO. There are many
examples, code snippets or complete projects to begin with, much more
than for VO.
Final question is: Vulcan or C#? For me, I understand code in Vulcan
better than I do for C# although I am getting more and more familiar
with C#. The {} in C# code drive me crazy together with the fact that
you see the whole program I have had many times that I pasted some new
code just on the wrong side of the {} and got bunches of error
messages, taking much time to solve. I also think C$ is very
unreadable; Vulcan code is cleaner and of course more like VO. The end
result basically the same, and with exception of some details
(workaround available) Vulcan is useable for everything. In short, C#
may be easier to directly use code you find on the internet, if you
are very familiar with VO, Vulcan definitely has an advantage.
Although I recommend quite some rewriting if you are transporting
existing VO applications, business logic can be used almost without
change. And if you use .dbf code, Vulcan has a benefit too!
My plan for the future is to gradually add components which benefit
from .Net options in Vulcan (or maybe C#, small chance) and just call
these via .COM (quite easy) from my VO program. This way my program
improves without too much changes at once and I can still keep doing
much of the work in a programming environment I consider vastly
superior above Visual Studio (any language).
I hope this helps.
Dick
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web