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

Structure of gui files for deployment #21

Closed
KenT2 opened this issue Oct 22, 2015 · 0 comments
Closed

Structure of gui files for deployment #21

KenT2 opened this issue Oct 22, 2015 · 0 comments

Comments

@KenT2
Copy link
Contributor

KenT2 commented Oct 22, 2015

I would like to separate the code of my application from that of gui so that each can have its own licence etc. and gui is easily replaced when it changes.

The way I have done it is to have a two level directory structure

  • Top level contains the code and ancilliary files for my application.
  • The gui code and all its resources etc. is in a sub directory

Not a very clear description but you can see it in action in https://github.com/KenT2/manager-for-pipresents.

If you like the idea it would be good to arrange your github repository in the same way; the top level directory would contain the two examples.

The change requires gui to have an empty init.py file and for some changes to imports etc in the example Apps.

However at the moment the res directory and styles.css have to be moved from gui upwards to be with the examples. I think it would be better for separation if they stayed in gui. Is this possible?

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

1 participant