Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Examples: Problems with converting timeliner_gui to a module.
See original GitHub issuetimeliner_gui is one of the last libs in examples which is not yet available as a module. I’ve tried to convert it today but encountered many runtime errors. After some investigations it turned out that the code in timeliner_gui is not compatible with strict mode. Meaning you can reproduce the same runtime errors by adding 'use strict'; at the top of js/libs/timeliner_gui.min.js.
Since ES6 modules are always in strict mode, I see no obvious approach to convert the library to a module. Unfortunately, it also seems that the project is not maintained anymore.
Should we remove timeliner_gui.js and misc_animation_authoring.html from the repo?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
just a little update, I managed to get timeliner fully migrated to es modules. however I noticed that my internals and apis have diverged from the timeliner gui used in three.js example and so I’ll be planning to add a little compatibility layer for it. hopefully, something that can be done in the next week.
ah this looks like @tschw’s fork of the timeliner project. i could take a shot at reliving and modularising my timeliner version again, and see the example could be converted. i’m also cool if there’s a desire to remove example for improved maintainability