First off, really great work here! I especially like the chunking. So glad you wrote this. :+1:
I checked the source, and I didn't see any specific reason why jQuery would be needed. The $ calls could be replaced with document.querySelector (and document.querySelectorAll where appropriate) and $(el).attr(…) calls would just become el.getAttribute(…) calls.
In 0.1.0/master of aframe/aframe-core, we aren't exposing these utils. But when we release 0.2.0, you'll be able to do require('aframe').utils.$ (or window.AFRAME.utils.$).
First off, really great work here! I especially like the chunking. So glad you wrote this. :+1:
I checked the source, and I didn't see any specific reason why jQuery would be needed. The
$
calls could be replaced withdocument.querySelector
(anddocument.querySelectorAll
where appropriate) and$(el).attr(…)
calls would just becomeel.getAttribute(…)
calls.FWIW, we have some utils for querying elements à la jQuery's
$
:$
which returns a single element$$
which returns an array (instead of aNodeList
)In
0.1.0
/master
ofaframe
/aframe-core
, we aren't exposing theseutils
. But when we release0.2.0
, you'll be able to dorequire('aframe').utils.$
(orwindow.AFRAME.utils.$
).