-
Notifications
You must be signed in to change notification settings - Fork 219
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
base: master
Are you sure you want to change the base?
Update appguide.rst #439
Conversation
Clarify where to add apps to auto launch in sim. Add notes on auto launching the sim on changes.
There was a problem hiding this 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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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..."
What's a good way to spot the simulator process more precisely? Pkill isn't much help?
--
†øღ
Sent from a super computer that fits in my pocket and is connected to the sum total of all human knowledge
…On 24 August 2023 21:29:56 BST, Daniel Thompson ***@***.***> wrote:
@daniel-thompson commented on this pull request.
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
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
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..."
--
Reply to this email directly or view it on GitHub:
#439 (review)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
It's better to use dedicated tools such as |
Clarify where to add apps to auto launch in sim.
Add notes on auto launching the sim on changes.