Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #5070 > unrolled thread

Two good reasons to go to Vulcan

Started byD.J.W. van Kooten <public@ic2remove.this.com>
First post2013-04-17 01:17 +0200
Last post2013-05-13 11:34 -0800
Articles 20 on this page of 43 — 11 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-04-17 01:17 +0200
    Re: Two good reasons to go to Vulcan "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> - 2013-04-18 15:56 +0200
    Re: Two good reasons to go to Vulcan "Jamal" <jamal@examples.net> - 2013-04-19 12:41 -0400
      Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-04-21 10:56 +0200
        Re: Two good reasons to go to Vulcan Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2013-04-21 13:47 +0200
        Re: Two good reasons to go to Vulcan "Willie Moore" <williem@wmconsulting.com> - 2013-04-21 07:29 -0500
        Re: Two good reasons to go to Vulcan "Jamal" <jamal@examples.net> - 2013-04-21 21:36 -0400
          Re: Two good reasons to go to Vulcan "Jamal" <jamal@examples.net> - 2013-04-22 09:06 -0400
            Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-04-22 15:21 +0200
              Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-04-22 09:31 -0400
                Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-04-22 15:47 +0200
              Re: Two good reasons to go to Vulcan "Jamal" <jamal@examples.net> - 2013-04-22 13:41 -0400
              Re: Two good reasons to go to Vulcan "Willie Moore" <williem@wmconsulting.com> - 2013-04-22 14:12 -0500
                Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-04-23 14:12 +0200
                  Re: Two good reasons to go to Vulcan "Jamal" <jamal@examples.net> - 2013-04-23 09:44 -0400
                  Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-04-23 16:56 +0200
                    Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-04-23 17:19 +0200
                      Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-04-23 22:57 +0200
                        Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-04-24 09:56 +0200
                          Re: Two good reasons to go to Vulcan "Willie Moore" <williem@wmconsulting.com> - 2013-04-24 07:18 -0500
                            Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-04-24 14:47 +0200
                        Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-04-24 08:41 -0400
                          Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-04-24 19:24 +0200
                            Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-04-24 18:32 -0400
                              Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-03 14:07 +0200
                                Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-05-05 10:44 -0400
                                  Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-12 23:32 +0200
    Re: Two good reasons to go to Vulcan "richard.townsendrose" <richard.townsendrose@gmail.com> - 2013-04-29 06:57 -0700
      Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-03 13:10 +0200
        Re: Two good reasons to go to Vulcan Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2013-05-03 14:21 +0200
          Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-03 16:58 +0200
            Re: Two good reasons to go to Vulcan Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2013-05-03 17:52 +0200
    Re: Two good reasons to go to Vulcan "richard.townsendrose" <richard.townsendrose@gmail.com> - 2013-05-12 04:52 -0700
      Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-05-13 07:07 -0400
        Re: Two good reasons to go to Vulcan "Er!k \\/!$$Er" <nospam@nospam.url> - 2013-05-13 13:20 +0200
          Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-05-13 07:46 -0400
        Re: Two good reasons to go to Vulcan nicktekhne@googlemail.com - 2013-05-13 04:34 -0700
        Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-14 23:19 +0200
          Re: Two good reasons to go to Vulcan Mathias <mathias.hakansson@consultec.se> - 2013-05-14 23:59 -0700
            Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-15 13:11 +0200
          Re: Two good reasons to go to Vulcan "Ginny Caughey" <gcaughey@online.hotmail.com> - 2013-05-15 07:07 -0400
            Re: Two good reasons to go to Vulcan D.J.W. van Kooten <public@ic2remove.this.com> - 2013-05-15 17:17 +0200
      Re: Two good reasons to go to Vulcan Barbara <barbara*DeleteThis*@easytrip.net> - 2013-05-13 11:34 -0800

Page 1 of 3  [1] 2 3  Next page →


#5070 — Two good reasons to go to Vulcan

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2013-04-17 01:17 +0200
SubjectTwo good reasons to go to Vulcan
Message-ID<uqmrm8litmdhndu354c7l7ahc4h6dlahpv@4ax.com>
(Cross posted in the grafx public Vulcan NG)

For anyone who is still unsure between the choice Vulcan - VO, I have
2 good reasons:

1 http://www.ic2.com/cavo/WPFVersusVOScreen.jpg
2 The Grafx NG visitors

In 1, you see below a dialogbox which shows the users of my software
how many relations they have to approach today and the next few days.
The upper screen is the replacement: a WPF screen with lots of
features not or difficult to create in VO (I did wipe out recognizable
names a bit). WPF is the latest way to create windows using XAML code
to describe where you want what to display or happen. This mean you
can create almost any effect in Windows and could just pile up
anything into your window. So called code behind supports features you
define , e.g. what happens on a button click.


In the WPF window for example, the upper left title slides in like on
a Windows 8 Phone. Totally useless, but users seem to love this. The
buttons are W8 style and direct the user to the screen where the
reminders are displayed from. I call this screen from VO, passing
parameters and reading the choice made. The VO side is just a few
lines of code; making a suitable string to pass as arrays is not
possible and was one of the bigger jobs.

I think we will need this kind of lay-out to survive the upcoming
years.

As for the 2nd reason: you may argue that I could have done this all
in C#. True. There's lots of samples to start with. However, I usually
need to try half a dozen or more before one really works. I still
dislike the C# structure, especially the {} in which I always seem to
paste code on the wrong site of an { or } resulting in pages of
errors....And C# requires a lot more thinking about the syntax than
Vulcan. When I have a working C# sample, Reflector usually gives me
the right Vulcan code, or at least an idea how to get it. But most
important has been the tremendous amount of help I got on the Vulcan
NG; almost always directly usable and really beyond comparison with
more general C# websites.

Does this mean I will now rush to Vulcan? No, I must admit. I dislike
VS, really the only way to program Vulcan WPF programs currently. I
find the prg based editing instead of the sortable, movable and
selectable entity based VO editing a true disaster, and almost
anything I do takes considerable more time and effort in VS than it
takes in VO. Debugging WPF is non existent, the relation between the
visual WPF editor and the XAML code is tense to say it friendly and I
can add lots more like this. That is not to blame Vulcan, it's
.Net/Visual Studio and apparently to get these marvelous effects we
have to accept that. So for now I keep working in VO and gradually
move our UI towards the latest standards.

The code from VO:


	oVulcan := OLEAutoObject{"VulcanMethods.VOClass"}
	IF oVulcan:Finit
		cResult:=oVulcan:ShowWin(cDataParamaters)
	ENDIF


Dick

[toc] | [next] | [standalone]


#5086

From"Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it>
Date2013-04-18 15:56 +0200
Message-ID<kkott6$i10$1@dont-email.me>
In reply to#5070
The window you have made in WPF looks really nice.

Arne Ortlinghaus
ACS Data Systems



"D.J.W. van Kooten" <public@ic2remove.this.com> schrieb im Newsbeitrag 
news:uqmrm8litmdhndu354c7l7ahc4h6dlahpv@4ax.com...
> (Cross posted in the grafx public Vulcan NG)
>
> For anyone who is still unsure between the choice Vulcan - VO, I have
> 2 good reasons:
>
> 1 http://www.ic2.com/cavo/WPFVersusVOScreen.jpg
> 2 The Grafx NG visitors
>
> In 1, you see below a dialogbox which shows the users of my software
> how many relations they have to approach today and the next few days.
> The upper screen is the replacement: a WPF screen with lots of
> features not or difficult to create in VO (I did wipe out recognizable
> names a bit). WPF is the latest way to create windows using XAML code
> to describe where you want what to display or happen. This mean you
> can create almost any effect in Windows and could just pile up
> anything into your window. So called code behind supports features you
> define , e.g. what happens on a button click.
>
>
> In the WPF window for example, the upper left title slides in like on
> a Windows 8 Phone. Totally useless, but users seem to love this. The
> buttons are W8 style and direct the user to the screen where the
> reminders are displayed from. I call this screen from VO, passing
> parameters and reading the choice made. The VO side is just a few
> lines of code; making a suitable string to pass as arrays is not
> possible and was one of the bigger jobs.
>
> I think we will need this kind of lay-out to survive the upcoming
> years.
>
> As for the 2nd reason: you may argue that I could have done this all
> in C#. True. There's lots of samples to start with. However, I usually
> need to try half a dozen or more before one really works. I still
> dislike the C# structure, especially the {} in which I always seem to
> paste code on the wrong site of an { or } resulting in pages of
> errors....And C# requires a lot more thinking about the syntax than
> Vulcan. When I have a working C# sample, Reflector usually gives me
> the right Vulcan code, or at least an idea how to get it. But most
> important has been the tremendous amount of help I got on the Vulcan
> NG; almost always directly usable and really beyond comparison with
> more general C# websites.
>
> Does this mean I will now rush to Vulcan? No, I must admit. I dislike
> VS, really the only way to program Vulcan WPF programs currently. I
> find the prg based editing instead of the sortable, movable and
> selectable entity based VO editing a true disaster, and almost
> anything I do takes considerable more time and effort in VS than it
> takes in VO. Debugging WPF is non existent, the relation between the
> visual WPF editor and the XAML code is tense to say it friendly and I
> can add lots more like this. That is not to blame Vulcan, it's
> .Net/Visual Studio and apparently to get these marvelous effects we
> have to accept that. So for now I keep working in VO and gradually
> move our UI towards the latest standards.
>
> The code from VO:
>
>
> oVulcan := OLEAutoObject{"VulcanMethods.VOClass"}
> IF oVulcan:Finit
> cResult:=oVulcan:ShowWin(cDataParamaters)
> ENDIF
>
>
> Dick 

[toc] | [prev] | [next] | [standalone]


#5095

From"Jamal" <jamal@examples.net>
Date2013-04-19 12:41 -0400
Message-ID<kkrs3v$e56$1@speranza.aioe.org>
In reply to#5070
Dick,

One disadvantage: Without native 64bit DBF RDDs, you will still have to 
compile your app in x86 mode.

Jamal

"D.J.W. van Kooten"  wrote in message 
news:uqmrm8litmdhndu354c7l7ahc4h6dlahpv@4ax.com...

(Cross posted in the grafx public Vulcan NG)

For anyone who is still unsure between the choice Vulcan - VO, I have
2 good reasons:

1 http://www.ic2.com/cavo/WPFVersusVOScreen.jpg
2 The Grafx NG visitors

In 1, you see below a dialogbox which shows the users of my software
how many relations they have to approach today and the next few days.
The upper screen is the replacement: a WPF screen with lots of
features not or difficult to create in VO (I did wipe out recognizable
names a bit). WPF is the latest way to create windows using XAML code
to describe where you want what to display or happen. This mean you
can create almost any effect in Windows and could just pile up
anything into your window. So called code behind supports features you
define , e.g. what happens on a button click.


In the WPF window for example, the upper left title slides in like on
a Windows 8 Phone. Totally useless, but users seem to love this. The
buttons are W8 style and direct the user to the screen where the
reminders are displayed from. I call this screen from VO, passing
parameters and reading the choice made. The VO side is just a few
lines of code; making a suitable string to pass as arrays is not
possible and was one of the bigger jobs.

I think we will need this kind of lay-out to survive the upcoming
years.

As for the 2nd reason: you may argue that I could have done this all
in C#. True. There's lots of samples to start with. However, I usually
need to try half a dozen or more before one really works. I still
dislike the C# structure, especially the {} in which I always seem to
paste code on the wrong site of an { or } resulting in pages of
errors....And C# requires a lot more thinking about the syntax than
Vulcan. When I have a working C# sample, Reflector usually gives me
the right Vulcan code, or at least an idea how to get it. But most
important has been the tremendous amount of help I got on the Vulcan
NG; almost always directly usable and really beyond comparison with
more general C# websites.

