Author: Johan Nel
Posted: 2019-06-27 07:51:46 Link
Hi VFPers
I have asked this question on foxite too with very little feedback, so I
am asking it here too.
If you have to summarize the 1 or 2 features of VFP that you will feel
is a step backwards when migrating to .NET or any other platform as a
move forwards.
Looking forward to your replies.
Two things that was highlighted on Foxite:
1. Macro-compilation
2. Evaluate(<script>)
From a X# perspective the FOX release already has support for:
1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc, etc)
with full support planned in the foreseeable future;
2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
3. Macro-compilation;
4. Script engine that can make full use of the .NET framework.
XBase greetings,
Johan Nel
FOX Member: Friends of XSharp
George, South Africa
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/6554a136-dbab-31d5-63db-2453a6ab9236@xsinet.co.za
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: MB Software Solutions, LLC
Posted: 2019-06-27 10:08:40 Link
Steve Ellenoff and I were talking the other day about the beauty of
TEXTMERGE (TEXT/ENDTEXT) and iirc he indicated that wasn't in DotNet (or
earlier versions anyway). I use TEXT/ENDTEXT *HEAVILY* in code often.
On 6/27/2019 8:51 AM, Johan Nel wrote:
> Hi VFPers
>
> I have asked this question on foxite too with very little feedback, so
> I am asking it here too.
>
> If you have to summarize the 1 or 2 features of VFP that you will feel
> is a step backwards when migrating to .NET or any other platform as a
> move forwards.
>
> Looking forward to your replies.
>
> Two things that was highlighted on Foxite:
>
> 1. Macro-compilation
> 2. Evaluate(<script>)
>
> From a X# perspective the FOX release already has support for:
>
> 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
> etc) with full support planned in the foreseeable future;
> 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
> 3. Macro-compilation;
> 4. Script engine that can make full use of the .NET framework.
>
> XBase greetings,
>
> Johan Nel
> FOX Member: Friends of XSharp
> George, South Africa
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/dd5cb840-8e3f-56da-4007-c25d2eaec62e@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Johan Nel
Posted: 2019-06-27 11:36:39 Link
Thanks,
Good news is that X# in its current version is mapping TEXT/ENDTEXT to
an internal function... See personal communication regarding the command
with Robert.
TEXT .. ENDTEXT is also parsed and send to a function with the name
"__TextSupport". That function is not included in the runtime yet, but
if you include that function in your code then it works.
So in short, this will be supported by X#, the internals are just not
yet implemented, but will be with the final release of VFP support. If
somebody interested, it can be developed by a community member as part
of the opensource runtime...
Regards,
Johan.
On 2019/06/27 17:08, MB Software Solutions, LLC wrote:
> Steve Ellenoff and I were talking the other day about the beauty of
> TEXTMERGE (TEXT/ENDTEXT) and iirc he indicated that wasn't in DotNet
> (or earlier versions anyway). I use TEXT/ENDTEXT *HEAVILY* in code
> often.
>
>
> On 6/27/2019 8:51 AM, Johan Nel wrote:
>> Hi VFPers
>>
>> I have asked this question on foxite too with very little feedback,
>> so I am asking it here too.
>>
>> If you have to summarize the 1 or 2 features of VFP that you will
>> feel is a step backwards when migrating to .NET or any other platform
>> as a move forwards.
>>
>> Looking forward to your replies.
>>
>> Two things that was highlighted on Foxite:
>>
>> 1. Macro-compilation
>> 2. Evaluate(<script>)
>>
>> From a X# perspective the FOX release already has support for:
>>
>> 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
>> etc) with full support planned in the foreseeable future;
>> 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
>> 3. Macro-compilation;
>> 4. Script engine that can make full use of the .NET framework.
>>
>> XBase greetings,
>>
>> Johan Nel
>> FOX Member: Friends of XSharp
>> George, South Africa
>>
>>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/9aaedceb-c319-74e0-4152-84011da87881@xsinet.co.za
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Paul H. Tarver
Posted: 2019-06-27 11:53:12 Link
I would greatly miss the speedy import capabilities of Foxpro and the CREATE
CURSOR to build temporary files to temporarily hold imported data. I also
make extensive use of Class Libraries. More and more I'm using of creating
Empty Objects and adding properties to store and manage lots of variables
including making it possible to pass a single reference to the object as a
parameter and making all of the properties available to other modules. And I
agree 100% with wanting to keep the TEXTMERGE feature.
I think I could do this all day and because it seems I'm still learning new
ways to use VFP commands and features, I think I fear losing any of them!
Paul H. Tarver
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Johan
Nel
Sent: Thursday, June 27, 2019 7:52 AM
To: profoxtech@leafe.com
Subject: [NF] What would you miss from VFP, when migrating
Hi VFPers
I have asked this question on foxite too with very little feedback, so I
am asking it here too.
If you have to summarize the 1 or 2 features of VFP that you will feel
is a step backwards when migrating to .NET or any other platform as a
move forwards.
Looking forward to your replies.
Two things that was highlighted on Foxite:
1. Macro-compilation
2. Evaluate(<script>)
From a X# perspective the FOX release already has support for:
1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc, etc)
with full support planned in the foreseeable future;
2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
3. Macro-compilation;
4. Script engine that can make full use of the .NET framework.
XBase greetings,
Johan Nel
FOX Member: Friends of XSharp
George, South Africa
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/009601d52d08$cea53720$6befa560$@tpcqpc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Johan Nel
Posted: 2019-06-27 12:17:13 Link
VFP cursors are under discussion and will be supported, one way or the
other.
There are obviously some .NET features like DataSet/DataTable/DataReader
that are all
under scrutiny to see how these VFP specifics will/can be accommodated.
As you say, some of these we learn of everyday, same goes for me using
X#/.NET
and it is up to the community to assist in resolving these once the
public VFP support is
released. Again, first things first, get the basics in place then we as
community in
partnership with the DevTeam can sort out the outstanding more "unused"
features. It
is already clear now that the core of the language is stable, how quick
the DevTeam is
responding on fixing detected issues...
Johan
On 2019/06/27 18:53, Paul H. Tarver wrote:
> I would greatly miss the speedy import capabilities of Foxpro and the CREATE
> CURSOR to build temporary files to temporarily hold imported data. I also
> make extensive use of Class Libraries. More and more I'm using of creating
> Empty Objects and adding properties to store and manage lots of variables
> including making it possible to pass a single reference to the object as a
> parameter and making all of the properties available to other modules. And I
> agree 100% with wanting to keep the TEXTMERGE feature.
>
> I think I could do this all day and because it seems I'm still learning new
> ways to use VFP commands and features, I think I fear losing any of them!
>
> Paul H. Tarver
>
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Johan
> Nel
> Sent: Thursday, June 27, 2019 7:52 AM
> To: profoxtech@leafe.com
> Subject: [NF] What would you miss from VFP, when migrating
>
> Hi VFPers
>
> I have asked this question on foxite too with very little feedback, so I
> am asking it here too.
>
> If you have to summarize the 1 or 2 features of VFP that you will feel
> is a step backwards when migrating to .NET or any other platform as a
> move forwards.
>
> Looking forward to your replies.
>
> Two things that was highlighted on Foxite:
>
> 1. Macro-compilation
> 2. Evaluate(<script>)
>
> From a X# perspective the FOX release already has support for:
>
> 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc, etc)
> with full support planned in the foreseeable future;
> 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
> 3. Macro-compilation;
> 4. Script engine that can make full use of the .NET framework.
>
> XBase greetings,
>
> Johan Nel
> FOX Member: Friends of XSharp
> George, South Africa
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/f846de09-89ba-8fb2-2d5c-27d75c1c4ee3@xsinet.co.za
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Kevin Cully
Posted: 2019-06-27 12:25:21 Link
The VFP Report Writer is amazing compared to other development tools
I've seen, including my beloved Xojo. I've had to create my own report
writer that spits out HTML based reports just to get me close to what
VFP offered.
Another language command is the SCATTER NAME and GATHER NAME. The
ability to create an object with properties that corresponds to each
field of a record is incredibly useful. Especially when combined with
the TEXTMERGE command already stated earlier.
-Kevin
On 06/27/2019 08:51 AM, Johan Nel wrote:
> Hi VFPers
>
> I have asked this question on foxite too with very little feedback, so
> I am asking it here too.
>
> If you have to summarize the 1 or 2 features of VFP that you will feel
> is a step backwards when migrating to .NET or any other platform as a
> move forwards.
>
> Looking forward to your replies.
>
> Two things that was highlighted on Foxite:
>
> 1. Macro-compilation
> 2. Evaluate(<script>)
>
> From a X# perspective the FOX release already has support for:
>
> 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
> etc) with full support planned in the foreseeable future;
> 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
> 3. Macro-compilation;
> 4. Script engine that can make full use of the .NET framework.
>
> XBase greetings,
>
> Johan Nel
> FOX Member: Friends of XSharp
> George, South Africa
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/81fb1e78-e013-e1cc-ec87-f30a21348f09@cully.biz
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Stephen Russell
Posted: 2019-06-27 14:43:04 Link
Am I missing something about TEXT/ENDTEXT where it just mashes up a string
for you for whatever transpires within the loop?
What do you do with that output or the textmerge when you are done with
it?
On Thu, Jun 27, 2019 at 10:09 AM MB Software Solutions, LLC <
mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
> Steve Ellenoff and I were talking the other day about the beauty of
> TEXTMERGE (TEXT/ENDTEXT) and iirc he indicated that wasn't in DotNet (or
> earlier versions anyway). I use TEXT/ENDTEXT *HEAVILY* in code often.
>
>
> On 6/27/2019 8:51 AM, Johan Nel wrote:
> > Hi VFPers
> >
> > I have asked this question on foxite too with very little feedback, so
> > I am asking it here too.
> >
> > If you have to summarize the 1 or 2 features of VFP that you will feel
> > is a step backwards when migrating to .NET or any other platform as a
> > move forwards.
> >
> > Looking forward to your replies.
> >
> > Two things that was highlighted on Foxite:
> >
> > 1. Macro-compilation
> > 2. Evaluate(<script>)
> >
> > From a X# perspective the FOX release already has support for:
> >
> > 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
> > etc) with full support planned in the foreseeable future;
> > 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
> > 3. Macro-compilation;
> > 4. Script engine that can make full use of the .NET framework.
> >
> > XBase greetings,
> >
> > Johan Nel
> > FOX Member: Friends of XSharp
> > George, South Africa
> >
> >
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/CAJidMYK-waiwb_JA1XpcGiJwBDJVr+NkDhDnmDfRExhOTSzo2Q@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: MB Software Solutions, LLC
Posted: 2019-06-27 14:45:34 Link
In my largest case, it's usually helping to build SQLs dynamically
depending on a number of variables. In other cases, it's for building a
SET FILTER command which then gets executed.
On 6/27/2019 3:43 PM, Stephen Russell wrote:
> Am I missing something about TEXT/ENDTEXT where it just mashes up a string
> for you for whatever transpires within the loop?
>
> What do you do with that output or the textmerge when you are done with
> it?
>
> On Thu, Jun 27, 2019 at 10:09 AM MB Software Solutions, LLC <
> mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
>
>> Steve Ellenoff and I were talking the other day about the beauty of
>> TEXTMERGE (TEXT/ENDTEXT) and iirc he indicated that wasn't in DotNet (or
>> earlier versions anyway). I use TEXT/ENDTEXT *HEAVILY* in code often.
>>
>>
>> On 6/27/2019 8:51 AM, Johan Nel wrote:
>>> Hi VFPers
>>>
>>> I have asked this question on foxite too with very little feedback, so
>>> I am asking it here too.
>>>
>>> If you have to summarize the 1 or 2 features of VFP that you will feel
>>> is a step backwards when migrating to .NET or any other platform as a
>>> move forwards.
>>>
>>> Looking forward to your replies.
>>>
>>> Two things that was highlighted on Foxite:
>>>
>>> 1. Macro-compilation
>>> 2. Evaluate(<script>)
>>>
>>> From a X# perspective the FOX release already has support for:
>>>
>>> 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
>>> etc) with full support planned in the foreseeable future;
>>> 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
>>> 3. Macro-compilation;
>>> 4. Script engine that can make full use of the .NET framework.
>>>
>>> XBase greetings,
>>>
>>> Johan Nel
>>> FOX Member: Friends of XSharp
>>> George, South Africa
>>>
>>>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/10623272-006d-ef48-616f-3aaa90745c43@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Paul H. Tarver
Posted: 2019-06-27 15:09:46 Link
+1
Paul H. Tarver
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kevin Cully
Sent: Thursday, June 27, 2019 12:25 PM
To: profoxtech@leafe.com
Subject: Re: [NF] What would you miss from VFP, when migrating
The VFP Report Writer is amazing compared to other development tools
I've seen, including my beloved Xojo. I've had to create my own report
writer that spits out HTML based reports just to get me close to what
VFP offered.
Another language command is the SCATTER NAME and GATHER NAME. The
ability to create an object with properties that corresponds to each
field of a record is incredibly useful. Especially when combined with
the TEXTMERGE command already stated earlier.
-Kevin
On 06/27/2019 08:51 AM, Johan Nel wrote:
> Hi VFPers
>
> I have asked this question on foxite too with very little feedback, so
> I am asking it here too.
>
> If you have to summarize the 1 or 2 features of VFP that you will feel
> is a step backwards when migrating to .NET or any other platform as a
> move forwards.
>
> Looking forward to your replies.
>
> Two things that was highlighted on Foxite:
>
> 1. Macro-compilation
> 2. Evaluate(<script>)
>
> From a X# perspective the FOX release already has support for:
>
> 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
> etc) with full support planned in the foreseeable future;
> 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
> 3. Macro-compilation;
> 4. Script engine that can make full use of the .NET framework.
>
> XBase greetings,
>
> Johan Nel
> FOX Member: Friends of XSharp
> George, South Africa
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/00e401d52d24$44b14b00$ce13e100$@tpcqpc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Paul H. Tarver
Posted: 2019-06-27 15:09:46 Link
I use TEXT/ENDTEXT to create dynamic SQL Queries by merging static text and
dynamic variables, then pass the resulting string to SQLEXECUTE. Very
convenient when creating large query strings.
Paul H. Tarver
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Stephen
Russell
Sent: Thursday, June 27, 2019 2:43 PM
To: profoxtech@leafe.com
Subject: Re: [NF] What would you miss from VFP, when migrating
Am I missing something about TEXT/ENDTEXT where it just mashes up a string
for you for whatever transpires within the loop?
What do you do with that output or the textmerge when you are done with
it?
On Thu, Jun 27, 2019 at 10:09 AM MB Software Solutions, LLC <
mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
> Steve Ellenoff and I were talking the other day about the beauty of
> TEXTMERGE (TEXT/ENDTEXT) and iirc he indicated that wasn't in DotNet (or
> earlier versions anyway). I use TEXT/ENDTEXT *HEAVILY* in code often.
>
>
> On 6/27/2019 8:51 AM, Johan Nel wrote:
> > Hi VFPers
> >
> > I have asked this question on foxite too with very little feedback, so
> > I am asking it here too.
> >
> > If you have to summarize the 1 or 2 features of VFP that you will feel
> > is a step backwards when migrating to .NET or any other platform as a
> > move forwards.
> >
> > Looking forward to your replies.
> >
> > Two things that was highlighted on Foxite:
> >
> > 1. Macro-compilation
> > 2. Evaluate(<script>)
> >
> > From a X# perspective the FOX release already has support for:
> >
> > 1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
> > etc) with full support planned in the foreseeable future;
> > 2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
> > 3. Macro-compilation;
> > 4. Script engine that can make full use of the .NET framework.
> >
> > XBase greetings,
> >
> > Johan Nel
> > FOX Member: Friends of XSharp
> > George, South Africa
> >
> >
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message: https://leafe.com/archives/byMID/00e301d52d24$446e9cb0$cd4bd610$@tpcqpc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.