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


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

Vulcan.NET 3.02j now Available

Started by"Brian" <߮ian@g®afxsoft.com>
First post2014-02-05 10:00 -0500
Last post2014-02-07 10:14 -0500
Articles 15 — 5 participants

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


Contents

  Vulcan.NET 3.02j now Available "Brian" <߮ian@g®afxsoft.com> - 2014-02-05 10:00 -0500
    Re: Vulcan.NET 3.02j now Available "Willie Moore" <williem@wmconsulting.com> - 2014-02-05 09:04 -0600
      Re: Vulcan.NET 3.02j now Available "Brian" <߮ian@g®afxsoft.com> - 2014-02-07 10:02 -0500
    Re: Vulcan.NET 3.02j now Available "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-02-05 17:01 +0100
      Re: Vulcan.NET 3.02j now Available Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2014-02-05 19:12 +0100
        Re: Vulcan.NET 3.02j now Available "Brian" <߮ian@g®afxsoft.com> - 2014-02-07 10:11 -0500
      Re: Vulcan.NET 3.02j now Available "Brian" <߮ian@g®afxsoft.com> - 2014-02-07 10:06 -0500
        Re: Vulcan.NET 3.02j now Available "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-02-10 11:46 +0100
          Re: Vulcan.NET 3.02j now Available "Brian" <߮ian@g®afxsoft.com> - 2014-02-10 09:43 -0500
            Re: Vulcan.NET 3.02j now Available "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-02-10 17:06 +0100
              Re: Vulcan.NET 3.02j now Available Johan Nel <johan.nel@xsinet.co.za> - 2014-02-10 23:14 -0800
                Re: Vulcan.NET 3.02j now Available "Wolfgang Riedmann" <wriedmann@gmail.com> - 2014-02-11 14:58 +0100
                  Re: Vulcan.NET 3.02j now Available Johan Nel <johan.nel@xsinet.co.za> - 2014-02-12 01:31 -0800
    Re: Vulcan.NET 3.02j now Available Johan Nel <johan.nel@xsinet.co.za> - 2014-02-05 22:52 -0800
      Re: Vulcan.NET 3.02j now Available "Brian" <߮ian@g®afxsoft.com> - 2014-02-07 10:14 -0500

#6576 — Vulcan.NET 3.02j now Available

From"Brian" <߮ian@g®afxsoft.com>
Date2014-02-05 10:00 -0500
SubjectVulcan.NET 3.02j now Available
Message-ID<52f25231$0$2705$c3e8da3$66d3cc2f@news.astraweb.com>
Hello All,

GrafX is extremely pleased to announce the release of Vulcan.NET 3.02. It's
been 6 months since our last release but we think you find this new version
feature packed (new language features) and lot's of Intellisense working
better than ever. (See below for full list of what's new. )

What's New::

This build contains the following changes and fixes:

Compiler:
   Added support for Extension methods
   Added support for subscribing to/ unsubscribing from events with
   implicitly instantiated delegates (new delegate syntax)
   Fixed enum member attribute target

VS Integration:
   Intellisense support for CoClass when using COM Object
   Intellisense now support types from VULCAN.NET Project reference
   Intellisense now basically support types from CS/VB Project reference
   Intellisnese now supports code folding
   Intellisense now recognize PROPERTY were GET/SET don't have the same
   visibility
   Fixed some issues with the separate designer.prg file
   Now WinForm Designer support user-designed controls
   WinForm designer support for Events in inherited controls
   Formatting Code available through Edit/Advanced/Format Document or Format
   Selection

VODSK:
   Modified TextControl:ControlFont code in order to take account of the
   name
   change Font to ControlFont.
   Fix for bug #1165, updated Color class constructor so that it allows to
   pass in the color as a single value, as in VO
   Modified WinFormVOWindowHost:ProcessDialogKey() so that it better handles
   the TAB key.
   Updated Control:LinkDF(oDS, siDF) method so that it also handles the
   field param(siDF) passed as SYMBOL.
   Fix for bug #1166, now TreeView:SortChildren() uses a delegate instead of
   a function pointer for the sorting callback method.

RunTime Functions:
   Fix for bug #1167, File() function was throwing an exception, instead of
   returning FALSE for erroneous paths
   Fix for bug #1172, Proper() was only checking for whitespace as word
   separators.

Tools:
   Vulcan.NET language Add-In for RedGate's .NET Reflector available in

Tools Folder.
   Vulcan.NET Productivity pack for Visual Studio is installed per default.

Help System:
   Fix for Help System producing is errors with method having one USUAL
   parameter.

Please read the readme, and Help File for all the new features and Syntax
for new language features.

All the best,

On behalf of the Development team for Vulcan.NET 3.0
(Who deserves the credit...)

Upgrade from VOSP4.
http://www.grafxsoft.com/2vo28.htm

With out VO2.8SP4
http://www.grafxsoft.com/2vosubscribe.htm

Trial Version 3.00 Good for 60 days Free at
http://www.GoVulcan.NET


All the best,

Brian Feldman
GrafX Software 

[toc] | [next] | [standalone]


#6577

From"Willie Moore" <williem@wmconsulting.com>
Date2014-02-05 09:04 -0600
Message-ID<lctjtn$462$1@speranza.aioe.org>
In reply to#6576
Brian,

I love version 3.02j! It has fixed a lot of the issues I had. The extension 
methods are really cool.

Regards,
Willie
Vulcan VIP

"Brian"  wrote in message 
news:52f25231$0$2705$c3e8da3$66d3cc2f@news.astraweb.com...

Hello All,

GrafX is extremely pleased to announce the release of Vulcan.NET 3.02. It's
been 6 months since our last release but we think you find this new version
feature packed (new language features) and lot's of Intellisense working
better than ever. (See below for full list of what's new. )

What's New::

This build contains the following changes and fixes:

Compiler:
   Added support for Extension methods
   Added support for subscribing to/ unsubscribing from events with
   implicitly instantiated delegates (new delegate syntax)
   Fixed enum member attribute target

VS Integration:
   Intellisense support for CoClass when using COM Object
   Intellisense now support types from VULCAN.NET Project reference
   Intellisense now basically support types from CS/VB Project reference
   Intellisnese now supports code folding
   Intellisense now recognize PROPERTY were GET/SET don't have the same
   visibility
   Fixed some issues with the separate designer.prg file
   Now WinForm Designer support user-designed controls
   WinForm designer support for Events in inherited controls
   Formatting Code available through Edit/Advanced/Format Document or Format
   Selection

VODSK:
   Modified TextControl:ControlFont code in order to take account of the
   name
   change Font to ControlFont.
   Fix for bug #1165, updated Color class constructor so that it allows to
   pass in the color as a single value, as in VO
   Modified WinFormVOWindowHost:ProcessDialogKey() so that it better handles
   the TAB key.
   Updated Control:LinkDF(oDS, siDF) method so that it also handles the
   field param(siDF) passed as SYMBOL.
   Fix for bug #1166, now TreeView:SortChildren() uses a delegate instead of
   a function pointer for the sorting callback method.

RunTime Functions:
   Fix for bug #1167, File() function was throwing an exception, instead of
   returning FALSE for erroneous paths
   Fix for bug #1172, Proper() was only checking for whitespace as word
   separators.

Tools:
   Vulcan.NET language Add-In for RedGate's .NET Reflector available in

Tools Folder.
   Vulcan.NET Productivity pack for Visual Studio is installed per default.

Help System:
   Fix for Help System producing is errors with method having one USUAL
   parameter.

Please read the readme, and Help File for all the new features and Syntax
for new language features.

All the best,

On behalf of the Development team for Vulcan.NET 3.0
(Who deserves the credit...)

Upgrade from VOSP4.
http://www.grafxsoft.com/2vo28.htm

With out VO2.8SP4
http://www.grafxsoft.com/2vosubscribe.htm

Trial Version 3.00 Good for 60 days Free at
http://www.GoVulcan.NET


All the best,

Brian Feldman
GrafX Software 

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


#6583

From"Brian" <߮ian@g®afxsoft.com>
Date2014-02-07 10:02 -0500
Message-ID<52f4f55e$0$12641$c3e8da3$69010069@news.astraweb.com>
In reply to#6577
Willie,

>>I love version 3.02j! It has fixed a lot of the issues I had. The 
>>extension
methods are really cool.

Glad you like them. Extension methods are one of the building blocks to
LINQ.   Our next version 3.03 will also support 2013.  I'll be testing our 
first build (303) today.

All the best,

Brian



Regards,
Willie
Vulcan VIP

"Brian"  wrote in message
news:52f25231$0$2705$c3e8da3$66d3cc2f@news.astraweb.com...

Hello All,

GrafX is extremely pleased to announce the release of Vulcan.NET 3.02. It's
been 6 months since our last release but we think you find this new version
feature packed (new language features) and lot's of Intellisense working
better than ever. (See below for full list of what's new. )

What's New::

This build contains the following changes and fixes:

Compiler:
   Added support for Extension methods
   Added support for subscribing to/ unsubscribing from events with
   implicitly instantiated delegates (new delegate syntax)
   Fixed enum member attribute target

VS Integration:
   Intellisense support for CoClass when using COM Object
   Intellisense now support types from VULCAN.NET Project reference
   Intellisense now basically support types from CS/VB Project reference
   Intellisnese now supports code folding
   Intellisense now recognize PROPERTY were GET/SET don't have the same
   visibility
   Fixed some issues with the separate designer.prg file
   Now WinForm Designer support user-designed controls
   WinForm designer support for Events in inherited controls
   Formatting Code available through Edit/Advanced/Format Document or Format
   Selection

VODSK:
   Modified TextControl:ControlFont code in order to take account of the
   name
   change Font to ControlFont.
   Fix for bug #1165, updated Color class constructor so that it allows to
   pass in the color as a single value, as in VO
   Modified WinFormVOWindowHost:ProcessDialogKey() so that it better handles
   the TAB key.
   Updated Control:LinkDF(oDS, siDF) method so that it also handles the
   field param(siDF) passed as SYMBOL.
   Fix for bug #1166, now TreeView:SortChildren() uses a delegate instead of
   a function pointer for the sorting callback method.

RunTime Functions:
   Fix for bug #1167, File() function was throwing an exception, instead of
   returning FALSE for erroneous paths
   Fix for bug #1172, Proper() was only checking for whitespace as word
   separators.

Tools:
   Vulcan.NET language Add-In for RedGate's .NET Reflector available in

Tools Folder.
   Vulcan.NET Productivity pack for Visual Studio is installed per default.

Help System:
   Fix for Help System producing is errors with method having one USUAL
   parameter.

Please read the readme, and Help File for all the new features and Syntax
for new language features.

All the best,

On behalf of the Development team for Vulcan.NET 3.0
(Who deserves the credit...)

Upgrade from VOSP4.
http://www.grafxsoft.com/2vo28.htm

With out VO2.8SP4
http://www.grafxsoft.com/2vosubscribe.htm

Trial Version 3.00 Good for 60 days Free at
http://www.GoVulcan.NET


All the best,

Brian Feldman
GrafX Software 

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


#6578

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2014-02-05 17:01 +0100
Message-ID<blf5i8F1visU1@mid.individual.net>
In reply to#6576
Hi Brian,

I have ported all my live applications from Vulcan 2.x to 3.02 without
any issue.
I like Vulcan.NET and I hope to have all my VO applications running
under Vulcan some day in the future.

Wolfgang


-- 

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


#6579

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2014-02-05 19:12 +0100
Message-ID<3ov4f9hdtj0c70hsu25jnr4i75gc85j9kl@4ax.com>
In reply to#6578
>I have ported all my live applications from Vulcan 2.x to 3.02 without
>any issue.
Here too :-)
Thx
Karl

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


#6585

From"Brian" <߮ian@g®afxsoft.com>
Date2014-02-07 10:11 -0500
Message-ID<52f4f760$0$12673$c3e8da3$69010069@news.astraweb.com>
In reply to#6579
Hi Karl,

>I have ported all my live applications from Vulcan 2.x to 3.02 without
>any issue.  Here too :-)

Great !   I know your using VIDE, which is much closer to the VO's IDE. It's 
(VIDE) and extremely nice piece of work by Chris Pygras, about 200,000 + 
lines of pure Vulcan.NET code.  I guess you like this better than Visual 
Studio ?   In any case we are making a lot of progress on both IDE's

Brian

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


#6584

From"Brian" <߮ian@g®afxsoft.com>
Date2014-02-07 10:06 -0500
Message-ID<52f4f64e$0$12549$c3e8da3$69010069@news.astraweb.com>
In reply to#6578
Hi Wolfgang,

I have ported all my live applications from Vulcan 2.x to 3.02 without
any issue.
I like Vulcan.NET and I hope to have all my VO applications running
under Vulcan some day in the future.

Wow, not to long ago, about a year or so, I can remember you telling me that 
you didn't think Vulcan.NET was going to be in the "Cards" for you.    I'm 
happy to see you changed your mind.  After you get started with it, its sill 
pretty much the same VO language, and I guess you could say what 
"transporter" did and didn't do for you.

Glad to see your post !!!!

All the best,

Brian

--  

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


#6589

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2014-02-10 11:46 +0100
Message-ID<blrp0aFmifgU1@mid.individual.net>
In reply to#6584
Hi Brian,

> Wow, not to long ago, about a year or so, I can remember you telling
> me that you didn't think Vulcan.NET was going to be in the "Cards"
> for you.    I'm happy to see you changed your mind.  

I'm touching more and more the walls of the standard Win32 API,
specially when it comes to user interface.
Customers are demanding zoomable interfaces (try to use a VO app on a
10" tablet with FullHD resolution), better graphics (with .NET I can
use PNG bitmaps with transparent background), and better integration
with other applications (the Google API has .NET interfaces).


> After you get
> started with it, its sill pretty much the same VO language, and I
> guess you could say what "transporter" did and didn't do for you.

The transporter works very well, but I think I have used the VO
language for things that in Vulcan.NET are not allowed.
My biggest problem at the moment is my report engine, that makes a very
heavy use of the macro engine, using public/private variables combined
with the macro evaluator - and this simply does not work with
Vulcan.NET. So I'm rewriting the evaluator engine so I can pass in an
array with variables instead of using the MemVarPut() function.

The other problem I have is the large use of runtime-loaded DLLs: Some
parts of my apps are loaded with LoadLibrary() and the used with
CreateInstance().

At this moment, I have my FTP tool (based one the FTP sample) and my
dictionary editor in the Vulcan.NET version in daily use - both based
on the VO GUI classes. Printing is not needed in both...

At this moment, another Vulcan.NET based project should be start
according to the customer, but unfortunately, my time is too much
limited for doing all the work I should do.... After all, I need some
time to eat and sleep...

Wolfgang


-- 

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


#6590

From"Brian" <߮ian@g®afxsoft.com>
Date2014-02-10 09:43 -0500
Message-ID<52f8e54b$0$9172$c3e8da3$9f400e27@news.astraweb.com>
In reply to#6589
Wolfgang,


I'm touching more and more the walls of the standard Win32 API,
specially when it comes to user interface.
Customers are demanding zoomable interfaces (try to use a VO app on a
10" tablet with FullHD resolution), better graphics (with .NET I can
use PNG bitmaps with transparent background), and better integration
with other applications (the Google API has .NET interfaces).

>>
I think that a lot of VO programmers are hitting the same walls !
More walls to come, as hardware and OS's progress.
<<
The transporter works very well, but I think I have used the VO
language for things that in Vulcan.NET are not allowed.
>>

Yes, this is quite true. Pointers are just one example of a problem
area in .NET which require hand written solutions. It's that 2% to 5%
that transporter is unable to handle that keeps some VO programmers
away from Vulcan.NET   >>

My biggest problem at the moment is my report engine, that makes a very
heavy use of the macro engine, using public/private variables combined
with the macro evaluator - and this simply does not work with
Vulcan.NET. So I'm rewriting the evaluator engine so I can pass in an
array with variables instead of using the MemVarPut() function.

I assume this is a Custom Report Engine that you wrote in VO ?
Glad to hear, you doing a re-write in Vulcan.NET

Report Pro for .NET source is available as your probably aware.

<<<
The other problem I have is the large use of runtime-loaded DLLs: Some
parts of my apps are loaded with LoadLibrary() and the used with
CreateInstance().

At this moment, I have my FTP tool (based one the FTP sample) and my
dictionary editor in the Vulcan.NET version in daily use - both based
on the VO GUI classes. Printing is not needed in both...

>>
This is a really good example of a Protocal like Mail or FTP that is
changing for security reasons, that VO will just never handle.
Please check with Chris, on the Support forums about the the best
practices for  replacements for LoadLibary in .NET
<<

At this moment, another Vulcan.NET based project should be start
according to the customer, but unfortunately, my time is too much
limited for doing all the work I should do.... After all, I need some
time to eat and sleep...

I think we can all relate to that statement. Still only 24 hours in a day 
even with .NET

All the best,

Brian



--  

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


#6591

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2014-02-10 17:06 +0100
Message-ID<blsbnqFqhnlU1@mid.individual.net>
In reply to#6590
Hi Brian,

> Yes, this is quite true. Pointers are just one example of a problem
> area in .NET which require hand written solutions. It's that 2% to 5%
> that transporter is unable to handle that keeps some VO programmers
> away from Vulcan.NET   >>

Transporter was able to port more than 98% of my code... The most
problems were in my framework lib, used by all my applications.
I have tried to not use pointer arithmetic in my VO code: this type of
code maybe faster in execution, but harder to understand and harder to
fix when you go over it time later - and since most of my applications
are living more than 10 years, it is more important to write
understandable code than fast code.

> I assume this is a Custom Report Engine that you wrote in VO ?

I wrote "only" the expression engine, the output is done by VPE from
Ideal Software in Germany, a very fast and small printer virtualization
engine (you can write on every point of virtual paper, using
coordinates in 1/10 mm, using formatting espressions, and even RTF, go
forward and back between pages, so things like "page x from y" are very
easy to do).

> Glad to hear, you doing a re-write in Vulcan.NET
> 
> Report Pro for .NET source is available as your probably aware.

yes, I know, but I don't like graphic report writers (my report files
are simple text files to modify with NotePad or any ascii editor).

The most important of my report tool is that it is using not only
database fields, but also all instance variables from the server, so
calculated fields used in the report are defined in the application
itself, and I can use all functions allowed in macro expressions.

> Please check with Chris, on the Support forums about the the best
> practices for  replacements for LoadLibary in .NET

since loading time and size is not more an issue, at this moment I have
decided to use the DLLs directly as part of the application (Vulcan.NET
dlls are ways smaller than VO dlls using GUI classes)


But I seem to have another problem with encrypted and/or compressed
database fields from VO since Vulcan is not able to return the field
contents as they are (partly I'm using zlib compression to store
bitmaps in memo fields, partly Crypt, and partly own crypting
functions).
At this moment, I have not decided what to do - a (new) method
FieldGetAnsi() of the DBServer class or even a DBFieldGetAnsi()
function in the RDD would solve this problem.

Anyway - problems are there to be solved...

Wolfgang



-- 

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


#6592

FromJohan Nel <johan.nel@xsinet.co.za>
Date2014-02-10 23:14 -0800
Message-ID<57b72b84-a4fa-4a62-9441-189df06a9095@googlegroups.com>
In reply to#6591
Hi Wolfgang,

> Transporter was able to port more than 98% of my code... The most
> problems were in my framework lib, used by all my applications.
I have done some work on dynamic load libraries with Reflection, drop me a line if you interested in how I did it.

> > I assume this is a Custom Report Engine that you wrote in VO ?
> I wrote "only" the expression engine, the output is done by VPE from
> yes, I know, but I don't like graphic report writers (my report files
> are simple text files to modify with NotePad or any ascii editor).
> The most important of my report tool is that it is using not only
> database fields, but also all instance variables from the server, so
> calculated fields used in the report are defined in the application
> itself, and I can use all functions allowed in macro expressions.

I have also done a data-driven report writer, maybe we can share some ideas around this.
Regarding macro-expressions I also did a Vulcan.NET macro-compiler wrapper class that I tried to get around the issues of instance variables and accessing them, maybe we can share some ideas around this too.

> > practices for  replacements for LoadLibary in .NET

I have as mentioned done some work on this, so maybe I have some ideas that you can use.


Regards,

Johan Nel
Vulcan VIP
Durban, South Africa.

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


#6593

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2014-02-11 14:58 +0100
Message-ID<bluokaFbkciU1@mid.individual.net>
In reply to#6592
Hi Johan,

> I have also done a data-driven report writer, maybe we can share some
> ideas around this.  Regarding macro-expressions I also did a
> Vulcan.NET macro-compiler wrapper class that I tried to get around
> the issues of instance variables and accessing them, maybe we can
> share some ideas around this too.

I'm particularly interested in this, and will send you my VO code (I
have done several things like variable substitution because I prefer to
invert VOs variable substitution sequence: VO takes first the fields
from the current workarea, and then the memory variables, my code
inverts this to take first the values from the memory variables (or my
variable array, and then the values from the current server object, non
the workarea, so the report writer uses not only the access variables
from the server class, but also the picture clauses from the fieldspec)

Since my code uses things like _PublicFirst()/_PublicNext() and
_PrivateFirst()/PrivateNext() to check if a variable is existing as
memory variable, and then MemVarGet() to retrieve the value, the code
is not transportable to Vulcan.


Wolfgang


-- 

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


#6595

FromJohan Nel <johan.nel@xsinet.co.za>
Date2014-02-12 01:31 -0800
Message-ID<42093e78-8799-452c-9366-4a7335dd9edd@googlegroups.com>
In reply to#6593
Hi Wolfgang,

Waiting in anticipation for your mail.


> > I have also done a data-driven report writer, maybe we can share some
> > ideas around this.  Regarding macro-expressions I also did a
> > Vulcan.NET macro-compiler wrapper class that I tried to get around
> > the issues of instance variables and accessing them, maybe we can
> > share some ideas around this too.
>
> I'm particularly interested in this, and will send you my VO code (I
> have done several things like variable substitution because I prefer to
> invert VOs variable substitution sequence: VO takes first the fields
> from the current workarea, and then the memory variables, my code
> inverts this to take first the values from the memory variables (or my
> variable array, and then the values from the current server object, non
> the workarea, so the report writer uses not only the access variables
> from the server class, but also the picture clauses from the fieldspec)
> Since my code uses things like _PublicFirst()/_PublicNext() and
> _PrivateFirst()/PrivateNext() to check if a variable is existing as
> memory variable, and then MemVarGet() to retrieve the value, the code
> is not transportable to Vulcan.

