You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I analysed the workflow of Compound and found a way to include child applications as node_module in a parent's Compound application without doing any change in compound source code.
We have 4 applications working together without any problems so far (the portal and 3 tools).
Two of the tools are using AngularJS without problem (which is why there is an Angular section in the guide).
Each of the child application can still be run in standalone for easier development.
I had the guide tested by one of my co-worker for one of the tool and he could make it work, so I think it's easy enough to read.
I have been suggested by another co-worker to share my solution to help others and maybe get feedback, so here it is !
I hope you like it enough to merge it.
PS. The link in README.md already directs toward the future location on your server, so it's 404 for now.
Thank you for writing this guide. I'd like to do some cleanup and overview
common ways to extend apps. Actually there are two ways: mount app as
routing subtree; extend existing app with another app (mixin controllers,
models, etc). And there's cleaner way than described in readme, we are
using both ways in our apps, i will send you pull request with my edits.
Thanks!
I analysed the workflow of Compound and found a way to include child
applications as node_module in a parent's Compound application without
doing any change in compound source code.
We have 4 applications working together without any problems so far (the
portal and 3 tools).
Two of the tools are using AngularJS without problem (which is why there
is an Angular section in the guide).
Each of the child application can still be run in standalone for easier
development.
I had the guide tested by one of my co-worker for one of the tool and he
could make it work, so I think it's easy enough to read.
I have been suggested by another co-worker to share my solution to help
others and maybe get feedback, so here it is !
I hope you like it enough to merge it.
PS. The link in README.md already directs toward the future location on
@1602 I'd like to see the different options as well. Have you added this anywhere other than on SO?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We had multiple tool applications and we wanted to group them in a portal.
A saw a post on SO of someone who wanted to do something similar but without any answers and I had time for R&D so I used it to find a solution.
(http://stackoverflow.com/questions/18461997/how-to-run-multiple-applications-under-one-compoundjs-instance)
I analysed the workflow of Compound and found a way to include child applications as node_module in a parent's Compound application without doing any change in compound source code.
We have 4 applications working together without any problems so far (the portal and 3 tools).
Two of the tools are using AngularJS without problem (which is why there is an Angular section in the guide).
Each of the child application can still be run in standalone for easier development.
I had the guide tested by one of my co-worker for one of the tool and he could make it work, so I think it's easy enough to read.
I have been suggested by another co-worker to share my solution to help others and maybe get feedback, so here it is !
I hope you like it enough to merge it.
PS. The link in README.md already directs toward the future location on your server, so it's 404 for now.