You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now Beak is bundled together with the rest of the code for displaying NetLogo Web. Ideally Beak would be refactored with clear entry points so it could be published to a package registry and taken as a normal dependency by other projects (along with the Tortoise compiler and runtime engine). This would allow more easily making projects using Beak and Tortoise without manually getting a copy of the JavaScript artifacts. A good example of this would be NetTango Web, which currently lives in the Galapagos repo for convenient access to the NetLogo Web view scripts, but should really be split off into its own repository.
A possible requirement to make this happen properly would be to remove the last couple of webjars (Markdown.js and Google Caja) from the build.sbt and get them into the package.json for proper dependency resolution when published.
With #77 closed, this should be a more straightforward task to accomplish using Rollup.
The text was updated successfully, but these errors were encountered:
Right now Beak is bundled together with the rest of the code for displaying NetLogo Web. Ideally Beak would be refactored with clear entry points so it could be published to a package registry and taken as a normal dependency by other projects (along with the Tortoise compiler and runtime engine). This would allow more easily making projects using Beak and Tortoise without manually getting a copy of the JavaScript artifacts. A good example of this would be NetTango Web, which currently lives in the Galapagos repo for convenient access to the NetLogo Web view scripts, but should really be split off into its own repository.
A possible requirement to make this happen properly would be to remove the last couple of webjars (Markdown.js and Google Caja) from the
build.sbt
and get them into thepackage.json
for proper dependency resolution when published.With #77 closed, this should be a more straightforward task to accomplish using Rollup.
The text was updated successfully, but these errors were encountered: