The Future of ARnft and WebARKit

[kalwalt]

I want to start here a discussion about the future of ARnft. On our slack channel we @eddiecarbin @ThorstenBux and me are evaluating how we can evolve this little library, For now, we have stated that ARnft should be agnostic in rispect of every rendering engine used ( for now Three.js) but also planned. We have also agreed that we should use the typescript language, that will let us more control, flexibility and many other features. Share you ideas here, you are Welcome!

[kalwalt]

As a first step i was able to remove the ThreejsRenderer class see PR #180 and make ARnft free from Three.js. I started to develop a small package ARnft-threejs ( now it is in the dev branch, that let you attach a Three.js object onto the marker. This make ARnft lighter and it will possible to develop other packages with other rendering engines. I will do the migration to typescipt in a second step as i feel more confortable with the 'basic' javascript.

[albjeremias]

I stumble into an issue, shouldn't all software of webarkit be more like a LGPL rather than GPL license? I understand if it was decided to be GPL, but for me i will keep on using jsartoolkit5 with the LGPL 3.0 license.

[albjeremias]

@kalwalt @ThorstenBux

[albjeremias]

@kalwalt would it be possible to change the LICENSE to LGPL ?! do you understand the implications?
GPL -> Any executable or program which uses this library needs to have its code shared with GPL
LGPL -> Only changes to this library need to be shared with LGPL

[kalwalt]

@albjeremias I think it's already LGPL, where do you read that is GPL?

[albjeremias]

aaah sorry... you are right. awesome :) still learning a lot about all this stuff... let's keep it up! :)