xsharp.eu

alanbourke wrote: In terms of replicating the Visual FoxPro runtime, yes you would absolutely need native support for DBF and CDX, database containers and the rest. You could also probably drop 50% of the functions listed in the VFP help file as they were only there for FoxPro 2.x and DBase compatibility. Nobody in this day and age is using @ .. SAY for example.
Also anyone wanting an existing platform that handles VFP code could have a look at Lianja.

Karl-Heinz wrote: i think the VFP user base is larger than the Xbase++ community. Over the years some attempts have been made to move VFP to .net, but all silently died. Also, Alaska (Xbase++) announced years ago a PolarFox version, but nothing happened till now.

Here are some VFP -> .net links:

Monday, February 12, 2018
Managed Dbf using X# Language in VS2017
I tried using X# Language within Visual Studio 2017 and it's like writing CLIPPER using Visual Studio with all the bells and whistles of the .NET framework of course ?
Check out X Sharp : https://www.xsharp.eu/

Guineu The FoxPro runtime

Guineu is an opensource alternative runtime library for Microsoft Visual FoxPro® 9.0 that runs on any Microsoft .NET compatible platform.

Would be interesting if some of the daily VFP users would jump in, and explain the current situation..

Jamal wrote: I see one of challenges is the use of the dot notation for accessing methods and properties, etc and the equal sign:
For example:
FoxPro:
txtTest.Value = "Some text..."
In X# and VO:
txtTest:Value := "Some text..."
Since I develop mainly in C# and VO, sometimes my mind forgets which language I am using and I get mixed up between the dot and the colon! Arragghh! I mentioned it before the X# team even the Vulcan team, that the dot notation should be an option; so here we go if FoxPro syntax is to be implemented.

STATIC METHOD SubStr(cStr AS STRING, iOffSet AS INT, iLen AS INT) AS STRING
METHOD SubStr(cStr AS STRING, iOffSet AS INT, iLen AS INT) AS STRING
METHOD SubStr(iOffSet AS INT, iLen AS INT) AS STRING

Karl-Heinz wrote: Johan,
if you want to know more about the VFP commands, syntax etc., here´s the link to the VFP9 SP2 help file:

@Wolfgang
As you did already mention: The main problem is to *which* GUI-lib preprocessed commands like:

Code: Select all

DEFINE POPUP popFruits FROM 5,5 ;
   MULTISELECT MARGIN            && Create multi-choice menu
DEFINE BAR 1 OF popFruits ;
   PROMPT '<Apples'  MARK CHR(3)    && First item
ON SELECTION POPUP popFruits DO yourchoice    && Choice routine
ACTIVATE POPUP popFruits 

#command DEFINE POPUP <cls> [FROM <x>, <y>]   [MULTISELECT] [MARGIN] => ;
  VAR <cls> := System.Windows.Forms.ContextMenu{}

#command DEFINE BAR <n> OF <owner>   PROMPT <prompt>  [MARK <chr>] => ;
  VAR bar<n> := System.Windows.Forms.MenuItem{<prompt>};;
  <owner>:Add(bar<n>)

#command ON SELECTION POPUP <popMenu> DO <yourchoice>  => ;
  <popMenu>:Click += <yourchoice>

#command ACTIVATE POPUP <pop> => ;
  SELF:ContextMenu := <pop>

Karl-Heinz wrote: But i think what´s needed is a lib with wrapper classes around the required parts of the .net framework.

This can IMO only be done by experienced VFP people who exactly know what all these VFP Commands finally initiate.

Another todo is IMO to replace e.g. the form files .scx and .sct - which are a pair of a DBF and a memo file where the Painter stores the Form settings-, with pure text files.