Media
4 items
Description
Bridge between SAS Studio web sessions and the StatDataViewer desktop application. ``` SAS Studio Helper bridges your logged-in SAS Studio web session and the StatDataViewer desktop application running on the same computer. Once the bridge is up, most things you would normally do inside SAS Studio can be driven from the desktop app instead — same session, same auth. What it covers ============== • Programs — submit SAS code, stream log + status updates back live, fetch results / log HTML, cancel a running submission. • Datasets — automatic push when you open a dataset (columns + first page of rows); paginate through more rows; download the full .sas7bdat either streamed through the extension or directly by the desktop app via a URL+headers hint. • Files — browse folders, read text files (.sas, .txt, …), save or create files, upload binaries, rename, delete, mkdir. • Libraries — list libraries, list datasets in a library, mount a filesystem path as a new SAS library. • Diagnostics — a ring-buffer of recent SAS Studio API calls, exportable as JSON. Useful when adapting the extension to a new SAS Studio version. Why this exists =============== SAS Studio's in-browser editor and preview are great for quick checks but limited for serious data inspection or program iteration. StatDataViewer adds a real desktop UI without forcing you to log out of SAS Studio or download datasets through clunky workflows. This extension is the glue that lets the desktop app act on your behalf in the live web session. Requirements ============ • A SAS Studio deployment you can log into in your browser (SAS Studio 4.x, 5.x, and SAS OnDemand for Academics are supported). • The StatDataViewer desktop application installed and running on the same computer. (Without it, this extension does nothing useful.) How it works ============ The extension never sees data on its own — you add each SAS Studio host in the options page, and the browser asks you to grant access on a per-host basis. It harvests the session and CSRF token the SAS Studio front-end already uses, then proxies the same HTTP API calls on behalf of StatDataViewer. Communication with the desktop app is over the loopback interface (127.0.0.1) only. No data is sent to any remote server.