|
|
Home » Community » Coffee corner » WebWord - Turtle reference example issue
WebWord - Turtle reference example issue [message #49743] |
Wed, 18 April 2018 10:05 |
Tom1
Messages: 1242 Registered: March 2007
|
Senior Contributor |
|
|
Hi,
Was not sure where to put this, so I ended up here at the coffee corner... (Feel free to move this wherever it belongs.)
Anyway, I do not seem to be able to make WebWord reference example work. It compiles and links OK. When connecting to it at address 127.0.0.1:8088 from Firefox, I just get a 'Connection closed.' -dialog with an OK button. The terminal shows:
Accepted, header read
Sending HTML
I tried this on LinuxMint using both GCC and CLANG compilers. No difference there.
I think this used to work some years ago.
Best regards,
Tom
|
|
|
|
Re: WebWord - Turtle reference example issue [message #49745 is a reply to message #49744] |
Wed, 18 April 2018 14:54 |
Tom1
Messages: 1242 Registered: March 2007
|
Senior Contributor |
|
|
Hi,
Thanks, Oblivion. I found out that it is not working on Windows either.
The reason I'm currently tinkering with TURTLE is that I'm looking into a possibility to create a control application that runs on an embedded Linux (or Windows) computer offering its GUI over wireless network to phones and tablets using TURTLE.
Best regards,
Tom
|
|
|
|
|
|
Re: WebWord - Turtle reference example issue [message #49806 is a reply to message #49803] |
Tue, 08 May 2018 16:25 |
Tom1
Messages: 1242 Registered: March 2007
|
Senior Contributor |
|
|
Hi Mirek,
Thanks! I will test soon.
BTW: Would it alternatively be difficult to create a turtle application without the window frame, i.e. in a way that the full page area in the browser would be the application window's client area? When working with a single window application (potentially with menus and dialogs on top) the extra window frame just wastes space on a small smart phone display.
Best regards,
Tom
|
|
|
|
|
Re: WebWord - Turtle reference example issue [message #49811 is a reply to message #49808] |
Wed, 09 May 2018 09:53 |
Tom1
Messages: 1242 Registered: March 2007
|
Senior Contributor |
|
|
Hi Mirek,
Thanks, now it works from Firefox on localhost. (Tested on Windows 10.) Adding TopMost() did not change anything.
However, if I try to connect from an another computer running Firefox over the LAN (or from my Android phone over WLAN) I still receive "Connection closed." on the browser and the running Webword console shows again:
Accepted, header read
Sending HTML
Accepted, header read
Sending HTML
Should I change Webword some way to support external access... ?
I'm surely interested on this because a working Turtle GUI would open new possibilities. I cannot confirm production status for it yet. In any case I think that small embedded (blackbox) computers running all kinds of control applications based on Turtle GUI would give a very productive approach to accessing their configuration settings. Just a smart phone or a tablet with browser. No need for any special Android or iOS apps. This way the control logic and the GUI can both be programmed in the familiar U++ environment which is a great benefit.
Best regards,
Tom
[Updated on: Wed, 09 May 2018 09:54] Report message to a moderator
|
|
|
Re: WebWord - Turtle reference example issue [message #49998 is a reply to message #49811] |
Thu, 14 June 2018 20:32 |
Novo
Messages: 1371 Registered: December 2006
|
Ultimate Contributor |
|
|
I checked WebWord on both Linux (Ubuntu 18.04) and Windows (8.1) with the latest source code and got the same problem on both platforms: it works in Debug configuration, and it doesn't work in Release, although I'm getting "Accepted, header read Sending HTML" messages. It sometimes displays a "Connection Closed" dialog, which quickly disappears.
Am I doing something wrong?
Another observation. WebWord spends most of its time inside of Ctrl::StartSession() endlessly calling socket.Accept(server). It looks like server doesn't have any timeout associated with it.
Thanks in advance.
Regards,
Novo
|
|
|
Goto Forum:
Current Time: Fri Sep 20 10:54:26 CEST 2024
Total time taken to generate the page: 0.03241 seconds
|
|
|