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 approach demos better? #4

Open
stonier opened this issue May 3, 2013 · 1 comment
Open

How to approach demos better? #4

stonier opened this issue May 3, 2013 · 1 comment
Labels
Milestone

Comments

@stonier
Copy link
Member

stonier commented May 3, 2013

How to approach the next demo better?

  • More modular and robust startup/shutdown of each component
  • Better debugging/introspection tools
  • Gui remapping tools that auto-generate remap rules on the backend for us
  • Schedule two-three weeks for concert framework stability

Concert should work hard early each milestone, other components later.

@ghost ghost assigned stonier May 3, 2013
@stonier
Copy link
Member Author

stonier commented May 3, 2013

Integrate all steps in a fluid sequence. At the moment we have separate stages for building, semantically annotating etc.
Perhaps we could build these common parts all into the same fluid solution (think storyline - interact with the user!) rather than thinking of them as entirely separate. I have some ideas but need alot of discussion later.

jihoonl pushed a commit that referenced this issue Apr 16, 2015
@stonier stonier removed their assignment Apr 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant