These choices change the words on your screen only — nobody else's screen moves. They live on this device, so they greet you next time, and you can re-choose them in any browser in two taps.
When you join a room with a code, you enter its Waiting Room first — the host lets you in. When students come, they enter into a waiting room.
This meeting room is new — come in and test it. There is more here than you can see at first. Look around. Try everything. Discover what is here.
Tell us what you discovered — and tell us what else you desire. We are building this with you.
This page itself is the trial — no download; it opens in your browser. Your answers go into our own database, and we read every one. No email or phone is asked for.
The meeting stands in our database from the moment you make it — its code and joining link are ready at once, so you can send the link out days before. Times are shown in your own local time — a school in Bamenda and a guest in Maryland each see the hour as their own clock reads it.
Your meeting stands scheduled. Send this link to the people you invite:
VIEW
Log Out — leaves the room and signs you out on this device.
This test stays on your own device — nothing is sent or recorded anywhere.
VIEW
Room code — give this code, or the link, to the people joining:
Send this link to the people you invite:
People can arrive at any time while the room stands — latecomers wait here, and you can admit them whenever they come.
No one is waiting.
Only the instructor writes.
Cells stand one under another. Choose a cell's language at its head: Python · Script (JavaScript) · C++ · Java · R · PHP · Perl · Ruby · Go · Rust · C · SQL — and the shelf is OPEN: every language that is free to use stands on it, and a free language not yet listed can be added by name. Code reads and writes JSON as a first-class citizen — JSON stands in the power-coding work, and the notebook export (.ipynb) is itself JSON.
VIEW High — the higher level of VIEW, which runs POWER CODING: long runs, big data, the full library at full strength, and the compiled languages (C++, Java and the heavy shelf). In this TEST build VIEW High is the named coming level — its label stands here plainly; no power is invented for it. VIEW High also builds Docker — and that power carries its own VIEW name: VIEW DOCKER, VIEW's own container builder, standing beside View Prompt in the VIEW family of names — View Docker: Available at VIEW High (the power itself works at the High level's arming, not in this test face). From code and instructions worked on the board and in View Prompt, View Docker builds View Containers (Vcontainers) — the container in our system is the View Container, short form Vcontainer. View Docker builds container images (Docker) and stands them up as View Containers. And the Vcontainer RUNS CODE: the power-coding road of VIEW High stands plain — board / View Prompt → View Docker → View Container (Vcontainer) → running code. A Vcontainer can also be opened as a TEST WINDOW: the code is tried inside the container in a window of its own, seen and tested, before it is let stand as real work. And “U can install Linux directly on it”: a Vcontainer can carry LINUX installed directly on it — a full Linux living inside the View Container, so work that needs a Linux house has one, inside our own container, under VIEW High. And Linux stands “even on VIEW itself”: VIEW carries a Linux space of its own — a Linux working place inside VIEW, reached from the VIEW High level — beside the Vcontainer road. And “you can install on it”: a Vcontainer takes INSTALLS — libraries, packages and tools are installed into the View Container so the code it runs has what it needs (install once into the Vcontainer, and every run inside it finds them). No container is built by this test face, and nothing here pretends one was.
The download IS the “import all libraries” step, done once, on your own device: it brings the whole Python library shelf onto your device (a large download — the engine and standard library, tens of megabytes; data libraries follow your import lines). The face shows its progress in plain words. Once down, it stays on your device (browser-kept) and a cell's ordinary import works just as in normal Python. Without it you can still write code and see the class's code and outputs — only running Python waits on your own download. Script cells need no download: the browser runs them itself. The Python engine is fetched from the engine's public home (the Pyodide home on the jsDelivr road) when you tap.
The command prompt of VIEW is called View Prompt. It speaks Python and Script: type a line, tap Run in View Prompt, and the true output stands under it, seen by the whole class.
Pick a file on this device and VIEW reads it here, whatever its format — documents and PDFs, pictures, spreadsheets, plain text, code files, and the rest of the ordinary formats. No converting first. If a format arrives that no reader in this build can render, VIEW names the format plainly and offers the file itself to open on your own device — never a blank.
Only the instructor and the assistant write on the board in this state.
VIEW reads all file formats it can truly render — documents and PDFs, pictures, plain text and code files, spreadsheets saved as CSV, video and songs. If a format cannot be rendered inside the page, VIEW names it plainly and offers the file itself — never a blank.
Sharing your screen: the browser will ask what to share — your whole screen, one window, or one browser tab. You choose.
Turn a person up or down — only you hear the change.
If the host mutes you, only the host can unmute you. If the host closes your camera, only the host can allow it again.
Log Out — leaves the room and signs you out on this device.
Consultation rooms are private under the hospital rule and are not listed here — they stand on the Administration side only.
The Administration door is kept by a code. Type the house administration code to open it.
Records are never deleted — the register is the house's memory.