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


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

Vulcan build 208

Started by"Willie Moore" <williem@wmconsulting.com>
First post2011-09-30 14:01 -0500
Last post2011-10-04 12:03 +0200
Articles 20 on this page of 45 — 13 participants

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


Contents

  Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-09-30 14:01 -0500
    Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-04 09:59 +0200
      Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-05 19:34 -0500
        Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 09:09 +0200
          Re: Vulcan build 208 Johan Nel <johan.nel@xsinet.co.za> - 2011-10-06 00:35 -0700
            Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 11:33 +0200
              Re: Vulcan build 208 Johan Nel <johan.nel@xsinet.co.za> - 2011-10-06 03:51 -0700
                Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 13:28 +0200
                Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-06 15:28 +0200
              Re: Vulcan build 208 "Ginny Caughey" <ginny.online@hotmail.com> - 2011-10-06 08:08 -0400
                Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 07:47 -0500
                Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 17:03 +0200
                  Re: Vulcan build 208 "Ginny Caughey" <ginny.online@hotmail.com> - 2011-10-07 08:27 -0400
                    Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-07 08:51 -0500
                      Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-08 16:01 -0700
                        Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-09 10:11 -0500
                    Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 16:47 +0200
          Re: Vulcan build 208 "Dirk (Belgium)" <dirk.dot.herijgers@pbprojects.dot.be> - 2011-10-06 07:36 +0000
            Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 11:48 +0200
          Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 07:27 -0500
            Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-06 15:32 +0200
              Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 09:36 -0500
                Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-06 19:33 +0200
                  Re: Vulcan build 208 "Willie Moore" <williem@wmconsulting.com> - 2011-10-06 14:09 -0500
                  Re: Vulcan build 208 Massimo Bighelli <info@arcasistemi.it> - 2011-10-06 22:57 +0200
                    Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-06 23:39 +0200
                    Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-07 14:46 +0200
                      Re: Vulcan build 208 Massimo Bighelli <info@arcasistemi.it> - 2011-10-08 14:51 +0200
                  Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 12:04 +0200
                  Re: Vulcan build 208 "Marc Verkade [Marti]" <marcatm@rti.nl> - 2011-10-07 15:52 +0200
                    Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-08 14:16 +0200
            Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-06 17:15 +0200
              Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-06 19:07 +0200
                Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 12:03 +0200
                  Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-07 14:41 +0200
                    Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 17:03 +0200
                      Re: Vulcan build 208 Karl Faller <k.faller_withoutthat_@onlinehome.de> - 2011-10-07 17:26 +0200
                      Re: Vulcan build 208 Richard Wooters <Richard@rbj.com> - 2011-10-07 09:08 -0700
          Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-06 16:13 -0700
            Re: Vulcan build 208 "Jamal" <vodotnet_nospam@yahoo.com> - 2011-10-08 17:51 -0400
              Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-08 15:42 -0700
          Re: Vulcan build 208 Dieter <support@visualobjects.de> - 2011-10-06 16:41 -0700
            Re: Vulcan build 208 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-07 11:58 +0200
    Re: Vulcan build 208 info@softwareobjectives.com.au - 2011-10-04 02:47 -0700
      Re: Vulcan build 208 E®!k \\/!$$E® <nospam@nospam.url> - 2011-10-04 12:03 +0200

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


#2119 — Vulcan build 208

From"Willie Moore" <williem@wmconsulting.com>
Date2011-09-30 14:01 -0500
SubjectVulcan build 208
Message-ID<j653mq$85l$1@speranza.aioe.org>
Grafx released Vulcan 208 in VOPS today. It added a greatly improved
intellisence. Case synchronization of keyboard was added as IDE option. 208
also lets you define events.

I have tested all of my libraries and had no issue with any of them. The dev
team hit a home run with this build!

Regards,
Willie 

[toc] | [next] | [standalone]


#2137

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-04 09:59 +0200
Message-ID<3bel87p186igbgsmhgl7huklffdtt5keav@4ax.com>
In reply to#2119
On Fri, 30 Sep 2011 14:01:51 -0500, "Willie Moore"
<williem@wmconsulting.com> wrote:

Hello Willie,

>Grafx released Vulcan 208 in VOPS today. It added a greatly improved
>intellisence. Case synchronization of keyboard was added as IDE option. 208
>also lets you define events.
>
Good to know, but I think most visitors here would be more interested
in learning if a VO SP4 has been released and if that is greatly
improved.

