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

Change IFrame to create component on the fly #1

Open
chanjunweimy opened this issue Oct 16, 2017 · 4 comments
Open

Change IFrame to create component on the fly #1

chanjunweimy opened this issue Oct 16, 2017 · 4 comments
Assignees

Comments

@chanjunweimy
Copy link
Owner

Following the "Create-On-The-Fly" template, given in:
https://github.com/maximusk/Here-is-what-you-need-to-know-about-dynamic-components-in-Angular

Achieving this will eliminate the use of "IFrame", making the framework more robust

@chanjunweimy
Copy link
Owner Author

adding import of esnext to dynamically load module: https://stackoverflow.com/questions/36103641/dynamic-system-import-with-webpack

@chanjunweimy
Copy link
Owner Author

Using Systemjs as library: https://stackoverflow.com/questions/46321477/get-and-load-a-remote-component-module-in-an-angular-4-4-app

@charzhao
Copy link

charzhao commented Apr 4, 2018

Do you have any update about this, I am very interesting in this. have you got this solution working without iframe?

@chanjunweimy
Copy link
Owner Author

@charzhao actually I tried one solution, but it might have issue when inheriting css so I think it was a failure. One UI plugin example that I recently found out is Team Foundation Server: they chose to use IFrame as well (handled security etc), so I think the current method (iframe) is sufficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants