Afficher un message
Vieux 29/06/2008, 18h04   #13
Stefan Ram
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Designing lower level classes.

Juha Nieminen <nospam@thanks.invalid> writes:
>However, not all programs are like that. Many programs require, for
>example, user input in real-time (such as mouse and keyboard events),
>drawing things on screen, update some GUI elements (such as the value of
>some spinbutton) and other such GUI-dependent functionalities. This is
>where abstracting the core code from the GUI becomes laborious, if not
>outright unfeasible.


In this case, the UI-dependent part of the program is large
and the UI-independent part of the program is small or missing.
Sometimes it happens to be this way, and then a port to another
GUI library will nearly be a complete rewrite. I do not see
any other solution for this case than to live (cope) with it.

A indication of such a type of program might be that it can
not be ported to some kinds of environment at all. For example,
when the definition of a program includes »drawing with the
mouse«, it will not be possible to port it to a keyboard
interface by its definition.

  Réponse avec citation
 
Page generated in 0,05721 seconds with 9 queries