This info might even sell Grafx some VOPS'.

Dick

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


#2162

From"Willie Moore" <williem@wmconsulting.com>
Date2011-10-05 19:34 -0500
Message-ID<j6it34$np8$1@speranza.aioe.org>
In reply to#2137
Dick,

Are you going to attend VODC this year? I hear rumors that sp4 may make an 
appearance.

Regards,
Willie 

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


#2164

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-06 09:09 +0200
Message-ID<9ujq87ledb9elr4rqk0okbjdbcvuk482g8@4ax.com>
In reply to#2162
On Wed, 5 Oct 2011 19:34:49 -0500, "Willie Moore"
<williem@wmconsulting.com> wrote:

Hello Willie,

>Are you going to attend VODC this year? I hear rumors that sp4 may make an 
>appearance.

I found the website http://www.vodc.visualobjects.de/en/

The cast of speakers is impressive. I guess there are no VO sessions,
or maybe those of Meinhard. Although Vulcan is still somewhere on my
long term planning the only thing I am interested in for the short
term is VO. And Brian wrote about this conference:

"No more VOGUI  no more VO runtime ."

Except for the time I have to invest in transporting code (especially
3rd party etc.) I have 4 reasons which keeps me from wanting to use
Vulcan:

1 A small change+recompile+re-run costs much more time than in VO. As
I do that 100's of time on a full day of programming this would
introduce half an hour of waiting time which I find unacceptable.

2 I can not sort anymore on changed entities as all entities are in 1
program. Also I have lost program code occasionly in VO by editing
(and deleting)  more than I intended. Chances that this happens are
far higher in Vulcan: it's like Edit all entities in VO....

3 I've understood that it's not possible to set a general error
handler. If I would need to add error handling code on every few lines
which can go wrong I have to triple my amount of code.

4 The fact that the source code is visible without a lot of extra
effort

On the sunny side: I do expect a more stable program and I think I
could benefit from some code more widely available in .Net. For now
these benefits do not outweigh the drawbacks for me.

Apart from this: I have always wondered why VAT has to be paid on the
VODC conference fee.  Everything else I order or sell abroad is 0% VAT
as long as I supply/have the VAT number...


Dick

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


#2165

FromJohan Nel <johan.nel@xsinet.co.za>
Date2011-10-06 00:35 -0700
Message-ID<9021fe8e-0725-40e3-ba6a-78bcccb87da6@d26g2000vby.googlegroups.com>
In reply to#2164
Dick,

> 1 A small change+recompile+re-run costs much more time than in VO. As
> I do that 100's of time on a full day of programming this would
> introduce half an hour of waiting time which I find unacceptable.
If this is the case you need to relook how you structure your
Projects.  I for one never have to wait more than a couple of seconds
to compile.  It is bad programming practise to have all in one
big .EXE.  Restructure your code into smaller assemblies (.dll) and a
recompile of only the specific assembly is needed to compile/run your
application (except if you do a build all).

> 2 I can not sort anymore on changed entities as all entities are in 1
> program. Also I have lost program code occasionly in VO by editing
> (and deleting)  more than I intended. Chances that this happens are
> far higher in Vulcan: it's like Edit all entities in VO....
With Vulcan and .net we are back at using .prg files.  You can have
your environment setup to create a .prg.bak, easy to just copy
the .bak back again.  As stated above, break your code into smaller
assemblies.

> 3 I've understood that it's not possible to set a general error
> handler. If I would need to add error handling code on every few lines
> which can go wrong I have to triple my amount of code.
Not sure how you get this, a try catch finally in your main start
application will have a general error handler for all errors,
obviously with some overhead penalty.  I try to rather have my errors
trapped locally, so that my application can still run without having
to restart.

> 4 The fact that the source code is visible without a lot of extra
> effort
Do you mean through a program like Reflector?  If this is the case
that you scared other developers might hack your code, a program like
EasyObfusicator or Dotfusicator does the trick.

> On the sunny side: I do expect a more stable program and I think I
> could benefit from some code more widely available in .Net. For now
> these benefits do not outweigh the drawbacks for me.
I can second that, my applications are 100% more stable in Vulcan.NET.

Regards,

Johan Nel
Pretoria, South Africa.

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


