(01-05-2023, 03:53 AM)mnrvovrfc Wrote:(01-05-2023, 03:00 AM)madscijr Wrote: Speaking of, have we got HTTP functions built into QB64PE yet?
Because it would be cool to make a QB64PE program that can make REST calls to Google translate and autotranslate a text file (or QB code) word for word...
For somebody who knows English, this method might be unacceptably slow, depending very much on Internet speeds. Not everybody has "1000 MEGAS" and not even 100. Also there are people trying to leech off Wifi from restaurants, schools and community houses...
There are people who don't live in the capital of an African or Asian country with Internet access which could be slower than the "basic" plan for a given ISP in the States. Think about the people of a certain eastern European country. But what do I really know?
The upcoming "HTTP(S)" functionality could be a mixed blessing. It's something I'm not going to be waiting for as much as the sound counterpart to "_NEWIMAGE" and related stuff.
Translating code is even less desireable; allow an user to use variable and function names in the language he/she knows best. But to be kind please comment in English, in my case because otherwise I know Spanish, would have to depend on that to know what is in Portuguese, would have to depend on my high-school Italian, could barely make out French and that's it.
To say it another way, for example Kernelpanic almost doesn't comment what program he offers which has me trying to figure out what a variable does. But it could go two ways: I'm lazy and don't like long variable names, have to really sit down and comment my programs before sharing them.
I think the more important & useful part would be the ability to call REST services from QB64PE. That opens up a lot of doors. Translating is just an exercise. (I'll leave the arguments for & against SOA and considerations for people's Internet speeds in other parts of the world for someone else to argue.)
I'll take more sound commands, too!