Artyom Lebedev

Yes, it should be processed as it is read, line by line.

> Is this means that you want something like following: Yes, something like this. > Each user have their own schema (which can't be determined during library development), and they...

> Do you mean to implement your own parser? Yes, there is some work already started in this repository `v1.1.x` branch.

Hello, I would suggest you to simplify things and not rely on three.js built-in clipping planes functionality. First, it is 2D, so you can use clipping lines instead. I am...

> Your committed implementation could be even simpler because you don't use the new variable more than once and can safe the 4byte ram I think, the compiler is smart...

What about the second point? The commit does not touch the derivative.

Thanks for the report! Please check fix in v1.0.27.

No. You can use this example as reference to make it in plain old JS. Also you most probably will need to make a bundle to link with your HTML,...

Maybe it has hit the limit for single string allocation size, due to current parser design which reads the entire file into a single string. An alternative parser implementation is...

Hello, It should be quite easy. Most of public API is covered by several methods in [DxfViewer.js](https://github.com/vagran/dxf-viewer/blob/master/src/DxfViewer.js), they are documented in the code as much as possible. Vue.js [wrapper component](https://github.com/vagran/dxf-viewer-example-src/blob/master/src/components/DxfViewer.vue)...