Yes, I was able to run some labs under the prototype interface. Thanks again,
-- Raul On Sun, May 15, 2022 at 6:56 PM Joe Bogner <[email protected]> wrote: > > That's great to hear the engine is working. We can work on the UI to make > it more usable now that we know the engine is working on a variety of > devices > > The proof of concept Playground is more usable on my Android phone and is > still available. https://jsoftware.github.io/j-playground/bin/html/emj.html > .. It could be an option for some until a better option is available > > It should work on the iPhone and iPad too. My guess is that we'll end up > having multiple interfaces and I could see us making the j library somehow > packaged up nicer in npm for example to encourage other experiments and > experiences that leverage J > > > > On Sun, May 15, 2022, 6:49 PM Raul Miller <[email protected]> wrote: > > > The j engine now works for me on my little iphone. > > > > That said, at least two issues remain, with the interface, which make > > testing difficult: > > > > (1) Run All Lines only executes the line the cursor is on (and I do > > not seem to have a mechanism to "select all" in the editor pane), and > > > > (2) The menu bar has a tendency to vanish. > > > > Still, I am able to execute some sentences now. > > > > Thanks, > > > > -- > > Raul > > > > On Sun, May 15, 2022 at 4:53 PM Joe Bogner <[email protected]> wrote: > > > > > > On Sun, May 15, 2022 at 9:22 AM Raul Miller <[email protected]> > > wrote: > > > > > > > Well... on my older iphone (32gb memory, 18.33gb available), simple > > > > sentences return no results. > > > > > > > > > > Raul, thanks. Can you or Ed or someone else please retest on iPhone or > > > iPad? I was able to pinpoint that -msse2 and -msimd128 were causing a > > > problem on iPhone 12 and iPad Pro according to browserstack[1]. I removed > > > those flags and recompiled and it started working on that environment, > > but > > > I'd feel better testing on a real device. > > > > > > If it doesn't work, can you try on chrome and open a new tab at > > > chrome://inspect and start logging before accessing the J Playground? > > > Please send me a screenshot of what chrome://inspect shows or paste the > > > output in that case. > > > > > > thanks > > > > > > 1 - https://www.browserstack.com/ > > > ---------------------------------------------------------------------- > > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
