Re: Standard way of graphics in Linux

Hi,

Int 80 is the native interface to the Linux kernel and
no interrupt for graphics output.

Int80 is some arbitrary software interrupt which /may/ be some kernel interface opening some graphics window but it also may be the soft-int to send the actual register to the printer or to the power-off button on a future system.

In Unix there has been a standard environment around for many, many, many years which is called libc. All common system functionality has been made available there via standard functions and structures and will still be available in ten years.

Use of any lower interface is discouraged. You (and the people you want to teach something by your code) will not be able to understand what's going on if you don't use the libc interface.

As a result of all the answers here, I have done some further
reading and I will try to access the X server by it's native
socket interface and not use xlib.

That is as troublesome as not using libc. You'll spend more time debugging your socket interface communication than actually writing code. Xlib is available on all systems which provide X client functionality.

Using the socket interface is comparable to building your own milling machine just for milling one piece. You'll never even get close to a professional system and you run the risk that the tool holder suddently flies away, misses you by inches and gets stuck in the door. You wouldn't do this, would you?

Actually using Xlib is complicated enough by itself, if you write your own socket stuff you'll lose so much functionality (or would you spend additional code to write networking functions?) that you'll problably give up for frustration before even drawing a single window.

Just write your app in Xlib and if you feel confident by the time it's running you can still try to emulate Xlib and go for the socket interface - is this a convenient option for you? Start high-level and go low-level later - so you first understand the mechanisms and interfaces before you try to program them...

Ciao...
.

Relevant Pages

  • Re: multiple inheritance
    ... slice" of functionality, and use MI to get at it from a class that has this ... to think much more about the design at this level than any most programmers ... I'm a MI AND Interface fan. ... Point 1: Aggregation ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: setting local variables in a binding
    ... need to do to try to keep things from breaking since Ruby is dynamic. ... functionality into the classes your design is a tad less modular. ... not have to interface to other code to perform a broader function. ...
    (comp.lang.ruby)
  • Re: Great SWT Program
    ... orthogonal to whether or not a program has a decent user interface. ... A few also knew the arrow keys existed. ... "useful functionality required to qualify the application as an IDE". ... Or maybe you simply use "real text editor" as a synonym for IDE; ...
    (comp.lang.java.programmer)
  • Re: Ensuring a method exists
    ... When different classes offer similar functionality and you want ... Interface types are more flexible than class types because the former ... (defgeneric rem (collection object)) ... It's left up to the responsibility of the programmer to define the right methods, or to leave them out when they are actually not necessary. ...
    (comp.lang.lisp)
  • Re: When would you use an abstract class and when an interface?
    ... An abstract class is useful when you need a substantial amount of ... An example of where an interface is useful is where you have unrelated ... items that need to provide some similar functionality in a uniform ... but where the system caches them to disc as well as HTML ...
    (comp.lang.php)