Gentlemen,
Just started Geocoding all our customers and interfacing the Google maps to our VFP system here and it is going well in that we can now display interactive graphs of customers/prospects for our sales staff and throw the links to the graphs into the reps Google calendars on their phones/tablets/laptops... so far so good.
However, I have a question and I guess I am being a little lazy here, as I can't be bothered sifting through all the non-useful so called solutions on the net. The example Google API call for Geocoding given here:
https://developers.google.com/maps/documentation/geocoding/start
returns back a JSON response and I want to easily catch this from VFP ideally without showing the web interface.
Any ideas as to the best approach to initiate this data and capture the response? For the maps I have used the approach whereby VFP generates a HTML Page and embeds a map from a list of lat/long co-ordinates that are embedded into the page which works fine as I don't actually receive any data back, unlike the JSON response.
I guess it is going to be a little like the web services that were the rage some time ago .... I stayed away from them.
I would prefer 100% VFP but don't mind going the called C# program if I have to.
Any ideas?
Dave
_______________________________________________
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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/18725B8CD2D5D247873A2BAF401D4AB2902695F6@EX2010-A-FPL.FPL.LOCAL
** 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.
> I guess it is going to be a little like the web services that were the
> rage some time ago .... I stayed away from them.
Well, it *is* a web service, and web services are increasingly
fundamental to how the web operates. JSON is essentially just objects in
Javascript notation so you need some way of getting that into a format
you can work with in VFP, and almost all web services communicate in
either JSON or XML.
You need to at the very least be able to send a HTTP request to the
Google endpoint, receive a JSON response (and handle any errors), and
decode the JSON into a format you can work with. If you want to stay in
VFP-land I'd be looking at Rick Strahl's web tools for all that.
Otherwise .NET can do all that natively, you could for example create a
COM-callable DLL to do it, or just an assembly called with Rick's
WWDotNetBridge tool.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1472135457.718881.705912521.0BD02CC9@webmail.messagingengine.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.
I am doing this in SharePoint next month as another visual display of data.
On Thu, Aug 25, 2016 at 9:30 AM, Alan Bourke <alanpbourke@fastmail.fm>
wrote:
> > I guess it is going to be a little like the web services that were the
> > rage some time ago .... I stayed away from them.
>
> Well, it *is* a web service, and web services are increasingly
> fundamental to how the web operates. JSON is essentially just objects in
> Javascript notation so you need some way of getting that into a format
> you can work with in VFP, and almost all web services communicate in
> either JSON or XML.
>
> You need to at the very least be able to send a HTTP request to the
> Google endpoint, receive a JSON response (and handle any errors), and
> decode the JSON into a format you can work with. If you want to stay in
> VFP-land I'd be looking at Rick Strahl's web tools for all that.
> Otherwise .NET can do all that natively, you could for example create a
> COM-callable DLL to do it, or just an assembly called with Rick's
> WWDotNetBridge tool.
>
> --
> Alan Bourke
> alanpbourke (at) fastmail (dot) fm
>
[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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAJidMYLPBn_xTH+Bjvmp8K7oWz4jdp_E_=oFSQCqJgo1GcacYw@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.
Thanks Alan,
I have been looking at Rick's software along with Craig Boyd's JSON class, so I was on the right track... it just seems so damned complicated for a simple result.
Dave
-----Original Message-----
From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Alan Bourke
Sent: 25 August 2016 15:31
To: profoxtech@leafe.com
Subject: Re: VFP Call to Google Geocoding API
> I guess it is going to be a little like the web services that were the
> rage some time ago .... I stayed away from them.
Well, it *is* a web service, and web services are increasingly fundamental to how the web operates. JSON is essentially just objects in Javascript notation so you need some way of getting that into a format you can work with in VFP, and almost all web services communicate in either JSON or XML.
You need to at the very least be able to send a HTTP request to the Google endpoint, receive a JSON response (and handle any errors), and decode the JSON into a format you can work with. If you want to stay in VFP-land I'd be looking at Rick Strahl's web tools for all that.
Otherwise .NET can do all that natively, you could for example create a COM-callable DLL to do it, or just an assembly called with Rick's WWDotNetBridge tool.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
[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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/18725B8CD2D5D247873A2BAF401D4AB290269694@EX2010-A-FPL.FPL.LOCAL
** 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.
Hi Dave:
For the JSON part you have an Open Source project on VFPx:
http://vfpx.codeplex.com/wikipage?title=nfJson
Best Regards,
Fernando D. Bozzo.-
2016-08-25 16:05 GMT+02:00 Dave Crozier <DaveC@flexipol.co.uk>:
> Gentlemen,
> Just started Geocoding all our customers and interfacing the Google maps
> to our VFP system here and it is going well in that we can now display
> interactive graphs of customers/prospects for our sales staff and throw the
> links to the graphs into the reps Google calendars on their
> phones/tablets/laptops... so far so good.
>
> However, I have a question and I guess I am being a little lazy here, as I
> can't be bothered sifting through all the non-useful so called solutions on
> the net. The example Google API call for Geocoding given here:
>
> https://developers.google.com/maps/documentation/geocoding/start
>
> returns back a JSON response and I want to easily catch this from VFP
> ideally without showing the web interface.
>
> Any ideas as to the best approach to initiate this data and capture the
> response? For the maps I have used the approach whereby VFP generates a
> HTML Page and embeds a map from a list of lat/long co-ordinates that are
> embedded into the page which works fine as I don't actually receive any
> data back, unlike the JSON response.
>
> I guess it is going to be a little like the web services that were the
> rage some time ago .... I stayed away from them.
>
> I would prefer 100% VFP but don't mind going the called C# program if I
> have to.
> Any ideas?
>
> Dave
>
>
[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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAGQ_JumZOpauCZRGPzKVurWSTs+q_qhbWz3_TgR3fh2-x6rKOA@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.
Well, it's a lot better than XML for sending hierarchical info over the
wire.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1472141088.738824.706029201.35E6B5D5@webmail.messagingengine.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.
On Thu, Aug 25, 2016 at 12:04 PM, Alan Bourke <alanpbourke@fastmail.fm> wrote:
> Well, it's a lot better than XML for sending hierarchical info over the
> wire.
>
I do find the curly braces {} get snagged in the ethernet cable a lot
less that the pointy arrows <>.
{grin}
--
Ted Roche
Ted Roche & Associates, LLC
_______________________________________________
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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4u0FxQL3cO7V4aoTUGfBTfx=nR1qQuwqLHwjN98EFJNXA@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.
Hey Dave - what happened - you didn't want any answers back from Females in our group here??
:-)
Regards,
Kurt Wendt
Senior Systems Analyst
Tel. +1-212-747-9100
www.GlobeTax.com
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Dave Crozier
Sent: Thursday, August 25, 2016 10:06 AM
To: profoxtech@leafe.com
Subject: VFP Call to Google Geocoding API
Gentlemen,
Just started Geocoding all our customers ...
_______________________________________________
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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/80838F1CA795B14EA1AF48659F35166F2D8B6E@DREXCH02.corp.globetax.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.
Do you still need a vfp code example of this i lost most the thread
> On 25 Aug 2016, at 18:05, Kurt Wendt <Kurt_Wendt@globetax.com> wrote:
>
> Hey Dave - what happened - you didn't want any answers back from Females in our group here??
>
> :-)
>
> Regards,
> Kurt Wendt
> Senior Systems Analyst
>
>
> Tel. +1-212-747-9100
> www.GlobeTax.com
>
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Dave Crozier
> Sent: Thursday, August 25, 2016 10:06 AM
> To: profoxtech@leafe.com
> Subject: VFP Call to Google Geocoding API
>
> Gentlemen,
> Just started Geocoding all our customers ...
>
[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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/E09B07B0-75EA-4661-BC7A-385E63DDE485@actongate.co.uk
** 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: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2016-08-25 18:13:53 Link
On 2016-08-25 10:52, Dave Crozier wrote:
> it just seems so damned complicated for a simple result.
That pretty much sums up lots of the web and early DotNet stuff!!!! I
swear sometimes it seems like these uber-nerds create things to be so
complex simply because they can.
_______________________________________________
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: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/369bc67e5bc2800263fb94becd8652b9@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.