I was there and didn’t find itYou don’t need to mess with it if you recompile browservice with the changes he proposed. he detailed them on the issues page of his github project page. have a look on them.
I was there and didn’t find itYou don’t need to mess with it if you recompile browservice with the changes he proposed. he detailed them on the issues page of his github project page. have a look on them.
I was there and didn’t find it
According to the developer documentation on github, yes, at least Debian 10. I am using latest Raspbian on Raspberry Pi 3B.@Bruninho, thanks for the news (to me) about Browservice.
Do you know if it needs at least Debian 10 to run ? I've tried building it on a Debian 9 virtual machine, and it fails.
To prove or disprove this theory, we need to log all the HTTP requests that Browservice receives. Could you try to add the line INFO_LOG("HTTP ", request->method(), " ", request->path()); to the beginning of the function Context:nHTTPServerRequest in viceplugins/retrojsvice/src/context.cpp? To apply the change, you can simply re-run the make command and restart Browservice. After this, connecting with IE5 to the modified Browservice instance, see what HTTP GETlines there are in the command line output. If it was running correctly, the output would look something like topi@laptopi:~/vcs/browservice$ release/bin/browservice 2>&1 | grep HTTP INFO @ retrojsvice.so src/http.cpp:620 -- Starting HTTP server (listen address: 127.0.0.1:8080) INFO @ retrojsvice.so src/http.cpp:628 -- HTTP server started successfully INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET / INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET /1/XirNMFay3yQAXbdv2amTv8tNoKpLoEss/prev/ INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET /1/XirNMFay3yQAXbdv2amTv8tNoKpLoEss/ INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET /1/XirNMFay3yQAXbdv2amTv8tNoKpLoEss/next/ INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET /1/XirNMFay3yQAXbdv2amTv8tNoKpLoEss/ INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET /1/XirNMFay3yQAXbdv2amTv8tNoKpLoEss/image/1/1/1/1500/886/0/ INFO @ retrojsvice.so src/context.cpp:570 -- HTTP GET /1/XirNMFay3yQAXbdv2amTv8tNoKpLoEss/image/1/2/0/1500/886/0/ <Continues with lots of image requests> However, if my theory is correct, you only get the first four HTTP GET requests, after which IE5 uses the cached pages. An easy way to get around this bug is to disable the native Forward button forwarding by changing the initial value of preMainVisited_ from false to true on line 63 in viceplugins/retrojsvice/src/window.cpp. |
Oh, ok.. so are they in an updated version of Browservice ? I have 0.9.2.8 I think.You don’t need to mess with it if you recompile browservice with the changes he proposed. he detailed them on the issues page of his github project page. have a look on them.
void Context:nHTTPServerRequest(shared_ptr<HTTPRequest> request) { |
REQUIRE_API_THREAD(); |
Bruninho,
ok, where do I enter this new code ? I know how to compile it with make command, but where do I put all these changes to the code ?
Update: changing the block to an if else and declaring width -= 1; and height -= 2; for the else statement, works. The scrollbars are gone.
I think that probably ALL browsers can use these values? Meaning that an if else is not needed?
and also this - the forward button - also, do I use nano to make these changes ?
An easy way to get around this bug is to disable the native Forward button forwarding by changing the initial value of preMainVisited_ from false to true on line 63 in viceplugins/retrojsvice/src/window.cpp.
No no... I know, I saw what .cpp its in, just need to know under the void function, is that where I enter it ? I read it, but when I clicked on the .cpp file affected, I saw the void function and a couple of other things underneath. I was not sure if this "INFO_LOG("HTTP ", request->method(), " ", request->path());" goes like this:The developer already explained there on github, in your post excerpt above. You need to be more patient and carefully read his documentation and Issues thread on github. I highlighted there for you. Impossible to be more clear than that. ?♂️
void Context:nHTTPServerRequest(shared_ptr<HTTPRequest> request) { |
REQUIRE_API_THREAD(); |
No no... I know, I saw what .cpp its in, just need to know under the void function, is that where I enter it ? I read it, but when I clicked on the .cpp file affected, I saw the void function and a couple of other things underneath. I was not sure if this "INFO_LOG("HTTP ", request->method(), " ", request->path());" goes like this:
code from .cpp viceplugins/retrojsvice/src/context.cpp? -
void Context:nHTTPServerRequest(shared_ptr<HTTPRequest> request) {
REQUIRE(state_ == Running);
REQUIRE_API_THREAD();
"Then enter here-->" INFO_LOG("HTTP ", request->method(), " ", request->path());
Putting it all together:
void Context:nHTTPServerRequest(shared_ptr<HTTPRequest> request) {
REQUIRE_API_THREAD();
NFO_LOG("HTTP ", request->method(), " ", request->path());
Thats all...
Gotta find Monster Truck Madness for Win 9x now.
Dude, are you like suspended still ?You don’t need to mess with it if you recompile browservice with the changes he proposed. he detailed them on the issues page of his github project page. have a look on them.