-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Confusing things: #146
Comments
about # 1 ok cool. I was searching using the github codebase search and could not find it, i did not try a local search of the repo with an ide, as long as it's in the parsers, that clears things up. |
For example, i'm trying to add an expander to each item in leetsheet, such that clicking each item will instead dropdown an area below each with the example scroll code and processed output, instead of loading a new page with the code and generated code. What you are aiming for with scroll, i believe, is the ability to just write something like : printleetsheetparser expander or printleetsheetparser and have it do that but a more traditional structure will need to define something like: " i for i in each i, do" is it best practice to define this somehow on the page itself or modify printScrollLeetSheet ? |
|
Hope this is the best place to post this
Some confusing things as a newbie:
For printScrollLeetSheet in leetsheet.html
How and where is the scrollleetsheet parser defined?
leetsheet.html does not actually exist in the codebase files
How will users fork, share and save data.
Right now, it's a bit confusing: Do i clone scroll or scrollhub or PLDB ? What are these "folder" things ?
Once cloned, it still doesn't "work out the box" the leetsheet page for instance throws a GET error
Assuming this is because i do not have a server running, is there a way to have a Progressive web app that starts a js express server (assuming node and express are installed, and if not prompts to install them)
How will private versus public auth work ? (i.e some information i might want to use scroll to consume, but not share)
The text was updated successfully, but these errors were encountered: