Skip to content
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

Unable to render markdown #1654

Closed
wwj718 opened this issue Jul 30, 2024 · 3 comments · Fixed by #1658
Closed

Unable to render markdown #1654

wwj718 opened this issue Jul 30, 2024 · 3 comments · Fixed by #1658

Comments

@wwj718
Copy link
Contributor

wwj718 commented Jul 30, 2024

image

hi , I am a Smalltalk user and I like the liveness of Lively.

When I encounter errors while working in lively, how do I fix them within lively?

@merryman
Copy link
Member

merryman commented Jul 30, 2024

Hey @wwj718. As a general rule of thumb if you encounter an issue its worthwhile trying to load lively again with the fast load disabled. You do that by adjusting the fastLoad parameter in the URL to false and reloading via the browser. This should fix the issue you are observing above. Also you will be able to debug more easily since each module is its own file in the devtools.
I will be starting to work a bit on supporting source mapping in August, so maybe we will have proper source maps support by September or so.

@linusha
Copy link
Contributor

linusha commented Jul 30, 2024

Regarding fastLoad and "slow load", you can also change the default that lively.next uses when you are opening projects via the dashboard, @wwj718. We refer to what you see when loading localhost:9011 as the dashboard. In the bottom right corner there is a button showing either a hare or a turtle. It might be hard to see at the moment, due to #1655. If the hare is visible, opening a project will fastLoad it, while the turtle will slowload. For developing the core, slowload is recommended. This setting should get preserved inside of your browser. Setting the URL parameter explicitly will overwrite this setting.

@linusha
Copy link
Contributor

linusha commented Jul 30, 2024

@wwj718 what I wrote above is still true, sorry, I wrote in the wrong tab without thinking...

We will fix the underlying problem of both this and #1653, but the problem is a bit harder than we initially thought and we need to prioritize the finalization of the website, which we are currently working on. Dev capacity will go drastically down over the next few weeks, but after tomorrow, this has upmost prio!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants