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.

Sign up for GitHub

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

Jump to bottom

Decouple QGL from PyQLab #96

Closed
5 of 6 tasks
blakejohnson opened this issue Jan 4, 2016 · 4 comments
Closed
5 of 6 tasks

Decouple QGL from PyQLab #96

blakejohnson opened this issue Jan 4, 2016 · 4 comments
Assignees
@blakejohnson

Comments

@blakejohnson
Copy link
Collaborator

It really should be a distinct entity. To make it happen we need:

  • Remove DictManager dependency in Channels.py
  • Move logical and physical channel management out of QGL
  • Move ChannelViews.enaml out of QGL
  • Alternate dispatch mechanism in compile_to_hardware()
  • Figure out how to re-write startup.py to connect QGL channels to settings management from PyQLab
  • Where does ChannelMigrator belong?
@blakejohnson blakejohnson self-assigned this Jan 4, 2016
@blakejohnson
Copy link
Collaborator Author

in terms of the dispatch mechanism for compile_to_hardware, we probably just want a plugin mechanism to register translators with QGL.

@blakejohnson
Copy link
Collaborator Author

Travis is still failing for some reason I haven't tracked down yet, but here is the standalone QGL repo:

https://github.com/BBN-Q/QGL

@blakejohnson
Copy link
Collaborator Author

I think this is ready to go. Testing of #104 would be helpful.

@blakejohnson
Copy link
Collaborator Author

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@blakejohnson blakejohnson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blakejohnson