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

Debugging Ipelets #2

Open
Hirse opened this issue Feb 26, 2018 · 5 comments
Open

Debugging Ipelets #2

Hirse opened this issue Feb 26, 2018 · 5 comments
Assignees

Comments

@Hirse
Copy link

Hirse commented Feb 26, 2018

I am fairly new to both Lua and Ipe. For a course project, I would like to write my own Ipelet (in Lua).
I have found the manual and documentation describing how to write one and have been able to add my own simple Ipelet. As I begin to add more complex logic, it would be helpful to have a way to debug my code however. Is there any guide on how to practically develop Lua Ipelets?

@otfried
Copy link
Owner

otfried commented Feb 27, 2018

I simply use the Lua print statement. When I start Ipe from the command line, the output appears on stdout.

@otfried otfried self-assigned this Feb 27, 2018
@otfried
Copy link
Owner

otfried commented Feb 27, 2018

For guidance on writing Ipelets, you may have more luck asking on the ipe-discuss mailing list.

@Hirse
Copy link
Author

Hirse commented Feb 27, 2018

Thank you. Does this also work when running the compiled version?
I am currently using the Windows binary to skip the effort of building myself. Launching from the command line only opens Ipe, but doesn't keep stdout.

@otfried
Copy link
Owner

otfried commented Feb 27, 2018

I do all my development on Linux...

It seems running ipe.exe from cmd will not give you any terminal output.
However, running it from Bash (in the official Windows Subsystem for Linux of Window 10) works.

I guess I should provide an ipeDebug command for the Lua layer that will send output through the Ipe debug output system.

@Hirse
Copy link
Author

Hirse commented Feb 27, 2018

That would be great.
Thank you for the advice.

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

No branches or pull requests

2 participants