Does this mean I will now rush to Vulcan? No, I must admit. I dislike
VS, really the only way to program Vulcan WPF programs currently. I
find the prg based editing instead of the sortable, movable and
selectable entity based VO editing a true disaster, and almost
anything I do takes considerable more time and effort in VS than it
takes in VO. Debugging WPF is non existent, the relation between the
visual WPF editor and the XAML code is tense to say it friendly and I
can add lots more like this. That is not to blame Vulcan, it's
.Net/Visual Studio and apparently to get these marvelous effects we
have to accept that. So for now I keep working in VO and gradually
move our UI towards the latest standards.

The code from VO:


oVulcan := OLEAutoObject{"VulcanMethods.VOClass"}
IF oVulcan:Finit
cResult:=oVulcan:ShowWin(cDataParamaters)
ENDIF


Dick 

[toc] | [prev] | [next] | [standalone]


#5098

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2013-04-21 10:56 +0200
Message-ID<v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com>
In reply to#5095
On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to 
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application. 

Dick

[toc] | [prev] | [next] | [standalone]


#5100

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2013-04-21 13:47 +0200
Message-ID<ldk7n85ckfre30b2p12dqrufj4p9b9c4l3@4ax.com>
In reply to#5098
On Sun, 21 Apr 2013 10:56:37 +0200, D.J.W. van Kooten
<public@ic2remove.this.com> wrote:

> And I can choose the .Net version, I targetted .4. It seems to
>work fine on 32 and 64 bit PC's, but I don't access databases from
>this Vulcan application. 
which is no problem...

Karl

[toc] | [prev] | [next] | [standalone]


#5101

From"Willie Moore" <williem@wmconsulting.com>
Date2013-04-21 07:29 -0500
Message-ID<kl0m3a$vt9$1@speranza.aioe.org>
In reply to#5098
Dick,

With Vulcan, everything you compile is done in x86 mode (which in not a big 
deal) even though it says all cpus. Where you will see a problem is if you 
start mixing Vulcan c# and vb in the same solution. In that case, you will 
need to compile the c# and vb for x86 or you cannot mix the classes (runtime 
error, not compile time). If you ar enot using the macro compiler or rdd 
classes, you can just use corflags to remove the x86 flag from your Vulcan 
and it will now run on any cpu.

This is important is you try to run your Vulcan dlls on a ISP that does not 
allow 32bit dlls.

Regards,
Willie
Vulcan VIP

"D.J.W. van Kooten"  wrote in message 
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5104

From"Jamal" <jamal@examples.net>
Date2013-04-21 21:36 -0400
Message-ID<kl246e$qd$1@speranza.aioe.org>
In reply to#5098
Hi Dick,

If you access DBF files from your app, then you should be OK; just brought 
this fact from past experience so it does surprise anyone when they hit this 
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message 
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5108

From"Jamal" <jamal@examples.net>
Date2013-04-22 09:06 -0400
Message-ID<kl3ck4$7cd$1@speranza.aioe.org>
In reply to#5104
Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just 
brought
this fact from past experience so it does NOT surprise anyone when they hit 
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5110

From"Er!k \\/!$$Er" <nospam@nospam.url>
Date2013-04-22 15:21 +0200
Message-ID<atkrqeFtnnjU1@mid.individual.net>
In reply to#5108
Hi Jamal,

Are you sure? Are you sure you can compile without the use of the 
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows 
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a 
bit hard to get it running without the VulcanRuntime, and those days Don 
Caton told us it was and will not be a supported scenario. Especially the 
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another 
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5111

