Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Two good reasons to go to Vulcan
559 views
Skip to first unread message
D.J.W. van Kooten
Apr 16, 2013, 7:17:49 PM4/16/13
to
(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
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
Arne Ortlinghaus
Apr 18, 2013, 9:56:37 AM4/18/13
to
The window you have made in WPF looks really nice.
Arne Ortlinghaus
ACS Data Systems
"D.J.W. van Kooten" <pub...@ic2remove.this.com> schrieb im Newsbeitrag
news:uqmrm8litmdhndu35...@4ax.com...
Arne Ortlinghaus
ACS Data Systems
"D.J.W. van Kooten" <pub...@ic2remove.this.com> schrieb im Newsbeitrag
news:uqmrm8litmdhndu35...@4ax.com...
Jamal
Apr 19, 2013, 12:41:28 PM4/19/13
to
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:uqmrm8litmdhndu35...@4ax.com...
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:uqmrm8litmdhndu35...@4ax.com...
D.J.W. van Kooten
Apr 21, 2013, 4:56:37 AM4/21/13
to
On Fri, 19 Apr 2013 12:41:28 -0400, "Jamal" <ja...@examples.net>
wrote:
Hello Jamal,
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
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
>One disadvantage: Without native 64bit DBF RDDs, you will still have to
>compile your app in x86 mode.
>
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
Karl Faller
Apr 21, 2013, 7:47:12 AM4/21/13
to
On Sun, 21 Apr 2013 10:56:37 +0200, D.J.W. van Kooten
<pub...@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...
<pub...@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.
Karl
Willie Moore
Apr 21, 2013, 8:29:34 AM4/21/13
to
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:v6a7n8dg9v7rb2bhs...@4ax.com...
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
Jamal
Apr 21, 2013, 9:36:14 PM4/21/13
to
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:v6a7n8dg9v7rb2bhs...@4ax.com...
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
Jamal
Apr 22, 2013, 9:06:15 AM4/22/13
to
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...
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...
Er!k \/!$$Er
Apr 22, 2013, 9:21:15 AM4/22/13
to
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...
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...
Ginny Caughey
Apr 22, 2013, 9:31:43 AM4/22/13
to
Hi Erik,
Perhaps this has changed since Don left.
Ginny
"Er!k \/!$$Er" wrote in message news:atkrqe...@mid.individual.net...
Perhaps this has changed since Don left.
Ginny
"Er!k \/!$$Er" wrote in message news:atkrqe...@mid.individual.net...
Er!k \/!$$Er
Apr 22, 2013, 9:47:17 AM4/22/13
to
Hi Ginny,
Perhaps.. is not a confirmation.
<g>
Erik
"Ginny Caughey" schreef in bericht
news:51753ba2$0$38947$c3e8da3$dbd...@news.astraweb.com...
Perhaps.. is not a confirmation.
<g>
Erik
"Ginny Caughey" schreef in bericht
news:51753ba2$0$38947$c3e8da3$dbd...@news.astraweb.com...
Jamal
Apr 22, 2013, 1:41:38 PM4/22/13
to
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:atkrqe...@mid.individual.net...
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:atkrqe...@mid.individual.net...
Willie Moore
Apr 22, 2013, 3:12:32 PM4/22/13
to
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:atkrqe...@mid.individual.net...
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:atkrqe...@mid.individual.net...
Er!k \/!$$Er
Apr 23, 2013, 8:12:43 AM4/23/13
to
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...
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...
Jamal
Apr 23, 2013, 9:44:17 AM4/23/13
to
Erik,
>> enthousiasm of Jamal >>
Hardly!! <vbg>
Jamal
"Er!k \/!$$Er" wrote in message news:atnc5t...@mid.individual.net...
>> enthousiasm of Jamal >>
Hardly!! <vbg>
Jamal
"Er!k \/!$$Er" wrote in message news:atnc5t...@mid.individual.net...
D.J.W. van Kooten
Apr 23, 2013, 10:56:28 AM4/23/13
to
On Tue, 23 Apr 2013 14:12:43 +0200, "Er!k \\/!$$Er"
<nos...@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
<nos...@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 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
Er!k \/!$$Er
Apr 23, 2013, 11:19:14 AM4/23/13
to
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:328dn8djtfgf6v7er...@4ax.com...
_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:328dn8djtfgf6v7er...@4ax.com...
D.J.W. van Kooten
Apr 23, 2013, 4:57:56 PM4/23/13
to
On Tue, 23 Apr 2013 17:19:14 +0200, "Er!k \\/!$$Er"
<nos...@nospam.url> wrote:
Hello Erik,
>
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
<nos...@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
>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.
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
Er!k \/!$$Er
Apr 24, 2013, 3:56:57 AM4/24/13
to
> I assumed indeed that would be enough. So there goes again
> another advantage of .Net...
This is a Vulcan limitation, not one of .NET
> another advantage 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
Willie Moore
Apr 24, 2013, 8:18:49 AM4/24/13
to
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
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
Ginny Caughey
Apr 24, 2013, 8:41:13 AM4/24/13
to
Hi Dick,
1. 32-bit is not a problem on 64-bit systems. (If it were you also couldn't
run VO apps on 64-bit systems, and they work just fine.) You just have to
make sure any DLLs you use are also 32-bit. The main problem you might have
would be working with 64-bit Excel.
2. .NET apps won't run as Windows Store or Windows Phone apps.
3. If you're seriously interested in cross-platform development for Windows,
Windows Store, Windows Phone, iOS and Android, you should be looking at
Xamarin, but you'll need to finally learn C# like the rest of us did a
decade ago. ;-)
Ginny
"D.J.W. van Kooten" wrote in message
news:m5tdn8loaqusncq1d...@4ax.com...
1. 32-bit is not a problem on 64-bit systems. (If it were you also couldn't
run VO apps on 64-bit systems, and they work just fine.) You just have to
make sure any DLLs you use are also 32-bit. The main problem you might have
would be working with 64-bit Excel.
2. .NET apps won't run as Windows Store or Windows Phone apps.
3. If you're seriously interested in cross-platform development for Windows,
Windows Store, Windows Phone, iOS and Android, you should be looking at
Xamarin, but you'll need to finally learn C# like the rest of us did a
decade ago. ;-)
Ginny
"D.J.W. van Kooten" wrote in message
Er!k \/!$$Er
Apr 24, 2013, 8:47:02 AM4/24/13
to
Willie,
You do not read what I wrote neither do you see the context of it. You do
not help Dick or anyone else if you do not explain the limitations of the
product.
I only use it as an example, in the context of Dick's questions.
If you prefer I could have mentioned the internet classes or a lot of other
stuff as well.
Erik
"Willie Moore" schreef in bericht news:kl8ij6$s6b$1...@speranza.aioe.org...
You do not read what I wrote neither do you see the context of it. You do
not help Dick or anyone else if you do not explain the limitations of the
product.
I only use it as an example, in the context of Dick's questions.
If you prefer I could have mentioned the internet classes or a lot of other
stuff as well.
Erik
"Willie Moore" schreef in bericht news:kl8ij6$s6b$1...@speranza.aioe.org...
D.J.W. van Kooten
Apr 24, 2013, 1:24:37 PM4/24/13
to
On Wed, 24 Apr 2013 08:41:13 -0400, "Ginny Caughey"
<gcau...@online.hotmail.com> wrote:
Hello Ginny, Erik, Willie,
Thanks for the explanations. It looks to me that these are not a
serious limitations for me. I don't see much advantage of going to
Vulcan and keeping everything the VO way, indeed I am using WPF now.
I'll just have to think about what to do with DBF access, but when
this is going to be important there are other ways to use them.
>3. If you're seriously interested in cross-platform development for Windows,
>Windows Store, Windows Phone, iOS and Android, you should be looking at
>Xamarin, but you'll need to finally learn C# like the rest of us did a
>decade ago. ;-)
>
First of all, I think that "the rest of us" isn't actually those VO
programmers who are potential or current Vulcan users. Those who moved
to C# will not be using Vulcan and just maintain existing VO
applications. I believe like you do. But second, you're behind in your
knowledge of what I have to learn <g> as I actually started using C# a
year ago. Currently I have a few small C# applications being the code
behind of ASP.Net screens.
There's definitely a lot I don't know yet, and I dislike C# as much as
VS (for the same reason I still don't like Vulcan, which is the
.cs/.prg based editing and in C# it's even worse because I always seem
to add code on the wrong side of one of these terrible accolades) but
I can and will use it if necessary. Vulcan saves a lot of lookup time
because of the familiair syntax.
Dick
<gcau...@online.hotmail.com> wrote:
Hello Ginny, Erik, Willie,
Thanks for the explanations. It looks to me that these are not a
serious limitations for me. I don't see much advantage of going to
Vulcan and keeping everything the VO way, indeed I am using WPF now.
I'll just have to think about what to do with DBF access, but when
this is going to be important there are other ways to use them.
>3. If you're seriously interested in cross-platform development for Windows,
>Windows Store, Windows Phone, iOS and Android, you should be looking at
>Xamarin, but you'll need to finally learn C# like the rest of us did a
>decade ago. ;-)
>
programmers who are potential or current Vulcan users. Those who moved
to C# will not be using Vulcan and just maintain existing VO
applications. I believe like you do. But second, you're behind in your
knowledge of what I have to learn <g> as I actually started using C# a
year ago. Currently I have a few small C# applications being the code
behind of ASP.Net screens.
There's definitely a lot I don't know yet, and I dislike C# as much as
VS (for the same reason I still don't like Vulcan, which is the
.cs/.prg based editing and in C# it's even worse because I always seem
to add code on the wrong side of one of these terrible accolades) but
I can and will use it if necessary. Vulcan saves a lot of lookup time
because of the familiair syntax.
Dick
Ginny Caughey
Apr 24, 2013, 6:32:35 PM4/24/13
to
hi Dick,
Good to hear you are using C# now! When you have used it for as long as I
have, you will prefer it to VO I assure.
I agree that as long as the VO code works there's no compelling reason to
rewrite it, and if someday Microsoft builds an OS that won't run it in some
way, that's the day they will be out of business. ;)
Ginny
"D.J.W. van Kooten" wrote in message
news:2h4gn8de1dgso4v1a...@4ax.com...
Good to hear you are using C# now! When you have used it for as long as I
have, you will prefer it to VO I assure.
I agree that as long as the VO code works there's no compelling reason to
rewrite it, and if someday Microsoft builds an OS that won't run it in some
way, that's the day they will be out of business. ;)
Ginny
"D.J.W. van Kooten" wrote in message
richard.townsendrose
Apr 29, 2013, 9:57:18 AM4/29/13
to
Dick
I agree with you on certain things, and not on others.
I see absolutely no reason why you shouldn't have designed your new window in VO ... its "different" thats all.
On editing ... VS is like going back to clipper editing. and then Peter Norton produced a tool to make it easier. phpDesigner uses similar techniques
and then came VO. It was hugely expensive to develop ... but it is THE FASTEST development environment around - and also hugely powerful.
I come form the VO is a TOOL to be used by engineers to develop applications to handle their data which they use in their "day job".
If you want to be a saaaaafi software man ... then play poke, drink whiskey, and use C# or visual studio.
It's the same as calling file manager "windows explorer" - simply a daft idea using FIVE syllables when THREE simpler more descriptive ones will do.
richard
I agree with you on certain things, and not on others.
I see absolutely no reason why you shouldn't have designed your new window in VO ... its "different" thats all.
On editing ... VS is like going back to clipper editing. and then Peter Norton produced a tool to make it easier. phpDesigner uses similar techniques
and then came VO. It was hugely expensive to develop ... but it is THE FASTEST development environment around - and also hugely powerful.
I come form the VO is a TOOL to be used by engineers to develop applications to handle their data which they use in their "day job".
If you want to be a saaaaafi software man ... then play poke, drink whiskey, and use C# or visual studio.
It's the same as calling file manager "windows explorer" - simply a daft idea using FIVE syllables when THREE simpler more descriptive ones will do.
richard
D.J.W. van Kooten
May 3, 2013, 7:10:45 AM5/3/13
to
On Mon, 29 Apr 2013 06:57:18 -0700 (PDT), "richard.townsendrose"
<richard.to...@gmail.com> wrote:
Hello Richard,
know how to accomplish in VO, like the sliding text and the rounded
boxes. In general, WPF allows me to do much more 'standard' while in
VO it would require large amount of incomprehensible code.
I still use Hover Buttons. This is a brilliant product which allows me
to add a limited amount of design options to the standard VO push
button but nor more than that. The code is 15 years old and I frankly
don't understand how it works. As a contrast, all Hover button effects
can be built in a WPF form in "no time"
>
>On editing ... VS is like going back to clipper editing. and then Peter Norton produced a tool to make it easier. phpDesigner uses similar techniques
>and then came VO. It was hugely expensive to develop ... but it is THE FASTEST development environment around - and also hugely powerful.
True. I still find VS a nightmare compared to VO.
Dick
<richard.to...@gmail.com> wrote:
Hello Richard,
>
>I see absolutely no reason why you shouldn't have designed your new window in VO ... its "different" thats all.
There are a few, in this window mainly graphical, things I wouldn't
>I see absolutely no reason why you shouldn't have designed your new window in VO ... its "different" thats all.
know how to accomplish in VO, like the sliding text and the rounded
boxes. In general, WPF allows me to do much more 'standard' while in
VO it would require large amount of incomprehensible code.
I still use Hover Buttons. This is a brilliant product which allows me
to add a limited amount of design options to the standard VO push
button but nor more than that. The code is 15 years old and I frankly
don't understand how it works. As a contrast, all Hover button effects
can be built in a WPF form in "no time"
>
>On editing ... VS is like going back to clipper editing. and then Peter Norton produced a tool to make it easier. phpDesigner uses similar techniques
>and then came VO. It was hugely expensive to develop ... but it is THE FASTEST development environment around - and also hugely powerful.
Dick
D.J.W. van Kooten
May 3, 2013, 8:07:01 AM5/3/13
to
On Wed, 24 Apr 2013 18:32:35 -0400, "Ginny Caughey"
<gcau...@online.hotmail.com> wrote:
Hello Ginny
>
seriously, with the exception of some nice things like lists or
FOR-EACH (the latter hardly more efficient than a for..next) I don't
see anything I prefer in C#, even when I try to rule out the factor
"being used to".
To summarize a few things:
* The entity based coding in VO which you can open, edit and move
everywhere and it keeps working, as the first line shows the class to
which it belongs. As Richard states in this post, with .Net we're back
to Clipper editing, but it's even worse, as adding any piece code
means that you always have to find out where exactly you add it,
within the right class-end class/namespace and outside the {}.
* VS versus VO
* Intellisense much more time saving in VO than in VS.
In other words, a year after starting VS (and C#) I have still no
reasons to change colours on this comparing overview:
www.ic2.com/cavo/VoVSVulcan.html
and even had to "downgrade" debugging as it doesn't seem to be the
improvement above VO I first thought it did.
Dick
<gcau...@online.hotmail.com> wrote:
Hello Ginny
>
>Good to hear you are using C# now! When you have used it for as long as I
>have, you will prefer it to VO I assure.
This must mean that you're using it a few 100 years now <g>. But
>have, you will prefer it to VO I assure.
seriously, with the exception of some nice things like lists or
FOR-EACH (the latter hardly more efficient than a for..next) I don't
see anything I prefer in C#, even when I try to rule out the factor
"being used to".
To summarize a few things:
* The entity based coding in VO which you can open, edit and move
everywhere and it keeps working, as the first line shows the class to
which it belongs. As Richard states in this post, with .Net we're back
to Clipper editing, but it's even worse, as adding any piece code
means that you always have to find out where exactly you add it,
within the right class-end class/namespace and outside the {}.
* VS versus VO
* Intellisense much more time saving in VO than in VS.
In other words, a year after starting VS (and C#) I have still no
reasons to change colours on this comparing overview:
www.ic2.com/cavo/VoVSVulcan.html
and even had to "downgrade" debugging as it doesn't seem to be the
improvement above VO I first thought it did.
Dick
Karl Faller
May 3, 2013, 8:21:50 AM5/3/13
to
Dick,
Talking of incomprehensible, yesterday hat a look at a sample
Sepa-Transfer XML-File , yeah....
Karl
>There are a few, in this window mainly graphical, things I wouldn't
>know how to accomplish in VO, like the sliding text and the rounded
>boxes. In general, WPF allows me to do much more 'standard' while in
>VO it would require large amount of incomprehensible code.
at least with Graphics4Vo i'd assume this not to be true ;-)
>know how to accomplish in VO, like the sliding text and the rounded
>boxes. In general, WPF allows me to do much more 'standard' while in
>VO it would require large amount of incomprehensible code.
Talking of incomprehensible, yesterday hat a look at a sample
Sepa-Transfer XML-File , yeah....
Karl
D.J.W. van Kooten
May 3, 2013, 10:58:25 AM5/3/13
to
On Fri, 03 May 2013 14:21:50 +0200, Karl Faller
<mail_withoutthat_@_drei-f_andthat_.de> wrote:
Hello Karl,
>at least with Graphics4Vo i'd assume this not to be true ;-)
No, certainly true. Still I am not sure if I could use this for
buttons.
>Talking of incomprehensible, yesterday hat a look at a sample
>Sepa-Transfer XML-File , yeah....
Well, that is true too. XML/XAML isn't necessarily clear. For a simple
screen I've got a lot XAML lines. But in general I think I am able to
understand how things are build up, while I have not that idea with
lines like this:
GetIconInfo(SELF:lpHBInfo.hIcon,@lpIcon)
GetObject(lpIcon.hbmColor,_SIZEOF(_WINBITMAP),@lpBitmap)
Dick
<mail_withoutthat_@_drei-f_andthat_.de> wrote:
Hello Karl,
>at least with Graphics4Vo i'd assume this not to be true ;-)
buttons.
>Talking of incomprehensible, yesterday hat a look at a sample
>Sepa-Transfer XML-File , yeah....
screen I've got a lot XAML lines. But in general I think I am able to
understand how things are build up, while I have not that idea with
lines like this:
GetIconInfo(SELF:lpHBInfo.hIcon,@lpIcon)
GetObject(lpIcon.hbmColor,_SIZEOF(_WINBITMAP),@lpBitmap)
Dick
Karl Faller
May 3, 2013, 11:52:56 AM5/3/13
to
Dick,
... New function for 3D text.
Font-smoothing (anti-aliasing) for text selectable.
New round and rounded transparent and opaque Pushbuttons with text and
images.
New gradient and spot functions with color saturation.
....
>>Talking of incomprehensible, yesterday hat a look at a sample
>>Sepa-Transfer XML-File , yeah....
>
>
>Well, that is true too. XML/XAML isn't necessarily clear. For a simple
>screen I've got a lot XAML lines. But in general I think I am able to
>understand how things are build up, while I have not that idea with
>lines like this:
>
>GetIconInfo(SELF:lpHBInfo.hIcon,@lpIcon)
>GetObject(lpIcon.hbmColor,_SIZEOF(_WINBITMAP),@lpBitmap)
not sure. To understand this, you have to "learn" some basics. But to
"understand" xml, too, only then you have to "digest" the heaps of
blabla in most xml...
BTW, just got me through half of "CSS3 The Missing Manual", which
makes good read, especially what you may do with HTML5. But what
really made me chuckle, was in the introduction: About Html it's way
to XHtml and how this simply failed in the den, so back to 5 with Css
;-)
Karl
>>at least with Graphics4Vo i'd assume this not to be true ;-)
>
>No, certainly true. Still I am not sure if I could use this for
>buttons.
just from Fred's site copied:
>
>No, certainly true. Still I am not sure if I could use this for
>buttons.
... New function for 3D text.
Font-smoothing (anti-aliasing) for text selectable.
New round and rounded transparent and opaque Pushbuttons with text and
images.
New gradient and spot functions with color saturation.
....
>>Talking of incomprehensible, yesterday hat a look at a sample
>>Sepa-Transfer XML-File , yeah....
>
>
>Well, that is true too. XML/XAML isn't necessarily clear. For a simple
>screen I've got a lot XAML lines. But in general I think I am able to
>understand how things are build up, while I have not that idea with
>lines like this:
>
>GetIconInfo(SELF:lpHBInfo.hIcon,@lpIcon)
>GetObject(lpIcon.hbmColor,_SIZEOF(_WINBITMAP),@lpBitmap)
"understand" xml, too, only then you have to "digest" the heaps of
blabla in most xml...
BTW, just got me through half of "CSS3 The Missing Manual", which
makes good read, especially what you may do with HTML5. But what
really made me chuckle, was in the introduction: About Html it's way
to XHtml and how this simply failed in the den, so back to 5 with Css
;-)
Karl
Ginny Caughey
May 5, 2013, 10:44:27 AM5/5/13
to
Hi Dick,
It looks like most of your Visual Studio complaints are really Vulcan
complaints.
Ginny
"D.J.W. van Kooten" wrote in message
news:op67o85vud49rnahc...@4ax.com...
It looks like most of your Visual Studio complaints are really Vulcan
complaints.
Ginny
"D.J.W. van Kooten" wrote in message
richard.townsendrose
May 12, 2013, 7:52:17 AM5/12/13
to
Dick, Ginny
the problem with vulcan and vs is that they do NOT meet the objective of providing professionals like engineers with a TOOL within which to develop a solution WITHOUT being a software nerd.
Dr Pick invented dbase to allow mcdonnell douglas engineers to manage their data direct on screen ... viz the "the dot prompt"
dbase led to clipper - same syntax a lot faster
then clipper to vo - same syntax plus a lot lot more and in windows, tho for many years windows was simply not up to running decent applications
now [that says how old i am] since NT came out - NOT written originally in house but by the dec-vax team i believe we have something thats half ways stable
anyway life moves on ... but preferably NOT [aka microsoft tools] backwards
see here for some fun ..
http://web.archive.org/web/20000916120827/http://ourworld.compuserve.com/
homepages/TDOC/
and now go here http://www.wp.tdocplus.co.uk/
that's joomla 2.5.11 under php 4.4.17 with sql 5.5.27
joomla meets the objective mentioned above - but visual studio - another long word for a pile of sh******** like file manager >>>> windows explorer which means actually file manager so why not say so ? all designed to bull shit accountants into parting with more and more cash ... or something ...
richard
the problem with vulcan and vs is that they do NOT meet the objective of providing professionals like engineers with a TOOL within which to develop a solution WITHOUT being a software nerd.
Dr Pick invented dbase to allow mcdonnell douglas engineers to manage their data direct on screen ... viz the "the dot prompt"
dbase led to clipper - same syntax a lot faster
then clipper to vo - same syntax plus a lot lot more and in windows, tho for many years windows was simply not up to running decent applications
now [that says how old i am] since NT came out - NOT written originally in house but by the dec-vax team i believe we have something thats half ways stable
anyway life moves on ... but preferably NOT [aka microsoft tools] backwards
see here for some fun ..
http://web.archive.org/web/20000916120827/http://ourworld.compuserve.com/
homepages/TDOC/
and now go here http://www.wp.tdocplus.co.uk/
that's joomla 2.5.11 under php 4.4.17 with sql 5.5.27
joomla meets the objective mentioned above - but visual studio - another long word for a pile of sh******** like file manager >>>> windows explorer which means actually file manager so why not say so ? all designed to bull shit accountants into parting with more and more cash ... or something ...
richard
D.J.W. van Kooten
May 12, 2013, 5:32:35 PM5/12/13
to
On Sun, 5 May 2013 10:44:27 -0400, "Ginny Caughey"
<gcau...@online.hotmail.com> wrote:
Hello Ginny,
C# quite inferior to what I am used to in VO.
Dick
<gcau...@online.hotmail.com> wrote:
Hello Ginny,
>
>It looks like most of your Visual Studio complaints are really Vulcan
>complaints.
>
In that overview I compare VO versus Vulcan. But I also find VS with
>It looks like most of your Visual Studio complaints are really Vulcan
>complaints.
>
C# quite inferior to what I am used to in VO.
Dick
Ginny Caughey
May 13, 2013, 7:07:22 AM5/13/13
to
I agree that Visual Studio is targeted at professional software developers
rather than accountants or other kinds of engineers. It's not the right tool
for everybody. Since I am a professional software engineer supporting
several platforms, it works quite well for me. It is painful to me to have
to do maintenance work in VO, but I would say the same if I still maintained
embedded C++ apps or any other equally old technology.
Vulcan is an interesting hybrid. It retains some aspects of the old
Clipper/dBase language but is modern in other ways. it is also not the right
tool for everybody, but like Visual Studio could be the ideal tool for some
people.
Ginny
"richard.townsendrose" wrote in message
news:6cdc8b7e-6b00-467f...@googlegroups.com...
rather than accountants or other kinds of engineers. It's not the right tool
for everybody. Since I am a professional software engineer supporting
several platforms, it works quite well for me. It is painful to me to have
to do maintenance work in VO, but I would say the same if I still maintained
embedded C++ apps or any other equally old technology.
Vulcan is an interesting hybrid. It retains some aspects of the old
Clipper/dBase language but is modern in other ways. it is also not the right
tool for everybody, but like Visual Studio could be the ideal tool for some
people.
Ginny
"richard.townsendrose" wrote in message
news:6cdc8b7e-6b00-467f...@googlegroups.com...
Er!k \/!$$Er
May 13, 2013, 7:20:22 AM5/13/13
to
Hi Ginny,
Agreed.
> Since I am a professional software engineer
I think you could have been an excelent diplomat as well!
Erik
"Ginny Caughey" schreef in bericht
news:5190c94e$0$1252$c3e8da3$fdf4...@news.astraweb.com...
Agreed.
> Since I am a professional software engineer
Erik
"Ginny Caughey" schreef in bericht
nickt...@googlemail.com
May 13, 2013, 7:34:06 AM5/13/13
to
Ouchhhh... that's got to hurt!
Nick
Nick
Ginny Caughey
May 13, 2013, 7:46:20 AM5/13/13
to
Thanks, Erik! :)
"Er!k \/!$$Er" wrote in message news:avc0jo...@mid.individual.net...
"Er!k \/!$$Er" wrote in message news:avc0jo...@mid.individual.net...
Barbara
May 13, 2013, 3:34:14 PM5/13/13
to
> Dr Pick invented dbase to allow mcdonnell douglas engineers to manage their
> data direct on screen ... viz the "the dot prompt"
this information. dBase was a derivation of a project created by
programmers at JPL. It was taken over by Jeb Long and Ashton-Tate was
the marketing company.
From Wikipedia:
"While working at JPL as a contractor, C. Wayne Ratliff entered the
office football pool. He had no interest in the game, but felt he could
win the pool by processing the post-game statistics found in the
newspapers."
I happen to still be good friends with one of the six (or maybe seven)
of the original C programmers that created dBase II. The stories are
wild and oddly involve a fair amount of alcohol. My desk was right next
to the person that wrote the dot prompt and he always thought it was
strange.
One other interesting fact about the original team was that no one knew
C at the time, they learned it while writing dBase II.
Barbara
D.J.W. van Kooten
May 14, 2013, 5:19:45 PM5/14/13
to
On Mon, 13 May 2013 07:07:22 -0400, "Ginny Caughey"
<gcau...@online.hotmail.com> wrote:
Hello Ginny,
>I agree that Visual Studio is targeted at professional software developers
Below a question I asked in the Grafx NG as I couldn't find a solution
on the internet. It has not been answered (yet) while most posts get
an answer there very quickly. Hence I assume that assigning a separate
shortcut key to just search in the current document is not possible;
one of the growing list of things where I find VS inferior to VO.
Just our of curiosity: do professional software developers like to add
a few extra mouse clicks to do basic searching (compared to, I assume,
the non professional VO developer who can use Ctrl Alt F)? Or, more in
general, is it more professional to work with slower compilers and do
more typing for the same amount of coding nowadays than we were used
to in VO?
I think it is important that we have the defined what a "professional
software developer" all appreciates.
(PS: I understand that developing for multiple platform in just one
enviroment has advantages. But IMO it comes at a huge price in terms
of efficiency that this platform has to be VS) .
Dick
===============
"In VO, I find the new (SP4) option very handy to use Ctrl Alt F for
just searching in the current document (as opposed to Ctrl F,
searching in the last used range)
It looks like this is not possible in VS. Ctrl F always searches in
the last used range, so you will usually need to use the mouse to
select Current Document. And I didn't find a suitable edit.find in
Customize/keyboard either."
<gcau...@online.hotmail.com> wrote:
Hello Ginny,
>I agree that Visual Studio is targeted at professional software developers
on the internet. It has not been answered (yet) while most posts get
an answer there very quickly. Hence I assume that assigning a separate
shortcut key to just search in the current document is not possible;
one of the growing list of things where I find VS inferior to VO.
Just our of curiosity: do professional software developers like to add
a few extra mouse clicks to do basic searching (compared to, I assume,
the non professional VO developer who can use Ctrl Alt F)? Or, more in
general, is it more professional to work with slower compilers and do
more typing for the same amount of coding nowadays than we were used
to in VO?
I think it is important that we have the defined what a "professional
software developer" all appreciates.
(PS: I understand that developing for multiple platform in just one
enviroment has advantages. But IMO it comes at a huge price in terms
of efficiency that this platform has to be VS) .
Dick
===============
"In VO, I find the new (SP4) option very handy to use Ctrl Alt F for
just searching in the current document (as opposed to Ctrl F,
searching in the last used range)
It looks like this is not possible in VS. Ctrl F always searches in
the last used range, so you will usually need to use the mouse to
select Current Document. And I didn't find a suitable edit.find in
Customize/keyboard either."
Mathias
May 15, 2013, 2:59:30 AM5/15/13
to
Hi Dick,
Haven't tried this myself, but this tool seems to do searching in the current code window...
http://visualstudiogallery.msdn.microsoft.com/4269ce70-ca0f-4ca9-8132-700ec72b41d4
There's also a lot of other addons for Visual Studio that does useful things.
/Mathias
Haven't tried this myself, but this tool seems to do searching in the current code window...
http://visualstudiogallery.msdn.microsoft.com/4269ce70-ca0f-4ca9-8132-700ec72b41d4
There's also a lot of other addons for Visual Studio that does useful things.
/Mathias
Ginny Caughey
May 15, 2013, 7:07:36 AM5/15/13
to
Hi Dick,
I'm really not familiar with the way Vulcan and Visual Studio work together,
sorry. Using C# and Visual Studio 2012 you can search or search/replace
within the current document, project, or solution, or find all. I use it all
the time but I've never bothered to try using extra short-cut keys for it.
The Search dialog remember what I wanted the last time so if it was current
document, then it still is unless I change it. What I use far more often are
the refactoring tools, which I don't know if Vulcan supports.
Ginny
"D.J.W. van Kooten" wrote in message
news:8m95p8dmqu9ls29ea...@4ax.com...
I'm really not familiar with the way Vulcan and Visual Studio work together,
sorry. Using C# and Visual Studio 2012 you can search or search/replace
within the current document, project, or solution, or find all. I use it all
the time but I've never bothered to try using extra short-cut keys for it.
The Search dialog remember what I wanted the last time so if it was current
document, then it still is unless I change it. What I use far more often are
the refactoring tools, which I don't know if Vulcan supports.
Ginny
"D.J.W. van Kooten" wrote in message
D.J.W. van Kooten
May 15, 2013, 7:11:18 AM5/15/13
to
On Tue, 14 May 2013 23:59:30 -0700 (PDT), Mathias
<mathias....@consultec.se> wrote:
Hello Mathias,
>Haven't tried this myself, but this tool seems to do searching in the current code window...
>
>http://visualstudiogallery.msdn.microsoft.com/4269ce70-ca0f-4ca9-8132-700ec72b41d4
Terrific! This works exactly as want it, thank you. I found a couple
of websites (like stackoverflow) where people also asked for this
feature; I must be posting them this link.
>There's also a lot of other addons for Visual Studio that does useful things.
I've downloaded some other add ons from this site already but hadn't
found that one. With a bit of luck, and lots of add ons installed, VS
may come close to VO some day in terms of professionalism <g>.
Dick
<mathias....@consultec.se> wrote:
Hello Mathias,
>Haven't tried this myself, but this tool seems to do searching in the current code window...
>
>http://visualstudiogallery.msdn.microsoft.com/4269ce70-ca0f-4ca9-8132-700ec72b41d4
of websites (like stackoverflow) where people also asked for this
feature; I must be posting them this link.
>There's also a lot of other addons for Visual Studio that does useful things.
found that one. With a bit of luck, and lots of add ons installed, VS
may come close to VO some day in terms of professionalism <g>.
Dick
D.J.W. van Kooten
May 15, 2013, 11:17:57 AM5/15/13
to
On Wed, 15 May 2013 07:07:36 -0400, "Ginny Caughey"
<gcau...@online.hotmail.com> wrote:
Hello Ginny,
>
the day having done quickly. I requested Ctrl Alt F in VO SP4 and it
saves me a lot of time not having to look what my latest search was.
Before, countless time I had to start over my seach action to use the
current document and I found it very disappointing that in VS this all
started again.
Fortunately both Mathias solution as Marc's (using Ctrl I(ncremental)
as a trick are doing the job here.
>What I use far more often are
>the which I use all the day tools, which I don't know if Vulcan supports.
Sure that is something which is not present in VO. I willl take a look
later to see if these work and are of any use in Vulcan.
Dick
<gcau...@online.hotmail.com> wrote:
Hello Ginny,
>
>I use it all the time but I've never bothered to try using extra short-cut keys for it.
>The Search dialog remember what I wanted the last time so if it was current
>document, then it still is unless I change it.
I think I am very focussed on sometimes small things which I use all
>The Search dialog remember what I wanted the last time so if it was current
>document, then it still is unless I change it.
the day having done quickly. I requested Ctrl Alt F in VO SP4 and it
saves me a lot of time not having to look what my latest search was.
Before, countless time I had to start over my seach action to use the
current document and I found it very disappointing that in VS this all
started again.
Fortunately both Mathias solution as Marc's (using Ctrl I(ncremental)
as a trick are doing the job here.
>What I use far more often are
Sure that is something which is not present in VO. I willl take a look
later to see if these work and are of any use in Vulcan.
Dick
0 new messages