#2167

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-06 11:33 +0200
Message-ID<2fsq87ttdife0p4ik3kabjeuookslhhkq8@4ax.com>
In reply to#2165
On Thu, 6 Oct 2011 00:35:55 -0700 (PDT), Johan Nel
<johan.nel@xsinet.co.za> wrote:

Hello Johan, 

Thanks for the quick reaction. First of all I want to emphasize that
my concerns are in no way a Vulcan problem. It's mainly .Net I think.
If there would ever be a reason to abandon VO, Vulcan still seems to
me the best logical solution as my impression is that it's progress is
remarkable given the small community and the major problem of re-using
existing code is still best solved in Vulcan..

>Restructure your code into smaller assemblies (.dll) and a
>recompile of only the specific assembly is needed to compile/run your
>application (except if you do a build all).

I used to do that especially in the time of floppies and later: slow
internet connections, when a small exe would just fit or be sent fast
enough. There's no need to do that anymore: I've got a full exe
uploaded as zip in a minute and VO takes care of what is changed. What
you're basically saying is that have to go back to the time consuming
splitting of code and DLL's + administrating who has got the latest
DLL as we did in the '80's of the last century to  reach an acceptable
speed.

>With Vulcan and .net we are back at using .prg files.  You can have
>your environment setup to create a .prg.bak, easy to just copy
>the .bak back again.  As stated above, break your code into smaller
>assemblies.

This still doesn't solve the problem that I can not see&sort on which
entity I changed last unless you suggest I divide my program in 80.000
.prgs'.

I once had an interesting discussion with Robert about this. On
saving, it should be possible to compare the new and old code and
store somewhere which "entity" was changed. I think it would even be
possible to store the changes in a large database that way. I am not
sure if the save action can be intercepted by the end user or if the
devteam must provide something for that.

>Not sure how you get this, a try catch finally in your main start
>application will have a general error handler for all errors,
>obviously with some overhead penalty.  I try to rather have my errors
>trapped locally, so that my application can still run without having
>to restart.
>

Ah, good to know. I did get this answer once, but can't remember where
or from who. That would take care of problem 3 at least!

>Do you mean through a program like Reflector?  If this is the case
>that you scared other developers might hack your code, a program like
>EasyObfusicator or Dotfusicator does the trick.

It's more that others have the option to see program protection,
passwords etc. This is not the biggest problem, it just adds costs and
programming effort which is not necessary to do in VO. 
>
>I can second that, my applications are 100% more stable in Vulcan.NET.
>
100%?? That sounds like your VO applications were a nightmare <g>.
Fortunately, we do not have this big a problem. We do have the usual
regular problems, difficult to estimate how much is because of plain
bugs or bad programming, and how much would be gone after Vulcan/.Net
takes care of the handling.

Dick

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


#2170

FromJohan Nel <johan.nel@xsinet.co.za>
Date2011-10-06 03:51 -0700
Message-ID<01dec312-19be-4e38-a23d-82f780b4db4d@f6g2000vbm.googlegroups.com>
In reply to#2167
Hi Dick,


> Thanks for the quick reaction. First of all I want to emphasize that
> my concerns are in no way a Vulcan problem. It's mainly .Net I think.
> If there would ever be a reason to abandon VO, Vulcan still seems to
> me the best logical solution as my impression is that it's progress is
> remarkable given the small community and the major problem of re-using
> existing code is still best solved in Vulcan..
Glad we agree on this one.  And yes I am happy with the level of
support and progress in Vulcan.  As indicated by the devteam, progress
was slow initially since VO compatibility was the major concern,
however it is changing and we will see a lot more improvement now
coming about.

> uploaded as zip in a minute and VO takes care of what is changed. What
> you're basically saying is that have to go back to the time consuming
> splitting of code and DLL's + administrating who has got the latest
> DLL as we did in the '80's of the last century to  reach an acceptable
> speed.
Again, I don't have this issue.  I wrote an application launcher that
will poll a FTP site and compare local installation to that on the ftp
server and download only what has changed.  So from my perspective, I
only need to ensure that each of my client installations are up to
date in 1 place (if there are differences in the application between
different clients), and the environment takes care of the rest.  It is
up to each client to decide how they manage my updates, e.g. trust my
ftp site to have a "bug" free and up to date application, or do they
have their own local ftp site that they will manage in ensuring every
body is on the correct/same version.

