Joe FWIW works fine on my Pixel OG/Chrome too
the UI is hard though i can pinch to zoom but it take a LOT of scrolling there might be someway to put the two panes on separate, shippable, pages each with their own cursor the raw text requires magnification in a desktop browser version ~greg heil picsrp.github.io i.tgu.ca/real_cal twitter.com/g1h twitter.com/tweitku -- from: Ed Gottsman <[email protected]> to: [email protected] date: May 15, 2022, 6:58 AM subject: Re: [Jgeneral] J Playground update - more tests passing & hopefully better mobile support Joe, Not much noise yet so I’m replying-all. >First, thank you for pursuing this effort. I lack a “real” machine and so >welcome alternate J delivery vehicles, particularly when they don’t involve >paying Google for VM time. >iPad Pro running 15.4.1: On both Chrome and Safari, expressions return no >results and Labs do not seem to launch, though the examples do load into the >editor. iPhone 11 running 15.3.1: Ditto. >Perhaps I’m doing something wrong. Happy to take guidance or perform specific >diagnostics. Thanks again. Ed -- from: Raul Miller <[email protected]> to: General forum <[email protected]> date: May 15, 2022, 6:22 AM subject: Re: [Jgeneral] J Playground update - more tests passing & hopefully better mobile support >Well... on my older iphone (32gb memory, 18.33gb available), simple sentences >return no results. >I should probably stick with the j7 app on this phone. FYI, -- from: Joe Bogner <[email protected]> to: [email protected] date: May 15, 2022, 6:05 AM subject: [Jgeneral] J Playground update - more tests passing & hopefully better mobile support >Hi all, I'm looking for some volunteers to test the latest J Playground on >their mobile device. https://jsoftware.github.io/j-playground/bin/html2/ >Many people reported that the Playground was unstable on their mobile devices >or devices with more limited memory. I also experienced it intermittently. The >latest playground change sets a parameter to initialize memory to 32MB (using >TOTAL_MEMORY aka INITIAL_MEMORY)[1]. My working theory is that the default >16MB caused the heap to expand which stressed the lower memory/mobile device. >I've tested on my Samsung FE20 and an older original Google Pixel from 2016 >and both devices could use the playground examples without crashing the >browser. >A future step could be to make a more mobile-friendly version of the >playground. The current version works reasonably well yet I'm thinking there >could be some things we do to make it easier to work with on a device with a >smaller screen. >Also, work has been done to fix some issues in the original adjustments to the >source code to get it to build under emscripten/WASM. The changes fixed 7 >failing test files (e.g. g200, g131) and fixed some issues with surface plots >and other glitches. >If you test, please either reply-all if there hasn't been much reporting on >the issue or reply to me directly if it seems too noisy on the mailing list or >if you'd prefer to send directly. Thanks for the help Joe 1 - https://github.com/jsoftware/j-playground/commit/0f022dea1706ebd0dc0900ff06fb4f81d896d6a9#diff-d42f4e1542def2ab6129051634fec87b7578f9d109918947ca2a0597a524be21R30 2 - https://github.com/emscripten-core/emscripten/blob/main/src/settings.js#L170 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
