Folks, An update. I was thinking about releasing yesterday but to make a long story short, some of what I've done needs a rethink. Otherwise I'm releasing something you're not going to like...
Let me explain. I did get through all the properties and methods and everything on my todo list. While tracking down a random issue that turned out to be a misnamed property, it hit me that I hadn't done much testing against large data. More background... The goal of this is to have a Visual Foxpro object mimic the related Chilkat object. For instance, the Chilkat EMail object has a FromName property. The related VFP object, apply named Email has a FromName object. Beneath the sheets, when you reference the VFP Email FromName property, it goes out to retrieve the Chilkat Email FromName property. Pretty straightforward. I was fortunate enough to actually deal with a Chilkat character property that is 260 characters in length. When I referenced it, VFP blew up. And it turns out it's a hard coded limitation *if you define it on the property sheet*. See AddProperty Method in the help file. I've tried to trick VFP into making something larger but it doesn't work. But the Comment and Tag properties of VFP objects can be as large as you like (within reason), but these are predefined. The AddProperty() function also doesn't have that limitation. Yes, you can use the AddProperty() function on an existing property but the Access method fires before the redefinition and it gets ugly. In this specific example the Chilkat property was named "P". So the VFP property with the Access/Assign methods was named "P_VFP" but wrote the value to the "P" property (with no Access/Assign methods). In the Init method of the object I AddProperty() the existing "P" property out to 260 characters. And it works, though it's not as clean as one would like... But now think of the size of some web pages, binary file contents, and so forth. I need to either come up with a cleaner solution or make a second pass and ripple this idea through more character and binary data. Bill Anderson On Mon, Aug 1, 2022 at 2:01 PM Bill Anderson <billan...@gmail.com> wrote: > Paul, > > Well, I can report that the wrapper coding was finished over the weekend. > > There's still lots to do. There's about a dozen classes to review and a > bunch of how-to-use documentation to write. But I've finally got my arms > fully around it. Took 7 months to put together. > > It's....big. The VCT is approaching 21MB, of which a vast majority is > Chilkat's own documentation. > > I'd say "soon" but my development laptop is getting repaired and who knows > what'll happen there, etc. I'd guess it's about a month away. > > Bill Anderson > > On Mon, Jul 11, 2022 at 11:44 AM Paul H. Tarver <p...@tpcqpc.com> wrote: > >> Sounds very interesting. Do you have some ETA in mind for >> selling/releasing >> the tool? >> >> Paul H. Tarver >> Tarver Program Consultants, Inc. >> >> -----Original Message----- >> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Bill >> Anderson >> Sent: Saturday, July 09, 2022 7:05 PM >> To: profoxt...@leafe.com >> Subject: Re: Need Help - Foxpro & Chilkat & Rest API >> >> >> A Foxpro wrapper would be too much to hope for, but that would be even >> better if it is exists.<< >> >> It exists, you haven't seen it yet. I'm working on a VFP tool that wraps >> *everything* in the Chilkat library. Over halfway done. There's 103 >> classes >> (1 deprecated) and I've wrapped maybe 61 of them? >> >> I too experienced *exactly* what you experienced re: Chilkat. The upside - >> They do document well. The downside? They document well. It's all on one >> web page per class and hard to see the big picture. To their defense, I >> don't necessarily have a better way to display such information on the >> web. >> >> Rest is one of the classes I've wrapped, FWIW but that may not necessarily >> help clarify your issue. If you think it might, just send me an email - or >> I'll take a look at it. >> >> If I complete the wrapping I may do something similar with their example >> code. >> >> Bill Anderson >> >> On Sat, Jul 9, 2022 at 10:46 AM Paul H. Tarver <p...@tpcqpc.com> wrote: >> >> > I have a spec project where I need to build an application using a REST >> API >> > to extract data elements and then post those data elements to a >> different >> > system. The API requires me to get a token upfront (which has a >> five-minute >> > life span), issue my requests with the token and then get the results >> back >> > in a JSON or XML format. Based on recommendations I received at the >> Virtual >> > FoxFest earlier this year, I purchased the Chilkat tools and dove into >> what >> > has turned out to be the deep end without knowing how to swim. The >> > documentation at Chilkat while extensive is almost too extensive for me >> to >> > understand exactly what I've got to do to make this work. >> > >> > >> > >> > So far, I've been unable to even get a token back. All I seem to be able >> to >> > get back from the server is >> > >> > >> > >> > 400 Bad request >> > >> > Your browser sent an invalid request. >> > >> > >> > >> > That response has been less than helpful. I've reached out to the API >> > Provider but their answers are focused on requests issued after I get >> the >> > token. >> > >> > >> > >> > My question is this: Does anyone have any sample Foxpro code they use >> for >> a >> > similar process (Request a token, then make requests with the token) >> using >> > the Chilkat tools they would be willing to share? A Foxpro wrapper would >> be >> > too much to hope for, but that would be even better if it is exists. >> I've >> > got to get to a point where I'm beyond this initial stage to prove I can >> > make this work. >> > >> > >> > >> > Help! I know this is possible, but so far, I'm not making much headway. >> > >> > >> > >> > Paul H. Tarver >> > Tarver Program Consultants, Inc. >> > >> > >> > >> > >> > >> > >> > >> > --- StripMime Report -- processed MIME parts --- >> > multipart/alternative >> > text/plain (text body -- kept) >> > text/html >> > --- >> > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CA+O1enFA0NATRLea8ONTDQNO=3mcJS5NKaP3z0g=vpundjp...@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.