Also, .net applications are astronomically smaller than win32/vo
applications.  My experience so far is that my Vulcan.NET applications
are about 25% the size of my VO apps.  So yes even with an exe and
multiple dlls I am now again able to send my applications on a 1.4Mb
stiffy and in some cases even a 360k floppy:)

For me it is a huge benefit that I have an exe that is about 15kb in
size, 10-15 dlls that are mostly less than 20kb in size, the Vulcan
runtime about 500kb that only needs upgrade when I compile with a new
build, zgraph again +-500k, sharpmap (700k).

> This still doesn't solve the problem that I can not see&sort on which
> entity I changed last unless you suggest I divide my program in 80.000
> .prgs'.
Are you saying you have 80 000 Entities in your application?  I use
basically some standard dlls that are approximately 10 in total, add
another 5-10 dlls specific per application, so I cannot see how you
get to 80 000 dlls...

> I once had an interesting discussion with Robert about this. On
> saving, it should be possible to compare the new and old code and
> store somewhere which "entity" was changed. I think it would even be
> possible to store the changes in a large database that way. I am not
> sure if the save action can be intercepted by the end user or if the
> devteam must provide something for that.
Hmmm this might be an easy piece of Vulcan software you can write
yourself if you have a need to list changes...
RUN "dir %vulcanprojectpath%\*.* /s > vulcandir.txt"
FOREACH line IN vulcandir.txt
  cFile := ExtractFileName(line)
  cTime := ExtractTime(line)
  IF oDb:Seek(cFile, FALSE)
    IF oDb:FieldGet("time") < cTime
      oDataTable:Updated(....)
    ENDIF
  ELSE
    oDataTable:AddNewFile(...)
  ENDIF
NEXTEACH
oForm := Form{}
oDataGrid := DataGridView{}
oDataGrid:DataSource := oDataTable
oForm:Controls:Add(oDataGrid)
oForm:Show()

> It's more that others have the option to see program protection,
> passwords etc. This is not the biggest problem, it just adds costs and
> programming effort which is not necessary to do in VO.
EasyObfusicator is free as well as DotFusicator (inside VS).

Dangerous to store passwords in the EXE itself, why not write a small
function in your code that will take a password and encrypt it to a
number, then only store the number and check if password supplied
matches the number when you encrypt?

> 100%?? That sounds like your VO applications were a nightmare <g>.
> Fortunately, we do not have this big a problem. We do have the usual
> regular problems, difficult to estimate how much is because of plain
> bugs or bad programming, and how much would be gone after Vulcan/.Net
> takes care of the handling.
<VBG> well was maybe a bit over-reacting.  But I must say, the only
issues I had so far with my Vulcan applications were connection issues
to the database on very slow connections (satelite) where the timeout
was set too low for the specific client site.

Johan.

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


#2171

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-06 13:28 +0200
Message-ID<9h3r875vsp4l2vfqsj6nk2l36n6bu5uemj@4ax.com>
In reply to#2170
On Thu, 6 Oct 2011 03:51:03 -0700 (PDT), Johan Nel
<johan.nel@xsinet.co.za> wrote:

Hello Johan,
>
>Also, .net applications are astronomically smaller than win32/vo
>applications.  My experience so far is that my Vulcan.NET applications
>are about 25% the size of my VO apps.  So yes even with an exe and
>multiple dlls I am now again able to send my applications on a 1.4Mb
>stiffy and in some cases even a 360k floppy:)


I think you misunderstood my concern here. I don't care much about the
size of the exe. I just want my program language to take care of what
is changed. Now your suggestion (Chris told me the same earlier) is
that I start taking care of dividing the program in smaller pieces in
order to keep the recompile and restart speed acceptable.

Bottom line is that I can change, compile and rerun any VO application
in litteraly a few seconds while I've seen a small application in
Vulcan taking over 12 seconds for that. And to achieve this
unfavourable value I have to do a lot of extra work in dividing and
distributing changed versions. This is (besides finding the time to
seriously start converting and learning!) the main reason I expect to
prefer VO for as long as possible I think. A few 100 x say 8 seconds
is at least half an hour extra waiting time.
>
>Hmmm this might be an easy piece of Vulcan software you can write
>yourself if you have a need to list changes...

>Are you saying you have 80 000 Entities in your application?  I use
>basically some standard dlls that are approximately 10 in total, add
>another 5-10 dlls specific per application, so I cannot see how you
>get to 80 000 dlls...

