Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit support
Dave
I guess that would include SQL Server bigint and dot NET longs.
Laurie
On 20 October 2017 at 10:13, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit supportDave
[excessive quoting removed by server]
Multi threading support.
Best Regards Vassilis Aggelakos
On Fri, Oct 20, 2017 at 12:19 PM, Laurie Alvey trukker41@gmail.com wrote:
I guess that would include SQL Server bigint and dot NET longs.
Laurie
On 20 October 2017 at 10:13, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit supportDave
[excessive quoting removed by server]
I would vote for Object Relational Mapping with different database dialects. See knex.js & Bookshelf.js
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virus-free. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Fri, Oct 20, 2017 at 8:19 PM, Laurie Alvey trukker41@gmail.com wrote:
I guess that would include SQL Server bigint and dot NET longs.
Laurie
On 20 October 2017 at 10:13, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit supportDave
[excessive quoting removed by server]
Native runtimes on OS X, Linux and Windows.
On Fri, Oct 20, 2017 at 5:13 AM, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit supportDave
[excessive quoting removed by server]
And browsers like Java Runtime? And now, Web Extensions since NPAPI support is being dropped....
On Fri, Oct 20, 2017 at 6:37 PM, Ted Roche tedroche@gmail.com wrote:
Native runtimes on OS X, Linux and Windows.
64 bits version, integration with WPF,...
Jose Enrique Llopis
-----Mensaje original----- De: ProFox [mailto:profox-bounces@leafe.com] En nombre de Dave Crozier Enviado el: viernes, 20 de octubre de 2017 11:14 Para: ProFox Email List Asunto: VFP - What upgrades would VFP10 have had...
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit support
Dave
[excessive quoting removed by server]
1. 64bit VFP IDE for access to virtually unlimited RAM 2. 64bit compiled applications 3. Simultanous compilation to multiple target platforms: Linux, Mac, Windows 4. Add the target platform of Web and allow me to cross use business objects I also use in desktop applications. 5. Make it as easy to develop the Web applications as it is easy to develop desktop applications. 6. Add the target of Raspberry Pi as well for their Linux OS distros 7. While we're at it add iOS and Android phone support as a target 8. Strong typing. I'm tired of my own coding errors. Typed issues should be found at compile time, not during testing. That'd save me a ton of time. 9. Keep the database agnostic nature of VFP 10. Keep the reasonable license fee, with unlimited distributions per compiled application.
-Kevin
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Dave Crozier Sent: Friday, October 20, 2017 5:14 AM To: ProFox Email List Subject: VFP - What upgrades would VFP10 have had...
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit support
Dave
[excessive quoting removed by server]
Sounds to me much like all you've got in Xojo Kevin!!
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Kevin J Cully Sent: 20 October 2017 13:49 To: ProFox Email List profox@leafe.com Subject: RE: VFP - What upgrades would VFP10 have had...
1. 64bit VFP IDE for access to virtually unlimited RAM 2. 64bit compiled applications 3. Simultanous compilation to multiple target platforms: Linux, Mac, Windows 4. Add the target platform of Web and allow me to cross use business objects I also use in desktop applications. 5. Make it as easy to develop the Web applications as it is easy to develop desktop applications. 6. Add the target of Raspberry Pi as well for their Linux OS distros 7. While we're at it add iOS and Android phone support as a target 8. Strong typing. I'm tired of my own coding errors. Typed issues should be found at compile time, not during testing. That'd save me a ton of time. 9. Keep the database agnostic nature of VFP 10. Keep the reasonable license fee, with unlimited distributions per compiled application.
-Kevin
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Dave Crozier Sent: Friday, October 20, 2017 5:14 AM To: ProFox Email List Subject: VFP - What upgrades would VFP10 have had...
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit support
Dave
[excessive quoting removed by server]
Hi Kevin,
you basically described Lianja with your wishlist. (Lianja is a SpinOff of the Recital core, which was a FoxPro Clone on Big-Iron-boxes). They use the VFP objectmodel, and can use an enhanced VFP-syntax or PHP, Phyton and Javascript /Typescript (whatever you prefer)
I always coined Lianja as "this would be VFP11, if Microsoft would have been intelligent enuf"
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox [mailto:profox-bounces@leafe.com] Im Auftrag von Kevin J Cully Gesendet: Freitag, 20. Oktober 2017 14:49 An: ProFox Email List Betreff: RE: VFP - What upgrades would VFP10 have had...
1. 64bit VFP IDE for access to virtually unlimited RAM 2. 64bit compiled applications 3. Simultanous compilation to multiple target platforms: Linux, Mac, Windows 4. Add the target platform of Web and allow me to cross use business objects I also use in desktop applications. 5. Make it as easy to develop the Web applications as it is easy to develop desktop applications. 6. Add the target of Raspberry Pi as well for their Linux OS distros 7. While we're at it add iOS and Android phone support as a target 8. Strong typing. I'm tired of my own coding errors. Typed issues should be found at compile time, not during testing. That'd save me a ton of time. 9. Keep the database agnostic nature of VFP 10. Keep the reasonable license fee, with unlimited distributions per compiled application.
-Kevin
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Dave Crozier Sent: Friday, October 20, 2017 5:14 AM To: ProFox Email List Subject: VFP - What upgrades would VFP10 have had...
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit support
Dave
[excessive quoting removed by server]
64-bit DBF and data structures support Unicode UI and report controls Bridge with for dotNet stuffs?
On Fri, Oct 20, 2017 at 5:13 PM, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
On 2017-10-21 09:07, Man-wai Chang wrote:
Bridge with for dotNet stuffs?
Do you mean like wwDotNetBridge from WestWind? https://www.west-wind.com/wwDotnetBridge.aspx
Expanding on my earlier comment a bit,
- Open Source, and compilable on all reasonable targets
To explain and expand a little bit, I use languages like Python, PHP, Ruby and scripting languages like bash, and... They Just Work. In a console in Linux, on Windows, on Mac. On a Chromebook, on a Raspberry Pi. On a NAS box. On a big-endian CPU. On my router. On a RISC chip. On my rooted AppleTV. On a little-endian chip. It Just Works. That's "normal." That's what computer languages do.
The idea that there is a proprietary language that only runs on one OS, which only runs on one CPU family, which is all controlled by one manufacturer, well, that's foolish. What if you need it to run somewhere else, like a Snapdragon chip on your phone? Or the new weather station you're building? Or to control your solar panel battery charger?
Well, then, clearly, FoxPro is not the language for you.
Which is too bad, because it is an awfully fun language to work in.
On Fri, Oct 20, 2017 at 5:13 AM, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit supportDave
[excessive quoting removed by server]
Nice fantasies, but we all know MS will never release the source code. Ah well.
Laurie
On 21 October 2017 at 18:09, Ted Roche tedroche@gmail.com wrote:
Expanding on my earlier comment a bit,
- Open Source, and compilable on all reasonable targets
To explain and expand a little bit, I use languages like Python, PHP, Ruby and scripting languages like bash, and... They Just Work. In a console in Linux, on Windows, on Mac. On a Chromebook, on a Raspberry Pi. On a NAS box. On a big-endian CPU. On my router. On a RISC chip. On my rooted AppleTV. On a little-endian chip. It Just Works. That's "normal." That's what computer languages do.
The idea that there is a proprietary language that only runs on one OS, which only runs on one CPU family, which is all controlled by one manufacturer, well, that's foolish. What if you need it to run somewhere else, like a Snapdragon chip on your phone? Or the new weather station you're building? Or to control your solar panel battery charger?
Well, then, clearly, FoxPro is not the language for you.
Which is too bad, because it is an awfully fun language to work in.
On Fri, Oct 20, 2017 at 5:13 AM, Dave Crozier DaveC@flexipol.co.uk wrote:
Alan's comment post regarding VFP not having any upgrades put me in the
realm of thinking that IF VFP development had continued what updates and additions we could have seen.
Floor open to anyone with useful additions.
For myself I'll start off with:
Native 64bit supportDave
[excessive quoting removed by server]
-
Dave Crozier -
José Enrique Llopis -
Jürgen Wondzinski -
Kevin J Cully -
Laurie Alvey -
Man-wai Chang -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Paul Hemans -
Ted Roche -
Vassilis Aggelakos