I will look at what you have done once I receive your mail.  I had similar issues, although I already did something in VO to encapsulate it, which I think in Vulcan works even better (using the NoIVarGet()/Put() and NoMethod() methods of late binding in a small macro-compiler wrapper class in conjunction with delegates, put into a seperate assembly so that the rest of my application is still early bound.

Regards,

Johan Nel
Vulcan VIP
Durban, South Africa.

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


#6580

FromJohan Nel <johan.nel@xsinet.co.za>
Date2014-02-05 22:52 -0800
Message-ID<e3193190-ffea-45c6-b7f2-9f0f28c51a15@googlegroups.com>
In reply to#6576
Hello Brian,

I have to confirm what others are saying, just love the new release and cannot imagine having to go back to VO or Win32 programming for that matter.

Regards,

Johan Nel
Vulcan VIP
Durban, South Africa.

On Wednesday, February 5, 2014 5:00:47 PM UTC+2, Brian wrote:
> Hello All,
> 
> 
> 
> GrafX is extremely pleased to announce the release of Vulcan.NET 3.02. It's
> 
> been 6 months since our last release but we think you find this new version
> 
> feature packed (new language features) and lot's of Intellisense working
> 
> better than ever. (See below for full list of what's new. )
> 
> 
> 
> What's New::
> 
> 
> 
> This build contains the following changes and fixes:
> 
> 
> 
> Compiler:
> 
>    Added support for Extension methods
> 
>    Added support for subscribing to/ unsubscribing from events with
> 
>    implicitly instantiated delegates (new delegate syntax)
> 
>    Fixed enum member attribute target
> 
> 
> 
> VS Integration:
> 
>    Intellisense support for CoClass when using COM Object
> 
>    Intellisense now support types from VULCAN.NET Project reference
> 
>    Intellisense now basically support types from CS/VB Project reference
> 
>    Intellisnese now supports code folding
> 
>    Intellisense now recognize PROPERTY were GET/SET don't have the same
> 
>    visibility
> 
>    Fixed some issues with the separate designer.prg file
> 
>    Now WinForm Designer support user-designed controls
> 
>    WinForm designer support for Events in inherited controls
> 
>    Formatting Code available through Edit/Advanced/Format Document or Format
> 
>    Selection
> 
> 
> 
> VODSK:
> 
>    Modified TextControl:ControlFont code in order to take account of the
> 
>    name
> 
>    change Font to ControlFont.
> 
>    Fix for bug #1165, updated Color class constructor so that it allows to
> 
>    pass in the color as a single value, as in VO
> 
>    Modified WinFormVOWindowHost:ProcessDialogKey() so that it better handles
> 
>    the TAB key.
> 
>    Updated Control:LinkDF(oDS, siDF) method so that it also handles the
> 
>    field param(siDF) passed as SYMBOL.
> 
>    Fix for bug #1166, now TreeView:SortChildren() uses a delegate instead of
> 
>    a function pointer for the sorting callback method.
> 
> 
> 
> RunTime Functions:
> 
>    Fix for bug #1167, File() function was throwing an exception, instead of
> 
>    returning FALSE for erroneous paths
> 
>    Fix for bug #1172, Proper() was only checking for whitespace as word
> 
>    separators.
> 
> 
> 
> Tools:
> 
>    Vulcan.NET language Add-In for RedGate's .NET Reflector available in
> 
> 
> 
> Tools Folder.
> 
>    Vulcan.NET Productivity pack for Visual Studio is installed per default.
> 
> 
> 
> Help System:
> 
>    Fix for Help System producing is errors with method having one USUAL
> 
>    parameter.
> 
> 
> 
> Please read the readme, and Help File for all the new features and Syntax
> 
> for new language features.
> 
> 
> 
> All the best,
> 
> 
> 
> On behalf of the Development team for Vulcan.NET 3.0
> 
> (Who deserves the credit...)
> 
> 
> 
> Upgrade from VOSP4.
> 
> http://www.grafxsoft.com/2vo28.htm
> 
> 
> 
> With out VO2.8SP4
> 
> http://www.grafxsoft.com/2vosubscribe.htm
> 
> 
> 
> Trial Version 3.00 Good for 60 days Free at
> 
> http://www.GoVulcan.NET
> 
> 
> 
> 
> 
> All the best,
> 
> 
> 
> Brian Feldman
> 
> GrafX Software

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


#6586

From"Brian" <߮ian@g®afxsoft.com>
Date2014-02-07 10:14 -0500
Message-ID<52f4f810$0$12663$c3e8da3$69010069@news.astraweb.com>
In reply to#6580
Johan,

>>I have to confirm what others are saying, just love the new release and 
>>cannot imagine having to go back to VO or Win32 programming for that 
>>matter.

Thanks on behalf of the entire development team !   Just like Clipper win32 
will be around for a while, but I agree, why fight the tide !   There are 
just too many good .NET languages to move forward with for application 
developers.

Brian


Regards,

Johan Nel
Vulcan VIP
Durban, South Africa.

On Wednesday, February 5, 2014 5:00:47 PM UTC+2, Brian wrote:
> Hello All,
>
>
>
> GrafX is extremely pleased to announce the release of Vulcan.NET 3.02. 
> It's
>
> been 6 months since our last release but we think you find this new 
> version
>
> feature packed (new language features) and lot's of Intellisense working
>
> better than ever. (See below for full list of what's new. )
>
>
>
> What's New::
>
>
>
> This build contains the following changes and fixes:
>
>
>
> Compiler:
>
>    Added support for Extension methods
>
>    Added support for subscribing to/ unsubscribing from events with
>
>    implicitly instantiated delegates (new delegate syntax)
>
>    Fixed enum member attribute target
>
>
>
> VS Integration:
>
>    Intellisense support for CoClass when using COM Object
>
>    Intellisense now support types from VULCAN.NET Project reference
>
>    Intellisense now basically support types from CS/VB Project reference
>
>    Intellisnese now supports code folding
>
>    Intellisense now recognize PROPERTY were GET/SET don't have the same
>
>    visibility
>
>    Fixed some issues with the separate designer.prg file
>
>    Now WinForm Designer support user-designed controls
>
>    WinForm designer support for Events in inherited controls
>
>    Formatting Code available through Edit/Advanced/Format Document or 
> Format
>
>    Selection
>
>
>
> VODSK:
>
>    Modified TextControl:ControlFont code in order to take account of the
>
>    name
>
>    change Font to ControlFont.
>
>    Fix for bug #1165, updated Color class constructor so that it allows to
>
>    pass in the color as a single value, as in VO
>
>    Modified WinFormVOWindowHost:ProcessDialogKey() so that it better 
> handles
>
>    the TAB key.
>
>    Updated Control:LinkDF(oDS, siDF) method so that it also handles the
>
>    field param(siDF) passed as SYMBOL.
>
>    Fix for bug #1166, now TreeView:SortChildren() uses a delegate instead 
> of
>
>    a function pointer for the sorting callback method.
>
>
>
> RunTime Functions:
>
>    Fix for bug #1167, File() function was throwing an exception, instead 
> of
>
>    returning FALSE for erroneous paths
>
>    Fix for bug #1172, Proper() was only checking for whitespace as word
>
>    separators.
>
>
>
> Tools:
>
>    Vulcan.NET language Add-In for RedGate's .NET Reflector available in
>
>
>
> Tools Folder.
>
>    Vulcan.NET Productivity pack for Visual Studio is installed per 
> default.
>
>
>
> Help System:
>
>    Fix for Help System producing is errors with method having one USUAL
>
>    parameter.
>
>
>
> Please read the readme, and Help File for all the new features and Syntax
>
> for new language features.
>
>
>
> All the best,
>
>
>
> On behalf of the Development team for Vulcan.NET 3.0
>
> (Who deserves the credit...)
>
>
>
> Upgrade from VOSP4.
>
> http://www.grafxsoft.com/2vo28.htm
>
>
>
> With out VO2.8SP4
>
> http://www.grafxsoft.com/2vosubscribe.htm
>
>
>
> Trial Version 3.00 Good for 60 days Free at
>
> http://www.GoVulcan.NET
>
>
>
>
>
> All the best,
>
>
>
> Brian Feldman
>
> GrafX Software 

[toc] | [prev] | [standalone]


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


csiph-web