I think you mix up 2 things here. Yes, I 've got many 1000's (I think
a few 10.000's of ENTITIES) (not DLL's or .prg's): every method,
resource, class, function = 1 entity. The program you gave stores when
a PRG is updated, not when 1 method in that prg is updated. 


>Dangerous to store passwords in the EXE itself, why not write a small
>function in your code that will take a password and encrypt it to a
>number, then only store the number and check if password supplied
>matches the number when you encrypt?

As this costs extra time too. With a little bit of effort in VO I can
check certain 'super user' passwords without a realistic chance that
someone can find that in the .exe. But In Vulcan/.Net this can all be
retrieved easily unless you play a lot of tricks.

Dick 

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


#2177

FromE®!k \\/!$$E® <nospam@nospam.url>
Date2011-10-06 15:28 +0200
Message-ID<9f5ongFgrrU1@mid.individual.net>
In reply to#2170
Johan,  Dick

> Dangerous to store passwords in the EXE itself, why not write a
> small function in your code that will take a password and encrypt
> it to a  number, then only store the number and check if password
> supplied matches the number when you encrypt?

This is not a very safe scenario IMO, as the function can be 
reverse-engineered also.

And Dick, if you put a password as a literal in your VO exe, it is very 
readable if you have a look at the exe in a Hex-editor.

Erik




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


#2173

From"Ginny Caughey" <ginny.online@hotmail.com>
Date2011-10-06 08:08 -0400
Message-ID<4e8d9985$0$19689$c3e8da3$c8b7d2e6@news.astraweb.com>
In reply to#2167
I have to comment on your concern about passwords being visible in your 
apps.

1. Don't put passwords inside your apps! Why do you do that?
2. If you want to store passwords, encrypt them first!
3. .NET apps that store passwords can be obfuscated. I have a successful 
Windows Phone app in the marketplace for storing passwords. The passwords 
are encrypted before they are stored and the app is obfuscated. Encrypted 
passwords are even backed up and restored via email.
4. I have one C DLL I've used since the Clipper days (yes the very same 
DLL!) that I use to hide the internals of how I stamp my production VO and 
C# apps with the licensed user's name. This is not a new problem, and 
neither is the solution.

So if you decide that you should move to .NET (and I really doubt in your 
case that you will) there are solutions to your concerns - just ask around.

Ginny

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


#2176

From"Willie Moore" <williem@wmconsulting.com>
Date2011-10-06 07:47 -0500
Message-ID<j6k81j$no8$1@speranza.aioe.org>
In reply to#2173
Ginny,

Your password app for the Windows Phone sounds really good.

Regards,
Willie

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


#2180

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-06 17:03 +0200
Message-ID<rpfr87ddah6ooac2d949ipmprajc6e1gtf@4ax.com>
In reply to#2173
On Thu, 6 Oct 2011 08:08:39 -0400, "Ginny Caughey"
<ginny.online@hotmail.com> wrote:

Hello Ginny,

>1. Don't put passwords inside your apps! Why do you do that?
>2. If you want to store passwords, encrypt them first!

I basically do it as in point 2. Sure everything can be re-engineered,
but .Net applications make that job far too easy.

>3. .NET apps that store passwords can be obfuscated. 
Sure. As said, I know this is not a show stopper, simply more work due
to the technology (instead of less)

>So if you decide that you should move to .NET (and I really doubt in your 
>case that you will) there are solutions to your concerns - just ask around.
>
Well, that depends. I read this with W8 coming:

"Many Silverlight and .Net developers fear their skill sets may become
legacy ones. Microsoft officials have not clarified where .Net fits in
the Windows 8 world."

And in the official Silverlight forum, people seem to doubt about the
future of .Net too, e.g.

http://forums.silverlight.net/t/238971.aspx/1

So if -by the time I chose/have to leave VO for some reason- .Net has
become a relic from the past, your doubt is justified. If it's there
to stay, well, it's the only option we have, right?

Dick

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


#2193

From"Ginny Caughey" <ginny.online@hotmail.com>
Date2011-10-07 08:27 -0400
Message-ID<4e8eef63$0$3998$c3e8da3$b23f186d@news.astraweb.com>
In reply to#2180
Dick,

