How to extract an entire element from an HTML file?

Keith Clarke keith.clarke at
Mon Nov 26 10:18:13 EST 2018

Thanks for the warning and the link to the parsers, Trevor. 

I get the point regarding unclean HTML - as I won’t be in control of the source. Following a cursory glance through the dictionary, I’m also a tad concerned about the variability in HTML tag content (e.g. 

<div class=“red box”>content & elements</div>
<div class=“box red”>content & elements</div>

...and hence, how much wrangling might be needed to identify all the nodes in the tree with a specific class, where jQuery’s "$j(‘.red’).html();” saves a lot of the heavy lifting involved.

I’ll have a look at those parsers, too - though I doubt my coding chops are up to creating a library wrapper - indeed, I’ll have to Google what one is! :-)

> On 26 Nov 2018, at 13:42, Trevor DeVore via use-livecode <use-livecode at> wrote:
> On Mon, Nov 26, 2018 at 3:30 AM Keith Clarke via use-livecode <
> use-livecode at> wrote:
>> Thanks for the steer, Paul - I’ve not worked with XML in LiveCode so
>> hadn’t made the connection between the HTML markup structure & XML.
> Keith,
> I’ve used revXML for parsing HTML in somewhat controlled conditions. While
> revXML can work for HTML, your results will vary based on how well
> structured the HTML is. If there are tags that are not closed or are out of
> balance then revXML won’t give you the results you expect. If you are
> generating the HTML then it shouldn’t be a problem. If it is third party
> HTML then you may have to massage the HTML input to get it to work.
> It would be great if there were a library wrapper around one of the
> dedicated HTML parsers listed on this page:
> -- 
> Trevor DeVore
> ScreenSteps
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list