From"Ginny Caughey" <gcaughey@online.hotmail.com>
Date2013-04-22 09:31 -0400
Message-ID<51753ba2$0$38947$c3e8da3$dbd57e7@news.astraweb.com>
In reply to#5110
Hi Erik,

Perhaps this has changed since Don left.

Ginny

"Er!k \/!$$Er"  wrote in message news:atkrqeFtnnjU1@mid.individual.net...

Hi Jamal,

Are you sure? Are you sure you can compile without the use of the
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a
bit hard to get it running without the VulcanRuntime, and those days Don
Caton told us it was and will not be a supported scenario. Especially the
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5112

From"Er!k \\/!$$Er" <nospam@nospam.url>
Date2013-04-22 15:47 +0200
Message-ID<atktb8Fu2beU1@mid.individual.net>
In reply to#5111
Hi Ginny,

Perhaps..  is not a confirmation.
<g>

Erik





"Ginny Caughey"  schreef in bericht 
news:51753ba2$0$38947$c3e8da3$dbd57e7@news.astraweb.com...

Hi Erik,

Perhaps this has changed since Don left.

Ginny

"Er!k \/!$$Er"  wrote in message news:atkrqeFtnnjU1@mid.individual.net...

Hi Jamal,

Are you sure? Are you sure you can compile without the use of the
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a
bit hard to get it running without the VulcanRuntime, and those days Don
Caton told us it was and will not be a supported scenario. Especially the
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5118

From"Jamal" <jamal@examples.net>
Date2013-04-22 13:41 -0400
Message-ID<kl3soe$ohn$1@speranza.aioe.org>
In reply to#5110
Hi Erik,

You got me! That would be problematic. I would think that If you use only 
.NET classes without using the 32bit Vulcan runtime assemblies, then you can 
build native 64bit apps.  If this has changed or does not work or works with 
new versions of Vulcan, I do not know. BTW, I have not used Vulcan for at 
least 2 years. This is no information on the Vulcan website on the various 
gotchas.

In the past, I ran into some issue where I wanted to run an app that uses 
the RDD runtime in x64 mode on Windows 2008 Server 64bit, and it would not 
work. The app had to be compiled in x86.

Jamal

"Er!k \/!$$Er"  wrote in message news:atkrqeFtnnjU1@mid.individual.net...

Hi Jamal,

Are you sure? Are you sure you can compile without the use of the
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a
bit hard to get it running without the VulcanRuntime, and those days Don
Caton told us it was and will not be a supported scenario. Especially the
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5121

From"Willie Moore" <williem@wmconsulting.com>
Date2013-04-22 14:12 -0500
Message-ID<kl422s$94o$1@speranza.aioe.org>
In reply to#5110
Erik,

You can compile a program that does not use any Vulcan Runtime. The dropbox 
link is a small Vulcan app that I showed at VODC a few years ago that is 
running with no runtime needed.

What is in the Vulcan runtime is the array support, macro compiler, and 
usual support. If you aren't using them, then you do not need the runtime. I 
use Vulcan because I like the syntax. I do not generally use the RDDs, 
Usuals, or runtime functions.

Regards,
Willie
Vulcan VIP

https://dl.dropboxusercontent.com/u/26130378/World%20Time.exe


"Er!k \/!$$Er"  wrote in message news:atkrqeFtnnjU1@mid.individual.net...

Hi Jamal,

Are you sure? Are you sure you can compile without the use of the
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a
bit hard to get it running without the VulcanRuntime, and those days Don
Caton told us it was and will not be a supported scenario. Especially the
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5125

From"Er!k \\/!$$Er" <nospam@nospam.url>
Date2013-04-23 14:12 +0200
Message-ID<atnc5tFg8h1U1@mid.individual.net>
In reply to#5121
Hi Willie,

I know it is possible to write/compile code without using the VulcanRuntime.
Question is, will it still be VO -alike syntax.
What about all the VO-Functions? They are part of the VulcanRuntime aren't 
they?

