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

How to import phy into another project #14

Open
fatbatman opened this issue Jun 14, 2023 · 5 comments
Open

How to import phy into another project #14

fatbatman opened this issue Jun 14, 2023 · 5 comments

Comments

@fatbatman
Copy link

Is there an example template project that demonstrates importing phy and using it in another project?
Using rollup or vite

@fatbatman
Copy link
Author

I can use Phy.module.js in an external project however that only exports "phy" (Motor).

It doesn't contain all the extra stuff used within the demos such that under src/3TH/

I'd like to have my own application starting point in a separate project, similar to phy/src/Main.js which can make use of the classes from 3TH/ etc

Is that your intention for how the engine can be used?

@lo-th
Copy link
Owner

lo-th commented Jul 4, 2023

yes i have to think how organize that well
phy contain majorité of 3th

@fatbatman
Copy link
Author

There is a circular dependency between Main.js <--> /3TH/Hub.js
which conflates things logically imo. It seems to just be referencing settings values that could be pulled into a separate object

@lo-th
Copy link
Owner

lo-th commented Jul 21, 2023

is fixed and i add main build
idea is to keep minimal module for each engine
but yea have to organize well thing

@diogohartuiqdebarba
Copy link

Phy should be just as a lib for using any physics engine and leaving the rendering code in another game engine project. It would be more organized.

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

3 participants