Hello, CEMb, you wrote: CEM> Describe, please, a problem explicitly CEM> Actually, what it would be desirable to receive, and why the kernel itself cannot lift a window for an output? The jacket is a program-editor, and the kernel is an application-oriented application. The kernel can be launched independently, creating the window and working in a normal mode, and can - from the editor, in this case the editor creates a window (it MDI applications), creates process of application-oriented application, informing through command line on a window, which application should . In this mode the debag/analysis/editing of application-oriented application is produced. It is necessary that the window of application-oriented application did not argue for a place on the screen with the program-editor, and took a place of the normal document within client area. Pushed ctrl+tab - switched from application-oriented application to any document, edited, switched reversely and you look result. Or laid out a tile nearby, and you look at all in real time. CEM> redefinition of flows of input-output Arises, recently did such (with technical curiosity), launching from pluses (jacket) the console application (kernel) on . Java threw in the console (System.out.print/println) the quitting data, pluses them received and displayed in the window. Approaches for any console kernel. Yes, I something such also think. The master windows (jacket) will read out messages, to pack them in a file, and application-kernel will take away them from a file and ostensibly to "process".