Bainespal wrote:Thanks for doing this! We've needed a web interpreter since forever, so this will be great breakthrough.
The file selection and command input interfaces appear to work okay on Chrome.
The only problem - as I said in a long obscenity-filled tirade in another message - is that it doesn't work in Internet Explorer. Everyone says that if you have a submit event with a return false it cancels the submit, which is what I want to do. Internet Explorer is not following this, and nobody ever said this doesn't work with IE.
I assume you're getting the list of games from the IF Archive?
Yeah, I just grabbed a few files for testing purposes so that I could see what was happening and analyze what was going on.
I'm sure it's too early to comment on design, but I don't have a problem with the input/command prompt being separated from the main display window. I kind of prefer it that way; it's how MUD clients work. However, I wonder how it will integrate with Hugo's display properties, specifically, with games that try to design their own windows. But even if the web runner only works for text games, it will be a great breakthrough.
The problem I had was that for a javascript application, if I just kept writing new lines on the screen it eventually causes the screen to have too much material and the scroll bars pop up, so the user then has to scroll down after every input. Keeping about the last 10 or so lines of input/response and having a full scrollback buffer seemed a good compromise.
I like the scrollback buffer. I don't know if it will be possible to integrate it with the main design window in the future, but even if it has to be separate, it's good that the feature is already in development.
I'm glad to see this. :)
I'm glad you liked it. However, if I can't get the EXPLETIVE DELETED Internet Explorer to allow me to have a javascript program that can process typed in information without causing the submit even to be triggered, I'm going to have to abandon it and go to a straight PHP application.
I can't abandon 75% of the people using the Internet just because Chrome and Firefox work correctly and IE does not.
[quote="Bainespal"]Thanks for doing this! We've needed a web interpreter since forever, so this will be great breakthrough.
The file selection and command input interfaces appear to work okay on Chrome.[/quote]
The only problem - as I said in a long obscenity-filled tirade in another message - is that it doesn't work in Internet Explorer. Everyone says that if you have a submit event with a return false it cancels the submit, which is what I want to do. Internet Explorer is not following this, and nobody ever said this doesn't work with IE.
[quote]I assume you're getting the list of games from the IF Archive?
[/quote]
Yeah, I just grabbed a few files for testing purposes so that I could see what was happening and analyze what was going on.
[quote]I'm sure it's too early to comment on design, but I don't have a problem with the input/command prompt being separated from the main display window. I kind of prefer it that way; it's how MUD clients work. However, I wonder how it will integrate with Hugo's display properties, specifically, with games that try to design their own windows. But even if the web runner only works for text games, it will be a great breakthrough.
[/quote]
The problem I had was that for a javascript application, if I just kept writing new lines on the screen it eventually causes the screen to have too much material and the scroll bars pop up, so the user then has to scroll down after every input. Keeping about the last 10 or so lines of input/response and having a full scrollback buffer seemed a good compromise.
[quote]I like the scrollback buffer. I don't know if it will be possible to integrate it with the main design window in the future, but even if it has to be separate, it's good that the feature is already in development.
I'm glad to see this. :)[/quote]
I'm glad you liked it. However, if I can't get the EXPLETIVE DELETED Internet Explorer to allow me to have a javascript program that can process typed in information without causing the submit even to be triggered, I'm going to have to abandon it and go to a straight PHP application.
I can't abandon 75% of the people using the Internet just because Chrome and Firefox work correctly and IE does not.