I can't comment to the items below, but if you're asking about goog in general, Royale also uses goog.events heavily, and based on my experience, I don't think that's going to be easy to replace.
On 7/11/2021 6:13 AM, Harbs wrote: > To express this another way: > > I’m trying to figure out exactly what we’re using goog for and what can be > dropped. > > It seems to me that we’re calculating the dependencies in the compiler, so > there shouldn’t be any reason why we can’t write all the scripts as simple > script tags. > > It’s also likely that using ES6 output might solve these issues. I’m not sure > how difficult it would be to switch to ES6 output —especially for library > code. > > If we don’t go the ES6 route, it seems we’re using: > > In compiles js files: > goog.provide > goog.require > goog.inherits > The “base” method added to classes by base.js > > We’re using goog.addDependency in index.html and goog.require for the main > class. It seems like writing scipt tags should remove the need for > goog.addDependency and likely goog.require in the index.html file. > > I’m not sure what’s going to happen with the goog.requires in the compiled js > files. > > I’m not sure of the best way to go about unravelling all of this… > > Harbs
