I think the VBA and Java document object model are similar, if not the same. With it, a program can access a web page and all of its attributes (get text, change fields, click buttons, etc.) as an object, rather than resorting to screen scraping. I would assume that a J implementation would access the page hierarchy using the j-unique approach of locale class names and __numeric__ objects. > On Aug 26, 2019, at 6:06 PM, Raul Miller <rauldmil...@gmail.com> wrote: > > [message composed and "sent", earlier, but now gmail is telling me > that it actually never got sent...] > > On Mon, Aug 26, 2019 at 2:26 PM 'Jim Russell' via Programming > <programm...@jsoftware.com> wrote: >> In fact, JHS is the only J access still available on my old MacBook (JQT is >> no longer compatible.) I hadn’t seen anything approaching DOM, but I’ll >> look again. Thanks. > > You might want to describe what you are doing in a little more detail? > > Older versions of 32 bit J support > https://code.jsoftware.com/wiki/Addons/xml/sax -- for example -- which > might be useful for some manipulations of an XHTML representation of a > DOM. But there's still quite a bit of retooling needed, for more > recent versions of 64 bit J to support all of what the older systems > supported. > > That said, if you want to specifically manipulate a DOM built by > someone else, Javascript is where most of that community's effort has > gone (and applications written in other languages may use Javascript > for some DOM operations, though not necessarily on the same machine). > > Thanks, > > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm
---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
