Thread overview
Arrogant - HTML5 dom with CSS selectors
Jun 13, 2018
Andrea Fontana
Jun 13, 2018
Andrea Fontana
June 13, 2018
On behalf of the company I work for [1] today I released a new library: arrogant.

It is a fully conformant HTML5 dom library with CSS selectors.

It wraps Modest library [2] by Alexander Borisov that is a quite bigger library/framework.

As pointed out promptly by rikkimax [3] it doesn't rely on dynamic loading of modest but it links it during building. So you need to compile modest (not a big effort, is a plain C library without external dependencies) as prerequisite (check readme on github).

It is in its early days so any help / pull request / opened issue / benchmark / suggestion are welcome.

Developed and tested on Linux. Should work fine on OSX. Never tried on windows.

GitHub: https://github.com/2night/arrogant/
Documentation: https://arrogant.dpldocs.info/index.html
Dub: https://arrogant.dub.pm

[1] http://lab.2night.it
[2] https://github.com/lexborisov/Modest
[3] https://github.com/2night/arrogant/issues/1

Andrea Fontana
June 13, 2018
On 06/13/2018 09:23 AM, Andrea Fontana wrote:
> On behalf of the company I work for [1] today I released a new library:
> arrogant.
>

Nice!

> It is a fully conformant HTML5 dom library with CSS selectors.
> 

Does this mean that it requires the raw HTML input to already be fully conformant HTML5 or simply that it supports and outputs valid HTML5?
June 13, 2018
On Wednesday, 13 June 2018 at 18:06:02 UTC, Nick Sabalausky (Abscissa) wrote:
> Does this mean that it requires the raw HTML input to already be fully conformant HTML5 or simply that it supports and outputs valid HTML5?

The second one. If you parse invalid html it tries to fix it and output valid html5.

And that it can parse correctly any valid html5 syntax. Or at least it should!

Andrea

June 13, 2018
On 06/13/2018 02:25 PM, Andrea Fontana wrote:
> On Wednesday, 13 June 2018 at 18:06:02 UTC, Nick Sabalausky (Abscissa) wrote:
>> Does this mean that it requires the raw HTML input to already be fully conformant HTML5 or simply that it supports and outputs valid HTML5?
> 
> The second one. If you parse invalid html it tries to fix it and output valid html5.
> 
> And that it can parse correctly any valid html5 syntax. Or at least it should!
> 

Awesome. I'll have to check it out.