I think it's pretty silly for you to worry about Silverlight since you've 
never used it, never plan to use it, and probably don't know anything about 
it other than a search to find anything negative somebody might have to say 
about it. Silverlight, just like VO, still runs on Windows 8. Moreover the 
skills needed to build a Silverlight app, unlike VO, can be used to build 
leading edge WinRT "Metro" Windows 8 apps. .NET isn't going away, but unlike 
VO it is continuing to evolve. There will never be just one option for 
developers, but there will be options that pay better than others, and 
usually those are the newer ones.

Ginny

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


#2196

From"Willie Moore" <williem@wmconsulting.com>
Date2011-10-07 08:51 -0500
Message-ID<j6n045$d4c$1@speranza.aioe.org>
In reply to#2193
Ginny,

I agree. The skills that I have learned using Silverlight and WPF will 
continue to pay benefits. I only wish that when I did the rewrite of my 
Cafeteria App I would have used WPF instead of Winforms. The business logic 
went from COM in VO to WCF in Vulcan. I may end up changing the GUI out 
again but my business classes are set. One of my sessions at VODC this year 
is on WCF.

I have not tried Windows 8 yet but I am going to set up a VM and install it 
before too long. That way when my customers ask, I will be able to make an 
informed answer about my software instead of guessing. This applies to all 
my of my software, not just on my commercial apps. I want to be able to 
answer questions on rightSLE, gridPro, AWT, etc.

Back to VODC. Last year Dieter had a really nice keynote from Microsoft on 
cloud development. Even though the session was in German, I still got a lot 
out of it. Dieter always puts on a nice conference. I am very excited about 
going again.

Regards,
Willie 

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


#2214

FromDieter <support@visualobjects.de>
Date2011-10-08 16:01 -0700
Message-ID<68897a25-28be-4a8d-8879-bb493258921a@i30g2000yqd.googlegroups.com>
In reply to#2196
On 7 Okt., 15:51, "Willie Moore" <will...@wmconsulting.com> wrote:
> Ginny,
>
> I agree. The skills that I have learned using Silverlight and WPF will
> continue to pay benefits. I only wish that when I did the rewrite of my
> Cafeteria App I would have used WPF instead of Winforms. The business logic
> went from COM in VO to WCF in Vulcan. I may end up changing the GUI out
> again but my business classes are set. One of my sessions at VODC this year
> is on WCF.
>
> I have not tried Windows 8 yet but I am going to set up a VM and install it
> before too long. That way when my customers ask, I will be able to make an
> informed answer about my software instead of guessing. This applies to all
> my of my software, not just on my commercial apps. I want to be able to
> answer questions on rightSLE, gridPro, AWT, etc.
>
> Back to VODC. Last year Dieter had a really nice keynote from Microsoft on
> cloud development. Even though the session was in German, I still got a lot
> out of it. Dieter always puts on a nice conference. I am very excited about
> going again.
>
> Regards,
> Willie

To all,
Willie's statement might suggest that VODC does present a good share
of German spoken sessions. I know Willie knows that quite the opposite
is true. Almost 90 percent of the sessions are presented in English
only. And even German speakers will present a repeat session in
English by attendees' request. Just contact VODC management and we'll
make arrangements. VODC is definitely designed for int'l attendees,
risking complaints from German prospects. I could move VODC to London
or elsewhere in Europe it wouldn't make any difference. But Stuttgart
is simply a first-class venue with state-of-the-art AV equipment.

Regards
Dieter
VODC Management

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


#2218

From"Willie Moore" <williem@wmconsulting.com>
Date2011-10-09 10:11 -0500
Message-ID<j6sdi4$9du$1@speranza.aioe.org>
In reply to#2214
Dieter,

Stuttgart is really a first class venue. I am sorry if I gave the impression 
that all of the sessions were in German. It is exactly opposite. Almost all 
of the session are in English. What I was trying to convey is that the 
keynote was enjoyable even though I don’t speak German. Out of all the VODC 
venues I have been to, Stuttgart is my first choice followed by Munich.

Regards,
Willie

"Dieter"  wrote in message 
news:68897a25-28be-4a8d-8879-bb493258921a@i30g2000yqd.googlegroups.com...

