Emi

icon indicating a website link https://emidoots.com icon indicating an email [email protected]

icon company Sourcegraph icon location Arizona icon location Building the Mach game engine in Zig; Developer @sourcegraph

Results 458 comments of Emi

Should provide better errors when DOM has unexpectedly changed (e.g. if a library like fontawesome modifies the DOM, I get an invalid memory address or nil pointer dereference instead of human-readable error)

Apologies for not taking a look into this yet. From a cursory glance, this definitely looks like it should work today and appears to be a bug in Vecty.

Should provide better errors when DOM has unexpectedly changed (e.g. if a library like fontawesome modifies the DOM, I get an invalid memory address or nil pointer dereference instead of human-readable error)

#204 is about supporting interoperability with JS libraries in a form that is even better than how React does it, AFAIK, or having better documentation for how to do so...

Should provide better errors when DOM has unexpectedly changed (e.g. if a library like fontawesome modifies the DOM, I get an invalid memory address or nil pointer dereference instead of human-readable error)

The problem here is that FontAwesome applies its own modifications to the DOM structure and violates work that Vecty has done and expects in subsequent renders. In specific, when your...

Should provide better errors when DOM has unexpectedly changed (e.g. if a library like fontawesome modifies the DOM, I get an invalid memory address or nil pointer dereference instead of human-readable error)

I updated the issue title to reflect that we should make this much more obvious when this occurs. Let me know if the above helps or not! :)

Inline SVG

Looks correct at first glance. Is the element getting created in the DOM with the right attributes etc? i.e. have you looked at the Chrome inspector?

Inline SVG

> This behaviour is only really meant as a stop-gap to make SVGs at least possible to work with, until we can generate an SVG package: #54 I actually don't...

Inline SVG

Consider the generated `elem.Anchor` code: ```go func Anchor(markup ...vecty.MarkupOrChild) *vecty.HTML { return vecty.Tag("a", markup...) } ``` If we needed to specify the `vecty.Namespace` there, too, we'd end up with TONS...

Canvas binding

I can't speak for others using Vecty obviously, but if you're looking for an 'official' response here: Sure, of course you can use Vecty for 2d/3d canvas applications in just...

Canvas binding

> The other thing i want to try is using vecty to drive a desktop app that uses a few native components and a glfw window etc. I know shurcool...

comparison between vecty and vugu?

Will indeed add a comparison page once we have the new website up.