Interesting.. And that might even still be well formed and standard compliant HTML… I’ll definitively dig into that for Brix. Thanks!

@lexa I do not see the point of a talk on Brix before the current refactoring is more advanced. So OK please do it if you really want it.

Nope, as I told you, there won’t be very probably any talk on Brix this year. Free the place for someone else please.

I forgot to precise one important thing: the point of my proposition is that Cocktail bases its HTML parsing on the haxe XML parser, which is not ideal as it doesn’t accept doctypes, doesn’t manage HTML out of […]

He is perfectly right. Brix uses Cocktail to parse HTML DOM at macro time.

Appart from Cocktail, there is no other HTML Parser nor DOM manipulation library in haxe (or if there is one, please do tell me where […]

It will be a motivation for us to make the move

OK, then go for haxe 3!

There are several new features that will make things easiers: […]

Interesting, that’s a limitation of embedding the HTML in a Brix app…

Until the next refactoring, I think you’ll have to disable HTML embedding if you want to add pure js code triggered at document load…

Why not make it useable with vanilla javascript? The js community is bigger than the Haxe community and maybe one way to use brix would be in pure js…

We should definitively consider making it useable in […]

But I am not sure what it will do if a component defines its HTML and extends another component which used to define its HTML too…

The solution I’ve thought of to avoid a big mess at macro time is a two steps […]

It would be possible to add HaxeJS code right into the HTML source of the component in a script tag, where to define callback methods for example.

And also include other components which would be defined in […]

Brix core should be a Haxe library and Brix components the framework part, downloadable separately?

Yes, Brix core and Brix components downloadable separately.

And the “Brix components project”, should it […]

I see what you mean !

I’ve mentioned it during our last hangout: it’s what kendoUI also do (and probably few other js UI libs).

That shouldn’t be a big pain to do that in Brix…