On 7 Okt., 15:51, "Willie Moore" <will...@wmconsulting.com> wrote:
> Ginny,
>
> I agree. The skills that I have learned using Silverlight and WPF will
> continue to pay benefits. I only wish that when I did the rewrite of my
> Cafeteria App I would have used WPF instead of Winforms. The business 
> logic
> went from COM in VO to WCF in Vulcan. I may end up changing the GUI out
> again but my business classes are set. One of my sessions at VODC this 
> year
> is on WCF.
>
> I have not tried Windows 8 yet but I am going to set up a VM and install 
> it
> before too long. That way when my customers ask, I will be able to make an
> informed answer about my software instead of guessing. This applies to all
> my of my software, not just on my commercial apps. I want to be able to
> answer questions on rightSLE, gridPro, AWT, etc.
>
> Back to VODC. Last year Dieter had a really nice keynote from Microsoft on
> cloud development. Even though the session was in German, I still got a 
> lot
> out of it. Dieter always puts on a nice conference. I am very excited 
> about
> going again.
>
> Regards,
> Willie

To all,
Willie's statement might suggest that VODC does present a good share
of German spoken sessions. I know Willie knows that quite the opposite
is true. Almost 90 percent of the sessions are presented in English
only. And even German speakers will present a repeat session in
English by attendees' request. Just contact VODC management and we'll
make arrangements. VODC is definitely designed for int'l attendees,
risking complaints from German prospects. I could move VODC to London
or elsewhere in Europe it wouldn't make any difference. But Stuttgart
is simply a first-class venue with state-of-the-art AV equipment.

Regards
Dieter
VODC Management 

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


#2198

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-07 16:47 +0200
Message-ID<h14u87df2iajck4cpsrj2a8j2gd55c5qua@4ax.com>
In reply to#2193
On Fri, 7 Oct 2011 08:27:15 -0400, "Ginny Caughey"
<ginny.online@hotmail.com> wrote:

Hello Ginny,
>
>I think it's pretty silly for you to worry about Silverlight since you've 
>never used it, never plan to use it, and probably don't know anything about 
>it other than a search to find anything negative somebody might have to say 
>about it. 

Where did I write that I worried about Silverlight?? Silly of you to
assume I worried... I couldn't care less indeed. But I found messages
like this this in more than a few websites, and it happens to combine
.Net with Silverlight. 

>.NET isn't going away, but unlike VO it is continuing to evolve. 

Well, that is where poeple seem to doubt about. It's not my opinion,
it's just something I found, as said, more than once.

Dick

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


#2166

From"Dirk (Belgium)" <dirk.dot.herijgers@pbprojects.dot.be>
Date2011-10-06 07:36 +0000
Message-ID<BTcjq.172$JT.108@newsfe14.ams2>
In reply to#2164
Hi Dick,

Some answers:

3) It is possible to have a big TRY ... CATCH ... END TRY in the
start() function of your program. This catch all the errors. You don't
have to make error handling on every few lines...

4) Obfuscating your code does NOT cost a lot of effort. it just cost
you one time about 200 euro. The time to obfuscate is about 10 seconds.
The time to implement this obfuscation is about 5 minutes.

Concerning the VAT : You have to pay VAT, because the 'product' you buy
is delivered in the same country. You get an invoice from germany, and
your product is delivered in germany. It doesn't matter if you are
comming from America, Cuba or The Netherlands... This are the VAT rules
for all euro countries...

Dirk (Belgium)



D.J.W. van Kooten wrote:

> On Wed, 5 Oct 2011 19:34:49 -0500, "Willie Moore"
> <williem@wmconsulting.com> wrote:
> 
> Hello Willie,
> 
> > Are you going to attend VODC this year? I hear rumors that sp4 may
> > make an appearance.
> 
> I found the website http://www.vodc.visualobjects.de/en/
> 
> The cast of speakers is impressive. I guess there are no VO sessions,
> or maybe those of Meinhard. Although Vulcan is still somewhere on my
> long term planning the only thing I am interested in for the short
> term is VO. And Brian wrote about this conference:
> 
> "No more VOGUI  no more VO runtime ."
> 
> Except for the time I have to invest in transporting code (especially
> 3rd party etc.) I have 4 reasons which keeps me from wanting to use
> Vulcan:
> 
> 1 A small change+recompile+re-run costs much more time than in VO. As
> I do that 100's of time on a full day of programming this would
> introduce half an hour of waiting time which I find unacceptable.
> 
> 2 I can not sort anymore on changed entities as all entities are in 1
> program. Also I have lost program code occasionly in VO by editing
> (and deleting)  more than I intended. Chances that this happens are
> far higher in Vulcan: it's like Edit all entities in VO....
> 
> 3 I've understood that it's not possible to set a general error
> handler. If I would need to add error handling code on every few lines
> which can go wrong I have to triple my amount of code.
> 
> 4 The fact that the source code is visible without a lot of extra
> effort
> 
> On the sunny side: I do expect a more stable program and I think I
> could benefit from some code more widely available in .Net. For now
> these benefits do not outweigh the drawbacks for me.
> 
> Apart from this: I have always wondered why VAT has to be paid on the
> VODC conference fee.  Everything else I order or sell abroad is 0% VAT
> as long as I supply/have the VAT number...
> 
> 
> Dick



-- 

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


#2168

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2011-10-06 11:48 +0200
Message-ID<sftq87tlj59tc7qhartopfs93m7mj2uh5j@4ax.com>
In reply to#2166
On Thu, 06 Oct 2011 07:36:01 GMT, "Dirk (Belgium)"
<dirk.dot.herijgers@pbprojects.dot.be> wrote:

Hello Dirk,

>Some answers:

See the reply to Johan.
>
>Concerning the VAT : You have to pay VAT, because the 'product' you buy
>is delivered in the same country. You get an invoice from germany, and
>your product is delivered in germany. It doesn't matter if you are
>comming from America, Cuba or The Netherlands... This are the VAT rules
>for all euro countries...
>
You're partly right. Even though a service is invoiced and taken in
the same country, a foreign business is entitled to an invoice with
"BTW verlegd" (VAT shifted") I just found out. However, access to
conferences etc. are an exception. 

I also learned that recuperation in the EU has been made much easier
since 2010. In my login, I can apply for recuperating EU VAT on line;
the only limitation is that it has to be at least 50 euro. So you
don't need to hire someone for that as it used to be.

Dick

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


#2174

From"Willie Moore" <williem@wmconsulting.com>
Date2011-10-06 07:27 -0500
Message-ID<j6k6qo$kir$1@speranza.aioe.org>
In reply to#2164
Dick,

I am not sure where you got the idea that you cant have a general error 
handler. I use the framework below in the start of all of my winforms app. I 
have a slightly different one for my WPF apps but both use the same error 
logging routine. Error handling is handled a bit differently from VO but in 
my opinion, it is a better system. In my methods, I use local handlers (try 
catch blocks) to catch and handle things that are specific to that method. 
If an exception happens, dotNet first looks for a local errorblock. If it 
does not find one it then looks at the next method up the call stack for a 
handler that can handle the exception. If it reaches the root of the 
application without finding a block then you get a error box that looks a 
lot like VO's.  By adding the try block in my start function I can catch and 
log the errors.

As far as the other points. I structure my apps so all of the projects in my 
solution output to the same directory. I rarely touch my base libraries so I 
don’t compile them unless I make a change. I do the same with my GUI. I 
separate all of my GUI forms into their own assembly. In my exe I subclass 
each form and add my event handlers to the subclass just like I did in VO. 
One of the nice things about Visual Studio is that you can have different 
settings for different config tasks (ie debug, staging, release, etc). In 
debug I don’t recompile everything but in release I do so all of the DLLs go 
out with the same datetime stamp.

Regards,
Willie

GLOBAL goSysInfo As SysInfo

/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread] ;
FUNCTION Start() AS VOID
    LOCAL oShell    AS ShellWindow
    LOCAL lRunApp   AS Logic
   TRY
       SetupRightSLE()
       Application.EnableVisualStyles()
       Application.SetCompatibleTextRenderingDefault( false )
       oShell   := ShellWindow{}
       lRunApp  := oShell:Start()
       IF lRunApp
        Application.Run( oShell )
       ENDIF
   CATCH ex as System.Exception
        LOCAL oLog  as ErrorLog
        oLog    := Errorlog{}
        oLog:DumpException(ex)
        MessageBox.Show(ex:ToString())
   END TRY
   RETURN
FUNCTION SetupRightSLE() AS VOID
    rightSLE.DefaultSelectionOnFocus    := focusBehavior.All
    RightSLE.DefaultProcessEnter        := KeyHandling.Process
    RightSLE.DefaultProcessArrow        := KeyHandling.Process
    RightSLE.DefaultOverwrite           := OverwriteBehavior.Never
    RETURN
 

[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