Jürgen,
That's exactly what I've said: you cannot have multiple windows without
having multiple apps. Basic tech is not angular-specific: window.open,
window.postMessage, window.opener, window.addEventListener('message', ...).
Those are all parts of the regular JavaScript API.
So, basically, you start the app twice. But you can still communicate
between the two windows, you can probably find a few good modules that do
similar things on angular-specific way, or just JavaScript packages that
you can wrap in an angular service. Here, here's a super-faulty and ugly
demo of the base functionality, if I understood that correctly:
https://stackblitz.com/edit/angular-cross-window-messaging?file=app/parts.component.ts
Go there, click on the "map window" link, then you can "talk" between the
two app instances.
On Monday, March 26, 2018 at 1:00:50 PM UTC+2, Jürgen Stolz wrote:
>
> Hi Zlatko,
> I did not understand why you said it is not Angular specific. I wrote an
> Angular app witch contains several Angular (View) components and this Views
> I need to show on several monitors. So everything is inside Angular, shure
> I could open another window but that is not I want, I want to open the
> Angular (View) component (.css, .html) in an other (new) window.
>
> @Sander I will search your answer and check if it fit my needs.
>
> I try again :) describing my problem with multi monitor in a single app,
> using another example.
>
> I developed an Angular application which contains >3 Angular components,
> every component uses Angular material, the main.css for styling and a data
> service which holds the data.
>
> - First => Order component (table grid) contains a lot of data > 1000
> rows (example) and the user always need to see this table
> - Second => Order detail component, shown after a click. As the name
> said this are the details of the order and the user could show or modify
> details of the order.
> - Third => a component which shows trips (table)
> - Forth => a map component (shows orders, trips, or whatever was
> selected)
>
> In the application everything works but the user always need to switch
> back to the First component if he wants to see the OrderGrid again. I do
> not like this behaviour, so I changed the application and show 2 components
> side by side. Shure this works too, but if the the user shows all possible
> columns of the OrderGrid there isn´t enough space and it looks terrible. My
> next thought was, ok, I show the OrderDetails in a separate window on the
> second monitor and this is my problem I could not figure out how to use my
> application WITHOUT starting the application twice. (Perhaps this is not
> possible??)
> The next step, the user use the orders and plan a trip. Trip is the third
> component and should be displayed on the third monitor, this view should
> always be visible too, because sometimes events occour and they should
> displayed immediatley.
>
> At the moment I use a data service to share the data between the
> components, this is perhaps a part which I need to change too (as you
> mentioned).
>
>
> Best wishes
> Jürgen
>
>>
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
