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

Update appguide.rst #439

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Conversation

tomchiverton
Copy link
Contributor

Clarify where to add apps to auto launch in sim.

Add notes on auto launching the sim on changes.

Clarify where to add apps to auto launch in sim.

Add notes on auto launching the sim on changes.
Copy link
Collaborator

@daniel-thompson daniel-thompson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also squash into one patch and add a DCO signoff (see https://wasp-os.readthedocs.io/en/latest/contributing.html ).

@@ -280,10 +280,13 @@ by swiping or using the Arrow keys to bring up the launcher and then clicking
on your application.

The application can also be registered automatically when you load the
simulator if you add it to ``wasp/main.py``. Try adding lines 5 and 6 from
simulator if you add it to ``wasp/boards/simulator/main.pywasp/main.py``. Try adding lines 5 and 6 from
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change doens't look right.

the above example into this file (between ``import wasp`` and
``wasp.system.run()``).

You can use something like ``while inotifywait -e modify hello.py; do killall python3; nohup make sim 2>&1 & done`` to
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice concept. However killall python3 is pretty brutal so I think it needs to be "Kill any existing simulator processes (and any other python3 interpretters that are currently running) and (re)launch..."

@tomchiverton
Copy link
Contributor Author

tomchiverton commented Aug 24, 2023 via email

@fgaz
Copy link
Member

fgaz commented Aug 25, 2023

What's a good way to spot the simulator process more precisely? Pkill isn't much help?

It's better to use dedicated tools such as watchexec or entr. Both have options to terminate the process if it's still running.

@fgaz fgaz marked this pull request as draft September 27, 2023 09:44
@fgaz fgaz added the documentation Improvements or additions to documentation label Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants