Three.js: Editor as a stand-alone project?

Created on 19 Jan 2017  路  9Comments  路  Source: mrdoob/three.js

A 2-cents idea: it would be wonderful to contribute to the Editor as a dedicated project.

Suggestion

Most helpful comment

The reason I'm hesitant about moving it to its own repo would be that it would increase the maintaining requirements (which is something I'm already struggling about). I can also see it getting easily "out of sync". Right now it evolves in sync with the library.

All 9 comments

It could be wrapped as standalone using Electron or NW (Electron is more popular, although Electron has issues with Web Workers, and NW uses a more recent version of Node and Chromium).

Also, one advantage of having it as standalone is the ability to have a dedicated file format for projects, and register the extension to open in the editor.

Thanks, but I am not talking about packaging (which is obviously possible). My title should have been clearer: I mean Editor as a stand-alone GitHub repo/project.

The reason I'm hesitant about moving it to its own repo would be that it would increase the maintaining requirements (which is something I'm already struggling about). I can also see it getting easily "out of sync". Right now it evolves in sync with the library.

Hmm, that makes sense. I'm currently using the editor in a project and have to manually copy files and update paths. Not that big a deal but I see the value in both arguments.

As it stands, the editor is largely useless, as it is broken with any version of THREE from the last year or so. It's actually a source of confusion, teaching us how things used to work, but not how the library currently works.

As it stands, the editor is largely useless, as it is broken with any version of THREE from the last year or so.

Could you elaborate?

It's actually a source of confusion, teaching us how things used to work, but not how the library currently works.

Please, elaborate on that too.

My mistake. Seemed like just yesterday it was still defaulting to version 57 or so. I see now it's showing version 84. Lots of things are different between the two, hence the confusion I was referring to. While we're here, I'd say one majorly frustrating issue with the editor is when an infinite loop is created simply by editing the text in a loop condition. There's no way to cancel the loop! If you haven't saved, your code is lost.

Just in case someone stumbles on this issue from a search, there is someone working on a standalone editor for three.js: https://twitter.com/ArthurShefer/status/854847174953246720

And there is also http://nunustudio.org/

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ghost picture ghost  路  81Comments

fernandojsg picture fernandojsg  路  85Comments

qornflex picture qornflex  路  113Comments

lmcd picture lmcd  路  74Comments

kumavis picture kumavis  路  153Comments