The simple test worked, but the missing file errors still showed up.

I will try some old fashioned answer “hello” lines in the stack scripts, to see 
how far the real stack is getting.
 
> On Mar 23, 2020, at 9:53 AM, Pi Digital via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> You shouldn’t need the stdio.html file at all. It is a placeholder 
> effectively for some other command you are referencing. 
> 
> Again, both using community and Indy and html5deployment versions I have no 
> issue with 404 errors like this. So it’s likely something in your setup. So a 
> step-by-step guide of your process will help us pin it down for you 
> 
> Sean Cole
> Pi Digital
> 
> 
>> On 23 Mar 2020, at 15:48, Colin Holgate via use-livecode 
>> <use-livecode@lists.runrev.com> wrote:
>> 
>> stdio.h is file I/O, and I have copies of that in Unity. The missing file 
>> is stdio.html, not sure what that is, but maybe a JavaScript variation of 
>> the C header file. 
>> 
>> I have Indy installed now, and am trying to retrieve my license to give that 
>> a go.
>> 
>>> On Mar 22, 2020, at 5:59 PM, Pi Digital via use-livecode 
>>> <use-livecode@lists.runrev.com> wrote:
>>> 
>>> Hi Colin
>>> 
>>> I’ve done a bit of digging and stdio is an api for file IO used in 
>>> emscripten. It’s also used for accessing external site pages. Additionally, 
>>> LC uses it to write to the log message box on your main page. 
>>> 
>>> So, I’m curious about the method you go through to get to this point of 
>>> error. Here are a series of questions that should get to the bottom of it. 
>>> 
>>> What platform are you running on?
>>> What platforms are you building for as set in the standalone settings?
>>> What browser are you running the HTML5 deployment in?
>>> How have you setup your localhost server?
>>> 
>>> Finally
>>> What is your recipe for failure from the point you load your stack in to LC 
>>> to when you get the 404 message, step by step?
>>> 
>>> Sean Cole
>>> Pi Digital
>>> 
>>> 
>>>>> On 21 Mar 2020, at 23:30, Colin Holgate via use-livecode 
>>>>> <use-livecode@lists.runrev.com> wrote:
>>>> 
>>>> I have only used the standalone publishing, I’m not doing anything 
>>>> custom. Line 48 of standalone-community-9.5.1.js is what is talking to the 
>>>> stdio.html file. That part of the code says this:
>>>> 
>>>> http.open("POST",”stdio.html"
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode@lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your 
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to