@phuang07 Thanks for your interest! Let me explain how Algorithm Visualizer supports Java first, since supporting Python would almost exactly resemble it.

git push to tracers.java triggers Travis CI to:
1. publish a new version of the visualization library to the JitPack repository.
After the publication, it triggers another Travis CI on extractor.java to:
1. download the newest version of the visualization library from JitPack, and
2. build/deploy the AWS Lambda function.
When the AWS Lambda function receives a request having user-submitted code as payload, it compiles/runs it and sends back the extracted visualization.json.

Looking into the following files would be helpful to understand the concept:

Travis CI setup on tracers.java:
https://github.com/algorithm-visualizer/tracers.java/blob/master/.travis.yml
Travis CI setup on extractor.java:
https://github.com/algorithm-visualizer/extractor.java/blob/master/.travis.yml
AWS Lambda function:
https://github.com/algorithm-visualizer/extractor.java/blob/master/src/main/java/org/algorithm_visualizer/Extractor.java

For now, you can forget about 1-i and 2-i. (This is because I am thinking of NOT publishing the visualization library to an external repository at all and only using it within the AWS Lambda function, hence merging tracers.* into extractor.* eventually.)

Here are the steps needed to be done when you work on the extractor.py repository:

Manually install the visualization library (by copying the content of tracers.py probably?), so that the AWS Lambda function can compile/run user-submitted code with it. This step would replace 1-i and 2-i.
Rewrite Extractor.java in Python.
Adjust .travis.yml for Python.

Let me know if you have any questions!

Uh oh!

Add Python Tracer #244

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions