-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could gibberwocky live and max be packaged as npm packages ? #16
Comments
Cool. Are you OK with the code annotations going away? I've thought about trying to abstract them so that they could be re-implemented for other editors besides CodeMirror but it would be a ton of work... There might be a few other editor-dependent issues to look at. Did you see this project? https://www.youtube.com/watch?v=SEvG3dqVk18 |
Great thanks. Yes I saw that, should provide a good starting point. That's fine for the annotations, I expected that. Waveform display will probably be trickier though but that will be a second step. |
Cool, I hadn’t seen that decorator example before. Looks promising! CodeMirror is also getting a dramatic rewrite (which will include support for mobile devices), so I might need to refactor the annotations soon anyways; if so I could try and do a vscode implementation at the same time. |
I’m struggling a bit with the window.foo global variables as these don’t work outside the browser, wouls you have a suggestion for a quick workaround ? |
I don't know how the global object works in vscode, but I just changed the export method in gibber.js so that it doesn't explicitly call window: If you change the line in |
Thanks ! As far as I can tell so far there isn't a global object that can be freely written to but I'm still digging. |
Hmmm... interesting. I guess you could declare an object (maybe even name it You'd need to add the |
Thank you! not 100% sure whether this will work yet but I've done this for now to keep moving forward with other issues. I'm guessing that the genish.js that is on npm is out of date ? |
Yep, exactly. I just bumped up the version on npm to fix this. Thanks! |
I believe there's an issue with the package's code, but it should be: ? |
Ugh, I don't know how that even happened. Fixed. |
No worries, thank you ! hopefully should have at least the communication working soon. |
Hi Charlie, |
I'd like to write a vscode extension to write gibberwocky in there rather than in the browser.
Rather than copy the code it would be cleaner if I could require an npm package ( like the atom gibber package does ).
The text was updated successfully, but these errors were encountered: