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
have a Diagram tab for OSGi bundle dependencies #44
Comments
Is someone working on this ? I have some code that produces a dot file from my OSGi cantainer. It might be kind of hawt to migrate that to hawt. Hawt project, btw :) |
Thanks! Nobody's working on this currently, but we consider pull requests to be pretty hawt ;-) |
Sorry for the delay. I will start on this this week...hope to get something to show soon. Best regards |
Awesome! Let us know if there's anything you need help on. We're often on IRC in #hawtio http://hawt.io/community/index.html if thats any help or feel free to post questions here. We've a few graphs now; the camel route diagram was the first one; then there's the d3 force diagram when browsing activemq destinations; and recently we've added a visual editor for camel - which uses pure HTML DOM stuff now (rather than SVG as the camel route viewer did) which is much easier to use and style. here's the layout code: https://github.com/hawtio/hawtio/blob/master/hawtio-web/src/main/webapp/app/wiki/js/camelCanvas.ts#L269-269 if its any help here's the template: https://github.com/hawtio/hawtio/blob/master/hawtio-web/src/main/webapp/app/wiki/html/camelCanvas.html#L168-168 note this is a very complex controller (as its got all the camel editing stuff) so there's lots of noise in there ;) but i might help as some code to grab for the layout bits |
Service Dependencies are implemented now; probably easy to add the same for package dependencies. |
gonna close this as its already hawt! Raised #605 for the package diagram idea |
kinda like either the ActiveMQ force-layout one or the more graphviz style camel one, so folks can see a dependency tree of bundles/packages/services
The text was updated successfully, but these errors were encountered: