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

better way to provide library #28

Open
garaemon opened this issue Apr 7, 2014 · 3 comments
Open

better way to provide library #28

garaemon opened this issue Apr 7, 2014 · 3 comments
Assignees
@garaemon

Comments

@garaemon
Copy link
Contributor

garaemon commented Apr 7, 2014

need to find better way to provide visualization_rwt as a library.

It may include css and html not only js.
@garaemon garaemon self-assigned this Apr 7, 2014
@garaemon
Copy link
Contributor Author

garaemon commented Apr 7, 2014

one of the solutions is using client-side MVC such as angular.js and backbone.js.

@garaemon
Copy link
Contributor Author

garaemon commented Apr 7, 2014

cc @furushchev

@garaemon
Copy link
Contributor Author

garaemon commented Apr 7, 2014

the problem of visualization_rwt is that dependency between view and logic is too strong.

Our goal is to build widgets easy to reuse.

First step is separate css from other resources (html and js).

we should provide 'theme' package only including css files.

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

@garaemon garaemon

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@garaemon