I've copied out all the APIs from the docs into Typescript. Took me a little while, naturally :)

I've tried to match things up with the DOM library from the Typescript repo, where possible.

Right now they're in a barebones npm thing so we can experiment with docs generation. TypeDoc seems to work fairly well; just run npx typedoc *.d.ts to generate the HTML.

We could also use TSDoc to parse the comments, then emit jekyll markdown with a custom script, but if we like TypeDoc I'd propose going with that to save the effort!

Issue #33

This PR started from scratch and was more careful to preserve the style of the original website.

On a desktop, this PR should look the same as the existing website except for two items: (1) The top navbar text and GitHub symbol does not extend edge-to-edge (this is an easy fix if preferred), (2) the highlighted text when an API item is selected from the right window only highlights the text, the highlight does not extend across the entire anchor element (this one was a challenge for me since padding the top was the only solution I could come up with so that the item was not hidden under the top nav bar):

The mobile views should look the same as the last PR, except I changed the bottom nav bar to look more like the existing website:

This may be a bit more than requested. I had to make substantial changes to the layouts (about.html, documentation.html, and development.html) to leverage some of the benefits of bootstrap. The documentation pages should display better on mobile devices. The top navigation bar also adjusts to a dropdown menu on mobile devices. Screencaps below are from iPhone 5, which is the smallest screen available in the Chrome dev tools for testing. The website will display "normally" on tablets and larger screens. The breakpoint occurs at 752 pixels screen width (anything less than 752 gets the mobile version, anything greater gets the normal full page layout. Please let me know if it needs any more tweaking!

Main Page:

Canvas Page:

Canvas Page w/ Top Navigation Menu Extended (toggles):

Canvas Page - Mid-Page (Top Nav Bar disappears to create more space for content)

Add the possibility of import export js file

export function hello(){
    console.log("hello world")
}

import {hello} from "./imported.js"

hello()

This doesn't happen very often but is very annoying in the GitHub workflows.

It's also very hard to reproduce locally, but happens after hundreds of runs like this:

$ while xvfb-run out-debug/windowjs tests/run_tests.js; do sleep 1; done

Super unclear why this happens though. It's likely a race or some indeterminism in the subprocess spawning code, or in child/parent event dispatching.

Hello, @joaodasilva , I am improving the website of windowjs, If any feature you want, inform me, I will try to Implement that. This will be my first contribution.

The project doesn't have any test coverage so far, other than checking out the examples.

Issues like #34 require changing a large number of places, and this only scales when test coverage to confirm that everything is still working as expected.

The idea is to build a test runner that runs on Window.js itself:

• it spawns subprocesses to run individual test suites
• all documented APIs should have test coverage, in all their variants, including invalid invocations and thrown errors
• also have some pixel-diff tests to verify that rendering is working as expected.

This is my first ever contribution to open source! I apologize in advance if I am breaking protocol! I wanted to see if this file meets the open issue to make these pages look more like the website. Please let me know if this is what you are looking for and I take a shot at the rest of the files in the doc folder.

Relative links were used in the update. Extra header row added since GitHub tables require it.

With this pull request I would like to add the new logo to the website as discussed in #24, alongside with other small changes, such as adding favicons, applying an enhanced color palette, and adjusting the navbar on mobile.

Added

• Favicon and app icons
• Logo
• Logo to navbar
• Icon tags to <head>

Changed

• Updated color palette
• Improved responsive styling of navbar

The prebuilt binaries are blocked by Windows and macOS by default, and the security checks must be bypassed manually by the user.

Figure how to sign the binaries for distribution to avoid these warnings.

Likewise, avoid the malware warning in Chrome when the binaries are downloaded.

I would like to be able to disable keyboard shortcuts, (console, console overlay, performance info), so the user would not be able to access them. Also each individually, the console overlay is nice. :)

Would be great if I can use tooltips like in the browser, with a window.js API, obviously. For example, I hover an element made on the canvas and, checking hover with mouse API, I can decide to show a tooltip if user stop the mouse in this position.

The API could be simply implemented so:

// default don't show any tooltip
window.tooltip = "";

// shows a description while hovering "interesting" content
window.tooltip = "This is a description of what are you hovering!";

// if element is not anymore hovered
window.tooltip = "";

Please, if you like my idea, add a :+1: below!

This is similar to #88.

1. Support running a ZIP bundle instead of running a main JS file. Any file operations start by looking for the file in the ZIP, and then fallback on the filesystem when that fails.

2. Support merging that ZIP with the executable, to distribute as a single binary. This might work by just concatenating the binary and the ZIP, because the ZIP header is at the end of the file:

https://en.wikipedia.org/wiki/ZIP_(file_format)

The downside is that the original executable can't be signed (or its signature becomes invalid).

Let's say I create a cool app and I want to send it to my friend I want them to just open the executable and have the page shown to be my application. I can think of two ways this can be implemented:

• flag for --export or option.
• during the compilation of windowjs give it path for default application.

The program in attachment crashes after 10 to 100 runs on debug builds with MSVC on Windows.

This seems to come from a destructor running at shutdown, possibly reaching for memory from an object that has already been destroyed. The issue only reproes on early exits via std::exit, which is often used in child processes (and in tests).

Window.js doesn't have any destructors at shutdown, and this is likely coming from one of the libraries used. It's quite tricky to pin this down.

The temporary fix at in commit f56ae2fe uses std::quick_exit instead, to bypass the atexit callbacks. This isn't great; this bug is to change that back to std::exit and fix the shutdown issue.

https://gist.github.com/joaodasilva/f5fe471c7b27a2606689c6aeeb7398ed

GitHub has updated "windows-latest" from "windows-2019" to "windows-2022":

https://github.com/actions/virtual-environments/issues/4856

The v8 build fails to start with that change:

Building v8 in libraries/v8/out/Release"

        1 file(s) copied.
Traceback (most recent call last):
  File "D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py", line 573, in <module>
    sys.exit(main())
  File "D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py", line 569, in main
    return commands[sys.argv[1]](*sys.argv[2:])
  File "D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py", line 546, in GetToolchainDir
    runtime_dll_dirs = SetEnvironmentAndGetRuntimeDllDirs()
  File "D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py", line 106, in SetEnvironmentAndGetRuntimeDllDirs
    os.environ['GYP_MSVS_OVERRIDE_PATH'] = DetectVisualStudioPath()
  File "D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py", line 197, in DetectVisualStudioPath
    version_as_year = GetVisualStudioVersion()
  File "D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py", line 186, in GetVisualStudioVersion
    raise Exception('No supported Visual Studio can be found.'
Exception: No supported Visual Studio can be found. Supported versions are: 16.0 (2019), 15.0 (2017).
ERROR at //build/config/win/visual_studio_version.gni:27:7: Script returned non-zero exit code.
      exec_script("../../vs_toolchain.py", [ "get_toolchain_dir" ], "scope")
      ^----------
Current dir: D:/a/windowjs/windowjs/libraries/v8/out/Release/
Command: D:/a/windowjs/windowjs/libraries/depot_tools/[email protected]_8_10_chromium_23_bin/python3/bin/python3.exe D:/a/windowjs/windowjs/libraries/v8/build/vs_toolchain.py get_toolchain_dir
Returned 1.
See //build/toolchain/win/BUILD.gn:9:1: whence it was imported.
import("//build/config/win/visual_studio_version.gni")
^----------------------------------------------------
See //BUILD.gn:1516:1: which caused the file to be included.
action("postmortem-metadata") {
^------------------------------

GN failed!