Anyway, I do not want to debate all the limitations of Vulcan again. I just 
jumped in to make a comment on the enthousiasm of Jamal: Vulcan, as if in a 
VO compatible .NET language,  is bound to Win32.

Erik



"Willie Moore"  schreef in bericht news:kl422s$94o$1@speranza.aioe.org...

Erik,

You can compile a program that does not use any Vulcan Runtime. The dropbox
link is a small Vulcan app that I showed at VODC a few years ago that is
running with no runtime needed.

What is in the Vulcan runtime is the array support, macro compiler, and
usual support. If you aren't using them, then you do not need the runtime. I
use Vulcan because I like the syntax. I do not generally use the RDDs,
Usuals, or runtime functions.

Regards,
Willie
Vulcan VIP

https://dl.dropboxusercontent.com/u/26130378/World%20Time.exe


"Er!k \/!$$Er"  wrote in message news:atkrqeFtnnjU1@mid.individual.net...

Hi Jamal,

Are you sure? Are you sure you can compile without the use of the
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a
bit hard to get it running without the VulcanRuntime, and those days Don
Caton told us it was and will not be a supported scenario. Especially the
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5128

From"Jamal" <jamal@examples.net>
Date2013-04-23 09:44 -0400
Message-ID<kl637c$b8b$1@speranza.aioe.org>
In reply to#5125
Erik,

>> enthousiasm of Jamal >>

Hardly!! <vbg>

Jamal

"Er!k \/!$$Er"  wrote in message news:atnc5tFg8h1U1@mid.individual.net...

Hi Willie,

I know it is possible to write/compile code without using the VulcanRuntime.
Question is, will it still be VO -alike syntax.
What about all the VO-Functions? They are part of the VulcanRuntime aren't
they?

Anyway, I do not want to debate all the limitations of Vulcan again. I just
jumped in to make a comment on the enthousiasm of Jamal: Vulcan, as if in a
VO compatible .NET language,  is bound to Win32.

Erik



"Willie Moore"  schreef in bericht news:kl422s$94o$1@speranza.aioe.org...

Erik,

You can compile a program that does not use any Vulcan Runtime. The dropbox
link is a small Vulcan app that I showed at VODC a few years ago that is
running with no runtime needed.

What is in the Vulcan runtime is the array support, macro compiler, and
usual support. If you aren't using them, then you do not need the runtime. I
use Vulcan because I like the syntax. I do not generally use the RDDs,
Usuals, or runtime functions.

Regards,
Willie
Vulcan VIP

https://dl.dropboxusercontent.com/u/26130378/World%20Time.exe


"Er!k \/!$$Er"  wrote in message news:atkrqeFtnnjU1@mid.individual.net...

Hi Jamal,

Are you sure? Are you sure you can compile without the use of the
VulcanRuntime or is the VulcanRunTime.dll 64 bits currently?
Years ago I have wrote a small datadriven  Vulcan app running on Windows
Mobile (using SqlServerCE ) (demo-ed it on the Cologn conference). It was a
bit hard to get it running without the VulcanRuntime, and those days Don
Caton told us it was and will not be a supported scenario. Especially the
operator-overloads could not be used.

Also I doubt the Vulcan macrocompiler will be able to run on another
platform than Win32.

I'm looking forward to your response

Erik




"Jamal"  schreef in bericht news:kl3ck4$7cd$1@speranza.aioe.org...

Sorry, I meant to write:

If you do NOT access DBF files from your app, then you should be OK; just
brought
this fact from past experience so it does NOT surprise anyone when they hit
this
limitation.

"Jamal"  wrote in message news:kl246e$qd$1@speranza.aioe.org...

Hi Dick,

If you access DBF files from your app, then you should be OK; just brought
this fact from past experience so it does surprise anyone when they hit this
limitation.

Jamal

"D.J.W. van Kooten"  wrote in message
news:v6a7n8dg9v7rb2bhsh1o8qucj57h90nb03@4ax.com...

On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <jamal@examples.net>
wrote:

Hello Jamal,
>
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>

I am not sure what I would need to do or do differently? In Visual
Studio, I have a choice Active (Any CPU) and that's the only one I can
choose. And I can choose the .Net version, I targetted .4. It seems to
work fine on 32 and 64 bit PC's, but I don't access databases from
this Vulcan application.

Dick 

[toc] | [prev] | [next] | [standalone]


#5129

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2013-04-23 16:56 +0200
Message-ID<328dn8djtfgf6v7erpcdok1abugsq5r228@4ax.com>
In reply to#5125
On Tue, 23 Apr 2013 14:12:43 +0200, "Er!k \\/!$$Er"
<nospam@nospam.url> wrote:

Hello Erik, Willie,

I probably miss the point here....

>I know it is possible to write/compile code without using the VulcanRuntime.
>Question is, will it still be VO -alike syntax.
>What about all the VO-Functions? They are part of the VulcanRuntime aren't 
>they?


I have a W7/64 installation. In my Vulcan created DLL, called from VO,
I added the following code as a test:

LOCAL odb as dbserver
	odb:=dbserver{"d:\iconnect\adres.dbf"}
	system.Windows.Forms.MessageBox.Show(odb:Fieldget(#naam))

I included 
C:\PF\Vulcan.NET 2.0\Assembly\v4.0\VulcanVORDDClasses.dll
as a reference.

Now when I call that Vulcan method, it shows the first name of the
DBF.

It works apparently on my 64 bit W7 system, I would say I don't care
if it's 64 or 128 or 16 bits?

Dick

[toc] | [prev] | [next] | [standalone]


#5130

From"Er!k \\/!$$Er" <nospam@nospam.url>
Date2013-04-23 17:19 +0200
Message-ID<atnn3kFimk1U1@mid.individual.net>
In reply to#5129
Hi Dick,

_As_long_as_ your OS supports Win32 applications there is no problem.
But as mentioned, Windows mobile has a few limitations.  Windows for iOS? 
Windows for Linux?
The simple fact there is a .NET framework does not say your Vulcn app will 
run fine.


Erik

"D.J.W. van Kooten"  schreef in bericht 
news:328dn8djtfgf6v7erpcdok1abugsq5r228@4ax.com...

On Tue, 23 Apr 2013 14:12:43 +0200, "Er!k \\/!$$Er"
<nospam@nospam.url> wrote:

Hello Erik, Willie,

I probably miss the point here....

>I know it is possible to write/compile code without using the 
>VulcanRuntime.
>Question is, will it still be VO -alike syntax.
>What about all the VO-Functions? They are part of the VulcanRuntime aren't
>they?


I have a W7/64 installation. In my Vulcan created DLL, called from VO,
I added the following code as a test:

LOCAL odb as dbserver
odb:=dbserver{"d:\iconnect\adres.dbf"}
system.Windows.Forms.MessageBox.Show(odb:Fieldget(#naam))

I included
C:\PF\Vulcan.NET 2.0\Assembly\v4.0\VulcanVORDDClasses.dll
as a reference.

Now when I call that Vulcan method, it shows the first name of the
DBF.

It works apparently on my 64 bit W7 system, I would say I don't care
if it's 64 or 128 or 16 bits?

Dick 

[toc] | [prev] | [next] | [standalone]


#5131

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2013-04-23 22:57 +0200
Message-ID<m5tdn8loaqusncq1dn94o231lio4438dm6@4ax.com>
In reply to#5130
On Tue, 23 Apr 2013 17:19:14 +0200, "Er!k \\/!$$Er"
<nospam@nospam.url> wrote:

Hello Erik,
>
>_As_long_as_ your OS supports Win32 applications there is no problem.
>But as mentioned, Windows mobile has a few limitations.  Windows for iOS? 
>Windows for Linux?
>The simple fact there is a .NET framework does not say your Vulcn app will 
>run fine.

I assumed indeed that would be enough. So there goes again another
advantage of .Net...

If I understand you correctly:

1 Vulcan applications will work on all .Net systems as long as none of
the Vulcan  dll's are included (so reading/writing dbf should be done
otherwise, which I have once tested and seen working in a C# program) 
2 Including Vulcan DLL's will not be a problem on Windows systems
3 Vulcan DLL's are basically 32 bits,  which may limit the working on
possible 64 bit systems as you mention above.

Can you or anyone confirm if one or more of these statements are
correct?

Dick

[toc] | [prev] | [next] | [standalone]


#5132

From"Er!k \\/!$$Er" <nospam@nospam.url>
Date2013-04-24 09:56 +0200
Message-ID<atphibFcknU1@mid.individual.net>
In reply to#5131
> I assumed indeed that would be enough. So there goes again
>  another advantage of .Net...

This is a Vulcan limitation, not one of .NET

The idea behind .NET is to offer a layer above the OS.  Every OS can / 
should have its own .NET framework
The application runs on top of the layer and as long as it does not interact 
with the OS directly, the app should run. (in theory)
Vulcan however does interact with the OS (Win32 API) and that is the reason 
it is bound to the OS that supports the Win32 API

So  a Vulcan Form (for example Datawindow ) uses the VulcanRuntime to call 
the Win32 API function CreateWindow.
On a Win32 compatible OS WinForm uses .NET to call the Win32 API function 
CreateWindow also, but on a Linux OS the .NET framework calls the Linux-GUI 
variant of CreateWindow.  So if you use Winform there is no problem, if you 
use Datawindow there is.


ad 1) In theory, but not all .NET systems implement the full .NET framework. 
For example if you code for Windows Mobile Phone there is only a subset of 
the framework available.
ad 2) In theory yes, but again, on a tablet you might run into limitations 
you do not face on a workstation
ad 3) Correct. See Willie's comment about ISP that do not allow 32-bit DLL's

In general, if the OS runs your VO app, your Vulcan app should run fine and 
Vulcan then offers you the wide spectrum of .NET abilities.


All this is based on my understanding of the material and in very few 
occasions I could be slightly wrong <g>

Erik







"D.J.W. van Kooten"  schreef in bericht 
news:m5tdn8loaqusncq1dn94o231lio4438dm6@4ax.com...

On Tue, 23 Apr 2013 17:19:14 +0200, "Er!k \\/!$$Er"
<nospam@nospam.url> wrote:

Hello Erik,
>
>_As_long_as_ your OS supports Win32 applications there is no problem.
>But as mentioned, Windows mobile has a few limitations.  Windows for iOS?
>Windows for Linux?
>The simple fact there is a .NET framework does not say your Vulcn app will
>run fine.

I assumed indeed that would be enough. So there goes again another
advantage of .Net...

If I understand you correctly:

1 Vulcan applications will work on all .Net systems as long as none of
the Vulcan  dll's are included (so reading/writing dbf should be done
otherwise, which I have once tested and seen working in a C# program)
2 Including Vulcan DLL's will not be a problem on Windows systems
3 Vulcan DLL's are basically 32 bits,  which may limit the working on
possible 64 bit systems as you mention above.

Can you or anyone confirm if one or more of these statements are
correct?

Dick 

[toc] | [prev] | [next] | [standalone]


#5134

From"Willie Moore" <williem@wmconsulting.com>
Date2013-04-24 07:18 -0500
Message-ID<kl8ij6$s6b$1@speranza.aioe.org>
In reply to#5132
Erik,

You make a very large assumption that everyone who uses Vulcan has stuck 
with datawindow. The only time I use a datawindow is when I am teaching 
someone how to take the first steps of moving from VO to Vulcan. I use 
Winforms or WPF depending on the job. I know for a fact that Dick is using 
WPF.

Regards,
Willie
Vulcan VIP

[toc] | [prev] | [next] | [standalone]


Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web